Key takeaways
- A directory of Google Search Console indexing statuses with plain-English meanings, why they happen, and the exact follow-up checks
- Use this as a map into the full library of status-specific guides
Table of Contents
If your pages are “crawled” but not showing — or you keep bouncing between statuses — you’re not alone. Search Console is describing a pipeline problem, not giving you a single “fix”.
This page is a directory: pick the exact status you see, then open the dedicated guide for the meaning + what to check next.
Start with the overview if you want the big picture:
- GSC indexing statuses guide (2026): what they mean and what to do
- URL Inspection Tool (2026): what it really shows
Sitemap statuses and errors
If Google can’t read your sitemap, discovery stalls before indexing even starts.
Sitemap could not be read:
Sitemap errors (root causes and what to fix first):
Indexing / processing statuses
Crawled — currently not indexed → meaning + what actually moves the needle:
Discovered — currently not indexed → why discovery can stall:
Canonical / duplication statuses
If canonicals are noisy, the system often “understands you faster” — and then decides against visibility faster too.
Duplicate without user-selected canonical:
Google chose different canonical:
Alternate page with proper canonical tag:
Primitives (if you need the concept first):
Robots / noindex / access restriction statuses
Submitted URL marked ‘noindex’:
Submitted URL blocked by robots.txt:
Robots.txt unreachable:
Indexed, though blocked by robots.txt (yes, it happens):
Blocked due to access forbidden (403):
Blocked due to other 4xx:
Redirect / crawl issue / “it’s there but not really” statuses
Page with redirect:
Too many redirects:
Redirect loop fix:
Submitted URL has crawl issue:
Crawl anomaly:
Server error (5xx):
Not found / soft 404 statuses
Not found (404):
Soft 404:
If your real problem is “indexed but invisible”
If the page is indexed and technically fine, but visibility is unstable or absent, these are the essays that explain the “why”:
Next in SEO & Search
Up next:
Sitemap could not be read (Google Search Console): what it means and how to fix it (2026)“Sitemap could not be read” means Google failed to fetch or parse your sitemap as a sitemap. This guide explains the failure modes (HTTP, redirects, content-type, format, size), how to diagnose fast, and what changes actually remove the error.