Why Is My Sitemap Coverage Low in Google Search Console?
Seeing a large gap between the number of URLs submitted in your sitemap and the number actually indexed is one of the most common and frustrating SEO problems. Google Search Console shows you this discrepancy clearly, but explaining why it exists requires investigating several potential root causes — from thin content to crawl budget issues to indexing policy signals Google sends back to your pages.
Understanding Submitted vs. Indexed Count
In GSC, the Sitemaps report shows two numbers: URLs submitted (from your sitemap) and URLs indexed (pages Google chose to include in its index). The gap between these is your "low coverage." A small gap is normal — not every page merits indexing, and Google routinely excludes low-quality or near-duplicate pages. A large gap (over 20–30%) usually signals a systemic problem. The Coverage report's "Excluded" section is the key diagnostic tool — it shows exactly why Google chose not to index each excluded page.
Cause 1: Thin or Duplicate Content
The most common reason for low sitemap coverage is that the excluded pages contain thin, duplicate, or near-duplicate content. Google's "Crawled - currently not indexed" and "Discovered - currently not indexed" statuses often indicate content quality issues. Pages with fewer than 300 words, boilerplate text, auto-generated content, or content that closely mirrors other pages on the site are frequently excluded. Adding substantive, unique content to these pages is the most reliable path to increasing indexed coverage.
Cause 2: Noindex Tags on Sitemap URLs
A critical conflict occurs when a URL appears in your sitemap but carries a noindex meta tag or HTTP header. Google will not index a noindexed page, regardless of sitemap submission. This situation is a double signal of confusion — you're simultaneously telling Google to index the page (via sitemap) and not to index it (via noindex). GSC flags these as "Excluded by noindex tag." Audit your sitemap URLs against their meta robots tags and remove any noindexed URLs from the sitemap.
Cause 3: Canonical Tag Conflicts
If a sitemap URL has a canonical tag pointing to a different URL, Google treats the canonical as the authoritative version and excludes the sitemap URL from indexing. GSC labels these as "Alternate page with proper canonical tag." This is another version of the sitemap-noindex conflict — submitting the wrong URL variant. The fix is to only include the canonical URL in your sitemap, ensuring perfect alignment between your sitemap entries and your pages' canonical declarations.
Cause 4: Crawl Budget Constraints
Large sites with hundreds of thousands of pages may have more URLs in the sitemap than Googlebot can feasibly crawl and index within reasonable time. "Discovered - currently not indexed" at scale often indicates crawl budget pressure. Google has seen the URL but hasn't prioritized crawling it. Improving internal linking to important pages, removing low-value pages from the sitemap, and ensuring fast server response times all help concentrate crawl budget on pages that matter most.
Cause 5: Server Errors and Redirect Chains
URLs returning 5xx errors, long redirect chains, or soft 404s (pages that return 200 but show error-like content) will not be indexed. The Coverage report's "Error" section shows these. Use GSC's URL inspection on failing URLs to see the exact HTTP response Google received. Fix server-side errors, reduce redirect chains to a maximum of one hop, and ensure soft 404s are corrected to either proper 404/410 responses or real content pages.
Cause 6: Robots.txt Blocking Crawl
If your robots.txt disallows Googlebot from accessing URLs that appear in your sitemap, those pages will never be crawled or indexed. Check for overly broad Disallow rules that may inadvertently block important URL patterns. Use GSC's robots.txt tester to verify each sitemap URL is accessible. A sitemap URL blocked by robots.txt appears in the Coverage report as "Blocked by robots.txt." Removing the block and resubmitting the sitemap prompts recrawling.
How to Read the GSC Coverage Report
Navigate to GSC → Pages (formerly Coverage). Filter by "Sitemap" to see only URLs submitted via your sitemap. Review the "Not indexed" section and expand each exclusion reason. Export the list, then cross-reference with your sitemap to identify patterns — are the excluded pages all from a specific template, category, or URL pattern? Patterns reveal root causes. A random scatter of excluded URLs suggests individual page-level quality issues, while a pattern suggests a systematic technical or content problem.
Prioritizing Which Gaps to Fix First
Not every excluded URL is worth fixing. Prioritize by business value: product pages, service pages, and high-traffic blog posts warrant the most attention. Pagination pages, faceted navigation, and parameter-based URLs that duplicate content may reasonably stay excluded — consider removing them from the sitemap entirely if they're not meant to rank. Focus your efforts on pages with real search demand that Google is currently refusing to index, and use SitemapFixer to audit which sitemap URLs are most at risk.