Search Console's Missing June Data Isn't Coming Back

Site owners opening the page indexing report this week have found a hole in it. A large section of June 2026 simply isn't there — not zeroes, not a dip, just absent. It appears to affect every property, not a subset.

It is not a new bug. It is the permanent scar left by an old one.

What John Mueller said

Responding to the complaints, Mueller gave the explanation:

This is likely from the time in June where the data was delayed – there just isn't any data for that period, the page indexing report wasn't updated. We don't back-fill indexing data.

That last sentence is the whole story. The gap is not going to fill in.

The June delay this traces back to

For most properties, the page indexing report stopped updating on 11 June. Reports froze mid-month, and a lot of site owners read the flat line as pages falling out of the index.

They hadn't. The evidence at the time pointed to a reporting lag rather than any indexing failure — crawling and indexing continued normally throughout, and URL Inspection returned live results while the aggregate report sat still.

The delay ran close to three weeks before Google caught the report up, at which point it showed data through 29 June. What nobody said out loud then is what Mueller has now confirmed: the pipeline was never re-run over the stalled window. The report resumed from the far side of the gap and left the middle empty.

Why "we don't back-fill" matters more than it sounds

Search Console's other reports have accustomed people to eventual consistency. Performance data lands late, then settles. Numbers move for a couple of days and then stop moving. The mental model most of us carry is that Search Console catches up with itself.

Indexing data does not work that way. It is a record of what the report observed at the time it ran. If it did not run, there is no observation to recover — the underlying crawl state has long since moved on, and reconstructing what the index looked like on 18 June is not something Google is set up to do retroactively.

So the practical position is: June 2026 has a permanent hole in your page indexing history, it is Google's hole rather than yours, and no amount of waiting or re-verifying will close it.

What to actually do about it

Annotate it now, before you forget. Anyone looking at a twelve-month indexing chart in six months' time will see a cliff in June and start hunting for a cause. Put a note in whatever your team reads — the annotation costs you two minutes now and saves somebody a day's false investigation later.

Don't let it distort year-on-year comparisons. June 2026 will read as a catastrophic month against June 2027 if you compare the raw report totals. Exclude the window or flag it explicitly in any period-over-period analysis.

If you export, check your archives. If you have been pulling the page indexing report to a warehouse or a sheet on a schedule, your own exports from mid-June may hold what the live report no longer shows. That copy is now the only record you have.

Separate this from the 8 September blip. Those were two different faults. The September one was an overnight display error that reclassified indexed pages as "Crawled - currently not indexed" and resolved itself within hours. This one is a data gap from June that is permanent. If you are logging Search Console incidents, they belong in different rows.

The wider point

This is the second distinct page indexing reporting fault in three months, against a background of unusually loud indexing complaints. That is worth holding in mind when the report tells you something alarming.

It does not mean the report is useless. It means the report is a measurement instrument with its own failure modes, and those failures look exactly like the thing you are trying to measure. A flat line can be your site losing pages, or it can be the pipeline not running. A missing month can be a deindexing event, or it can be a job that was never re-run.

The defence is the boring one: corroborate anything alarming against a second source before you act on it. URL Inspection for individual pages, server logs for crawl activity, actual clicks and revenue for whether it matters. If the page indexing report is the only thing telling you there's a problem, the problem may well be the page indexing report.

Sources

• Search Engine Roundtable: Google Search Console Indexing Report Missing Old June 2026 Data
• Google Search Console Help: Page Indexing report