Back to blog
Indexation·2026-08-28·4 min read

What your indexation health is actually telling you

Indexed, not indexed, blocked, error — the four buckets and what to do about each one without panic.

Indexation reports usually arrive as a spreadsheet with four counts and a vague sense of dread. The four buckets are meaningful — if you know what each one actually means.

Indexed

Your page is in the index. This is the default good state. It doesn't mean the page is ranking well — it means Google knows it exists and has decided to keep it. Most of your attention should go elsewhere.

Not indexed

Google has crawled the page but chosen not to index it. Common reasons: low value or thin content, duplicate or near-duplicate content, or a canonical pointing elsewhere. This is usually a content or signal problem, not a technical one.

The fix is usually one of: improve the page's unique value, consolidate it with a stronger page, or check whether a canonical is pointing the wrong way.

Blocked

The page is blocked from indexing — by robots.txt, a noindex directive, or a robots meta tag. This is technical and usually a mistake, unless the page genuinely shouldn't be indexed (thank-you pages, internal tools, staging).

Check robots.txt first, then meta robots, then any CDN or edge config that might be injecting headers. The fix is almost always deleting something that shouldn't be there.

Error

Google tried to crawl the page and couldn't — 4xx or 5xx, timeout, or connectivity issue. This is a technical problem and usually the most urgent of the four, because a page in error state is a page Google has given up on.

Fix the underlying error, then request reindexing via Search Console. Don't assume it'll come back on its own — it usually won't.

What indexation health percentage actually means

“92% indexation health” sounds reassuring. It means 92% of the pages you submitted are indexed. The interesting number is the 8% — and what those pages are. Ten blocked pages that include your money pages are worse than fifty not-indexed pages that are thin blog posts you forgot about.

See this in the console

Book a 30-minute demo and we'll walk you through your own data — or a realistic sample.