Fixing Google Index Coverage: 7 Common Causes and What to Do

TL;DR — When Search Console reports "Discovered – currently not indexed" or "Crawled – currently not indexed", the cause is almost always one of seven things, and you can confirm it with a single curl.

Most small online stores share the same problem: the site loads, prices are good, and yet Google shows nothing. The customer buys from whoever they happened to hear about, and your traffic never arrives.

Find the cause first. Here are the seven usual suspects, most likely first.

Start here: read the Coverage report

Open Google Search Console and go to Pages (or Indexing). Three statuses matter:

• Discovered – currently not indexed: Google found the URL but chose not to keep it. Usually thin content, weak internal links, or duplication.
• Crawled – currently not indexed: the URL was fetched and then dropped. It signals low perceived value.
• Excluded by noindex tag: you are literally asking Google to skip the page. A leftover noindex in the theme is the usual cause.

If you see Excluded, you do not need to guess. Just find the tag.

| Search Console status | What it means | First thing to check | | --- | --- | --- | | Excluded by noindex tag | You are blocking indexing yourself | Response header and theme code | | Discovered – currently not indexed | Seen, then dropped | Content depth and internal links | | Crawled – currently not indexed | Fetched, then dropped | Duplication and page quality | | Crawl error | Server error or timeout | Server logs and response time | | Page with redirect | The URL points elsewhere | Fix the redirect chain | | Duplicate without user-selected canonical | Two URLs for one page | Add a canonical tag |

1. A stray noindex header

The most common mistake. Many shop themes mark draft or filtered pages as noindex and nobody ever removes it.

Check the response header yourself:

If noindex comes back, indexing is impossible until you remove it. In Next.js it usually comes from metadata:

For a published product, drop robots or set index: true.

2. robots.txt blocks the path

Some stores block the whole product directory, thinking they are protecting low-value pages.

Look for Disallow: /product or Disallow: /. For a shop, blocking the product path means blocking all organic revenue.

3. The sitemap is empty or points at the wrong host

A sitemap does not tell Google to index anything; it tells it which URLs exist. If it is empty, you have introduced nothing.

If the domain inside the sitemap differs from your live host (www vs non-www, or https vs http), every page looks like a duplicate. Fix the base URL in your sitemap config or metadataBase used for the robots file.

4. Duplicate URLs across variants

If mobile and desktop render the same page and neither declares a canonical, Google picks one and the other becomes a wasted duplicate.

Each page needs exactly one canonical:

Point it at the version you want in search results. For filter and sort pages, canonicalize to the clean URL without query parameters.

5. Orphan pages: zero internal links

A page that no internal link points to effectively does not exist for the crawler. This is common in shops: a new product is added and never linked from anywhere.

Practical rule: every product should receive at least one link from a category page and one from another page on the site. Low-selling products can also go into a "bestsellers" block.

6. Slow pages weaken crawl signals

Poor Core Web Vitals reduce how much a crawl budget gets spent on your site. Practical fixes: serve WebP images, keep LCP under 2.5 seconds, and use font-display: swap. See our site speed and Core Web Vitals guide for details.

7. Content too thin to be worth indexing

A page with one heading and two lines of text is not worth fetching. Add at least a specifications section, a usage section, and a short FAQ block. Our product page guideproduct-page-that-sells covers the structure.

Practical checklist for this week

• [ ] Run curl -sI on one product page and confirm there is no X-Robots-Tag: noindex
• [ ] Audit robots.txt for unwanted Disallow rules
• [ ] Verify the sitemap is non-empty and uses the correct domain
• [ ] Confirm every page has exactly one canonical tag
• [ ] Register both example.com and the www variant in Search Console
• [ ] Use URL Inspection on three key pages and click Request Indexing
• [ ] Remove the theme-level noindex and retest after 48 hours
• [ ] Check the speed of three key pages in PageSpeed Insights

How long should you wait after requesting indexing?

Requesting indexing means "look now", not "index now". It usually takes a few hours to a few days. If the status is unchanged after a week, go back and find which of the seven causes is still standing — until you fix the real cause, any extra work is just wasted time and money.

For a broader page-by-page audit, grab the technical SEO checklist and work through it with these same items.

FAQ

Q: Does requesting indexing on 50 URLs help rankings?

Not by itself. It only queues the URL for inspection. Internal linking and genuine external links matter more for rankings.

Q: My site is in Search Console but still not indexed, why?

You may have the wrong property type registered, or your server returned 5xx errors during the crawl. Check both under Settings.

Q: How long do new pages take to get indexed?

For small stores, usually a few days to two weeks. Lots of duplicate or filtered URLs pushes that number up.

Sources

• Google Search Central — Inspect a URL on Google Search Console: https://support.google.com/webmasters/answer/9012289
• Google Search Central — Robots meta tag and X-Robots-Tag specifications: https://developers.google.com/search/reference/robots_meta_tag
• Google Search Central — Build and submit a sitemap: https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
• Webmasters Stack Exchange — Will a robots noindex meta tag completely prevent indexing? https://webmasters.stackexchange.com/questions/126335/
• Reddit r/SEO — Discovered, currently not indexed: how to solve? https://www.reddit.com/r/SEO/comments/17o4syr/