GSC Indexing Statuses Explained — Discovered vs Crawled Not Indexed

Part of our Google indexing learning path and technical SEO guide. See also how Google Search works in 2026.

Search Console indexing statuses are not decorative labels. They tell you which stage of Google's pipeline failed — and applying the wrong fix wastes weeks. Rewriting content won't help a URL Google hasn't crawled yet. Requesting indexing won't help a URL Google crawled and rejected for quality.

Definitions below come from Google's Page indexing report documentation and practitioner cross-checks against Crawl Stats.

The decision tree (read this first)

Discovered – currently not indexed → crawl priority problem. Google knows the URL exists; it hasn't fetched it yet (or not recently enough). Fix: internal links, sitemap hygiene, reduce low-value URL noise, fix crawl efficiency.

Crawled – currently not indexed → quality or duplication problem. Google visited, read the page, and chose not to index it. Fix: content depth, canonicals, consolidate thin variants, improve E-E-A-T signals on the template.

Excluded (noindex, redirect, 404, etc.) → intentional or technical block. Read the specific exclusion reason; don't blanket-request indexing.

Getting this wrong is expensive. We see teams spend a month "improving content" on Discovered URLs that simply aren't linked from anywhere important.

Discovered – currently not indexed

Google found the URL — typically via sitemap submission, an internal link, or an external link — but has not crawled it yet. On large or low-authority sites, this can persist for weeks.

Common causes

• Orphan URLs with no internal links from indexed pages
• New site or section with weak crawl priority
• Crawl budget spent on parameterized URLs, faceted navigation, or stale sitemap entries
• Server intermittently slow or returning errors (check Crawl Stats host status)

Fix workflow

1. Confirm the URL is in your XML sitemap and returns 200. Validate with our sitemap validator.
2. Add contextual internal links from high-traffic indexed pages — not just footer boilerplate. See internal linking strategy.
3. Check robots.txt isn't blocking the path or burning crawl on junk URLs. Use our robots.txt tester.
4. Wait 2–4 weeks after structural fixes; crawl priority changes are not instant. Request indexing via URL Inspection only after links and sitemap are correct.

Crawled – currently not indexed

Googlebot fetched the page and Google's indexing systems evaluated it — then declined to add it to the index. This is a quality or redundancy signal, not a crawl failure.

Common causes

• Thin or near-duplicate content (programmatic templates with minimal unique value)
• Canonical pointing elsewhere; Google agreed and indexed the other URL
• Weak site-wide quality signals on a new or unproven template
• Content that doesn't match what Google expects for the URL pattern

Fix workflow

1. URL Inspection → View crawled page → confirm what Google actually rendered (especially for JS sites).
2. Compare against indexed competitors for the same intent. If your page adds nothing new, consolidation beats expansion.
3. Verify canonical tags with the SEO Scout extension on the live URL — wrong self-referential canonicals are common after migrations.
4. Improve depth: original data, first-hand steps, cited sources — not synonym spinning. See our editorial standards.
5. After substantive changes, request re-indexing once — not daily. Repeated requests without meaningful diffs do not help.

Cross-reference Crawl Stats

Page indexing tells you outcomes. Crawl Stats (Settings → Crawling in GSC) tells you how Googlebot behaved: total requests, response codes, robots.txt fetch failures, average response time, host availability.

High crawl volume + flat indexed count usually means one of:

• Google is crawling redirects, errors, or noindex URLs that never enter the index
• Many URL variants are crawled; only the canonical is indexed
• Pages are crawled but fail the quality threshold repeatedly

If Crawl Stats shows a spike in 5xx or robots.txt failures, fix infrastructure before touching content. No amount of copywriting compensates for a server Google cannot reliably fetch.

Indexed but no traffic?

Indexing is gate two. Serving is gate three. A URL can be indexed and still earn zero clicks because it ranks on page four, targets irrelevant queries, or loses impressions to AI Overviews. That's a ranking/SERP problem — not an indexing problem. Diagnose in the Performance report, not Page indexing.

Third-party data: quality dominates exclusions

A February 2026 analysis of 1.7 million pages across 18 sites (Indexing Insight) found 88% of not-indexed pages tied to quality-related issues — not technical blocks. Treat that as directional, not Google gospel: it's one vendor study, not official Search Console documentation. But it matches what we see on client sites after core updates: Crawled-not-indexed often clusters on thin template pages, not broken robots.txt.

Quick reference table

Sources

1. Google Search Console Help — Page indexing report
2. Google Search Console Help — Crawl Stats report
3. Google Search Central — How Google Search works
4. Indexing Insight — Why pages are not indexed (1.7M page study, Feb 2026)

Try our free SEO tools or explore more in-depth guides.