TutorialPractitioner8 min read

Search Console Page Indexing Report: Statuses, Fixes and Priorities

Read the Search Console Page indexing report as a marketer: what each status means, which to fix first, and how to validate fixes.

Dipuck Jones
Written by Founder of MentionX · 13+ years in B2B SaaS growth and SEO
Reviewed
Short answer

The Page indexing report shows which of your URLs Google has indexed and, for those it hasn't, why. For marketers, the job isn't to get every URL indexed. It's to make sure the pages that matter are, and to spot problems after releases.

Key takeaways
  • Indexed pages are the only ones that can appear in Search, AI Overviews or AI Mode.
  • Not every URL should be indexed. Focus on the pages that matter.
  • "Crawled - currently not indexed" is common and not always an issue.
  • Filter the report by a sitemap of key pages to see what's indexed among the URLs you care about.
  • Validate fixes so Google rechecks affected pages.

Checked 4 November 2026 (CET) against Search Console Help and Google Search Central documentation. Search Console reports and rollouts change often, and some features only appear for eligible properties, so confirm in your own property. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.

01What does the report show?

From Google's Page indexing report help:

  • A chart of indexed and not indexed pages over time.
  • Why pages aren't indexed: reasons with page counts, each with up to 1,000 example URLs.
  • Improve page experience: indexed pages with issues worth fixing.
  • A filter at the top for All known pages, All submitted pages or a specific sitemap.

Google suggests validating against a sitemap containing only your key pages; that's the pro tip most teams miss.

02How should marketers prioritise?

PrioritySituationWho fixes
1Key pages blocked by noindex or robots.txtDeveloper, same day
2Server errors or redirect errors on key pagesDeveloper
3Google chose a different canonical for a key pageSEO + developer
4Key pages in Crawled or Discovered - not indexed for weeksSEO + content: improve quality, internal links
5Soft 404s on real contentContent
IgnoreAlternate pages, intended redirects, parameter duplicates-

03How does indexing relate to AI answers?

AI Overviews and AI Mode use pages from Google's index. A page that isn't indexed can't be a source. See How websites get crawled and indexed and Canonicals and duplicates in AI answers.

Our view: "not indexed" totals are noisy on most sites. A filtered view of your key pages is a much better weekly metric than the site-wide count.

04Which statuses matter?

StatusUsually meansAct when
Crawled - currently not indexedGoogle crawled it and chose not to index for nowIt's an important page
Discovered - currently not indexedFound but crawl was rescheduled to avoid overloading the siteMany important pages sit here for weeks
Duplicate without user-selected canonicalGoogle sees duplicates and picked a canonicalThe chosen canonical is wrong
Duplicate, Google chose different canonical than userYour canonical tag was overriddenThe page you wanted indexed isn't
Alternate page with proper canonical tagWorking as intendedRarely
Excluded by 'noindex' tagYou told Google not to indexThe page should be indexed
Blocked by robots.txtCrawling blockedThe page should be crawled
Not found (404)Page is goneIt's linked internally or should exist
Soft 404Page looks empty or like an errorIt has real content
Server error (5xx)Server failedAlways investigate
Redirect errorChain, loop or bad URLAlways fix
Page with redirectWorking redirectRarely

05Troubleshooting a drop in indexed pages

  1. Check whether the drop matches a release, migration or CMS change. Annotate it.
  2. Open the reason with the biggest increase and inspect five example URLs.
  3. Use URL Inspection's live test on one example (lesson 11).
  4. If it's noindex or robots.txt, check templates and robots.txt history.
  5. If it's duplicates, check canonical tags and parameters.
  6. Fix, then click Validate fix. Validation can take days or weeks.

06A triage method for large sites

On sites with thousands of URLs, the reasons list can look alarming. Triage like this:

  1. Filter to your key-pages sitemap. Fix anything wrong here first.
  2. Filter to each content-type sitemap (lesson 10). Note which type has the highest share of non-indexed URLs.
  3. For each reason with a rising trend, open the example URLs and classify a sample of 20: intended (fine), accidental (fix), or low value (improve or remove).
  4. Group fixes by template. One template fix usually resolves hundreds of URLs.
  5. Validate once per template fix, not once per URL.

07Fixes by reason, with the marketer's role

ReasonDeveloper fixMarketer or content fix
Crawled - currently not indexedCheck rendering and duplicatesImprove depth, merge thin pages, add internal links
Discovered - currently not indexedImprove server capacity and response timeReduce low-value URLs; link key pages from hubs
Duplicate, Google chose different canonicalConsistent canonicals, redirectsStop linking to duplicate versions in campaigns
Soft 404Return real 404s for empty pagesAdd content to thin category pages or remove them
Excluded by noindexRemove accidental noindexConfirm which pages should be noindexed
Blocked by robots.txtUpdate rulesConfirm with SEO which sections should be crawled

08Edge cases

  • Parameter URLs from campaigns. UTM-tagged URLs linked from your own site can create duplicates. Use UTMs only on external links.
  • Faceted navigation. Filter combinations can create huge numbers of crawled-not-indexed URLs. That's often fine; the fix is to limit crawling of them, not to get them indexed.
  • Validation "failed". It means at least one example still has the issue. Open the validation details and check a few remaining URLs.
  • Big jumps after a migration. Old URLs move into "Page with redirect" and new ones into Indexed over weeks. Annotate the migration and compare key pages only.

09Questions practitioners ask

How long should a key page stay unindexed before I worry? If a key page is linked from your navigation and sitemap and still isn't indexed after a few weeks, inspect it and look at quality and duplication.

Does Request indexing fix "Crawled - currently not indexed"? Rarely on its own. Improve the page or consolidate it, then request indexing.

Should I noindex thin pages? If they serve users (for example, account pages), noindex is fine. If they're thin content, improving or merging is usually better.

10A weekly five-minute check

Open Page indexing, filter to your key-pages sitemap, and compare the Not indexed count with last week. If it rose, open the reason that grew and inspect two example URLs before doing anything else.

11Where this fits in the monthly routine

In week 2, check key-page indexing and record the count of key pages not indexed. Anything above zero gets an owner and a ticket.

12Quick checks before you move on

  • You can name the top three Not indexed reasons for key pages.
  • Every key page that is not indexed has an owner and a next step.

13Worked example: Ledgerline's release check

Ledgerline is a fictional accounts-payable software company. Details and numbers are illustrative.

A week after Ledgerline's new site template went live, Page indexing filtered to the key-pages sitemap showed four product pages under "Excluded by 'noindex' tag". URL Inspection confirmed a staging noindex tag left in the template. The developer removed it the same day; the SEO lead clicked Validate fix and annotated the release date. All four were indexed again within the validation period.

Walkthrough

  1. Open Indexing > Pages.
  2. Read the indexed vs not indexed chart for the last 3 months.
  3. In Why pages aren't indexed, open the reason with the most pages.
  4. Read the example URLs. Note whether they are pages you care about.
  5. Use the sitemap filter at the top to show only URLs in your key sitemap.
  6. Inspect one URL with URL Inspection.
  7. After fixing, return to the reason and click Validate fix.

14Try it yourself

Create a key-pages sitemap (or list) of your 50 most important URLs. In Page indexing, filter to it and record how many are indexed. Investigate every key URL that isn't, and write down the reason and fix.

15Quick quiz

1. Is Crawled - currently not indexed always a problem?

Answer: No. It's common and not necessarily an issue.

2. What does Discovered - currently not indexed mean?

Answer: Google found the URL but rescheduled crawling, often to avoid overloading the site.

3. How many example URLs does the report show per reason?

Answer: Up to 1,000.

4. What does Validate fix do?

Answer: Asks Google to recheck the affected URLs and tracks progress.

16What should you check before the next lesson?

  • You know the indexed status of your 50 key pages.
  • You checked the top not-indexed reason.
  • You know who fixes each issue type.
  • You have a key-pages sitemap or list to filter by.

Next: Sitemaps report. Or return to the Search Console for Marketers track.

17Common questions

Should every page be indexed? No. Duplicates, filtered URLs and thin utility pages are often better left out.

Why are some sitemap URLs not indexed? Submitting a sitemap is a hint, not a guarantee. Google still decides what to index.

Does the indexing report cover AI features? Indexing is a prerequisite for appearing in AI Overviews and AI Mode, but the report doesn't show AI feature status.

Questions people ask

3 answers

Should every page be indexed?

No. Duplicates, filtered URLs and thin utility pages are often better left out.

Why are some sitemap URLs not indexed?

Submitting a sitemap is a hint, not a guarantee. Google still decides what to index.

Does the indexing report cover AI features?

Indexing is a prerequisite for appearing in AI Overviews and AI Mode, but the report doesn't show AI feature status.

Sources

  1. Search Console Help, Page indexing reportsupport.google.com
  2. Search Console Help, URL Inspection toolsupport.google.com
  3. Search Console Help, Sitemaps reportsupport.google.com
  4. All accessed 4 Nov 2026.
Written and reviewed by Dipuck JonesHow we research and testReport an error