What "Found - Not Currently Indexed" Reveals About the Website
This status indicates that a URL is known, but no crawl has yet resulted in indexing. Patterns across page types are crucial.
For SEO managers and web developers, the "Found, not currently indexed" status highlights the difference between "Pattern by Page Type" and "Actual Retrieval." "Only rewrite content" is a typical warning sign.
Published: 3 min read · Author: Sebastian Geier
What does the "Found, not currently indexed" status reveal about a website?
If many URLs of a certain type are found but not crawled, this often indicates weak prioritization, large redundant URL spaces, or limited confidence in the expected benefits. Technical accessibility should be checked first; then the pattern of internal links, sitemaps, quality, and server behavior becomes crucial.
Priority Signals
Percentage of discovered but not yet crawled URLs per template and publication cohort.
Time until the first bot request after improvements to links, sitemap, or URL generation.
Actual Request
Affected URLs are grouped by template, discovery source, publication time, and internal depth.
URL inspection and logs confirm the missing crawl; robots.txt, server response, and host variants are excluded.
Subsequently, URL space, internal priority, and redundant content are corrected systemically and monitored as a cohort.
Patterns by Page Type
Test criterion
Patterns by Page Type
Individual URLs and entire template cohorts are separated because systemic causes only become visible when viewed as a group.
Test criterion
Actual Request
Server logs clarify whether Googlebot actually hasn't requested the address or whether a report simply doesn't yet reflect a more recent version.
Priority Signals Internal link position, sitemap cohort, recency, and similarity to other URLs all influence the expected relevance.
Rewriting Content Only
Rewriting Content Only Text changes are ineffective if bots cannot access the URL due to link structure, URL overload, or server control issues.
Indexing Request as a Strategy Manually submitting individual examples does not scale and does not address common page type patterns.
Sitemap Overload Numerous weak or non-canonical targets in the same sitemap can dilute the diagnosis of prioritized pages.
Defining Case: "Rewriting Content Only"
Hundreds of automatically generated site combinations are listed in the sitemap, but they have few internal links and very similar content. Instead of triggering individual URLs, the inventory is reduced to viable locations and prioritized via regional hubs.
Related questions and next steps
Crawl Budget: When it's truly relevant and when it isn't delves deeper into the "Patterns by Page Type" checkpoint. The key question is: For which websites is crawl budget a real problem, and when is it merely a distraction?
A complementary perspective is offered Interpreting HTTP status codes correctly, instead of just counting error numbersIt answers the question: "How do you meaningfully interpret HTTP status codes instead of just counting error numbers?"
If you want to practically implement "Find, not currently indexed" behavior, you can refer to Robust Website Systems This focuses on "Index Management and Diagnostics" and "Patterns by Page Type."
Conclusion: Found, not currently indexed
This status describes a pending retrieval decision and focuses attention on the entire discovered URL space. It only becomes meaningful when compared to a pattern of similar pages.
Sources and Further Information
The classification of "Found, not currently indexed" is based on the following official documentation and standards.
Faceted Navigation – Google Search CentralOfficial Google practice for controlling combinatorial filter and sort URLs.
Page Indexing Report – Google Search Console HelpOfficial definition and interpretation of indexing statuses in Search Console.
Robots Meta Tags Specifications – Google Search CentralOfficial specification of noindex and other indexing and preview controls, including necessary crawlability.
Key Thesis
It can indicate low internal priority, large URL spaces, server limitations, or a recent discovery. Logs, links, sitemaps, and affected groups help narrow down the cause.
What This Is Not About
The "Found, not currently indexed" status is not a final quality penalty and does not identify a single, definitive cause.
What it's about
It shows that Google is aware of the URL but has postponed fetching or further processing.
Crawling, Indexing & Canonicals
What "Crawled – not currently indexed" can actually mean
A separate step in the "Found, not currently indexed" process is to ask: What are the actual causes of the "Crawled, not currently indexed" status?
Crawling, Indexing & Canonicals
Orphan Pages from the perspective of users and search engines
Adds a separate decision to the "Found, not currently indexed" step: How should orphan pages be evaluated from the perspective of users and search engines?
Insights Overview
All VELUNO Insights at a Glance
Further analyses on Website Systems, digital visibility, and robust working models.
The "Found, not currently indexed" step is added to the "Orphan Pages" section.
An affected cohort should be sorted by discovery source and internal link path. The first systemic hypothesis can then be tested using logs instead of individual requests.