Why Google Isn’t Indexing Your Product Pages (and How to Fix It)

Why Google Isn’t Indexing Your Product Pages (and How to Fix It)
Why Google Isn’t Indexing Your Product Pages (and How to Fix It)
Affiliate disclosure: This post contains affiliate links. If you buy through them, I may earn a commission at no extra cost to you. Full disclosure

You add 800 products to your store, wait a few weeks, and check Google. Only a fraction of them shows up. Search sales stay flat, and the products you spent the most time on are nowhere to be found. It is a very common problem in ecommerce, and in most stores it is fixable once you know where to look.

TL;DR: Product pages may stay out of Google because they are difficult to discover, crawling is spent on duplicate URLs, their content adds too little value, or indexing directives and canonical signals point elsewhere. Start with the Page indexing report in Search Console, then compare a site crawl with your sitemap. Indexing has no fixed deadline and is never guaranteed.

Below is a practical way to find out which of the four reasons applies to your store, with a checklist you can run in about half an hour.

What do “Discovered – currently not indexed” and “Crawled – currently not indexed” mean for a store?

Both statuses mean Google knows a URL exists but has not added it to its index. “Discovered” means Google found the URL but has not crawled it yet. “Crawled” means it fetched the page and decided not to index it, at least for now.

For a store, the two statuses usually point to different problems. A pile of “Discovered” URLs suggests a crawling problem: too many URLs, weak internal links, a bloated sitemap. A pile of “Crawled” URLs suggests a quality problem: thin, duplicated or near-identical pages. Google’s own crawl budget guide treats sites with many URLs in the “Discovered – currently not indexed” status as the ones that need to manage crawling actively. Open Page indexing in Search Console and write down how many URLs sit in each status today. That number is your baseline.

How do you find which product pages Google can’t see?

You need to compare what you have with what Google has. Search Console tells you what Google decided, but it does not tell you why, and it does not list pages Google has never heard of. A crawl of your own site fills that gap, and server logs show whether Googlebot ever requested a given URL.

An SEO tool for eCommerce can help compare a site crawl with server logs and identify product pages that receive few internal links. JetOctopus is one option for this kind of technical analysis. Check its current features against the size and needs of your store.

You do not need a catalog that size for the method to work. The same three comparisons apply to a store with 500 products:

1.       Sitemap against index. Count the product URLs in your sitemap and the product URLs Search Console reports as indexed. The gap is your problem list.

2.       Crawl against sitemap. Crawl the site and list product pages that exist but are missing from the sitemap, and pages with no internal links pointing to them. Pages nobody links to are the first to be ignored.

3. Logs against crawl. If you have access to server logs, check whether Googlebot requested the missing pages. A page with no Googlebot requests may have a discovery or crawling problem; logs alone cannot establish the cause.

Why does Google skip pages on a store with filters and variants?

Because it spends its crawling time on URLs that add nothing. Google’s crawl budget guide names the usual culprits: duplicate URLs that lead to the same content, sorted and filtered variants of category pages, noindex pages that Google still has to request before dropping them, soft 404 pages, long redirect chains and outdated sitemaps.

Filters multiply fast. As a purely hypothetical illustration, a category with 10 filters, each with five values and the option to leave it unselected, allows 6^10, or more than 60 million, different URL combinations. A real store exposes only a fraction of that, but even a small fraction can outnumber your actual products many times over, and Googlebot has to fetch URLs to find out that they are duplicates.

The fix is to decide which facets deserve to be indexed:

·         Keep indexable: facets people actually search for (brand, material or a product type inside a category), with a clean URL and a canonical pointing to itself.

· Close off low-value sorting, price sliders, view settings and unnecessary filter combinations. Reduce crawlable links to duplicate combinations where appropriate. Do not block a URL in robots.txt if Google still needs to crawl it to see a noindex directive; a blocked URL can remain indexed without its content.

Are your product pages too thin or duplicated?

If the crawl shows that Google reaches the pages but does not keep them, look at the content. Typical store problems are supplier descriptions copied across dozens of shops, near-identical pages for every color or size, and empty collection pages.

Before rewriting everything, inspect representative URLs in Search Console. New pages can take time to be discovered and evaluated, but there is no universal 30-day waiting period. Fix clear technical errors when you find them rather than waiting for an arbitrary deadline.

Improve important missing pages where it matters most. Rewrite repetitive supplier descriptions, make canonical signals consistent, and remove or noindex empty collections when appropriate. Keep genuinely distinct product variants accessible when they serve useful search demand.

A 30-minute indexing checklist for store owners

1.       Open Page indexing in Search Console and note the numbers for “Discovered” and “Crawled – currently not indexed”.

2.       Compare the number of product URLs in your sitemap with the number of indexed ones.

3.       Inspect five unindexed product pages for a noindex tag, a canonical pointing elsewhere, or a robots.txt block.

4.       Check whether those pages are linked from a category or collection page.

5.       List the filters and parameters that create duplicate URLs, and decide which to keep.

6.       Rewrite the descriptions of your 10 most important products.

7.       Repeat the check after 30 days and compare it with your baseline.

Conclusion

Unindexed product pages are rarely a mystery. They are found, crawled or judged in the wrong order: Google must discover a page, spend time on it and consider it worth keeping. Work through that order, fix the earliest step that fails, and measure again in a month.

FAQ

How long does Google take to index a new product page?

There is no fixed indexing time, and Google does not guarantee indexing. Links from relevant category pages, accurate sitemaps and useful product content help discovery and evaluation. Repeatedly requesting indexing does not guarantee faster inclusion.

Should I block filter and sort URLs from Google?

Keep useful facets with real search demand accessible. Reduce crawlable sorting and redundant filter combinations. Robots.txt controls crawling, while noindex controls indexing only when Google can fetch the page and see the directive. Choose the approach for the actual problem rather than applying one rule to every URL.

Does a sitemap guarantee that product pages get indexed?

No. A sitemap helps Google discover URLs but does not guarantee crawling or indexing. Keep canonical, live, indexable product URLs in it and use Search Console to investigate representative exclusions.

Is crawl budget a problem for a small store?

Usually not. Google aims its crawl budget guide at sites with more than a million unique pages that change weekly, or 10,000 or more that change daily. Small stores more often suffer from thin pages and weak internal links. The exception is a store whose filters generate thousands of URLs, and the warning sign is a large “Discovered – currently not indexed” count in Search Console.

Do I need server logs to find indexing issues?

Not for a small catalog. Search Console and a crawl are enough to find most problems. Logs become useful when the crawl finds pages that Search Console never mentions, or when the catalog is large, because logs show whether Googlebot requested a specific URL and what status it got.