A page that won't index is rarely a mystery — in most audits the cause is one of nine repeat offenders. Work through them in order: the first five are technical blockers you can fix today, the last four are quality calls that take longer.
Technical blockers
- noindex — in meta robots or the X-Robots-Tag header, including values set by the platform or theme rather than by you.
- robots.txt block — Google can't fetch the page at all. A robots block and noindex are different mechanisms with different fixes; a page blocked in robots.txt can't even see your noindex removal.
- Canonical pointing elsewhere — the content may be indexed under the URL Google selected as canonical, not the one you're checking. URL Inspection shows the Google-selected canonical.
- Soft 404 — the page returns 200 but reads as “not found” or near-empty, so Google drops it.
- 4xx/5xx or redirect chains — dead placements and long chains fall out of the crawl queue.
Quality and crawl-priority causes
- Thin or near-duplicate content — crawled, evaluated, skipped. If ten URLs differ by one paragraph, expect Google to keep one.
- Orphan pages — no internal links pointing at the URL. The classic quiet killer on large sites.
- “Crawled – currently not indexed” — Google saw the page and declined, usually a quality or demand signal. Step-by-step triage: fix guide for Crawled – currently not indexed.
- “Discovered – currently not indexed” — Google knows the URL exists but hasn't fetched it; a crawl-priority problem, common on new sites and deep sections.
The triage workflow
First confirm what's actually out: run the full list through a bulk checker to check which URLs are really indexed — Search Console's report lags and samples. Then split the non-indexed pile: causes 1–5 → fix and resubmit; causes 6–7 → improve or consolidate; causes 8–9 → strengthen signals (internal links, submission) and re-check at day 14 and 28.
Related reading