All posts
Why Isn't Google Search Console Data Updating? Common Causes and Fixes

Why Isn't Google Search Console Data Updating? Common Causes and Fixes

Search Console data looks frozen or stale? Here's why GSC reporting normally lags, what's actually broken vs. expected, and how to tell the difference.

August 7, 2026 · 11 min read

If you've refreshed the Performance report three times today hoping for new numbers, you're not alone. "Google search console stopped updating" and "search console data not updating" are both real, recurring searches — and most of the time nothing is actually broken. Google's own help page says collected data "is usually available in 2–3 days," so the last couple of days are always missing or incomplete. But sometimes the data really has stopped, and knowing which situation you're in saves you from either panicking over nothing or missing a real problem for weeks.

The short version: if the report's last date is two or three days behind today, that's normal. If it hasn't moved in a week, or the line has dropped to zero while the dates keep advancing, something else is going on — and the sections below show how to tell which.

Why Search Console Data Lags By Default

Search Console was never built to show you real-time numbers. Impressions and clicks have to be collected, deduplicated, and processed before they appear, and Google's troubleshooting page for the Performance report lists "time lag" as one of the standard reasons its numbers differ from other tools: "Collected data is usually available in 2–3 days."

A few details about how the report handles recent data explain most of the "it's not updating" moments:

  • Complete days only, by default. The standard date ranges (last 7 days, last 28 days, and so on) only include complete days. Today — and often yesterday — simply aren't in the chart unless you set a custom date range that starts on that day.
  • Preliminary data is marked. When the newest data is still being collected, Google calls it preliminary and draws it as a dotted line. It "may change in the next few hours," so a dotted segment that looks low isn't a final number.
  • The "24 hours" view is the exception. Since December 2024, the Performance report has a "24 hours" view with hourly data that appears "with a delay of only a few hours." If you want to see whether a post published this morning is getting impressions, that view is where to look — not the default 28-day chart.
  • Days are Pacific Time. Outside the 24-hour view, every daily data point is labeled in Pacific Time (PT). If you're in Europe or Asia, "yesterday" in Search Console may not be the yesterday you're thinking of, which makes the lag feel a day longer than it is.

So the first rule: if the gap is around three days or less, this is not a bug. It's the system working as designed.

"Stuck" or "Dropping"? Two Different Problems

When people say Search Console data isn't updating, they usually mean one of two things, and they have completely different causes:

  1. The date is stuck. The report's last available date hasn't moved forward. This is a reporting problem — something between Google and the report you're looking at.
  2. The dates move, but the line falls. New days keep appearing, but clicks and impressions trend toward zero. That's not a reporting delay at all. Search Console is updating fine; it's showing you that your pages are getting fewer impressions.

The second one is easy to misread as the first, especially when the drop is sudden. A post that was deindexed by an accidental noindex, or a site whose robots.txt started blocking Googlebot after a CMS update, will produce exactly this pattern: fresh dates, falling numbers. If that's what you're seeing, skip ahead to the diagnosis in why blog traffic drops instead of waiting for the "lag" to resolve.

How to Tell Normal Delay From an Actual Break

| What you see | Most likely explanation | What to do | |---|---|---| | Last date is 2–3 days behind today | Normal processing lag | Nothing — wait | | Dotted line on the newest point | Preliminary data still being collected | Check again in a few hours | | Today shows nothing in the default view | Default ranges show complete days only | Use the 24-hour view or a custom range | | Last date hasn't moved in a week or more | Reporting problem, Google-side or property-specific | Check status pages, then your property | | Every property in your account stuck on the same date | Google-side issue | Check the Search Status Dashboard and data anomalies page | | Only one property stuck, others fine | Property-specific setup issue | Check property type and URL | | Dates advance, numbers fall toward zero | Real loss of impressions, not a lag | Check indexing, robots.txt, and recent site changes |

The single most useful comparison is across properties. If you manage more than one site and they're all frozen on the same date, the cause is almost certainly not on your end.

Common Reasons GSC Data Actually Stops Updating

When the date really has been stuck for longer than the normal window, these are the causes that come up again and again:

  • You're looking at a property that no longer matches your site. A URL-prefix property only includes URLs that start with the exact protocol and hostname you entered. If your site moved from http:// to https://, or from www. to the bare domain, a URL-prefix property for the old version stops receiving new data, even though the site itself is doing fine. Google's help page notes that a property with no data after several days may simply have the wrong URL — "for example, you specified http instead of https." A Domain property covers every protocol and subdomain at once, so it doesn't break this way. This is one of the things worth checking right after a website redesign or relaunch.
  • A known Google-side logging issue. Google keeps a public data anomalies page that records known issues from the last few months — logging errors, aggregation changes, and similar events that cause dips or gaps in report data. If your graph shows a strange gap, check this page before changing anything on your site.
  • A broader Search incident. The Google Search Status Dashboard reports widespread issues with crawling, indexing, ranking, and serving from the last seven days. Google says it aims to post an incident within an hour of confirming one.
  • A brand-new property. Google's verification help says data starts being collected as soon as anyone adds a property, "even before verification occurs. However, it takes a few days for data to start to accrue for the property." An empty report on day one isn't a fault.

One common explanation that doesn't hold up: losing verification doesn't stop data collection. According to Google's help page, "Data collection continues as long as any user has that property in their account, whether or not it has a verified owner." If your verification token disappears, the risk is losing access — Search Console notifies you, and your permissions expire after a grace period. Re-verify to get back in, but don't expect re-verifying to "unfreeze" the numbers.

What To Check, Step By Step

Work through these in order rather than jumping around:

  1. Read the actual last date. Look at the last day in the chart, not whether the graph "looks" flat. Remember the default ranges skip incomplete days.
  2. Switch to the 24-hour view. If hourly data is showing up there, reporting is working and you're just looking at the normal daily lag.
  3. Compare properties. If every site in your account is stuck on the same date, it's on Google's end — check the Search Status Dashboard and the data anomalies page, then wait.
  4. Check the property definition. For a URL-prefix property, confirm the protocol and hostname match the URLs your site actually serves today. If they don't, add a Domain property (or a URL-prefix property for the current version).
  5. Confirm your access. Open Settings → Ownership verification and make sure you still have a verified owner on the property.
  6. Inspect a live URL. Use the URL Inspection tool's live test on a recently published page to see whether Google can fetch it right now. This checks the page directly instead of relying on report data.
  7. Rule out a real drop. If dates are advancing but impressions are falling, test your robots.txt with a robots.txt tester and check the Page indexing report for pages excluded by a noindex tag.
  8. Wait out the standard window before escalating. If everything above checks out, a Google-side delay resolves without any action from you.

Why Do Third-Party Tools Show Older Data Than Search Console?

If a dashboard, spreadsheet, or SEO tool that pulls from Search Console looks a day or two further behind than Search Console itself, the cause is often how the data is requested. The Search Console API has a dataState setting: if it's set to "final" or omitted, Google's documentation says "the returned data will include only finalized data." Set to "all", the response includes fresh data, which may still change. Since April 2025, a third option, "hourly_all", returns hourly data for up to 10 days.

So a tool that only asks for finalized data will always trail the Search Console interface, which shows preliminary data as a dotted line. Neither is wrong — they're answering different questions. If you need numbers that match the interface, use the same date range in both and compare complete days only. The same "drop the trailing days" rule applies when you compare Search Console with Google Analytics, where time zones add another layer of mismatch.

What If It's the Page Indexing Report That Isn't Updating?

The Page indexing report measures something different from the Performance report — whether Google has indexed your URLs, not how they performed in search — so a stale-looking indexing report and a stale Performance report usually aren't the same problem. A page you published this morning won't show as "indexed" right away — Google has to discover it, crawl it, and decide whether to index it, and that takes as long as it takes for your site. If a post is still missing after the first week or two, the guide on new blog posts not showing up in Search Console covers what's normal and when to act.

If you're seeing statuses like "crawled — currently not indexed" or "discovered — currently not indexed" on pages you expected to rank, that's a related but separate issue from a reporting delay. Discovered vs Crawled — Currently Not Indexed: What Each One Actually Means explains what each status means and when to worry about it.

What to Do While You're Waiting

The frustrating part of a Search Console freeze isn't the delay itself — it's not having any visibility while it lasts. A dedicated monitoring layer can't make Google's processing lag disappear, but it does change how much you depend on watching the report by hand. Traffic Monitor pulls your Search Console clicks and impressions every day and keeps the history in its own dashboard, so once Google releases a day's data you see it without opening the report. On paid plans, it also records your tracked keywords' Google rankings each week, including their actual position in live search results — a separate source from Search Console's own numbers. If you're reading the report yourself in the meantime, the Search Console Performance report guide covers which numbers to trust and which to ignore.

Search Console Data Not Updating: Quick Answers

How long does Google Search Console take to update?

For the standard Performance report, Google says collected data is usually available in 2–3 days. The "24 hours" view shows hourly data with a delay of only a few hours, though the newest points may be preliminary.

Why does today show no data in Search Console?

The default date ranges only include complete days. Today's data appears in the 24-hour view, or in a custom date range that starts today. Days in the standard views are counted in Pacific Time.

Does losing verification stop Search Console from collecting data?

No. Google's help page says data collection continues as long as any user has the property in their account, whether or not it has a verified owner. Losing verification affects your access, not data collection.

Is there an official page that shows Search Console outages?

Two. The Google Search Status Dashboard reports widespread crawling, indexing, ranking, and serving issues from the last seven days, and the "Data anomalies in Search Console" help page records known logging and reporting issues that affect report data.

Between checking your own setup methodically and knowing where Google posts its own issues, a temporary Search Console freeze becomes a minor inconvenience instead of a source of ongoing anxiety about whether your SEO work is actually landing.

Track your blog rankings automatically

Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.

Start free →