Google Search Console’s Missing June Data Was a Reporting Glitch, Not Deindexing

Google Search Console experienced a series of reporting problems in June 2026, including a prolonged delay in the Page Indexing report . For many site owners, the report stopped updating on June 11, making it appear that indexing activity had stalled or that pages had disappeared from Google. The evidence later showed a reporting lag, not a broad indexing failure. Google documented the incident among its official Search Console data anomalies . The Page Indexing data pipeline was subsequently fixed and the report refreshed to show data through June 29. For businesses that use Search Console data in weekly SEO reporting, the incident is a useful reminder that a dashboard trend is not always a change in search performance or index coverage. What happened to Page Indexing data in June? The Page Indexing report, previously known as the Coverage report, stopped updating for many users on June 11. By around June 26, the delay had persisted for roughly two weeks. Contemporary reporting by Search Engine Land noted that the report timestamps pointed to a data lag rather than evidence that Google had suddenly removed large numbers of pages from its index. Independent reporting published on July 3 said Google had repaired the indexing data pipeline and refreshed the report with data through June 29. That recovery clarified the apparent mid-June decline: it was a historical reporting artifact , not a sudden mass deindexing event. The June issues were not limited to the Page Indexing report. Google's data anomalies documentation also records a June 24 logging error affecting Discover performance data. For properties with AI features in Discover , affected impressions were included in that issue. Google later stated, in an August 21 update, that missing data for the affected period had been restored in Performance reports. Period or report What changed What it meant Page Indexing report, from June 11 The report stopped updating for many users. Stale dashboard data could resemble