Page indexing report

Every Search Console Page indexing status, explained

Find the exact reason Search Console shows for your URLs. Each page explains what Google means by it, when you can ignore it, what usually causes it and how to fix it.

Last updated: 2026-10-30

In short

The Page indexing report gives a reason for every URL Google knows about but has not indexed, plus warnings for URLs that are indexed with a problem. Many of these reasons are intentional, and Google itself says you should not expect every URL to be indexed. First confirm the affected URLs are pages you want in Google, then fix the cause for those only.

Why pages aren't indexed

Crawled - currently not indexed

Crawled - currently not indexed means Googlebot fetched the page but Google decided not to add it to the index, at least for now. Google says it may or may not be indexed later and that you do not need to resubmit it. For pages that matter, make them clearly distinct and useful, link to them internally and check canonical signals.

Read the fix →
Discovered - currently not indexed

Discovered - currently not indexed means Google found the URL, through a link or a sitemap, but has not crawled it yet. Google says it typically postponed the crawl because crawling was expected to overload the site. Fix it by cutting low-value URLs, improving server response and linking to the pages that matter.

Read the fix →
Duplicate without user-selected canonical

This status means Google sees the URL as a duplicate of another page, you did not declare a canonical, and Google picked the other URL to show in Search. Google calls this working as intended. Act only if Google picked the wrong URL or if the page is not really a duplicate.

Read the fix →
Duplicate, Google chose different canonical than user

This status means the page is marked as canonical for a set of pages, but Google decided another URL is the better representative and indexed that one instead. A canonical tag is a hint, not a rule. Compare the pages involved, then make redirects, canonical tags, internal links and sitemaps all point at the same URL.

Read the fix →
Alternate page with proper canonical tag

This status means the URL is an alternate version that correctly points to another canonical page, and that canonical is indexed. Google says there is nothing you need to do. Spot-check that the canonical is the URL you want and that no important page ended up here by mistake.

Read the fix →
Page with redirect

Page with redirect means the URL is a non-canonical URL that redirects to another page, so Google does not index it. That is expected for old URLs, HTTP or www variants and moved pages. Check that the redirect target is correct and indexable, and stop linking to redirecting URLs from your pages and sitemap.

Read the fix →
Soft 404

A soft 404 is a URL that returns a 200 (success) status code but looks to Google like a not-found, empty or error page. Google excludes these pages from Search. Return a real 404 or 410 for missing pages, 301 redirect moved ones to a real replacement, and fix rendering for real pages that Google misread.

Read the fix →
Not found (404)

Not found (404) means Google requested the URL and your server answered 404. Google says a 404 is not necessarily a problem when a page was removed without a replacement. Fix the 404s you link to yourself or list in a sitemap, and 301 redirect pages that moved.

Read the fix →
Blocked by robots.txt

Blocked by robots.txt means a rule in your robots.txt file stops Googlebot from crawling the URL, so Google cannot index its content. If the block is intentional, leave it. If the page should be in Google, remove or narrow the rule; if you want it out of Google, use noindex instead, because robots.txt does not reliably prevent indexing.

Read the fix →
Excluded by 'noindex' tag

This status means Google crawled the page, found a noindex rule in a robots meta tag or an X-Robots-Tag HTTP header, and therefore did not index it. If you do not want the page in Google, this is working. If you do, remove the noindex at its source, confirm with Test live URL and request indexing.

Read the fix →
Server error (5xx)

Server error (5xx) means your server returned a 500-level error when Googlebot requested the page. Google slows crawling when it sees these errors and eventually drops URLs that keep failing. Check host status in Crawl Stats, reproduce the error, then fix capacity, timeouts or rules that block Googlebot.

Read the fix →
Redirect error

Redirect error means Google tried to follow a redirect from the URL and failed. Google lists four causes: a chain that was too long, a redirect loop, a URL that grew past the maximum length, and a bad or empty URL in the chain. Trace the redirect hop by hop and point the URL straight at a working final page.

Read the fix →
Blocked due to unauthorized request (401)

This status means the server answered Googlebot with 401 Unauthorized, asking for credentials Googlebot does not have. If the page is private, that is correct and the page stays out of Google. If it should be public, remove the authorization requirement or, if you must keep it, let verified Googlebot requests through.

Read the fix →
Blocked due to access forbidden (403)

This status means your server returned 403 Forbidden to Googlebot. Google points out that Googlebot never sends credentials, so a 403 to Googlebot is usually returned incorrectly. If the page should be in Google, find the firewall, CDN or server rule that blocks it and allow verified Googlebot.

Read the fix →
Blocked due to other 4xx issue

This status means Googlebot received a 4xx client error that is not one of the codes with their own row, such as 401, 403 or 404. Google gives no further detail, so the first step is to find the exact code your server returned. Then fix how your server handles the request for pages that should be public.

Read the fix →

Indexed, with a warning