Google Search Console Indexing Statuses
On this page: Quick jump links to help you
- Understanding the Page Indexing Report
- Valid (Indexed) Statuses Explained
- Excluded Statuses and What They Mean
- Warning Statuses to Address
- Discovered vs Crawled: the two “currently not indexed” statuses
- From the Index Coverage Report to the Page Indexing Report
- Canonical and Duplicate Statuses
- Error Statuses and How to Fix Them
- Single-URL Status: “URL is not on Google”
- Prioritizing Indexing Issues
- Monitoring Indexing Health Over Time
- Advanced Indexing Troubleshooting
- Frequently asked questions
Google Search Console indexing reports provide detailed visibility into how Google is treating your pages. Rather than just knowing whether a page is indexed or not, the page indexing report categorizes each page with specific statuses that explain exactly what Google did with it and why. Understanding these indexing statuses is essential for diagnosing and fixing problems that prevent your content from ranking.
The Page Indexing Report in Google Search Console has evolved to provide more granular information than ever before. Instead of simple “indexed” or “not indexed” categories, Google now provides specific statuses like “Valid,” “Valid with warnings,” “Excluded,” and “Error.” Each status carries important information about what’s happening with your pages and what action you might need to take.
In this comprehensive guide, we’ll walk through every indexing status Google displays, explain what each one means, and show you exactly how to address problems when they appear. Whether you’re seeing unexpected exclusions, warnings you don’t understand, or errors preventing indexation, this resource will help you interpret your data and take corrective action to improve your site’s overall indexing health and SEO performance.
Understanding the Page Indexing Report
The Page Indexing Report in Google Search Console is your primary window into how Google is handling your site’s pages. This report shows you every page that Google has discovered and provides a status for each one. The report is organized by status categories that indicate whether pages are indexed and whether there are any issues you need to address.
Accessing the report is straightforward. In Google Search Console, look for “Indexing” in the left navigation menu, then select “Pages.” The report displays a breakdown of all discovered pages organized by their current status. You’ll see total counts for each status category and can drill down to see individual pages within each category.
The data in this report comes from Google’s continuous crawling of your site. When Google crawls a page, it evaluates whether the page meets the requirements for indexation and assigns it a status accordingly. As you fix issues or add new content, Google updates these statuses through subsequent crawls, so the report changes over time as your site evolves.
It’s important to note that the Page Indexing Report only shows pages that Google has discovered. If you have pages that haven’t been discovered yet, they won’t appear in any category. For completely new sites or sites with poor crawlability, the absence of pages in the report can itself be a problem worth investigating.
From the Index Coverage Report to the Page Indexing Report
If you learned Search Console a few years ago, you will have called this screen the index coverage report. Google renamed it to the Page Indexing report and reorganised the categories at the same time, which is why older tutorials describe buttons that are no longer there (documented — see Google’s Page indexing report documentation). The underlying job has not changed: it still sorts every URL Google knows about into indexed and not-indexed buckets, and tells you which rule decided the outcome.
The rename matters for two practical reasons. First, when you search for help on a status you will land on posts written against the old index coverage report, where category names such as “Valid” and “Excluded” were used differently — check the date on anything you follow. Second, exports and third-party dashboards built before the change may still label their columns with the old names, so a status that looks unfamiliar in a report may simply be an old label for a state you already understand.
Whichever name your tooling uses, the Google Search Console indexing statuses themselves are the stable part. Learn what each status asserts about a URL and you can read any version of the report, including whatever Google calls it next.
Valid (Indexed) Statuses Explained
When a page shows a “Valid” status, it means Google has successfully indexed the page and found no significant issues preventing it from ranking. Pages with valid statuses are the backbone of your organic traffic potential.
Valid Status
This is the best-case scenario. A page with "Valid" status has been crawled by Google, meets all technical requirements for indexation, contains no detected errors, and is now in Google’s index. These pages are eligible to rank in search results for relevant queries. Your goal should be to get as many of your important pages into this status as possible. Valid pages require no action—they’re working as intended.
Valid with Warnings Status
A page marked as "Valid with warnings" is indexed and can rank, but Google detected one or more issues that could potentially affect its performance. Common warnings include missing meta descriptions, very short page content, or crawlability issues that don’t completely prevent indexation but could improve.
Pages with warnings aren’t in danger of losing their indexed status, but addressing the warnings can improve their performance. Review the specific warnings Google reports for each page and prioritize fixing them based on severity. A missing meta description is a quick fix that could improve click-through rates in search results, while thin content warnings might require significant content additions.
Excluded Statuses and What They Mean
Excluded pages are discovered by Google but deliberately not indexed. Understanding why pages are excluded helps you determine whether the exclusion is intentional or a problem to fix:
| Exclusion Status | Meaning | Action Required |
|---|---|---|
| Excluded by ‘noindex’ tag | The page has a meta noindex tag or X-Robots-Tag header preventing indexation. This is intentional blocking by the page owner. | Remove the noindex tag if you want the page indexed. If you want to keep it excluded, no action is needed. |
| Excluded by robots.txt | The page’s URL matches a rule in your robots.txt file that blocks Google from crawling it. Google discovered the page through a link but respects the crawl block. | Remove the blocking rule from robots.txt if you want Google to crawl and index the page. Test changes in Search Console before deploying. |
| Excluded by canonical tag | The page has a canonical tag pointing to a different URL, indicating that another version is the preferred version for indexation. | If this page should be indexed, update the canonical to point to itself or remove it. If another version should be indexed instead, keep the canonical pointing there. |
| Excluded by parameter handling | Google is treating this page as a duplicate parameter variation of another page based on URL parameter configuration in Search Console. | Review your parameter handling settings in Search Console. Adjust if the parameter handling classification is incorrect. |
| Excluded as duplicate | Google has determined this page is substantially similar to another page and chose to index the other version instead to avoid duplicate content. | Consolidate duplicate pages through internal linking strategy or redirects. Use canonical tags to designate preferred versions. |
| Excluded by pagination | The page is part of a paginated series and Google has chosen not to index it to avoid thin content issues. | Ensure your pagination markup is correct. Consider consolidating thin paginated pages into single comprehensive pages or infinite scroll. |
| Excluded as soft 404 | Google found the page returns a successful status code but contains little to no actual content, resembling a 404 error page. | Add substantial, meaningful content to the page. If the page shouldn’t exist, implement a proper 404 response code instead. |
| Excluded based on user agent | This status appears rarely and indicates Google-bot is being treated differently than regular user agents by your server. | Ensure your server doesn’t differentiate between Google’s crawlers and regular users. Fix any user-agent-based blocking or cloaking. |
Canonical and Duplicate Statuses
One group of Google Search Console indexing statuses catches people out more than any other: the ones that say the page was crawled, understood, and then set aside because Google decided a different URL was the better copy. Nothing is broken in these cases, which is exactly why they get ignored for months.
The most common of the group is alternate page with proper canonical tag. It means Google followed the canonical you declared, agreed with it, and indexed the target instead. Seeing alternate page with proper canonical tag on a paginated URL, a filtered listing, or a tracking-parameter variant is the system working as designed. Seeing it on a page you actively want ranking is the signal to check: the canonical is probably pointing at a template default, or at the wrong member of a near-duplicate pair.
Its sibling status — where Google picked a canonical you did not declare — is the one to treat as a warning rather than a confirmation, because there the algorithm overrode your intent. Both are decided by the same markup, so both are fixed in the same place: our guide to canonical tag best practices covers how to declare one cleanly and how to spot a template applying it too widely.
Warning Statuses to Address
Warning statuses indicate that your page is indexed but Google found issues that could impact its performance or user experience. These warnings don’t prevent indexation, but addressing them should be a priority:
Indexed but Not Serving HTML
This warning appears when Google can’t retrieve the actual HTML content of your page properly. The page might require JavaScript to render, might return an error under certain conditions, or might have network connectivity issues during crawling. Google is indexing based on what it could access, but it might not have the complete picture of your page’s content.
Fix this by ensuring your pages load properly as HTML without requiring heavy JavaScript to display core content. Use technical SEO best practices to ensure pages are accessible to crawlers in all scenarios.
Indexed, Though Blocked by robots.txt
Google found this page indexed, but it’s also blocked by your robots.txt file. This typically happens when the page was indexed before the robots.txt rule was added, or when Google has other ways of discovering the page content (through links from other indexed pages). The situation creates confusion about whether the page should be accessible or not.
Decide whether you want the page indexed. If yes, remove the robots.txt rule. If no, use a noindex tag instead of robots.txt, which is clearer and prevents Google from wasting crawl budget on the page.
Worth being precise about what indexed though blocked by robots.txt actually reports: the block stopped Google reading the page, not indexing the URL. Google can still list the address on the strength of links pointing at it, which is why the result is an entry with no useful snippet. If the page must stay out of the index, a crawl block alone will not achieve it — Google has to be able to fetch the page to see the noindex directive telling it to stay away. Unblock it in robots.txt, let the noindex be read, then re-block later if you still want to save the crawl.
Crawled – Currently Not Indexed
Search Console labels this status “Crawled – currently not indexed”, and it is the one site owners ask about most. A page marked crawled currently not indexed has been fetched by Googlebot but has not been added to the index. The page might be new, or Google might be evaluating whether it meets quality standards. For new pages, this is temporary. For older pages showing this status, the page might have quality issues preventing full indexation.
If the page is new, wait a week or two and check again. If it remains in this status long-term, review on-page SEO quality, content depth, and keyword relevance. Request indexing through Google Search Console to accelerate the process.
Discovered vs Crawled: The Two “Currently Not Indexed” Statuses
Two entries in the Page Indexing report account for the majority of confusion, and they are easy to mix up because their names are nearly identical. Both sit in the “Not indexed” group, both mean the page is missing from search results, and both are fixed in completely different ways. Of all the Google Search Console indexing statuses, these are the two worth learning properly.
Discovered – Currently Not Indexed
A page marked discovered currently not indexed is one Google knows exists — usually from an internal link or your sitemap — but has not actually fetched yet. Googlebot has queued the URL and has not got to it. Nothing is technically broken on the page, because Google has not read the page.
This status is almost always a crawl-budget or site-quality signal rather than a page-level defect. Google throttles crawling on sites where previous crawls returned thin, duplicated, or slow-loading pages, so the queue backs up. Fixing it means making the site as a whole more worth crawling: strengthen internal links to the affected URLs so they are not buried, remove or consolidate low-value pages competing for the same crawl allowance, improve server response times, and keep your sitemap limited to canonical URLs that genuinely deserve indexing.
How the two statuses differ in practice
The distinction is simply how far Google got. Discovered means Google has not fetched the page; crawled means Google fetched it and declined to index it. That single difference redirects the entire fix:
| Status | What Google did | Where the problem usually is | First thing to fix |
|---|---|---|---|
| Discovered – currently not indexed | Found the URL, has not fetched it | Site level: crawl budget, internal linking, server speed | Link to the page from stronger pages and cut low-value URLs competing for crawl |
| Crawled – currently not indexed | Fetched the page, chose not to index it | Page level: content quality, duplication, thin coverage | Deepen the page so it says something the indexed alternatives do not |
Reading the two statuses the wrong way round wastes weeks. Rewriting a page that Google has never fetched changes nothing, because the new content is sitting behind the same crawl queue as the old content. Equally, requesting indexing over and over for a page that Google fetched and rejected does not address the reason it was rejected. Check which of the two statuses applies before choosing a fix.
Error Statuses and How to Fix Them
Error statuses indicate that Google encountered problems while trying to crawl or process your pages. These require investigation and correction:
| Error Status | Meaning | How to Fix |
|---|---|---|
| Couldn’t retrieve | Google attempted to crawl the page but couldn’t access it due to server errors, connectivity issues, or timeouts. The page might be temporarily down or returning 5xx errors. | Check your server logs to see what errors Google encountered. Fix the underlying server issue. Ensure your site is stable and responsive. Test the page in Google Search Console to confirm it’s now accessible. |
| Redirect error | The page has a redirect that loops, breaks, or goes to an inaccessible location. Redirect chains, redirect loops, or redirects to error pages create this status. | Review and fix your redirects. Ensure each redirect goes directly to a valid destination without creating chains. Test redirects in your browser and through Google’s testing tools. |
| Blocked by robots.txt | Google wants to crawl this page for indexing but can’t because robots.txt blocks it. This is an error status because Google is prevented from doing what it needs to do. | Remove the blocking rule from robots.txt. Alternatively, use noindex tags instead if you don’t want Google to crawl but want Google to know the page exists. |
| URL seems to be out of scope | Google determined this URL doesn’t belong to your primary domain and is therefore out of scope for your site’s indexing. | Verify the URL is actually part of your site. If it’s a subdomain you want indexed, ensure it’s properly configured in Google Search Console as a separate property or verified as part of your main domain. |
| Not found (404) | The page returns a 404 status code, indicating it doesn’t exist or has been deleted. Google can’t index pages that return 404 errors. | If the page should exist, fix whatever caused it to return 404. If the page was intentionally deleted, no action is needed—Google will eventually update its index. Implement proper redirects for deleted pages to preserve equity. |
Single-URL Status: What “URL is not on Google” Means
The Page Indexing report answers questions at site level. When you need the verdict on one specific address, the URL Inspection view answers at page level — and the line it returns first is either “URL is on Google” or “URL is not on Google”.
URL is not on Google is a summary, not a diagnosis. It tells you the page is absent from the index; the reason sits underneath it, in the same vocabulary the site-level report uses — excluded by a noindex tag, blocked from crawling, treated as a duplicate, or crawled and passed over. Read the detail line before acting, because the fixes point in opposite directions: one asks you to remove a directive, another asks you to improve the page.
Two habits make this view worth the trip. Run the live test to confirm the current state of the page rather than the state at the last crawl, and check the user-declared versus Google-selected canonical rows, which explain most surprising verdicts. Between the two views you can always place any of the Google Search Console indexing statuses on a real URL rather than on a count in a chart.
Prioritizing Indexing Issues
With potentially hundreds of indexing issues to address, prioritization is critical. Not all issues have equal impact on your organic performance:
Focus on Important Pages First
Prioritize fixing issues on your most important pages—those that drive the most traffic, lead to conversions, or represent core offerings. A homepage with a crawl error is more urgent to fix than a blog post from two years ago that receives minimal traffic.
Address Critical Errors Over Warnings
Error statuses preventing indexation should be addressed before warnings on already-indexed pages. A page that can’t be crawled is more critical than a valid page missing a meta description.
Batch Similar Issues
If multiple pages have the same problem (like all being excluded by robots.txt), fix the root cause once (update robots.txt) rather than addressing each page individually. Similarly, if numerous pages lack adequate content, implement a content strategy rather than editing pages one by one.
Calculate Impact vs. Effort
Consider both how many pages have an issue and how difficult it is to fix. An issue affecting 100 pages takes priority over an issue affecting one page, even if the single page is more important, because the ROI of the fix is higher.
Monitor Trends
Watch whether issues are growing, stable, or shrinking. A growing number of excluded pages indicates a systematic problem that needs immediate attention. Stable issues that have existed for months might be lower priority than emerging problems.
Monitoring Indexing Health Over Time
Effective SEO requires ongoing monitoring, not just one-time fixes. Establish a monitoring routine for your site’s indexing health:
Set Up Weekly Reviews
Dedicate time weekly to check the Page Indexing Report. Look for changes in numbers—newly indexed pages, newly excluded pages, or pages moving between statuses. Investigate any significant changes.
Create a Baseline
Record your current indexing metrics as a baseline. Track total indexed pages, pages excluded by noindex, pages with errors, and pages with warnings. Monitor whether these numbers improve or deteriorate over time as you make changes.
Set Alerts for Major Changes
Use Google Search Console’s notification system or third-party monitoring tools to alert you to significant drops in indexed pages, sudden increases in crawl errors, or new manual actions. Quick notification enables faster response to problems.
Correlate with Traffic Changes
When you notice changes in your organic traffic, check the Page Indexing Report to see if there were corresponding indexing changes. This helps you understand the relationship between indexing status and SEO performance.
Document Changes and Actions
Keep records of what you’ve changed and how it affected your indexing metrics. Over time, you’ll build knowledge about what actions most effectively improve your indexing health and should be prioritized in future efforts.
Advanced Indexing Troubleshooting
For persistent indexing problems that don’t resolve through standard fixes, consider these advanced troubleshooting approaches:
Use the URL Inspection Tool
For individual pages with persistent issues, use Google Search Console’s URL inspection tool. This shows the most recent crawl data for that specific page, including what content Google could access and any specific errors encountered. This granular information often reveals issues that the general report doesn’t show.
Review Crawlability with Third-Party Audits
Tools like Screaming Frog SEO Spider can crawl your site exactly as Google does, revealing crawlability issues before Google encounters them. Running regular crawls helps you catch and fix problems before they affect your indexing status.
Analyze Server Logs
Review your server logs to see exactly what status codes and responses Google’s crawlers receive. Sometimes server-side issues (like dynamic content problems or authentication issues) only show up in logs, not in high-level reports.
Test Dynamically Rendered Pages
If your site uses JavaScript for content rendering, use Google’s Mobile-Friendly Test or the URL inspection tool to see how Google renders your pages after executing JavaScript. Sometimes content only appears after JavaScript runs, and indexing problems stem from rendering issues.
Check for Soft 404 Patterns
If many pages are marked as soft 404s, examine them for common patterns. Maybe they’re parameter-heavy pages, paginated content, or pages with minimal unique content. Addressing the pattern (like through on-page optimization or page consolidation) is more efficient than fixing individual pages.
Evaluate Site-Wide Technical Changes
If indexing status suddenly changed across many pages, review your recent technical changes. Did you update robots.txt? Add noindex tags? Change your sitemap? Update your server configuration? A recent change often explains widespread indexing problems.
Request a Re-Crawl for Strategic Pages
Beyond using the standard “Request Indexing” button, you can signal importance by getting fresh internal links to pages you want indexed, updating their content to show freshness signals, and including them prominently in your XML sitemap. These signals accelerate re-crawling and indexing decisions.
Your Page Indexing Report in Google Search Console is one of the most valuable tools in your SEO toolkit. By understanding each status category, monitoring your indexing health regularly, and taking action to address issues, you ensure that your content gets discovered, indexed, and positioned to rank. The better your indexing status, the more traffic potential your site has, making this foundational work essential for long-term SEO success.
Google Search Console Indexing Statuses: Frequently Asked Questions
What does crawled currently not indexed mean in Search Console?
It means Googlebot fetched the page but decided not to add it to the index. The page is reachable and technically crawlable; Google simply judged it not worth indexing at that moment. On genuinely new pages this often clears on its own within a week or two. When it persists, treat it as a content-quality verdict: the page needs to cover something the already-indexed results do not, rather than restating them.
What does discovered currently not indexed mean in Search Console?
It means Google knows the URL exists but has not fetched it yet, so no quality judgement has been made at all. This is normally a crawl-budget signal at site level rather than a fault with the individual page. Strengthen internal links pointing at the URL, trim low-value pages competing for the same crawl allowance, and improve server response time.
How many indexing statuses does Google Search Console have?
The Page Indexing report groups every known URL under one of roughly seventeen states, spread across indexed, not indexed, intentionally excluded, duplicate and canonical, and technical error categories. Google adjusts the exact list over time, so treat the category a status sits in — indexed, excluded, warning, or error — as more stable than the count itself.
Is excluded by noindex bad for SEO?
Not by itself. Excluded by noindex simply reports that the page carries a meta robots noindex directive or an X-Robots-Tag header, which is the correct state for thank-you pages, filtered listings, internal search results, and staging URLs. It is only a problem when a page you want ranking appears in that list, which usually points to a template applying the tag more widely than intended.
How long does Google Search Console take to update indexing status?
Status changes follow Google's next crawl of the URL rather than your fix, so the report typically lags by a few days to a few weeks. The Page Indexing report itself also reports on a delay. Use the URL Inspection tool's live test to confirm the fix is in place immediately, then wait for the report to catch up rather than re-requesting indexing repeatedly.
How to fix crawled currently not indexed pages?
There is no switch for it, because the status is a judgement rather than an error. Work in this order: confirm the page is genuinely reachable and canonical to itself; then ask whether it adds anything the already-indexed results for that query do not — original data, a worked example, a real answer to the exact question. Strengthen internal links pointing at it from pages Google already indexes, since an orphan page rarely earns a second look. Request indexing once, then leave it: repeated requests do not raise priority.
Why is my page not indexed?
In almost every case the report already says why, and the answer falls into one of four groups: you asked Google to stay away (noindex or a robots.txt block), the page is treated as a duplicate of another URL, the crawl failed for a technical reason such as a server error or redirect, or the page was crawled and judged not worth indexing. Find the URL in the Page Indexing report or run URL Inspection on it, then match the status to the group — the first three are configuration fixes, and only the fourth is a content problem. Reading the Google Search Console indexing statuses this way turns a vague worry into one of four concrete jobs.
See where your site stands. The free AI-powered SEO audit is your first telemetry read.
Request your free auditSEO pricing calculatorBook a strategy call
Keep exploring this topic
This answer is part of the SEO FAQ.