Search Console page indexing report has stalled since 11 June

Google Search Console's page indexing report has been getting stuck since 11 June 2026, adding new numbers in weekly clumps instead of daily data points, and Search Engine Roundtable reported on 28 July 2026 that it had happened again the day before. This is latency, not lost data. Barry Schwartz's assessment is that the numbers do arrive, they are simply taking longer than normal. What you lose is the speed of your feedback loop.

What Search Engine Roundtable reported on 28 July

Schwartz wrote that he has kept a log of these delays since 11 June, that Google has fixed the report a few times since then, and that it stalled again the day before he published. Search Engine Roundtable ran the piece on 28 July 2026. His own read on how much it matters was measured: "This is not specifically an issue unless you are trying to debug a set of pages over a shorter period of time. But ultimately, you will get the data you need, it is just taking longer than normal."

Three gaps, grouped by Brodie Clark

Brodie Clark grouped the missing days into three periods, and they match the log Schwartz has been keeping. Schwartz notes the dates may shift by a day depending on time zone, since he is in New York.

Clark summed up the state of the report this way: "indexing data for pages in Search Console has been delayed for weeks now – we only have 3 unique data points since June 13th."

Why a stalled report makes a fix look bigger than it was

Clark also described the analysis problem, and it is the reason this is worth knowing about rather than shrugging at: "This is a pain from an analysis standpoint, as it means that you have to wait much longer than necessary in order to see an update in indexing data after making changes, so the results are far more dramatic than the reality."

The mechanism is simple. If a fortnight of gradual change lands as a single data point, the chart draws a step instead of a slope. Anyone who shipped an indexing fix in July and has been watching Search Console has a line that did not move for up to two weeks, then jumped. Neither shape reflects what actually happened on the site. A monthly client report built on that chart can present a reporting artefact as a recovery, or as a collapse, and nothing in the interface flags which it is.

What Google has and has not said

Attribution matters here, because the story is easy to overstate. There is no Google statement in the 28 July report and no Search Console data anomaly notice is cited. Schwartz writes that it is clear Google is aware of the issues, which is his characterisation rather than a confirmation from Google. The three date ranges come from Clark's observation and Schwartz's own log, not from a published incident report. No fix date has been given, and Schwartz notes the report has been fixed and then broken again more than once since 11 June.

What this means for Thai marketers

The page indexing report is one system, so a delay in its pipeline shows up the same way for a site in Bangkok as anywhere else. The source says nothing specifically about Thailand and does not need to. Where it bites is a site in the middle of a migration or an indexing cleanup, because a fortnight with no new data point means no way to tell whether last week's fix landed, and the temptation is to ship a second change on top of the first before the first has reported.

The workable response is to keep your own dated record of what shipped and when, so that when the report catches up you can line the step up against the deploy that caused it. If you are running an SEO audit or a technical cleanup right now, build the delay into the timeline you promise rather than into the conclusions you draw. Slower feedback is an argument for changing fewer things at once, which is usually better SEO practice anyway.

Frequently asked questions

Is Search Console losing my indexing data?

No, the data arrives late. Schwartz wrote on 28 July 2026 that you will get the data you need, it is just taking longer than normal, and the report has resumed several times since the delays began on 11 June.

How far behind has the page indexing report been?

Clark grouped the gaps into three stretches with no new data point: 13 June to 30 June, 1 July to 10 July, and 11 July to 24 July 2026. Schwartz says the dates may shift by a day depending on your time zone.

Has Google confirmed the delay or given a fix date?

Not in this report. Schwartz writes that it is clear Google is aware of the issues, which is his own characterisation, and no Google statement, data anomaly notice or fix date is cited anywhere in the piece.

Does this affect Search Console for sites in Thailand?

Yes, because the page indexing report is a single global system rather than a per-country one. The source says nothing about Thailand specifically, so treat that as the reason rather than as a claim it made.

How should I report on indexing while the data is delayed?

Say plainly in the report that the indexing chart is running behind and date-stamp your own changes against it. A jump in the line after a two-week gap is the report catching up on two weeks at once, not a two-week result, and Clark's point is that it will look far more dramatic than the reality.

Read the chart with the delay in mind

Nothing here needs fixing on your side, which is the good news. What it needs is a caveat on the slide, and a bit of patience before declaring a fix successful or failed. If you would rather have someone else watching the reports while you ship the changes, that is the kind of monitoring an SEO audit engagement is meant to cover.