Google Search Console has lost a substantial section of historical June 2026 data from its Page indexing report, and Google's current explanation is unusually definitive about one part of the problem: the missing interval will not be reconstructed later.
Barry Schwartz documented the issue on September 11 in Search Engine Roundtable after site owners noticed that a large portion of June had disappeared from charts where the data had previously appeared to be visible.
John Mueller responded that the gap likely corresponds to the period in June when the Page indexing report was delayed and was not being updated. He said there simply is no indexing-report data for that interval and that Google does not backfill this type of indexing data, although he plans to verify the situation with the team.
For SEO teams, the distinction is critical. A blank section in the Page indexing history is currently best interpreted as a reporting gap, not as evidence that Google suddenly removed a site's pages from the index during June.
A large part of June disappeared from Page indexing charts
The September 11 reports show a conspicuous blank interval on the left side of the Page indexing graph.
Dan Lauer said he was seeing the issue across his Search Console properties and noted that the data had been present earlier before disappearing.
Schwartz reported the same broad behavior and told readers not to panic because the issue was not isolated to one site.
That cross-property pattern is one of the strongest reasons not to begin an immediate site-level technical remediation based solely on the visual gap.
Mueller linked the missing history to June's reporting delay
Mueller's response provides the most important context.
He said the missing section is likely from the period in June when Search Console's Page indexing data was delayed and the report was not updated.
In other words, the system may not have collected or preserved the report snapshots needed to display that historical interval now.
Mueller added that he would check with the team when they return from holidays to make sure that explanation is correct, so the precise diagnosis should still be treated as likely rather than fully closed.
Google does not backfill Page indexing data
The most consequential sentence in Mueller's response is that Google does not backfill indexing data.
If the Page indexing report failed to update during a period, Google does not later reconstruct the missing daily historical points and insert them into the chart.
That means the June gap may remain permanently visible even though the report resumes normal operation before and after it.
For organizations that rely on Search Console as a historical record, this is an important limitation of the dataset.
The gap does not mean pages were absent from Google's index
The Page indexing report is a reporting product built on top of Google's indexing systems. It is not the index itself.
Google's official Page indexing documentation says the report shows the indexing status of URLs in a Search Console property that Google knows about, grouping pages into indexed and non-indexed states and explaining reasons for non-indexation.
If the reporting layer lacks historical data for a period, that does not establish that Google's underlying index lacked the pages during the same dates.
SEO teams should therefore avoid interpreting the empty chart as a June deindexing event unless independent evidence supports that conclusion.
Historical reporting and current URL status answer different questions
A historical Page indexing chart helps teams understand how site-wide indexing coverage changed over time.
For the current status of an individual URL, Google directs site owners to URL Inspection.
That distinction becomes especially important when the historical chart itself is incomplete.
If a critical page is currently indexed according to URL Inspection and appears in Search, a missing June reporting point should not override that current evidence.
Do not launch a technical SEO emergency from a blank chart
A sudden hole in Search Console can look alarming because indexing problems can have severe organic consequences.
The wrong reaction is to change robots.txt, canonical tags, sitemaps, internal linking or noindex directives before establishing that a real indexing problem exists.
Those changes can create genuine problems while attempting to fix a reporting artifact.
When a Search Console anomaly appears across unrelated properties at the same time, platform-level reporting should be investigated before site-level causes.
Search visibility can help distinguish reporting loss from index loss
SEO teams can triangulate the situation using independent signals.
If important pages continued receiving Google Search impressions and clicks through the missing interval, that is inconsistent with a theory that those pages vanished wholesale from the index.
Server logs, analytics, rank tracking and archived exports can provide additional evidence about what actually happened during June.
No single external signal perfectly reproduces the Page indexing report, but several consistent signals can prevent an erroneous diagnosis.
Search Console's Performance report is a different dataset
The Page indexing gap should not be conflated with Search Performance metrics.
Performance reports measure impressions, clicks, CTR and position from Search surfaces, while Page indexing reports describe indexing coverage and reasons.
A missing historical indexing snapshot does not automatically imply missing performance data for the same period.
Teams should audit each report independently rather than assuming that one visible gap has corrupted every Search Console dataset.
There were also Performance report loading complaints on September 11
Search Engine Roundtable reported a separate observation from Marie Haynes on the same day.
Haynes saw the Search Performance report become stuck on a loading spinner and suggested switching to another report, such as Page indexing, and then returning to Performance as a workaround.
Schwartz said he could not reproduce that behavior.
There is currently no evidence in the reviewed official documentation that this loading issue represents a confirmed Performance data-loss incident, so it should remain separate from the established June Page indexing history gap.
Search Console has had several reporting irregularities recently
The September 11 problem arrives after other Search Console reporting issues.
Earlier this week, Google briefly showed some pages as “Crawled - currently not indexed” even though they were actually indexed. Google described that incident as a short reporting blip that was resolved quickly.
Search Console users have also experienced delays in indexing-related reporting during previous months.
These incidents reinforce the need to distinguish Google's Search behavior from Search Console's representation of that behavior.
A legitimate indexing status can also appear during a reporting bug
“Crawled - currently not indexed” is normally a real and meaningful Search Console status.
Google's Page indexing documentation explains that non-indexed pages can have legitimate reasons for exclusion and that site owners should examine the specific reason before deciding whether action is required.
That creates an analytical challenge when a reporting bug temporarily assigns a legitimate status incorrectly.
The label itself is not evidence of a bug; the surrounding context, cross-property pattern and independent URL checks are what reveal the anomaly.
Google maintains a formal Data Anomalies page
Google's Search Console Data Anomalies documentation records known events that can affect report data, including logging problems and changes to aggregation methods.
As of September 11, the official page says there are no recent issues listed for the Page indexing report.
That means the newly observed June-history problem has not yet been formally recorded there as a current indexing-report incident.
Mueller's direct response remains the strongest available Google explanation while he checks with the team.
Google has previously documented data that will never be recovered
The idea that Search Console data can be permanently missing is not unprecedented.
Google's Data Anomalies page currently records a February 28 and March 1, 2026 technical issue that caused two days to be absent from bulk data exports for some properties.
Google explicitly says those data will not be recovered.
That example is from a different report and incident, but it demonstrates an important operational reality: Search Console should not be treated as an immutable, guaranteed-complete historical warehouse.
SEO teams should preserve their own exports
The June gap makes a strong case for maintaining independent historical copies of Search Console data that matters to the business.
For Performance data, teams can use scheduled exports, APIs or other supported data pipelines. For reports without equivalent granular export histories, periodic snapshots can still preserve useful evidence.
An external archive cannot manufacture data Google never produced, but it can protect against losing information that was visible at one point and later disappears from the interface.
This is particularly important for large sites where indexing history is used in migrations, incident reviews and technical SEO audits.
Dashboards should annotate the June gap
If an organization copies Search Console metrics into internal reporting, the missing interval should be marked explicitly.
Connecting the points immediately before and after the gap can create the false appearance of a smooth trend.
Replacing the gap with zero is even worse because zero has a very different meaning from unavailable data.
The correct analytical representation is “missing/not reported,” with a note explaining the Search Console reporting interruption.
Do not calculate June trend rates across the missing interval
Month-over-month and week-over-week indexing comparisons can become misleading when one period contains incomplete data.
A calculation may produce a large percentage increase or decrease simply because one side of the comparison lacks observations.
Analysts should exclude the affected interval or clearly flag the result as non-comparable.
Historical SEO reports are more useful when they preserve uncertainty instead of filling it with a misleading number.
The missing data limits retrospective incident analysis
Suppose a site experienced an organic traffic decline in late June and an SEO team wants to determine whether indexing coverage changed first.
The missing Page indexing history removes one potentially useful diagnostic source for that investigation.
Teams may need to reconstruct the story from Performance data, analytics, server logs, sitemap histories, crawl archives and deployment records instead.
This is why operational observability matters before an incident occurs, not only after one needs to be explained.
Large sites have the most to lose from incomplete indexing history
Google itself notes that the Page indexing report is particularly useful for sites with many pages.
On a large ecommerce, marketplace or publishing site, indexing coverage can shift by hundreds of thousands of URLs as templates, faceted navigation, inventory and canonicalization change.
A missing month can obscure the timing of a significant technical event.
Smaller sites can often verify their critical URLs individually, but that approach does not scale to millions of pages.
Current indexing totals can still be useful
A permanent historical gap does not make the entire Page indexing report worthless.
The report can still show the current balance of indexed and non-indexed pages, identify major exclusion reasons and help site owners investigate coverage problems before and after the missing interval.
The limitation applies to historical continuity.
Teams should use the report for what it can currently tell them without pretending it contains observations that Google says were never recorded.
Mueller's follow-up could refine the explanation
Although Mueller said the gap likely comes from the June reporting delay and that Google does not backfill indexing data, he also said he would confirm with the team.
That leaves room for Google to clarify the exact dates affected or whether the current disappearance from previously visible charts has another presentation component.
Any future official update should supersede assumptions made from today's screenshots.
For now, the core operational guidance remains unchanged: treat the interval as missing report data rather than evidence of a new indexing failure.
The Performance loading issue should be monitored separately
Because another Search Console report was reportedly behaving strangely on September 11, it is reasonable for teams to monitor the platform more closely today.
However, grouping every unusual interface behavior into one broad “Search Console outage” would overstate the evidence.
The Page indexing history gap has a direct response from Mueller. The Performance spinner has an individual observation and workaround but was not reproduced by Schwartz and has not been documented as a Google incident in the sources reviewed.
Different evidence levels should produce different levels of confidence.
Search Console is an observability tool, not the source of truth for the web
Search Console provides uniquely valuable first-party information from Google, but its reports are still generated datasets with update schedules, aggregation logic and occasional logging failures.
A site can be indexed while a report temporarily says otherwise. A historical period can be missing even though Search itself continued operating. A chart can lag behind current URL status.
Technical SEO becomes more reliable when Search Console is combined with direct page inspection, crawlability checks, server evidence and traffic data.
The platform should be treated as authoritative about the data it reports, but not assumed to be perfectly complete at every moment.
The June gap is likely permanent
The immediate story is not that Google suddenly lost a site's pages. It is that Search Console's Page indexing report no longer contains a broad section of June 2026 history, apparently corresponding to a period when the report itself was not updating.
Mueller's explanation makes the practical consequence clear: Google does not backfill Page indexing data, so the missing interval should not be expected to reappear through a later reconstruction.
That makes the incident more than a temporary visual glitch for historical analysis. SEO teams should annotate the gap, avoid false comparisons across it, preserve their own exports and use other evidence when reconstructing what happened during June.
Meanwhile, today's separate Performance-report loading complaints deserve monitoring but not conflation with the indexing issue. Search Console may be having a noisy week, but the correct response is careful diagnosis—not assuming that every broken chart represents a broken Google index.