Google Search Console shows indexed pages as unindexed in at least some accounts right now, and the contradiction is pushing site owners and agencies into an uncomfortable position. URLs that are plainly visible in Google search results are being flagged as not indexed in the URL Inspection Tool. Google has not yet confirmed the cause, and its Data Anomalies page currently lists no related problem.
Why Google Search Console Shows Indexed Pages as Unindexed
Google Search Console is showing indexed pages as unindexed because of a data inconsistency that appears to be affecting the URL Inspection Tool. Pages are still live in Google’s index, but Search Console’s diagnostic layer is returning a false “not indexed” verdict. The anomaly has been reported by multiple SEO professionals, including Ryan Tree and Glenn Gabe.
Why Does Google Search Console Say a Page Is Not Indexed When It Is?
Google Search Console says a page is not indexed when it is because the URL Inspection Tool is returning incorrect status information. The page exists in Google’s index and can appear in search results, but the tool reports it as not indexed. This is a false negative, not a sign that the page has been removed or penalized.
Search Console is a data interface on top of Google’s search systems, not a perfect mirror of the live index. When its internal state is out of sync, status messages can conflict with real-world search results.
The reports shared publicly so far focus on the URL Inspection Tool. It is not yet clear whether the Page Indexing report is reproducing the same false negatives, although both draw from the same family of Search Console data.
How the URL Inspection Tool Determines Index Status
The URL Inspection Tool is used to check a single URL’s indexing status. It can show whether Google has found the URL, whether Google can render its content, and whether the URL is included in Google’s index.
When a URL is not indexed, Search Console can display a reason such as “Discovered but not indexed”, “Crawled but not indexed”, “Excluded by noindex tag”, or “Blocked by robots.txt”. These statuses are designed to give site owners a reason why a page is unavailable in search results.
In the current situation, the tool is returning a not-indexed verdict that does not match reality. There is no indication in the publicly shared examples that the affected pages have a noindex tag, a robots.txt block, or a crawl-based exclusion. The pages simply appear in Google’s search results while the tool says they should not.
This makes the anomaly more alarming to site owners than a normal indexing delay. An indexed page that suddenly shows as unindexed can trigger unnecessary technical audits, client escalations, and destructive changes to pages that are performing well.
The Reports from Ryan Tree and Glenn Gabe
Ryan Tree and Glenn Gabe have both documented cases of this Google Search Console discrepancy. The examples they shared show the same basic contradiction: a URL appears in Google’s search results, yet the URL Inspection Tool marks it as not indexed.
The fact that multiple independent voices in the SEO community found the same problem within the same period is significant. It suggests the issue is not tied to a single site, account, hosting environment, or content management system. It is a Search Console-side anomaly.
The publicly documented cases do not show damaged pages. The affected URLs are not returning 404 errors, they are not blocked by robots.txt, and they are not behind login walls. They are indexed pages that Search Console is failing to recognize.
Why Google Has Not Yet Added the Issue to Its Data Anomalies Page
Google maintains a Data Anomalies page to disclose known issues that affect Search Console data. Currently, the page does not mention this indexing status problem. Google has not issued an official statement about it, and no explanation has appeared in the product’s help documentation.
Google contacts, including John Müller, have been notified. The absence of a public acknowledgment does not necessarily mean Google is unaware. It may simply mean the investigation is still in its early stage.
What Does a Missing Data Anomalies Entry Mean?
A missing Data Anomalies entry means the issue has not been officially confirmed by Google. It does not mean the reports are wrong. Google has previously resolved short-lived anomalies without announcing them on that page.
Site owners should treat the Data Anomalies page as an official status channel, but they should not wait for an update before checking whether their own pages are actually indexed.
How to Verify Whether a Page Is Really Indexed
The fastest way to test whether a page is truly indexed is to search for the page URL directly in Google.
Use the site: operator:
site:yourdomain.com/your-page/
If the page appears in the results, it is definitely indexed. The site: operator is not a complete list of every indexed URL, so the absence of a result does not prove the page is unindexed. But a visible result is direct evidence that the URL is in Google’s index.
Another useful test is to check whether the page still ranks for its target keyword. A page cannot rank in Google search results if Google has removed it from the index. If organic traffic to that page continues in Google Search Console’s performance reports or in your analytics platform, that is another strong signal that the page is alive and indexed.
Document what you see. Screenshots of the URL Inspection status and the corresponding search result can be valuable if the problem persists or if you need to communicate with Google support.
What Site Owners Should Do Right Now
The correct response to this anomaly is verification and restraint, not reactive changes to the site.
- Confirm that high-value URLs still appear in search results using the site: operator.
- Check whether those pages still rank for their primary keywords.
- Compare Search Console data with traffic data from Google Analytics or other measurement tools.
- Monitor the Data Anomalies page for a new entry.
- Keep a record of any false “not indexed” statuses you encounter.
For most sites, no action is required beyond monitoring. If the pages are still in search results and still receiving traffic, there is no indexing emergency.
What to Avoid During a Search Console Indexing Anomaly
False negatives can cause site owners to solve problems that do not exist. That kind of overreaction can create actual indexing problems where there were none before.
- Do not submit every affected URL for reindexing. This adds unnecessary crawl pressure and will not repair a Search Console status.
- Do not add noindex tags to pages that are indexed. That will turn a reporting problem into a genuine indexing ban.
- Do not change canonical tags because the tool says a page is not indexed. A wrong canonical directive can weaken the page’s ranking signal.
- Do not delete or redirect pages that still appear in search results. The visibility in Google is stronger evidence than the status message.
If Search Console says a page is not indexed but Google search shows the page, trust Google search. The page is indexed.
Could This Be a Real Indexing Problem Instead of a Bug?
It is highly unlikely that this is a real indexing problem. A page that appears in Google search results is, by definition, in Google’s index. Search Console’s status message cannot override that reality.
Real indexing issues are usually caused by a noindex directive, a server error, a robots.txt block, a password requirement, or a Google decision not to include the page due to quality or relevance concerns. Pages affected by those problems do not rank in search results. The reported pages do appear in search results, which is why the Search Console status is so contradictory.
There is also no indication of a manual action or security issue in the reported cases. Google rarely removes a healthy page from the index without a clear signal, and none appears to be present here.
What Might Be Causing the Mismatch Behind the Scenes
Without an official explanation, any cause remains speculative. Still, the most plausible explanations all point in the same direction: a breakdown or delay in the flow of data between Google’s indexing systems and Search Console’s reporting layer.
The URL Inspection Tool does not reflect a single static list of indexed pages. It responds to a request by checking a page against multiple internal systems. If those systems are updated at slightly different times, or if the tool is reading from a data set that is temporarily stale, false “not indexed” states can appear.
Another possibility is that Google’s systems are testing a different canonical representation for some URLs. In that case, Search Console might see the URL as replaced by an alternative canonical and therefore report it as not indexed, even though the URL still appears in search results. This has not been confirmed, but canonicalization is a known source of confusion in indexing diagnostics.
None of these potential explanations requires site owners to do anything. The common thread is that the problem lives in Google’s ecosystem, not in the website’s code.
The Practical Consequences for SEO Teams and Agencies
For agencies, this anomaly is a client communication risk as much as a technical issue. A client who opens Search Console and sees a page marked as not indexed may assume the site has lost positions, that a migration went wrong, or that the agency failed. That assumption can trigger urgent calls, unnecessary redesigns, and a loss of trust in work that is actually performing correctly.
For in-house SEO teams, false negatives can distort internal dashboards. Tools that connect to the Search Console API can present a sudden increase in unindexed pages, which may look like a penalty or an infrastructure failure. Teams should recognize this as a data quality issue and avoid building a narrative around it until Google corrects the source data.
The practical standard is straightforward: use Search Console data for trends and pattern recognition, but verify important findings against Google’s live search results. When the tool conflicts with a page’s actual visibility, the live results should win.
How Long Is This Likely to Last?
Google has not provided a timeframe, and no Data Anomalies entry has been published for this issue. Similar Search Console data issues have historically lasted anywhere from a few hours to several days. Some are resolved silently when the source systems resynchronize.
If Google publishes a Data Anomalies notice, it may include more specific information about the scope and expected timeline. Until then, site owners should prepare for a short waiting period rather than a permanent index status problem.
The best approach is to keep sitemaps updated, keep pages accessible, and let Google’s systems settle. If the page appears in search results and continues to draw organic traffic, it is indexed. Search Console will catch up eventually.
