Google Search Console's indexing reports tell you exactly which pages on your site Google has indexed, which it has found but chosen not to index, and which it cannot even access — and buried in those reports are the hidden errors silently preventing your pages from ranking. Most website owners check Search Console occasionally and glance at the top-level numbers without understanding what the individual status categories actually mean or what action each one requires. This guide walks through every section of the Google Search Console indexing reports, explains each status in plain language, and shows you exactly what to do when you find a problem.
Understanding how to interpret these indexing reports is one of the highest-leverage technical SEO skills you can develop. A single misunderstood status — like "Crawled – currently not indexed" affecting hundreds of your blog posts — can explain months of flat organic traffic with no obvious cause.
This guide covers the full Google Search Console Page Indexing report — every status category, what it means, how to diagnose the root cause, and the specific fixes for each. You will also learn how to use the URL Inspection tool for deep per-page diagnosis and how to build a workflow for monitoring indexing health on an ongoing basis.
Where to Find the Indexing Reports in Google Search Console
Google Search Console reorganised its reporting structure in recent years. The old "Coverage" report is now called the Page Indexing report, found under Indexing → Pages in the left sidebar. There is also a Video Indexing report (under Indexing → Video pages) for sites with video content, but the Pages report is the primary one for most sites.
The Page Indexing report shows a graph of indexed vs. not-indexed pages over time, followed by a categorised breakdown of every reason Google is or is not indexing your pages. This report is the central diagnostic dashboard for indexation issues.
- Go to search.google.com/search-console and select your property
- In the left sidebar, click Indexing to expand the section
- Click Pages — this opens the Page Indexing report
- Scroll past the chart to see the full list of status categories
- Click any status category to see the specific URLs affected and filter further
- Use the URL Inspection tool (top search bar) to inspect any individual URL
The report is split into two main tabs: All known pages (every URL Google has discovered) and pages filtered by your sitemap (if you have submitted one). Start with "All known pages" for the most complete picture.
Understanding the Four Top-Level Status Categories
Every URL Google discovers about your site falls into one of four high-level status categories. Understanding the distinction between them is the foundation of reading the indexing report correctly.
Not all "Not Indexed" statuses are problems. Some — like "Excluded by 'noindex' tag" or "Duplicate, Google chose different canonical than user" — may be exactly what you intended. The skill is knowing which statuses are intentional exclusions you chose, and which are hidden errors you need to fix.
The Critical "Not Indexed" Statuses and What They Mean
The "Not Indexed" section is where most hidden errors live. Each subcategory has a different cause and a different fix. Here are the most important ones explained in plain terms.
Crawled — currently not indexed
This is one of the most alarming and misunderstood statuses. It means Google successfully crawled the page, read its content, and decided not to index it. Google does not give a specific reason — it simply judged the page not worthy of inclusion in its index.
Common causes:
- Thin content: The page has too little substantive, original content to provide value to searchers
- Duplicate or near-duplicate content: The page's content is too similar to other pages on your site or elsewhere on the web
- Low-quality content signals: The page covers a topic but does not answer the query better than existing indexed results
- No internal links pointing to it: Orphaned pages with no links from the rest of your site signal low importance to Google
- New page not yet re-evaluated: For recently published pages, this can be a temporary state before Google decides to index them
Many site owners see "Crawled — currently not indexed" and immediately click "Request Indexing" in the URL Inspection tool. This rarely helps if the underlying content quality issue is not addressed first. Google will crawl the page again and make the same decision. Fix the content first, then request re-evaluation.
Discovered — currently not indexed
Google knows this URL exists (it found it via a link or sitemap) but has not yet crawled it. This is different from "Crawled — currently not indexed" — the page has not been evaluated yet. This usually means Googlebot deprioritised it due to crawl budget constraints or server speed issues.
Fix: Improve internal linking to the affected pages so they are easier for Googlebot to discover and prioritise. Check if server response time is slow — a TTFB above 500ms on these pages may cause Googlebot to deprioritise them. Ensure these URLs are in your XML sitemap.
Duplicate without user-selected canonical
Google found multiple versions of the same content and chose one to index — but you did not specify which version should be canonical using a rel="canonical" tag. Google made its own choice, which may or may not be the version you wanted indexed.
Fix: Add an explicit <link rel="canonical"> tag to every page pointing to the correct definitive version of that content. This removes ambiguity and tells Google exactly which version to index. Use the SEOGuy SEO Analyzer to audit pages for missing or incorrect canonical tags.
Not found (404)
The URL returns a 404 response — the page does not exist. These appear in the indexing report when Googlebot tries to crawl a URL it found via a link or sitemap and receives a 404 response.
Fix: Either restore the missing page, set up a 301 redirect to the most relevant live page, or — if the URL should permanently not exist — return a 410 (Gone) response to help Google deindex it faster. Update any internal links or sitemap entries pointing to these URLs.
Server error (5xx)
The server returned a 500-level error when Googlebot tried to access the page. This means the server is running but encountered a problem processing the request — a database connection error, a PHP timeout, an out-of-memory error, or similar.
Fix: Check your server error logs for the specific error. Common causes on WordPress include resource-intensive plugins, database timeouts during high traffic, or exhausted PHP memory limits. Address the underlying server error — these are genuine technical problems, not SEO configuration issues.
Blocked by robots.txt
Googlebot tried to access this URL but your robots.txt file has a Disallow rule blocking it. If these are important pages you want indexed, this is a serious hidden error — your own robots.txt is preventing Google from reading your content.
Fix: Review your robots.txt file using the SEOGuy Robots.txt Generator and remove or narrow any Disallow rules that are blocking pages you want indexed. Always test robots.txt changes in Google Search Console's robots.txt tester before deploying.
Understanding "Excluded" Statuses — Intentional vs Unexpected
Excluded URLs are not indexed, but many of them should not be indexed — they are pages you deliberately removed from Google's index. The key is distinguishing intentional exclusions from unexpected ones.
| Excluded Status | Usually Intentional? | When to Investigate |
|---|---|---|
| Excluded by 'noindex' tag | Yes — if you added the tag | If important pages appear here unexpectedly — a plugin may have added noindex automatically |
| Duplicate, Google chose different canonical | Partially | If the canonical Google chose is wrong, you need to add explicit canonical tags |
| Redirect | Yes — if redirects are intentional | If important pages are redirecting unexpectedly — check for accidental redirect rules |
| Blocked by page-level password / login | Yes — for gated content | If public pages appear here — check for accidental authentication barriers |
| Canonical points to another page (user-declared) | Yes — if you set the canonical | If the canonical destination itself is not indexed, the whole chain is broken |
| Alternate page with proper canonical tag | Yes — expected for language/region alternates | Rarely problematic for standard sites |
The most dangerous hidden error in Excluded statuses
The status to watch most carefully is "Excluded by 'noindex' tag" when pages you want indexed appear there. This happens more often than you would expect — WordPress SEO plugins like Yoast or Rank Math have settings that can apply noindex to categories, tags, or entire page types by default. A single misconfigured toggle can quietly remove hundreds of pages from Google's index without any visible error message on the site.
Check your SEO plugin settings, especially for category pages, tag pages, author archives, and any custom post types, to confirm no noindex rules are being applied that you did not intend.
Using the URL Inspection Tool for Deep Diagnosis
The Page Indexing report shows you patterns across your whole site. The URL Inspection tool lets you diagnose any specific URL in detail — it is the microscope to the Page Indexing report's binoculars.
To use it, paste any URL into the search bar at the top of Search Console. The tool returns:
- URL is on Google / URL is not on Google: Whether this specific URL is currently indexed
- Coverage: The specific status and reason for that status (the same categories as the Page Indexing report)
- Sitemaps: Whether the URL appears in your submitted sitemaps and when
- Referring page: One example of a page on your site linking to this URL
- Last crawl: When Googlebot last visited this URL
- Crawl allowed: Whether robots.txt permits crawling
- Page fetch: Whether Googlebot could successfully download the page
- Indexing allowed: Whether the page's meta robots tag permits indexing
- User-declared canonical: The canonical URL you specified (if any)
- Google-selected canonical: The URL Google has chosen as the definitive version
Within the URL Inspection tool, click "Test Live URL" then "View Tested Page" and select "Screenshot" to see exactly what Googlebot sees when it renders your page. This reveals whether JavaScript-dependent content is rendering correctly for the crawler — one of the most common hidden indexing issues on modern sites using React, Vue, or similar frameworks.
When user-declared canonical and Google-selected canonical differ
One of the most diagnostic signals in the URL Inspection tool is when your declared canonical (what you specified) and Google's chosen canonical (what Google actually uses) are different. This means Google disagrees with your canonical — typically because it found a stronger signal pointing elsewhere, such as a higher-authority version of the page, more internal links to a different URL, or an inconsistency in your hreflang or sitemap configuration.
When you see this mismatch, investigate whether your canonical is set correctly on the page, whether your sitemap includes the correct URL, and whether internal links are consistently pointing to the canonical version rather than alternate URL variants.
Sitemap Data vs All Known Pages — What the Difference Reveals
The Page Indexing report lets you filter results by sitemap submission. Comparing the "All known pages" view against your sitemap data reveals a set of hidden problems that neither view shows on its own.
URLs in your sitemap that are not indexed
These are pages you are actively telling Google to index via your sitemap, but Google is declining to do so. This is the highest-priority gap to investigate — your sitemap is a direct request to Google, and when Google ignores it, you need to understand why.
Export this list and investigate each URL individually using the URL Inspection tool. The most common causes are: thin content Google does not think is worth indexing, canonical mismatches where Google is indexing a different version, server errors returning non-200 status codes, and accidental noindex tags.
URLs indexed that are not in your sitemap
These are pages Google has found and indexed that you did not submit — often from internal links, external links, or parameter URLs. Some of these may be fine (old posts you forgot to add to the sitemap), but others may be parameter-generated duplicate pages or internal search results you did not intend to be indexed.
Use the SEOGuy URL Extractor on key pages to pull all outbound links and identify which URLs you are linking to that are generating unexpected indexed pages. Add noindex tags to any of these pages that should not be in Google's index.
A Practical Workflow for Diagnosing and Fixing Indexing Errors
When you open the Page Indexing report and see a long list of status categories with URL counts, it can feel overwhelming. This workflow gives you a clear order of operations for working through the issues systematically.
-
1Fix all server errors (5xx) and 404 errors firstThese are technical failures — Google wants to access the page and physically cannot. They are always wrong and always need fixing. Resolve server errors at the hosting/infrastructure level. For 404s, redirect important URLs to their correct destinations and update internal links and sitemaps accordingly.
-
2Resolve unexpected "Blocked by robots.txt" issuesCross-reference which pages are blocked against which pages you actually want indexed. If important content is blocked, update your robots.txt immediately — every day an important page is blocked is a day it loses ranking potential. Use the robots.txt tester in Search Console to verify fixes before deploying.
-
3Audit unexpected "Excluded by noindex tag" URLsExport the list and check each URL to confirm whether the noindex was intentional. For any important page with an accidental noindex, find the source — it may be a meta tag in the page template, an SEO plugin setting, or a category-level noindex rule. Remove the noindex, then request re-indexing via the URL Inspection tool.
-
4Investigate "Crawled — currently not indexed" pagesFor each affected URL, use the URL Inspection tool to check the last crawl date and rendered content. Then audit the page's content quality: is it substantive, original, and more useful than existing search results? If not, improve the content before re-submitting. For pages that genuinely should not be indexed, add a noindex tag to clean up the report.
-
5Fix canonical mismatchesFor "Duplicate" statuses where Google chose a different canonical than you intended, add or correct the
rel="canonical"tag on all affected pages. Ensure internal links, sitemaps, and hreflang tags are all pointing to the same canonical URL — consistency across all signals is what convinces Google to respect your declared canonical. -
6Address "Discovered — currently not indexed" pagesImprove internal linking to these pages so they become higher crawl priorities. Add them to your XML sitemap if they are not there. Check server response time for these URLs — slow response may cause Googlebot to skip them. For critical new pages, use the URL Inspection tool's "Request Indexing" function to speed up crawling.
-
7Validate fixes and monitor over timeAfter making fixes, use the URL Inspection tool to test live URLs and confirm changes are working. Google Search Console updates its indexing data over days to weeks — check back after ten to fourteen days to see whether fixed URLs have moved to "Indexed" status. Set a monthly reminder to review the Page Indexing report for new issues.
Connecting Indexing Reports to On-Page SEO Issues
Many indexing problems are symptoms of underlying on-page SEO issues. Pages that are "Crawled — currently not indexed" often have thin meta descriptions, keyword-stuffed or missing title tags, or content that does not clearly signal its topic to Google. Fixing the indexing status alone is not enough — the on-page quality needs to improve too.
After resolving indexing issues, run every affected URL through the SEOGuy SEO Analyzer to identify on-page problems that may be contributing to Google's decision not to index the page. Pay particular attention to title tags and meta descriptions — use the SEOGuy Meta Tag Generator to craft well-optimised tags that clearly signal the page's topic and value.
For pages recovering from indexing issues, adding structured data can accelerate re-indexation and improve SERP appearance once indexed. The SEOGuy Schema Markup Generator makes it straightforward to add valid JSON-LD schema to any page type.
Audit Any URL for On-Page Issues Alongside Your Indexing Work
Fixing indexing report errors is more effective when combined with on-page SEO improvements. Use the free SEOGuy SEO Analyzer to audit any URL for missing tags, crawlability problems, and on-page issues in seconds.
Run a Free SEO AuditTools You Can Use on SEOGuy.Online
These free tools from SEOGuy.Online complement your Google Search Console indexing report work — helping you diagnose, fix, and prevent the most common indexing issues:
Key Takeaways
- The Page Indexing report (Indexing → Pages) is the central dashboard for diagnosing all indexation issues in Google Search Console
- Every URL falls into one of four categories: Indexed, Not Indexed, Excluded, or Error — each with specific subcategories
- "Crawled — currently not indexed" means Google read the page and decided not to index it — always an indicator of content quality issues, not a technical error
- "Discovered — currently not indexed" means Google knows the page exists but has not crawled it yet — fix with better internal linking and sitemap inclusion
- Server errors (5xx) and 404 errors are always genuine technical problems requiring immediate investigation and fixing
- "Blocked by robots.txt" on important pages is a critical hidden error — your own configuration is preventing Google from reading your content
- Unexpected "Excluded by noindex tag" on important pages is often caused by misconfigured SEO plugin settings applying noindex to whole page categories
- When your declared canonical and Google's chosen canonical differ, Google is unconvinced by your signal — ensure consistency across the page, sitemap, internal links, and hreflang
- The URL Inspection tool is your per-URL diagnostic tool — always check it for individual pages before drawing conclusions from the aggregate report
- Fixing indexing errors in isolation is not enough — improve content quality and on-page optimisation for pages Google has declined to index
- Check the Page Indexing report monthly and after any major site changes — new errors accumulate silently over time
Learning to interpret Google Search Console indexing reports to find hidden errors is a skill that pays continuous dividends. Every error you identify and resolve is a page that moves from invisible to potentially ranking in Google Search. Make the Page Indexing report a regular part of your SEO monitoring routine — it is one of the clearest direct communication channels Google provides about exactly what it can and cannot access on your site.