Google Search Console Indexing Issues: Complete Fix Guide (2026)

Every indexing status in Google Search Console explained — what it means, why it happens, and exactly how to fix it. This guide covers every Valid, Warning, and Error status you'll encounter in the Pages report.

Overview

Google Search Console's Pages report (formerly "Coverage report") categorizes every URL Google has discovered on your site into one of several statuses. Understanding these statuses is critical because they directly tell you which pages are showing up in search results and which aren't — and why.

The statuses are grouped into three categories:

  • Valid — Pages that are successfully indexed and appearing in search results.
  • Warning — Pages that are indexed but have issues that may affect their performance or future indexing.
  • Error — Pages that are NOT indexed due to specific problems that need attention.
  • Excluded — Pages that Google intentionally chose not to index (often correct behavior).

Valid Statuses

Valid statuses mean the page is indexed. These are good — but you should still understand the nuances.

Indexed, submitted in sitemap

This is the ideal state. Google found the URL in your sitemap, crawled it, and indexed it. The page is eligible to appear in search results.

Action needed: None. Just make sure the content stays quality and the page remains accessible.

Indexed, not submitted in sitemap

Google found and indexed this page through links or other discovery methods — but it's not in your sitemap. This is fine for small sites but can indicate sitemap gaps on larger sites.

Action needed: Add the URL to your sitemap to help Google discover and prioritize it more efficiently.

Warning Statuses

Indexed, though blocked by robots.txt

Google indexed this page despite it being blocked in robots.txt. This usually happens because other sites link to it, so Google crawls it via those external links. The content may appear as a snippet without full rendering.

Fix: If the page should be indexed, remove the robots.txt block. If it should not be indexed, use a noindex meta tag or HTTP header instead — robots.txt is not a reliable way to prevent indexing.

Indexed, low traffic

A newer status in 2025/2026 GSC. The page is indexed but Google has detected it receives very little organic traffic. This may indicate thin content, poor keyword targeting, or low search demand.

Fix: Review the content quality and keyword targeting. Consider consolidating low-traffic pages into more comprehensive resources, or improving the content to better serve user intent.

Error Statuses

Error statuses mean Google tried to index the page but couldn't. These need your attention.

Server error (5xx)

Your server returned a 500-level error when Googlebot tried to access the page. This could be due to server overload, misconfiguration, or application crashes.

Fix:Check your server logs for 5xx errors during Googlebot visits. Increase server capacity, fix application bugs, and implement proper error monitoring. Use the "Validate Fix" button in GSC after resolving.

Redirect error

A redirect chain is too long (exceeds 5 hops), contains a loop, or points to a URL that returns an error.

Fix: Audit your redirect chains. Each redirect should point directly to the final destination. Eliminate intermediate hops and ensure the final URL returns a 200 status.

Blocked by robots.txt

Google cannot crawl this page because your robots.txt file blocks it. Unlike the "warning" version, here the page is NOT indexed.

Fix:If the page should be indexed, remove the block from robots.txt. If it should remain blocked, accept that it won't be indexed — this may be intentional for admin pages, search results, etc.

Excluded by 'noindex' tag

Google found a noindex meta tag or HTTP header on the page and respected it by not indexing.

Fix:If this is intentional (privacy pages, internal tools), no action needed. If it's a mistake — perhaps your CMS added noindex automatically — remove the tag and request re-indexing.

Not found (404)

The page returns a 404 HTTP status code. Google will eventually remove it from the index.

Fix: If the page was permanently removed, this is expected. If the URL should exist, restore the page or set up a 301 redirect to the most relevant alternative.

Soft 404

The page returns a 200 OK status but Google thinks the content is equivalent to a "not found" page. Common with empty category pages, expired listings, or thin placeholder content.

Fix:Add meaningful content to the page, return a proper 404/410 status if the content is truly gone, or redirect to a relevant page. For e-commerce: add "related products" to out-of-stock pages.

Unauthorized (401)

The page requires authentication that Googlebot doesn't have. Google cannot access the content.

Fix:If the page should be public, remove the authentication requirement. If it's intentionally behind a login, block it in robots.txt and accept it won't be indexed.

Crawl anomaly

An unexpected error occurred during crawling that doesn't fit other categories. Could be a timeout, connection reset, or unusual server response.

Fix: Use the URL Inspection tool to test the live page. Check server logs for the specific error during Googlebot visits. Common causes include CDN misconfigurations and firewall rules blocking Googlebot.

Duplicate content — Google chose different canonical

Google found this URL has the same or very similar content as another page, and Google chose a different URL as the canonical version.

Fix:If you agree with Google's choice, ensure proper canonical tags point to the selected URL. If you disagree, set explicit canonical tags to your preferred URL and ensure the content differences are clear.

Alternate page with proper canonical tag

This page has a canonical tag pointing to another URL, and Google is respecting it. The page itself is not indexed — the canonical version is. This is typically correct behavior for paginated pages, mobile/desktop variants, etc.

Fix: Usually no action needed. Verify that the canonical URL is the one you want indexed.

Discovered — currently not indexed

Google knows the URL exists (via sitemap or links) but has chosen not to crawl it yet. The page is in Google's crawl queue but hasn't been processed.

Fix:Improve internal linking to make the page more discoverable. Ensure your server can handle Googlebot's crawl rate. Submit the URL via the Indexing API or URL Inspection tool. See our detailed guide on fixing "Discovered — currently not indexed".

Crawled — currently not indexed

Google crawled the page but decided not to index it. This is a quality signal — Google doesn't think the content provides enough value to include in the index.

Fix: Improve content quality significantly. Add unique insights, original data, expert quotes, or multimedia. Ensure the page provides more value than competing pages on the same topic. Consider consolidating thin pages into more comprehensive resources.

Page removed because of legal complaint

Google received a legal request (DMCA, court order, etc.) to remove this URL from search results.

Fix:Review the legal complaint details in your Search Console. If you believe the removal was in error, you can submit a counter-notice through Google's legal process.

Page with redirect

This URL redirects to another page. Google is not indexing this URL but instead following the redirect to the destination.

Fix: This is usually expected. Update internal links to point directly to the final URL to avoid unnecessary redirect hops and conserve crawl budget.

Fix Priority Order

Not all indexing issues are equally urgent. Here's how to prioritize:

  1. Server errors (5xx) — These can cause widespread deindexing. Fix immediately.
  2. Redirect errors — Broken redirects lose link equity and user trust. Fix within 24 hours.
  3. Soft 404s on important pages — These indicate Google sees your content as low-value. Fix within a week.
  4. Excluded by noindex (if accidental) — A noindex tag on a page that should rank is a silent traffic killer. Fix within 48 hours.
  5. Discovered / Crawled — not indexed — These indicate quality or crawl budget issues. Address over the next 2-4 weeks with content improvements.
  6. Duplicate content issues — Fix canonical tags and consolidate content over the next month.
  7. Warnings (indexed but blocked) — Decide on a clear policy: either allow crawling or use noindex properly.

How IndexLens Helps

While Google Search Console shows you aggregate data and per-URL inspection, IndexLens gives you a different layer of visibility:

  • Bulk status checks — Check hundreds of URLs at once instead of one-by-one in GSC.
  • Daily monitoring — Track how statuses change over time, not just the current snapshot.
  • Instant alerts— Get notified the moment a page changes from "Indexed" to an error or excluded status.
  • One-click fixes — Submit URLs directly to the Indexing API for faster re-crawling.
Check Your Site's Index Status Now

Was this guide helpful?

Audit My Site Now