Search Console Index Coverage: Understanding Errors
Quick answer
Google Search Console's index coverage report lists the status of every URL on your site: indexed, excluded, or in error. To fix indexing errors, first identify their type (server error, redirect, noindex, blocked crawl), then handle each category. These issues can prevent your pages from appearing in search results.
You publish content regularly, yet some pages never show up in Google? The problem often hides in Google Search Console's index coverage report. This free tool tells you exactly why a page is indexed or not — but its technical vocabulary discourages many WordPress publishers. Server error 5xx, URL with a noindex tag, page discovered but not indexed: each status tells a different story, and each calls for a specific fix. In this hands-on guide, we break down the report step by step, from simplest to most complex. You'll learn to tell a normal exclusion from a real error that needs priority attention. We'll also see how a tool like Selfhook can automatically monitor this report and alert you when an important URL drops out of the index, without you having to open Search Console every morning.
Definition
Index coverage is the Google Search Console report that shows, for each URL on a site, whether it is indexed by Google, intentionally excluded, or blocked by an error preventing it from appearing in search results.
What is the index coverage report?
The index coverage report (called "Pages" in the current version of Google Search Console) sorts every URL known to Google into two main families: "indexed" pages and "not indexed" pages. An indexed page is stored in Google's database and can potentially appear in search results. A non-indexed page cannot, for a reason that is always specified. To understand this report, you need to distinguish two concepts. Crawling is the moment Google's robot, Googlebot, visits a URL. Indexing is the next step: Google decides to store the page and make it eligible for search results. A page can be crawled without being indexed, and that's often where confusion begins. The report groups non-indexed URLs by reason. Some reasons are perfectly normal: a page with an intentional noindex tag, a duplicate URL managed by a canonical tag, or a redirect are healthy exclusions. Other reasons are genuine errors requiring a fix. The first task is therefore to learn to read these categories to separate noise from signal. A 500-page site can perfectly well have 200 "not indexed" URLs without any SEO problem, if those exclusions are intentional.
- Indexed: the page is in Google's index and can rank
- Not indexed (normal exclusion): noindex, canonical, intentional redirect
- Not indexed (error): technical issue to fix as a priority
- Crawling: Googlebot visits the URL
- Indexing: Google decides to store the page
What are the most common indexing errors?
In Google Search Console, each non-indexing reason has a precise name. Understanding them lets you act methodically rather than fixing at random. Here are the most common statuses WordPress publishers encounter. "Server error (5xx)" signals that Googlebot received an error response from your host at the time of the visit. It's usually temporary, but if it persists, your server or a plugin is causing a problem. "Not found (404)" indicates a deleted page or a broken link — to check and redirect if the page had value. "Crawled, currently not indexed" is one of the most frustrating statuses: Google saw the page but chose not to index it, often due to perceived quality or relevance. "Discovered, currently not indexed" means Google knows the URL but hasn't crawled it yet, frequently due to crawl budget limits. "Alternate page with proper canonical tag" and "Duplicate, submitted URL not selected as canonical" concern duplicate content, where Google preferred to index another version. Finally, "Blocked by robots.txt" and "Excluded by noindex tag" are exclusions you — in principle — requested yourself. If an important page is there by accident, it's a configuration error to fix quickly, as it completely prevents indexing.
- Server error (5xx): error response from the host
- Not found (404): deleted page or broken link
- Crawled, currently not indexed: perceived quality issue
- Discovered, currently not indexed: limited crawl budget
- Blocked by robots.txt or noindex tag: technical exclusion
How do you fix index coverage errors?
Fixing indexing errors follows a simple logic: identify the reason, understand the cause, apply the right fix, then request revalidation from Google. Always start with errors affecting strategic pages (product pages, pillar articles, service pages), as these are the ones that weigh on your traffic. For a persistent 5xx error, contact your host or check that a WordPress plugin isn't overloading the server. For a 404 on a page that had value, set up a 301 redirect to the closest equivalent. For a page "blocked by noindex" that you wanted indexed, remove the noindex tag: in WordPress, a plugin like Yoast or RankMath lets you control this directive page by page. The "Crawled, currently not indexed" case requires more editorial work: strengthen the content, add relevant internal links from already well-indexed pages, and make sure the page provides genuine adapté value. For "Discovered, currently not indexed," improve your internal linking and submit an up-to-date sitemap to help Google prioritize crawling. Once the fix is applied, use the "Validate fix" button in the report, or the URL inspection tool to request reindexing. Google may take several days to revisit the page. Then measure progress directly in Search Console to confirm the status changes to "indexed." To automate this monitoring, see our guide on Google indexing monitoring.
- Prioritize errors affecting your strategic pages
- Remove accidental noindex tags via Yoast or RankMath
- Set 301 redirects for 404s with SEO value
- Strengthen content and internal linking for non-indexed pages
- Click "Validate fix" then measure in Search Console
With Selfhook, you no longer need to manually open the coverage report every morning. Selfhook continuously monitors your Google Search Console indexing report and automatically detects when an important URL moves from "indexed" to "excluded" or "error." As soon as a strategic page drops out of the index, you receive an immediate notification, which can considerably reduce your reaction time. Combined with its automated SEO audit, Selfhook also identifies likely causes — accidental noindex tag, robots.txt block, content judged thin — and points you toward the fix. You keep control of your indexing without daily manual monitoring.
Selfhook centralizes content generation, SEO/GEO optimization, WordPress publishing and tracking in a single workflow.
See all features →FAQ
How long does Google take to reindex a fixed page?
After clicking "Validate fix" or requesting a URL inspection, Google may take from a few hours to several weeks. The delay depends on your site's crawl frequency and the page's perceived importance. Measure progress directly in Search Console.
Are all non-indexed pages a problem?
No. Many exclusions are normal and healthy: pages with intentional noindex, duplicate URLs managed by canonical, or redirects. Only errors affecting pages you want to rank require a fix.
What does "Crawled, currently not indexed" mean?
Google visited the page but decided not to index it, often due to perceived quality or relevance. Strengthening content and internal linking can, in some cases, contribute to its indexing.
Is the coverage report 100% reliable?
Google Search Console data may show a slight time lag, usually of a few days. The report nonetheless remains the most reliable source for tracking the real state of your indexing.
Operational checklist
Normal exclusion vs error to fix
| Status | Nature | Recommended action |
|---|---|---|
| Excluded by noindex (intended) | Normal | None, verify intent |
| Crawled, not indexed | Potential error | Strengthen content and linking |
| Server error (5xx) | Technical error | Check host or plugin |
| Not found (404) | Possible error | Redirect if page has value |
| Blocked by robots.txt (accidental) | Config error | Unblock the URL quickly |
Common mistakes
Confusing normal exclusion with error
Trying to index every non-indexed page wastes time, since many exclusions are intentional and healthy.
Ignoring excluded strategic pages
Leaving a product or pillar page "not indexed" deprives your site of potentially significant traffic.
Requesting reindexing without fixing the cause
Validating a fix without actually solving the problem leaves the page in the same state after the next crawl.
Leaving a default noindex tag on WordPress
A misconfigured setting in Yoast or RankMath can block indexing of entire categories or archives without you realizing it.
Related cluster articles
Automate with Selfhook
Conclusion
Google Search Console's index coverage report is your most valuable dashboard for understanding why your pages appear — or don't — in search results. The key is to distinguish normal exclusions from genuine errors, then fix the latter in order of strategic priority. This monitoring requires consistency, as a page can drop out of the index at any time. That's where automated surveillance makes the difference: Selfhook monitors your coverage continuously and alerts you the moment an important URL switches to error, for a fast reaction and an index you always control.
Ready to automate your SEO content?
Book a 30-minute video demo: we show you Selfhook on your WordPress site, from SEO audit to publishing.
Request a demo