Learn

The Page indexing report: every reason Google lists, and what to do

Search Console's Page indexing report lists why URLs are not in Google's index. Some reasons are bugs on your site, some are Google's judgment, and some are the correct result. This guide uses Google's own reason names, says which ones need action, and links to the detailed fix where we have one.

By Adem ÇakalPublished 2 sources8 min read
Short answer

Open Search Console, then Indexing, then Pages, and read the "Why pages aren't indexed" table. Ignore reasons that describe intended behavior (alternate page with canonical, a 404 for a deleted page, a noindex you set on purpose). Fix first the ones that block pages you want indexed: server errors, redirect errors, robots.txt blocks, noindex, 401 and 403. Treat "crawled" and "discovered" as page-quality and priority questions, not errors.

The reasons, with Google's names

The table below uses the reason names and meanings from Google's Page indexing report help page. "Action needed" is our reading of that page: yes means the reason can block a page you want indexed, depends means it is only a problem for some URLs, and no means Google describes it as expected.

ReasonWhat it meansAction needed?First checkOur page
Server error (5xx)Your server returned a 500-level error when the page was requestedYesCrawl Stats report: was the host available? Is the server down or overloaded?Section below
Redirect errorA redirect chain too long, a loop, a redirect URL over the maximum length, or a bad or empty URL in the chainYesTrace the redirect with Lighthouse or another debugging toolSection below
URL blocked by robots.txtThe page was blocked by robots.txt; it may still be indexed by other meansDependsTest the URL against your robots.txt rulesBlocked by robots.txt
URL marked 'noindex'Google found a noindex directive when it tried to index the pageDependsLook for the tag in the HTML and the X-Robots-Tag header; run a live URL Inspection testNoindex stuck
Soft 404The page shows a "not found" style message but does not return a 404 statusYesLive test: how does Google render the page?Soft 404
Blocked due to unauthorized request (401)Googlebot was blocked by a request for authorizationDependsIs the page behind a login you did not mean to apply to bots?Section below
Not found (404)The page returned a 404 when requestedUsually noWas it deleted on purpose? Did it move?Section below
Blocked due to access forbidden (403)The server returned 403 to Googlebot, which sends no credentialsYesDoes the page load for a visitor who is not signed in?Section below
URL blocked due to other 4xx issueA 4xx error not covered by any other reasonYesDebug the URL with URL InspectionSection below
Crawled - currently not indexedGoogle crawled the page and did not index itDependsInspect the URL; judge the page's valueCrawled, not indexed
Discovered - currently not indexedGoogle found the URL but has not crawled it; the last crawl date is emptyDependsIs the URL in a sitemap and linked internally?Discovered, not indexed
Alternate page with proper canonical tagThe page is an alternate that correctly points to an indexed canonical pageNoConfirm the canonical target is the page you wantAlternate page
Duplicate without user-selected canonicalA duplicate with no declared canonical; Google picked another URLDependsInspect the URL to see Google's chosen canonicalDuplicate canonical
Duplicate, Google chose different canonical than userGoogle indexed the page it considers canonical instead of the one you declaredDependsCompare user-declared and Google-selected canonicalSection below
Page with redirectA non-canonical URL that redirects to another pageUsually noCheck whether the target is indexedPage with redirect

Google puts two further cases outside the not-indexed list. Indexed, though blocked by robots.txt and Page indexed without content are covered below. A normal indexed page shows as Page is indexed, which Google says may still carry other issues such as structured data problems.

Triage order

Triage in four tiers: access errors first, then directives, then duplicates, then Google's judgment 1. Access 5xx, 401, 403, other 4xx, redirect error 2. Directives robots.txt, noindex, soft 404 3. Duplicates canonical mismatch, redirected URLs 4. Judgment crawled / discovered, not indexed Ignore: alternate page with canonical, deleted 404, intentional noindex Order is our suggestion; the reasons and meanings come from Google's help page.
Work top to bottom. Errors you cause outrank decisions Google makes, because they are cheaper to confirm and fix.
  1. Filter to pages you care about. Export the URLs under each reason, then remove anything you never wanted indexed: tag archives, internal search, thank-you pages.
  2. Fix access errors on wanted pages. A 5xx, 401, 403 or other 4xx on a money page is a defect, not a judgment call.
  3. Check directives. A noindex or robots.txt rule left over from staging is a common cause of a missing page. Confirm each is intentional.
  4. Look at canonicals and redirects. Make sure the URLs you want indexed are the ones your canonical tags, sitemap and internal links point to.
  5. Only then deal with crawled or discovered. These depend on page value and crawl priority, and the fixes are slower.

Reasons without a page of their own

Server error (5xx)

Google defines it as your server returning a 500-level error on request. Google's action list: check host availability in the Crawl Stats report, reduce excessive page loading for dynamic requests, confirm the server is not down or overloaded, and make sure protection systems are not blocking Googlebot. If a firewall or bot filter answers Googlebot with an error, the pages look broken only to Google.

Redirect error

Google lists four causes: a chain that is too long, a loop, a redirect URL over the maximum length, or a bad or empty URL in the chain. Its suggestion is to use a debugging tool such as Lighthouse to see the redirect details. Follow the chain hop by hop and make the first URL redirect once, directly to the final page.

Blocked due to unauthorized request (401)

Googlebot was blocked by a request for authorization. If you want the page indexed, Google says to remove the authorization requirement or allow Googlebot after verifying its identity. If the page is a private area, the status is correct and you can leave it.

Not found (404)

The page returned a 404, and Google may have found the URL through a link or a page that was deleted earlier. Per Google, no action is needed if you removed the page without a replacement. If the page moved, use a 301 redirect to the new address. Check internal links and your sitemap so they do not keep pointing at the dead URL.

Blocked due to access forbidden (403)

Google explains that 403 means the user agent provided credentials but was not granted access. Googlebot never sends credentials, so Google says the server is returning the error incorrectly. The fix is to allow non-signed-in users to see the page, or to allow Googlebot without authentication after verifying its identity.

URL blocked due to other 4xx issue

This is a 4xx error not covered by another reason. Google's advice is to debug the page with the URL Inspection tool. Our URL Inspection walkthrough covers the fields to read.

Duplicate, Google chose different canonical than user

You declared a canonical, and Google indexed a different page it considers canonical. In URL Inspection, compare the user-declared and Google-selected canonicals, and compare the two pages in a browser. Google says that if your declared canonical is not similar to the page, it will not choose it, so either make the content match or change the declaration. Related background: noindex vs robots.txt vs canonical.

Indexed, though blocked by robots.txt

The page is in the index despite a robots.txt block, and Google says snippets are likely to be very limited. Robots.txt controls crawling, not indexing. To keep the page out of the index, Google's guidance on the blocked-by-robots reason is to remove the block and use a noindex directive, since Google must be able to fetch the page to see it. See blocked by robots.txt.

Page indexed without content

The page is in the index, but Google could not read its content. The help page does not give a remedy here, so start with a live URL Inspection test and view the rendered page to see what Google receives. Causes, checks and fixes are in Page indexed without content: how to fix it.

Summaries of reasons we cover in full

  • Crawled - currently not indexed. Google fetched the page and did not index it, which Google calls common and not necessarily a problem. Judge the page's value first. Full fix.
  • Discovered - currently not indexed. Google knows the URL but has not crawled it; per Google the crawl was rescheduled because it was expected to overload the site. Full fix.
  • Alternate page with proper canonical tag. The page correctly points to an indexed canonical, and Google says no action is needed. Details.
  • Duplicate without user-selected canonical. Google chose a canonical because you declared none; it is not treated as an error. Full fix.
  • Page with redirect. A non-canonical URL that redirects; inspect it to check the target's status. Details.
  • URL blocked by robots.txt. The robots.txt file stops the fetch. Details.
  • Soft 404. A "not found" style page without a 404 status; return a real 404 or add real content. Details.
  • URL marked 'noindex'. A noindex directive was found. If you removed it and the report still shows it, see noindex stuck after turning it off.

Two neighboring problems are not reasons in this report. A page that is indexed but gets no impressions is covered in indexed but not showing in search. A sitemap that Google cannot read is covered in sitemap could not fetch.

Common mistakes

  • Treating the total as a score. A long not-indexed list is normal. The count that matters is wanted pages under a blocking reason.
  • Blocking a page in robots.txt to remove it. The page can still end up indexed with limited snippets. Use noindex, and let Google crawl the page so it can see the directive.
  • Redirecting every 404 to the homepage. Google's advice for a moved page is a 301 to the new address; a deleted page with no replacement needs no action.
  • Requesting indexing for pages with an access error. Fix the 5xx or 403 first, confirm with a live test, then ask.
  • Blocking Googlebot by accident. Firewalls and bot protection can return 401 or 403 or 5xx to Googlebot only. Google says to verify Googlebot's identity before allowing it.
  • Chasing "Duplicate" reasons by adding more tags. Compare the two pages first. If they are near-identical, merge them; if not, make the content differ.

Before and after a fix, run a quick check with the noindex checker and read the URL Inspection result again.

Questions people ask

Do I need to get every URL in the report indexed?

No. Google's help page says the status Crawled - currently not indexed is common and not necessarily a problem, and it lists several reasons, such as Alternate page with proper canonical tag, where no action is needed. Work on the pages you want people to find.

What is the difference between a reason and a warning?

Reasons under not indexed describe pages Google did not add to the index. Google also lists two cases that appear in the page experience section: Indexed, though blocked by robots.txt, and Page indexed without content. Those pages are in the index.

Where do I see why one specific URL is not indexed?

Use the URL Inspection tool. The Page indexing report groups URLs by reason, and inspecting a URL shows its crawl, indexing and canonical details, including the live test.

Is Not found (404) something I must fix?

Not if you removed the page on purpose. Google says no action is needed when a page was removed without a replacement. If the content moved, Google says to use a 301 redirect.

Sources

  1. Search Console Help: Page indexing report, accessed 2026-11-16.
  2. Search Console Help: URL Inspection tool, accessed 2026-11-12.