Why Your Pages Aren't Indexed: Every Google Search Console Status Explained (2026)

Open Google Search Console, scroll to “Why pages aren't indexed,” and it is easy to panic. You see a list of official-looking statuses — Page with redirect, Crawled — currently not indexed, Alternate page with proper canonical tag — each with a number next to it. It all looks like something you broke.

I have looked at this screen on my own sites and on dozens of others. Here is the main thing to know: most of these are not emergencies, and several are Google working the way it should. The skill is not fixing every line. It is knowing which few lines matter and which ones you can leave alone.

Here is the report we are going to break down, line by line:

Why pages aren't indexed

Pages that aren't indexed can't be served on Google.

The short answer · every status at a glance

Status Breakdown

What is the Google Search Console Page indexing report?

The Page indexing report is Google's list of every URL it knows about on your site, and whether each one is in the index.

Every URL falls into one of two groups: Indexed (can show up in search) or Not indexed (cannot, for one of the reasons in the table).

Does “not indexed” mean my page is broken?

No. This is the most important idea in the whole guide. “Not indexed” does not mean “error.” Google's own help docs say it plainly: not every page Google crawls will be indexed. Many “not indexed” pages are ones Google left out on purpose — duplicates, redirects, alternate versions, and pages you told it to skip.

What does the “Source” column mean (Website vs Google systems)?

The Source column is the most useful and most ignored part of the report. It tells you who is responsible for a page not being indexed — and so, who can fix it.

• Website: The issue comes from your site. You have a lever — a redirect, a tag, a status code, a link.
• Google systems: Google made a judgment call — about quality, priority, or which duplicate to keep. There's no switch you flip.

Which not-indexed reasons should you actually fix?

Here is the whole report sorted the way I work through it. I call it the Source-First Triage: read the Source column, then drop each row into one of three buckets — fix now, look into it, or usually fine.

Fix Now

• Server error (5xx)
• Redirect error
• Soft 404
• Not found (404)
• Blocked by robots.txt

Investigate

• Crawled – currently not indexed
• Discovered – currently not indexed
• Duplicate without user-selected canonical

Usually Fine

• Alternate page with proper canonical tag
• Page with redirect
• Excluded by ‘noindex’ tag
• Duplicate, Google chose different canonical

The “Website” reasons: the ones you control

Page with redirect:

A URL that isn’t in Google because it forwards visitors (and Google) to another page.

Redirect error:

Set up a forward from one page to another, but it's broken — it loops in circles or leads nowhere. Google gave up trying to follow it.

Not found (404):

Google looked for this page and it simply wasn't there.

Soft 404:

The page loads “successfully,” but there's basically nothing on it, so Google treats it like a missing page.

Excluded by ‘noindex’ tag:

There's a hidden instruction on this page telling Google “don't list me.”

Blocked by robots.txt:

You put up a “do not enter” sign for this page, so Google never went in to read it.

Server error (5xx):

When Google knocked, your server answered with an error instead of handing over the page.

The “Google systems” reasons: Google's judgment calls

Discovered — currently not indexed:

Google knows this page exists but hasn't crawled it yet. It's sitting in the queue — often because the page looks low-priority or your server seemed slow.

Crawled — currently not indexed:

Google read the page and decided it's not worth adding — usually because the content feels thin or too similar to things already out there.

Duplicate, Google chose different canonical than user:

You declared one URL as canonical, but Google overrode you and indexed a different URL as the master version instead.

Duplicate without user-selected canonical:

Google found duplicate versions of a page, but you didn't specify a canonical at all.

What do the Validation states (Not started, Started, Passed) mean?

The Validation states track Google re-checking an issue after you fix it. Once you have fixed something, you can ask Google to re-check it.

• Not started: You haven't asked Google to re-check.
• Started: You clicked “Validate Fix.” Google is re-crawling the affected URLs in batches.
• Passed: Google re-checked and the issue is gone.

Key Takeaways

• Trying to drive “not indexed” to zero: A healthy site always has not-indexed pages.
• Reading the Source column last (or never): It's the best triage you have.
• Spamming “Request indexing”: Clicking it repeatedly doesn’t change quality decisions.
• Deleting or redirecting pages in a panic: Redirecting every 404 to the homepage creates soft 404s.
• Fixing per-page when it's site-wide: For the quality statuses, focus on overall quality.

Frequently asked questions

What is the difference between 'Discovered - currently not indexed' and 'Crawled - currently not indexed'?

• 'Discovered - currently not indexed' means the URL has not been crawled yet.
• 'Crawled - currently not indexed' means it has been crawled but not indexed.

Is 'Alternate page with proper canonical tag' a problem?

Usually not; it indicates correct canonicalization.

Why did Google choose a different canonical than the one I set?

Because a rel=canonical tag is a hint, not a directive.

Do I need to fix every page in the 'Why pages aren't indexed' report?

No. Prioritize by triage.