Reporting

Google Search Console not updating? Find which delay you have, by report

Search Console not updating? Normal lag by report, how to spot the wrong property, and how to tell a real Google outage from a reporting delay.

// in this article

Search Console usually isn’t broken when it looks stuck. Daily Performance data normally takes 2 to 3 days to show up, the Page indexing report trails behind what Google already knows, and reports like Core Web Vitals and Links run on long windows, so “not updating” is most often a normal delay or the wrong property.

The fix depends on which report looks frozen and for how long. Below, each symptom gets its likely cause and what to do, in the order they usually turn out to be the answer. If nothing fits after a week, the last section shows how to check whether Google itself has a problem.

First, check how much lag is normal

Google’s About Search Console data page says “collected data should be available in 2-3 days” and that “there can be a lag between when the numbers are calculated and when they are visible to site owners.” It also says you can see last updated dates on most reports, so read that date before anything else. A Performance report with nothing for yesterday or the day before is working as designed.

Each report has its own rhythm, and comparing them to each other is where most false alarms start.

Performance, 24 hours viewa few hours
Performance, daily data2 to 3 days
New property, first dataup to 7 days
Page indexing, Validate fixabout 14 days, often more
Core Web Vitals, window and tracking28 days
fig 1 · normal wait before each report reflects new data. Source: Google Search Console Help and the Search Central blog, checked November 2026

Symptom: the last 2 or 3 days are missing or look low

Cause: normal processing lag, plus preliminary data. Google’s Performance report help says “the newest data can be preliminary, meaning it’s still being collected and might change in the next few hours,” and preliminary data is drawn as a dotted line on the graph. A dip at the right edge of the chart that fills in later is this, not a traffic drop.

Fix: don’t compare a partial day with a full one. For weekly or monthly reporting, end your date range 3 days before today. If you want something fresher, use the 24 hours option in the date filter. Google’s December 2024 announcement says that view “will appear with a delay of only a few hours,” shows hourly data in your local time zone, and is available in the Search results, Discover and Google News reports.

One more cause of “yesterday looks wrong”: daily data is labelled by California time, per the data help page. If you’re on the East Coast, a Search Console day starts and ends 3 hours later than yours, so it won’t match Google Analytics or your call tracking day for day. The Search Console vs Google Analytics guide covers the other reasons the two disagree.

Symptom: no data at all on a new property

Cause: the property is new, or it’s pointed at the wrong version of the site. Google says it “can take up to a week to generate data for a newly created site, or a site newly added to Search Console.” Data collection starts when someone adds the property, even before verification, so you won’t get history from before that day.

Fix: wait a full week first. If it’s still empty, check two things Google lists. First, the protocol: a URL-prefix property for http:// collects nothing if the site runs on https://. Second, whether anyone is clicking yet. A brand new site with no rankings has nothing to report, and the 7-step indexing setup is the place to start.

Symptom: numbers stopped moving, or don’t match another tool

Cause: you’re looking at a property that only covers part of the site. A Domain property “aggregates data for all subdomains, protocols, and subpaths,” while a URL-prefix property only includes URLs that start with that exact prefix, according to Google’s property help. After a site moves from www to the bare domain, or from http to https, the old URL-prefix property flatlines while the real traffic lands somewhere you aren’t looking.

✕ Looks frozen
property: http://www.mapleleafvet.example/
site now on: https://mapleleafvet.example/
clicks since move: close to zero
✓ Updating normally
property: Domain, mapleleafvet.example
covers: http, https, www and every subdomain
clicks since move: all of them
fig 2 · the same made-up vet clinic in two properties after an https move. Illustrative, not measured data

Fix: open the property picker at the top left and see how many properties you have for the site. If a Domain property exists, use it for reporting. If not, add one (it needs DNS verification), and keep the old URL-prefix property for its history. If someone else set up the account, the user and role guide explains how to get access to the right one.

Two smaller mismatches are normal and need no fix. Chart totals can differ from table totals because, per the Performance report help, the chart is aggregated by property and the Pages table by page. And a query you know people search may never appear, because Google doesn’t track “some queries that are made a very small number of times” to protect privacy.

Symptom: you fixed a page, but the Page indexing report still shows the error

Cause: the Page indexing report trails Google’s index. Google’s Page indexing help says a URL that URL Inspection shows as indexed but the report doesn’t “was probably indexed recently, and will appear in the Page indexing report soon.” The report also only changes when Google recrawls the page, and if your fix went live after the last crawl, the old status stays.

Fix:

  1. Run URL Inspection on one fixed page and use Test live URL to confirm the fix is really live.
  2. Check the Last crawl date in the inspection result. If it’s before your fix, the report can’t know yet.
  3. Request indexing for that one page if it matters, then click Validate fix on the issue in the Page indexing report.
  4. Leave it alone. Google says validation “typically takes up to about two weeks, but in some cases can take much longer,” and emails you as it goes.
  5. If validation ends as Failed, open the examples list, fix the pages still listed and start validation again.

Step 2 is the one that saves the most worry. A stale status with a crawl date from before your fix isn’t a stuck report, it’s an old one. The Page indexing report guide explains each reason and which ones to leave alone.

Symptom: validation has said “Started” for days

Cause: that’s the normal state for most of the process. “Started” means you’ve begun a validation attempt and no remaining instances of the issue have been found yet, per the same help page. “Looking good” means every URL checked so far is fixed, and neither needs anything from you.

Fix: wait the two weeks before you worry. Google recrawls pages partly based on how often it thinks they change, so if the affected pages are ones that rarely change (old blog posts, deep service area pages), expect validation to run longer.

Cause: both reports move slowly by design. The Core Web Vitals report shows values from “the last 28 days” of real Chrome user data, so a speed fix shipped today only takes over the numbers about a month later. Clicking Start Tracking begins “a 28-day monitoring session,” and it doesn’t trigger recrawling. A new or low-traffic property can also show “No data available” because there isn’t enough Chrome data for that device type.

The Links report has no last updated date at all and refreshes irregularly. In 2026 it went months without fresh data, which the Search Console backlinks guide covers with the reported dates.

Fix: for Core Web Vitals, check a single page with PageSpeed Insights to confirm the fix worked in the lab, then judge the report after 28 days. For links, use the Latest links export for dates and don’t read anything into a report that hasn’t moved in a few weeks.

How to tell a real outage from a reporting delay

If the Performance report’s last updated date is more than about 4 days old, or every report in every property you manage stopped on the same day, it’s probably Google. Check these in order.

step_01 Read the date Last updated on the report itself. under 3 days is normal
step_02 Compare properties Is a second site stuck on the same day?
step_03 Data anomalies page Google's list of known logging issues.
step_04 Status dashboard Crawling, indexing, ranking, serving.
step_05 Note it and wait Annotate your report, don't refile.
fig 3 · the order to check before you decide search console itself is behind

Google’s Data anomalies in Search Console page records known issues that affected report data, grouped by report. Some entries are temporary and later restored, and some say the data “won’t be recovered.” The most recent Performance entry when I checked was a logging error from November 9 to November 11 that lowered impressions in the Generative AI report. If your dip lines up with an entry there, it isn’t your site.

The Google Search Status Dashboard covers crawling, indexing, ranking and serving. It’s useful for the opposite question: when the report is updating fine but the numbers fell. As of November 21, 2026 it listed the November 2026 core update as active since November 10, which is a ranking change, not a reporting fault. If you see a drop that started then, read it as a ranking story.

If neither page mentions anything and only your property looks stuck, go back through the property checks above. A fault on Google’s side would show up in your other properties too, so a single stuck property almost always points to a setup issue.

What to tell a client while you wait

If you report to a client or a business owner, a stalled report is a reporting problem, not an SEO problem, and it helps to say so plainly. Note the gap in the report, give the date range you used, and say which source confirmed the delay. If you build monthly reports, the SEO reporting template suggests running the monthly report on the 4th or later, which avoids most of these questions.

FAQ

How often does Google Search Console update?

Google doesn’t publish a fixed schedule, but it says collected data should normally be available in 2 to 3 days. The 24 hours view in the Performance report updates with a delay of a few hours.

Why does Search Console show data from 3 days ago as the latest?

That’s the normal processing lag for daily data. The newest days are preliminary, shown with a dotted line, and can change until processing finishes.

Can I get back data that's missing from Search Console?

Usually not. Collection only starts when the property is added, and Google’s data anomalies page says some logging gaps won’t be recovered. Adding a Domain property early is the only way to avoid gaps from the wrong property.

Does requesting indexing make the reports update faster?

It can get one page recrawled sooner, which updates that page’s own status in URL Inspection. It doesn’t refresh Performance data, and it only covers the single URL you submit.

Wait three days, then check the anomalies page

Most “not updating” reports clear up once you allow the 2 to 3 day lag, use the 24 hours view for anything fresher, and make sure you’re in the Domain property. If a report is still frozen after a week, compare it with another property and check Google’s anomalies page and status dashboard before you change anything on the site.

Portrait of Liam Fraser
// written byLiam FraserSEO specialist with 3 years of experience. Liam writes about what works in local, technical and AI search.About SerpSurfers →