What happened: The Search Console indexing report lost a whole month. On September 11, 2026, site owners opened Google Search Console and found a hole in the page indexing chart. All of the June 2026 data was gone, and it had been there the day before. Dan Lauer spotted it first on Bluesky and noted the data “was there yesterday.” John Mueller from Google answered that the gap is permanent, not a display bug: “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.” So the Search Console indexing report now has a missing month that will never come back.
Source(s): Search Engine Roundtable coverage of the missing June data, Google confirming the September 8 indexing reporting bug, and Google’s own page indexing report documentation.
Why the Search Console indexing report gap matters for SaaS sites
Most SaaS teams treat indexed page count as the health check that sits underneath everything else. You ship 400 integration pages, you watch the indexed line climb, and that line is how you tell your VP the programmatic bet is working. When a month vanishes from the Search Console indexing report, three things break at once.
Quarter reporting breaks first. Q2 comparisons that include June are now built on a blank. If your dashboard pulls the API and charts month over month, June reads as zero or as a straight line between May and July, and neither is true. Second, the shape of the chart lies. A sharp cliff followed by a recovery looks exactly like a deindexing event, and teams have burned a full week chasing a canonical problem that was never there. Third, any before and after you ran in June is gone. Migration, sitemap rebuild, robots change, all of it lost its measurement window.
This lands on top of a rough two weeks for indexing data generally. On September 8, pages across many properties flipped to “Crawled – currently not indexed,” including homepages that were plainly indexed. Google confirmed that one and said it resolved overnight. The June gap is a different animal because there is no fix coming.
Timeline of the Search Console indexing report problems
| Date | What happened | Status now |
|---|---|---|
| June 2026 | Page indexing report delayed for roughly two weeks | Data was never written |
| July 2026 | Report caught up and resumed normal updates | Gap left behind |
| Sept 8, 2026 | Pages flipped to “Crawled – currently not indexed” en masse | Confirmed bug, resolved overnight |
| Sept 11, 2026 | June data disappeared from the chart entirely | Permanent, no back-fill |
Worth saying plainly: the Search Console indexing report is a reporting layer, not the index. Nothing about your actual indexing changed on September 11. What changed is your ability to prove what happened in June.
What to do about the Search Console indexing report gap
- Export monthly and store it yourself. Pull the page indexing counts by status on the first of every month into a sheet or your warehouse. Google does not back-fill, so your own export is the only version of June that can exist. If you already run a SaaS SEO reporting dashboard, add a scheduled snapshot job this week.
- Annotate June before anyone sees the chart. Put a note on the June column in every deck and dashboard saying the data is missing at source. Do it before your next review, not after someone asks why indexing crashed.
- Cross-check with a second signal. Sitemap submitted-versus-indexed counts, server log hits from Googlebot, and a sampled
site:or URL Inspection spot check will tell you whether real indexing moved. Our guide on fixing SaaS indexing problems walks through which signal to trust when they disagree. - Do not open an incident over a chart shape. Before you pull engineers into a deindexing war room, confirm the drop appears in more than one source. The same discipline applies to the average position data Mueller talked about this week, where the metric moved but the rankings did not.
If you run a large templated footprint, this is also a nudge to keep your own indexing ledger for those URL sets rather than leaning on Google’s chart. The approach in our programmatic SEO for SaaS guide assumes you can see which templates index and which do not, and that assumption needs a local copy of the data now. Same goes for blocked by robots.txt cleanups where you need a clean before and after.
Quick recap: Search Console indexing report
- June 2026 data is missing from the Search Console indexing report and Google will not restore it.
- Mueller confirmed the cause: the report was not updated during the June delay, and Google does not back-fill indexing data.
- The gap is a reporting hole, not a change in how your pages are indexed.
- A separate September 8 bug showed pages as “Crawled – currently not indexed” and was fixed overnight, so recent chart noise has two causes.
- Export the Search Console indexing report monthly so future gaps cost you nothing.
- Validate any drop in the Search Console indexing report against sitemaps, logs, or URL Inspection before treating it as real.
