Rule (R3): "Discovered – not indexed" and "Crawled – not indexed" have DIFFERENT triggers — first is crawl-priority/site-wide quality signal, second is per-page quality decision; treat them differently
Rule
Rule: The two GSC "not indexed" states have different underlying causes and should be treated differently:
"Discovered – currently not indexed" = Google knows the URL exists but hasn't crawled it yet. At scale this is a crawl-priority / site-wide quality signal (A large "Discovered – currently not indexed" backlog is a SITE-WIDE quality signal, not a per-page problem — Google declines to spend crawl resources on URL patterns it predicts will be low-value). Fix: site-wide quality and internal-linking architecture.
"Crawled – currently not indexed" = Google has crawled the page and chose not to index it. This is a per-page quality decision (Search Console "Crawled – currently not indexed" is a deliberate quality decision, not a queue state — Google fetched and evaluated the page and CHOSE not to index it). Fix: improve the specific page, or accept that it isn't worth keeping.
Why: These two states are commonly conflated. "Discovered" looks like a queue problem; it's usually a site-wide signal. "Crawled" looks like a Google bug; it's usually a deliberate quality decision. Different triggers → different interventions. Misdiagnosing one as the other produces wasted effort.
How to apply: Read the GSC Page Indexing not-indexed breakdown by category, not aggregate count. If "Discovered" is rising while "Crawled" is steady → site-wide quality lift (internal linking, content depth, prune thin content). If "Crawled" is rising while "Discovered" is steady → per-page quality lift on the affected pages (rewrite, merge, or drop). Cross-link: Rule: a large or rising "Discovered/Crawled – currently not indexed" count is a SITE-WIDE quality signal — fix the site, not the page, Rule: if important pages remain unindexed after ~4 weeks despite good content and clean technicals, escalate to a content-quality and internal-linking audit — do NOT just keep clicking "request indexing".
Related entries
Related
- reference Search Console "Discovered – currently not indexed" can persist indefinitely — Mueller: "That can be forever. It's something where we just don't crawl and index all pages"
- reference A large "Discovered – currently not indexed" backlog is a SITE-WIDE quality signal, not a per-page problem — Google declines to spend crawl resources on URL patterns it predicts will be low-value
- reference Search Console "Crawled – currently not indexed" is a deliberate quality decision, not a queue state — Google fetched and evaluated the page and CHOSE not to index it
- rule Rule: a large or rising "Discovered/Crawled – currently not indexed" count is a SITE-WIDE quality signal — fix the site, not the page
- rule Rule: if important pages remain unindexed after ~4 weeks despite good content and clean technicals, escalate to a content-quality and internal-linking audit — do NOT just keep clicking "request indexing"
Referenced by (2)
- reference Research brief: how long does it actually take a new website to move through Google's pipeline — a methodology-graded benchmark report (June 2026) relates-to
- reference GSC instrumentation — URL Inspection (live + API, 2,000/day/property cap) is ground truth for a specific URL; Page Indexing report distinguishes Discovered-not-indexed vs Crawled-not-indexed; Performance report normally lags 2–6h relates-to