How to Fix Index Coverage Gaps in Google Search Console
An index coverage gap means pages you want in Google, usually the ones in your XML sitemap, are being crawled or discovered but not indexed. By the end of this guide you will have pulled the non-indexed URLs from Search Console, matched each one to its exclusion reason, fixed the cause, and asked Google to re-check them.

Why it matters
A page that is not indexed cannot rank, earn clicks, or be cited by Google's AI Overviews and other answer engines that draw on the search index. When 15% or more of a sample of your important URLs fail URL Inspection, it usually points to a site-wide cause rather than a few stray pages. Common causes are a leftover noindex, wrong canonicals, a sitemap full of redirects, or many thin pages.
Fixing that cause often brings back traffic for whole page templates at once.
What you need
Step-by-step fix
Confirm Search Console access for the right property
Open Google Search Console and check that you are in the property that covers every URL you care about. com) covers http/https and all subdomains. com/) only covers that exact prefix.
Go to Settings > Users and permissions and make sure the account or service account running the audit has Full or Owner access. URL Inspection data is not returned with restricted access or for URLs outside the property.
List the non-indexed URLs and their reasons
Go to Indexing > Pages. Above the chart, switch the filter from All known pages to All submitted pages so you only see URLs from your sitemaps. Scroll to Why pages aren't indexed and open each reason.
Export each list with the Export button (top right) to Google Sheets or CSV. For a specific URL, paste it into the inspection bar at the top. The Page indexing section shows the exact coverage state Google assigned.
Match each exclusion reason to its fix
Sort your export by reason and use this map:
- Excluded by 'noindex' tag: remove the noindex from the meta tag or the X-Robots-Tag header.
- Blocked by robots.txt: remove or narrow the Disallow rule.
- Page with redirect / Not found (404) / Soft 404: update the sitemap and internal links to point at the final 200 URL, or restore the page.
- Duplicate, Google chose different canonical than user / Alternate page with proper canonical tag: fix or align your canonical tags, and only list the canonical URL in the sitemap.
- Server error (5xx) / Blocked due to access forbidden (403): fix the hosting, firewall or bot rules.
- Crawled – currently not indexed / Discovered – currently not indexed / URL is unknown to Google: these are quality, discovery or crawl-budget issues (see step 5).
Remove technical blocks: noindex, robots.txt, canonical
Check what Googlebot actually receives for a failing URL, not just what your CMS settings say. Look for an X-Robots-Tag response header, a meta robots tag in the rendered HTML, and the rel=canonical target. Remove noindex from pages you want indexed.
Make each indexable page's canonical point to itself (absolute URL, same protocol and host). txt Disallow rule that matches those pages.
# Check headers for noindex and redirects curl -sIL -A "Googlebot" https://www.example.com/services/audit | grep -iE "^HTTP|x-robots-tag|location" # Check meta robots and canonical in the HTML curl -sL https://www.example.com/services/audit | grep -iE '<meta[^>]+robots|rel="canonical"' # Correct state in <head>: # <meta name="robots" content="index, follow"> # <link rel="canonical" href="https://www.example.com/services/audit">
Clean the sitemap so it lists only indexable URLs
txt. Remove redirected, 404, parameter, paginated-duplicate, tag-archive and other alternate URLs. Replace redirects with their final destination.
Use accurate lastmod dates; don't stamp every URL with today's date.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.example.com/services/audit</loc>
<lastmod>2026-01-14</lastmod>
</url>
<url>
<loc>https://www.example.com/blog/core-web-vitals-checklist</loc>
<lastmod>2025-11-02</lastmod>
</url>
</urlset>Fix 'Crawled' and 'Discovered – currently not indexed'
For these states, Google can reach the page but has not judged it worth indexing yet. Address these in order:
- Internal links: link to each page from relevant, already-indexed pages using descriptive anchor text, and keep important pages within 3 clicks of the homepage.
- Thin or near-duplicate pages: merge them into one stronger page and 301 the rest, or noindex them and drop them from the sitemap.
- Main content: make sure it is rendered in the HTML Google sees.
- Crawl health: check Settings > Crawl stats for slow average response times or rising 5xx errors, which throttle crawling.
Resubmit the sitemap and request recrawls
In Indexing > Sitemaps, resubmit your sitemap URL and confirm the status reads Success. For your most important fixed URLs, open URL Inspection and click Request indexing; this is capped at roughly 10-12 requests per day. Then go back to Indexing > Pages, open each reason you fixed and click Validate fix.
Google will recrawl the affected URLs and report progress, usually within 2-3 weeks.
Re-inspect a sample and confirm the gap is closed
After Google recrawls, inspect a sample of 20-50 sitemap URLs across all templates with URL Inspection or the URL Inspection API. Each should show URL is on Google with coverage Submitted and indexed. Aim for fewer than 15% of sampled URLs failing, then rerun the audit.
Check Indexing > Pages with the All submitted pages filter weekly for a month to catch regressions.
Platform-specific notes
WordPress
Go to **Settings > Reading** and make sure **Discourage search engines from indexing this site** is unchecked; it is often left on after a staging migration. In Yoast SEO (**Yoast SEO > Settings > Content types / Categories & tags**) or Rank Math (**Rank Math > Titles & Meta**), check which types are set to noindex. Those plugins drop noindexed types from /sitemap_index.xml automatically.
Shopify
The sitemap at /sitemap.xml is generated automatically and can't be edited directly. Product URLs reached through collections (/collections/x/products/y) canonicalise to /products/y, which is expected; don't submit them. To hide pages, use the theme's `seo.hidden` metafield or edit robots rules via **Online Store > Themes > Edit code > templates/robots.txt.liquid**.
Wix
Per page, go to **Pages > (page) > SEO basics** and check **Let search engines index this page**. For whole page types, use **Marketing & SEO > SEO > SEO Settings** to set indexing per page type. Wix manages the sitemap and robots.txt, so non-indexed URLs listed there usually trace back to these toggles.
Next.js
In the App Router, check `export const metadata = { robots: { index: false } }` or `generateMetadata` in layouts. A noindex in a root or segment layout applies to every child route. Generate the sitemap from `app/sitemap.ts` using only published, canonical routes. Also check middleware or `next.config.js` headers for an `X-Robots-Tag: noindex` left over from preview deployments.
Cloudflare
If URL Inspection shows **Server error (5xx)** or **Blocked due to access forbidden (403)**, look at **Security > Events** for blocked Googlebot requests. Verified bots should pass Bot Fight Mode, but custom WAF rules, country blocks or rate limits can still block them. Add a WAF skip rule for `cf.client.bot` if needed.
Check that it worked
✅ How to verify
- In Search Console URL Inspection, each fixed URL shows **URL is on Google** and **Page indexing: Page is indexed**, with **Submitted and indexed** under coverage.
- Indexing > Pages with the **All submitted pages** filter shows the indexed count rising and the fixed reasons with validation status **Passed**.
- A crawl of the sitemap (Screaming Frog list mode or similar) returns 100% 200-status, indexable, self-canonical URLs.
- Rerunning the audit shows fewer than 15% of inspected URLs failing, ideally 0.
⚠️ Common mistakes
- Leaving redirected, canonicalised or deliberately noindexed URLs in the sitemap. They will never show as indexed and keep counting as gaps.
- Fixing the noindex in the CMS while an X-Robots-Tag header from the server, CDN or framework config still sends noindex.
- Spamming Request indexing for 'Crawled – currently not indexed' pages without improving content or internal links. Google recrawls them and excludes them again.
- Blocking a page in robots.txt to remove it from the index. Google then can't see the noindex tag, and the URL may stay indexed or show as 'Indexed, though blocked by robots.txt'.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What does 'Crawled – currently not indexed' mean and how do I fix it?
Google fetched the page but chose not to add it to the index, usually because it looks thin, duplicative or low priority. Strengthen the content, merge near-duplicates, and add internal links from indexed pages. Then request indexing. There is no technical switch that forces inclusion.
How long does it take Google to index pages after fixing coverage issues?
Individual URLs submitted with Request indexing are often recrawled within a few days. A Validate fix run in the Pages report typically takes 1-3 weeks, and longer on large sites with limited crawl capacity.
Should every URL in my sitemap be indexed?
Yes, that is the goal. A sitemap should only list canonical, indexable, 200-status pages you want in search. If a URL shouldn't be indexed, remove it from the sitemap rather than leaving it to show up as excluded.
Is 'Alternate page with proper canonical tag' an error?
Not on its own. It means Google respected your canonical and indexed the preferred version instead. It only becomes a gap if that URL sits in your sitemap or is a page you actually want ranking. In that case, fix the canonical or remove the URL from the sitemap.
How to Fix Structured Data Errors on Your Website
How to Fix Conflicting Canonical and Noindex Tags
How to Fix Missing Organization Schema (JSON-LD Guide)
How to Fix Canonical Tags Pointing to Non-200 URLs
How to Fix Missing WebSite Schema (JSON-LD Guide)
How to Fix Duplicate URL Variants (Case, Slash, Index)