What the error means
Google fetched the page and decided not to add it to the index for now. The page may be indexed later without any change, or it may stay out. Unlike Discovered, Google has seen the content.
Why Google rejects it
Google does not index every page it crawls. Pages that look thin, duplicate another page, add little that is not already indexed, or look like a soft 404 are commonly left out. Google's own guidance is that there is no need to resubmit these URLs for crawling.
How to fix it
- Open URL Inspection for the page and confirm it returns 200, is indexable, and that Google's view of the page shows the real content.
- Compare the page with the ones Google did index. If several pages say nearly the same thing, merge them or make each one clearly different.
- Add substance: specific details, examples, original images or data that a searcher cannot get from the page you are competing with.
- Link to the page from relevant, indexed pages so Google sees it as part of the site, not an orphan.
- Remove or noindex low-value URLs of the same type so the pages you care about stand out.
Common causes
The page adds little unique information
Google fetched the page but may decide it does not add enough value to keep in the index. Thin category text, boilerplate product descriptions, and generated location pages often have little beyond shared template content. Compare the page with other indexed pages on the same site and in the search results.
Several URLs show substantially the same page
Variant, filter, tracking, or alternate-host URLs can duplicate a preferred page. Google may choose one representative and leave the others out. Check the user-selected and Google-selected canonical in URL Inspection and compare the actual rendered content.
Page appears empty or unavailable after rendering
A page may return 200 but show a blank shell, failed product data, or a not-found message after scripts run. Google can crawl the URL without seeing useful main content. Inspect the rendered page and server logs for failed API, theme, or database calls.
Internal signals favor another URL
A canonical tag, redirect, sitemap entry, or internal links can point Google toward a different version. Even a technically accessible page may be treated as secondary. Make the preferred URL consistent across canonical, links, sitemap, and redirects.
Fix it on your platform
On Shopify
- Check the live product page and confirm its content appears without a customer login. Review product publication status, Online Store availability, and the selected variant.
- For products with substantially identical variants, verify canonical URLs and use the platform's intended product and variant URL pattern rather than generating many thin duplicate pages.
- Improve manufacturer copy with details you can substantiate: materials, dimensions, use, compatibility, care, and what differentiates the product. Do not add filler to change a word count.
- Review collection and app-generated pages; remove or noindex pages that merely repeat the same product grid or are not intended for search.
On WooCommerce
- Inspect the rendered product or page while logged out. Confirm page builders, variation scripts, and product data requests complete for Google-visible content.
- Use the active SEO plugin to set the preferred canonical and decide whether thin archives should be indexed. Avoid conflicting canonical output from multiple plugins.
- Add original product details and useful category introductions where they help shoppers. Consolidate pages that target the same need instead of cloning boilerplate.
- Check cache and plugin logs if the page is empty or differs between the admin preview and public response.
On other platforms
- Test Google's live rendering and compare it with what an anonymous visitor sees. Repair scripts, APIs, or permissions that hide the main content.
- Choose one URL for duplicate content and align canonical tags, redirects, internal links, and sitemap entries to it.
- Improve only pages that serve a distinct searcher need; remove or noindex thin filter and archive pages that do not.
- Check whether page builder or localization templates publish near-identical pages with only a changed keyword or city name.
How to confirm it is fixed
- Use URL Inspection to check the indexed version and live test; compare rendered content, crawlability, and selected canonical.
- Make sure the page returns 200, has useful main content, and is linked and listed under the intended canonical URL.
- Run the index signals check for public status, canonical, and noindex signals, then request indexing once after substantive changes.
- Watch the Page indexing report after a later crawl; Google may still choose not to index a technically valid page.
A worked example
Hypothetical case: a WooCommerce store creates a separate URL for every filter combination in a bedding category. Search Console shows hundreds of Crawled – currently not indexed URLs. Inspection shows that the pages render correctly but differ only by sort order or a color filter, and most have the same introduction. The owner keeps the main category page, removes unnecessary filter links from crawlable navigation, and sets the intended canonical through the SEO plugin. They expand the main category with accurate size and fabric guidance. Google continues to exclude some filtered URLs, which is expected; the main category is inspected separately.
Questions
Why is Google not indexing a page it already crawled?
Will Google eventually index Crawled – currently not indexed pages?
Should I remove pages marked Crawled currently not indexed?
Shipwork checks the signals a crawler reads on each page: status, noindex, canonical, and whether the sitemap agrees, so you can rule out technical causes before working on content. Free, no account, no signup. Paste your store address.
Check my store for Crawled – currently not indexedOther errors like this