Technical SEO

Page indexing report: what each 'not indexed' reason means, and which to fix

Read the Search Console Page indexing report: the 15 reasons pages aren't indexed, which ones to ignore, how to fix the rest and how validation works.

// in this article

Of the 15 reasons Search Console’s Page indexing report gives for a page not being indexed, close to half describe Google working as intended and need nothing from you. The report lives under Indexing > Pages, splits every URL Google knows on your site into indexed and not indexed, and the only question that matters is whether a page you want in Google is sitting in the wrong column.

This guide goes through every reason in the “Why pages aren’t indexed” table, grouped by what you should do about it, using the wording in Google’s Page indexing report help. If you’re chasing one specific page instead of the whole site, start with URL Inspection, because this report can’t filter by URL.

Read the report in this order

The summary page has a chart of indexed and not indexed pages, then the “Why pages aren’t indexed” table. Before you open any reason, do three things.

  1. Switch the filter at the top from “All known pages” to “All submitted pages”. Google offers four views: all known pages (the default), all submitted pages, unsubmitted pages only, or one specific sitemap. Submitted pages are the ones your sitemap says you care about, so a problem there is a real problem. Unsubmitted URLs are mostly old links, parameters and duplicates.
  2. Look at the Source column. Each reason is marked “Website” or “Google”. Google’s help says you can generally fix only the ones marked Website. Google-sourced reasons, such as “Crawled - currently not indexed”, are Google’s decision, so you change the page and wait.
  3. Click a reason and read the example URLs. The list shows at most 1,000 URLs per reason, so on a big site look at the pattern (one folder, one template, one parameter) rather than trying to clear every row.

Step 1 changes the most. A small business site can show hundreds of not indexed URLs under “All known pages” and almost none under “All submitted pages”, which means the sitemap and the important pages are fine and the noise comes from elsewhere. If you don’t have a sitemap submitted yet, fix that first; our guide to sitemap fetch errors covers the common blocks.

Google is clear that not every URL on a site will be indexed. Duplicates and low-value URLs are meant to stay out. A large “Not indexed” number on its own is not a problem to solve.

Why pages aren't indexed · All submitted pages
ReasonSource · Pages
Page with redirectWebsite · 9
Alternate page with proper canonical tagWebsite · 4
Crawled - currently not indexedGoogle · 3
URL marked 'noindex'Website · 1
fig 1 · a made-up dental practice in tampa, filtered to submitted pages. only the two highlighted rows need a look. illustrative, not measured data, layout simplified

In that made-up example, 13 of the 17 submitted URLs that aren’t indexed are fine: the sitemap still lists 9 old URLs that now redirect (clean them out of the sitemap), and 4 are alternates pointing to a canonical. The 3 crawled pages and the 1 noindexed page are where the work is.

Reasons you can usually leave alone

These mean Google found a URL and correctly chose not to index it. Check the examples once to confirm nothing important is in the list, then move on.

Alternate page with proper canonical tag. The page points to another URL as its canonical, and Google agreed. Google’s help says no action is needed. Typical examples are tracking-parameter URLs, print versions and AMP pages.

Page with redirect. The URL redirects, so Google indexes the target instead. That’s what a redirect is for. The only fix worth making is removing redirected URLs from your sitemap and internal links, so the report under “All submitted pages” stays clean.

Not found (404). If you removed a page on purpose and there’s no replacement, a 404 is correct. If the page moved, use a 301 redirect. Our guide to fixing 404 errors covers which 404s are worth a redirect.

URL marked ‘noindex’. Fine for thank-you pages, cart and account pages, internal search results and tag archives. It’s a problem only if a page you want ranked is in the list (see the next section).

URL blocked by robots.txt. Fine when you blocked something like an admin folder on purpose. Note that robots.txt stops crawling, not indexing: Google’s robots.txt guide says a blocked URL can still be indexed without its content if other pages link to it. To keep a page out of Google, use a noindex tag or a password instead.

Duplicate without user-selected canonical. Google decided this URL is a copy of another page and picked that other page as the canonical. That’s often right (an uppercase URL, a trailing-slash variant). It becomes a problem only when Google picked the wrong one, which you can see by inspecting the URL.

pile_01 Usually leave alone
alternate with canonical
page with redirect
not found (404)
noindex, robots.txt
duplicate, no canonical
pile_02 Fix if the page matters
crawled, not indexed
discovered, not indexed
google chose different canonical
noindex on a money page
pile_03 Fix now
server error (5xx)
redirect error
soft 404
401, 403, other 4xx
fig 2 · the 15 reasons sorted into three piles. reason names from google search console help, november 2026

Reasons to fix when the page matters

These are the reasons where a page you want in Google often ends up. Filter to submitted pages and only act on URLs you’d want a customer to land on.

Crawled - currently not indexed. Google fetched the page and decided not to index it, for now. Google’s help calls this a common message for many sites, so a few old blog posts here is normal. When it’s a service or location page, the usual cause on a small site is a page that adds little: a thin page, a near copy of another city page, or a page with almost no text. Fix: make the page clearly useful and different from your other pages, or merge it into a stronger one. Then inspect it and request indexing once.

Discovered - currently not indexed. Google knows the URL exists but hasn’t crawled it yet. The help says Google may hold off to avoid overloading the site, but on a site with a few dozen pages that’s rarely the reason. More often the page has no internal links pointing to it, so it looks unimportant. Fix: link to it from your home page, menu or a related page, and make sure it’s in your sitemap. Our roundup of internal linking tools shows how to find pages with no links in.

Duplicate, Google chose different canonical than user. You set a canonical tag, but Google picked a different URL because it sees this page as a copy of that one. Google’s guide to duplicate URLs treats the canonical tag as a strong signal, not an order: a redirect is stronger, and listing a URL in your sitemap is a weak extra signal. If Google keeps choosing the other page, the two pages are probably too alike. Either make them different or redirect one to the other. Our canonical tag guide shows how to check which URL Google picked.

URL marked ‘noindex’ on a page you want ranked. This is the most expensive mistake in the report, because the fix takes seconds and the cost is total. Common causes are a “discourage search engines” setting left on after a site launch, or an SEO plugin applying noindex to a whole page type. Remove the tag (or the X-Robots-Tag header), then request indexing.

Reasons to fix now

These are server and setup errors. They’re marked “Website” because the cause is on your side, and they can hit important pages without you noticing.

Server error (5xx). Your server returned a 500-level error when Google asked for the page. One-off spikes during a hosting outage clear up on their own. Repeated errors on the same URLs point to a plugin, a timeout or a host blocking Googlebot under load. Ask your host to check the server logs for Googlebot requests on those URLs.

Redirect error. Google hit a redirect chain that was too long, a loop, a URL that grew too long, or a bad or empty URL in the chain. Point each old URL straight at its final destination in one hop.

Soft 404. The page returns a normal 200 status but looks like an error page to Google, often an empty category, an out-of-stock page with no content or a “no results” page. Either return a real 404 or 410, or give the page real content.

Blocked due to unauthorized request (401) and Blocked due to access forbidden (403). Googlebot doesn’t log in, so a page behind a login can’t be indexed. If the page should be public, this is usually a security plugin, firewall or staging password left in place. Google’s help calls a 403 to Googlebot a likely server misconfiguration.

URL blocked due to other 4xx issue. A 4xx error that doesn’t fit the other reasons. Inspect a few examples, or check them in your browser’s developer tools, to see which code the server sent.

For a symptom-first walk-through of the same problems (a page missing from Google, the wrong URL ranking), see technical SEO issues.

Two indexed statuses that still need a look

Not every warning sits in the not indexed table. The report can also flag two statuses for pages that are in the index:

  • Indexed, though blocked by robots.txt. Google indexed the URL from links but can’t read the page, so its result shows little or no description. If you want it in Google, remove the robots.txt block. If you want it out, remove the block and add noindex, because Google can’t see a noindex tag on a page it isn’t allowed to crawl.
  • Page indexed without content. The page is indexed, but Google couldn’t read its content. Google’s help mentions cloaking or a format it can’t index as possible causes, and says it isn’t a robots.txt issue. Inspect the URL and use the live test to see what Google gets.

How Validate fix works

Once every affected URL in a reason is fixed, open that reason and click Validate fix. Google then rechecks the URLs it knows have the issue, not your whole site.

step_01 Fix every URL Not just the first few in the list.
step_02 Validate fix Status moves to Started. click once only
step_03 Looking good No remaining issue found so far.
step_04 Passed or Failed Typically up to about two weeks.
fig 3 · the validation states for one reason. source: google search console help, november 2026

What Google’s help says about the process:

  • Validation typically takes up to about two weeks, sometimes longer.
  • Don’t click Validate fix again while a validation is running. Wait until it passes or fails.
  • If enough URLs still show the issue, validation fails. Fix the rest, then click Start new validation. Google rechecks only the URLs still marked pending or failed.
  • You don’t have to validate at all. Google also picks up fixes during normal crawling. Validation just asks it to check those URLs and tracks the result.
  • A reason stays in the table for 90 days after its last affected URL clears, so an empty-looking row isn’t a sign the fix didn’t work.

Don’t validate reasons from the first pile. There’s nothing to fix for “Alternate page with proper canonical tag” or a 404 you meant to create, so validating them only adds noise.

FAQ

How do I check whether one page is indexed?

Paste the full URL into the URL Inspection bar at the top of Search Console. “URL is on Google” means it’s indexed. The Page indexing report can’t filter by a single URL, so it’s the wrong tool for this.

Is it bad if more pages are not indexed than indexed?

Not on its own. Google says you shouldn’t expect every URL on a site to be indexed, and most sites have far more redirects, duplicates and parameter URLs than real pages. Switch to “All submitted pages” and judge the report by whether your important pages are indexed.

Why is my new page not in the report at all?

The report only lists URLs Google has found. A brand new page with no links to it and no sitemap entry won’t appear until Google discovers it. Add it to your sitemap, link to it from an existing page, and inspect it to request indexing.

Does requesting indexing fix "Crawled - currently not indexed"?

Not by itself. Google already crawled the page and chose not to index it, so asking again without changing the page rarely helps. Improve or merge the page first, then request indexing once.

Check the submitted pages filter every month

Once a month, open Indexing > Pages, switch to “All submitted pages” and read the reasons from the second and third piles. If your service, location and contact pages are all indexed, the rest of the not indexed count can wait. After a redesign, a plugin change or a hosting move, check it the same week, since that’s when noindex tags and server errors tend to appear.

Portrait of Liam Fraser
// written byLiam FraserSEO specialist with 3 years of experience. Liam writes about what works in local, technical and AI search.About SerpSurfers →