On the night of September 8-9, 2026, Google Search Console experienced a reporting bug that temporarily displayed indexed pages as "Crawled - currently not indexed," causing concern among SEO professionals who monitoring their sites' indexing status. Google's John Mueller confirmed the issue was a "short blip" resolved within approximately one hour, with no actual impact on indexing or search visibility.
What happened
Between approximately 1:00 AM and 2:30 AM UTC on September 9, 2026, Google Search Console's URL Inspection tool and indexing reports incorrectly showed pages with the status "Crawled - currently not indexed" when those pages were actually indexed and appearing in Google Search results. The discrepancy affected the reporting layer only—Google's actual search index continued functioning normally throughout the incident.
SEO professionals monitoring their properties during this window saw homepages and other key pages suddenly appear as if they had been removed from Google's index. For sites that rely on automated API pulls to track indexing health, the bug created a false alarm that required manual verification to resolve.
How the issue was spotted
The bug was first identified by SEO consultants monitoring client sites. Ryan Tree, an SEO consultant, posted on X (formerly Twitter) asking if others were seeing similar issues: "Are others reporting this? Many of my client sites show as not indexed even though they are."
Glenn Gabe, a well-known SEO consultant and president of Gabe Consulting, confirmed he was seeing the same problem. "I see this too. Wow, something is off with Google right now. I'll ping Google about this. Homepages of sites are showing up as 'Crawled, not indexed' but are definitely indexed," Gabe wrote in a post timestamped at 2:52 AM UTC on September 9.
Within minutes, both consultants confirmed the issue had resolved itself. Gabe later verified that the pages in question were still appearing in Google Search results, confirming the issue was limited to Search Console's reporting interface.
Google's response
John Mueller, Google's Search Relations team lead, addressed the issue on Bluesky later that morning. "I double-checked with the team, and it was a short blip that was resolved quickly in the night (before these posts happened). It's good that it's easy to double-check things like the indexing of the homepage. Sorry for the confusion!" Mueller wrote.
In a separate post, Mueller added context about the severity of the issue: "Also, fwiw nothing breaks if indexing is working as expected & it's just reported differently, and it's easy for people to double-check their homepage, so I don't see this particularly critical. Not every potential issue is a fire worth dropping everything for."
Mueller's comments suggest that while the reporting discrepancy was concerning for those who encountered it, the actual impact on search visibility was zero. Pages continued to rank and appear in search results throughout the incident—only the Search Console interface displayed incorrect status information.
Impact on SEO monitoring and API data
For SEOs who rely on the Search Console API to automate indexing reports, the bug created a more significant problem. Matthew Mellinger, an SEO professional, posted on LinkedIn that he had pulled data via the API during the bug window and captured the incorrect status for a large number of pages.
"Woah! I'm seeing a large number of pages across a multitude of properties go from indexed to 'Crawled - currently not indexed' today (especially on thinner or older pages). Like up to 20% of some smaller sites," Mellinger wrote.
The issue highlights a recurring challenge with automated monitoring: API data pulled during a reporting anomaly can create false historical records. Mellinger and others who captured data during the bug window would need to re-run their reports or manually correct their databases to reflect the accurate indexing status.
For sites that use Search Console data to trigger alerts or automated workflows, the bug could have generated false notifications about indexing problems that never actually occurred. This underscores the importance of building verification steps into monitoring systems—particularly for critical alerts about pages disappearing from the index.
Historical context: Search Console reliability issues
This is not the first time Google Search Console has experienced reporting discrepancies that caused concern among SEOs. The tool has a history of occasional bugs and delays that can create confusion about site health.
In August 2026, SEOs reported that Search Console's performance data (clicks, impressions, rankings) froze for several days, with data not updating since around August 8. That issue affected the ability to monitor traffic trends and diagnose ranking changes, though it did not impact actual search visibility.
Similarly, the Links report in Search Console has experienced delays in the past, with data sometimes running weeks behind schedule. These delays affect SEOs' ability to monitor backlink profiles and identify potentially harmful links in real time.
Search Console is a critical tool for SEO monitoring, but it is not infallible. Google has acknowledged that the tool provides "a view" of how Google sees a site, not a definitive real-time record of indexing status or search performance. Occasional reporting bugs, while frustrating, are part of operating a complex system that serves millions of websites.
How to verify indexing status independently
When Search Console reports suggest a problem, SEOs have several ways to verify whether pages are actually indexed:
Site: operator searches: The most direct method is to search for site:yourdomain.com in Google. If your homepage or key pages appear in the results, they are indexed regardless of what Search Console reports. This method provides a quick sanity check but does not give detailed information about individual URLs.
Direct URL searches: Searching for a specific URL in quotes (e.g., "https://yourdomain.com/page") can confirm whether that exact page is indexed. This is more precise than the site: operator but requires checking pages individually.
Manual inspection: Simply visiting a page and checking whether it appears in search results for relevant queries provides real-world confirmation of indexing. If a page ranks for its target keywords, it is indexed—regardless of Search Console status messages.
Third-party rank tracking tools: Tools that monitor rankings across multiple search engines can provide independent confirmation of whether pages are appearing in results. These tools query Google directly and are not affected by Search Console reporting bugs.
Google's cache: Searching for cache:yourdomain.com/page shows Google's cached version of a page, confirming that Googlebot has crawled and stored it. However, this method is less reliable than it once was, as Google has reduced the availability of cached pages in recent years.
The key takeaway is that Search Console is a diagnostic tool, not the source of truth for indexing. When its reports conflict with observable reality (pages appearing in search results), the observable reality is correct.
What this means for SEO monitoring practices
The September 9 incident highlights several important principles for SEO monitoring:
Don't panic based on a single data source: Search Console is valuable, but it should not be the only indicator of site health. Corroborating with direct search queries, rank tracking data, and traffic metrics provides a more complete picture.
Build verification into automated workflows: If you use Search Console API data to trigger alerts or automated actions, include a verification step. A sudden spike in "Crawled - currently not indexed" statuses should trigger a manual check before generating alerts or making changes.
Understand the difference between reporting and reality: Search Console reports what Google's systems believe about your site, but those systems can have bugs. Actual search visibility—whether pages appear in results and rank for target queries—is the ultimate measure of indexing health.
Maintain historical context: Keeping historical records of indexing status helps identify whether a change is a real problem or a reporting anomaly. If 20% of your pages suddenly show as "not indexed" but traffic and rankings are unaffected, it's likely a reporting issue rather than an actual deindexing.
Stay connected to the SEO community: The bug was identified and confirmed within minutes because SEO professionals were communicating on social media. Following SEO consultants and participating in professional communities helps you quickly distinguish between real issues and reporting glitches.
What has not been confirmed
Google has not published a detailed post-mortem or root cause analysis for this specific incident. It is unclear whether the bug affected all Search Console users simultaneously or rolled out gradually. Google has not indicated whether any data captured via the API during the bug window will be corrected or if users need to manually re-pull their reports.
There is also no public information about how long the bug persisted before it was detected by Google's internal monitoring systems. Mueller's comment that it was "resolved quickly in the night (before these posts happened)" suggests Google's systems detected and fixed the issue before SEOs began reporting it publicly, but the exact timeline remains unclear.
What to watch next
For SEOs concerned about Search Console reliability, the following developments are worth monitoring:
Google's communication about Search Console issues: Google has historically been transparent about major outages but less forthcoming about minor reporting bugs. Increased transparency about even small issues would help SEOs distinguish between real problems and temporary glitches.
Search Console API reliability: As more SEOs automate their monitoring workflows, the accuracy and reliability of API data becomes increasingly important. Any patterns of recurring bugs or data inconsistencies should be tracked and reported.
Alternative indexing verification methods: Google may introduce new tools or APIs that provide more direct, real-time information about indexing status, reducing reliance on Search Console's reporting interface.
Sources
John Mueller, Google Search Relations team lead. "I double-checked with the team, and it was a short blip that was resolved quickly in the night." Bluesky post, September 9, 2026.
Glenn Gabe, President, Gabe Consulting. "I see this too. Wow, something is off with Google right now." X post, September 9, 2026, 2:52 AM UTC.
Matthew Mellinger, SEO professional. "Woah! I'm seeing a large number of pages across a multitude of properties go from indexed to 'Crawled - currently not indexed' today." LinkedIn post, September 9, 2026.
Google Search Central Documentation. "Understand how Google Search works."
Author: Ethan Marlowe, GEO Measurement Lead Across 500+ Prompts at Auspia. Ethan writes about prompt tracking, citation reporting, and the visibility dashboards behind AI answer quality.
