Shopify Crawled, Not Indexed: Why It Happens and the Fix

Quick answer: “Crawled - currently not indexed” means Google fetched the page but has not added it to its index, and Google says it may or may not be indexed in future. The status gives no reason for any single URL and Google’s documentation promises no fix, so nobody can honestly name one cause. On a Shopify store, the URLs worth checking first are the ones that add little beyond a page you already have: tag-filtered collections, near-duplicate products, thin or overlapping collections and deep paginated pages. Sort the list first, because some of those URLs should not be indexed at all, then check live status, canonical, internal links and the page itself, in that order.

You open Search Console, go to Indexing, then Pages, and there is a grey row with a number next to it that looks like an accusation: Crawled - currently not indexed. Sometimes it is a dozen URLs. Sometimes it is several hundred.

Generic advice tends to say add more content, resubmit the URL and wait. That treats the status as one problem with one fix. It is a bucket, and very different pages can land in it for very different reasons.

This guide covers what Google actually says about the status, which Shopify page types are worth checking first, the order I work through when a store has this report, and what to do with each group. I am not going to give you an indexing timeframe. Google does not give one, and anyone who does is guessing.

What the status says, and what it does not

Google’s Page indexing report help describes the status in one line: the page was crawled but not indexed, it may or may not be indexed in future, and you do not need to resubmit the URL for crawling. That is the whole definition. It does not say the page is bad, penalised or broken, and it does not say why.

Three more statements from Google’s documentation frame how to work with it:

• Not every crawled page is indexed. Google’s “How Search works” page says indexing is not guaranteed and depends on the page’s content and metadata. The common issues it lists are low-quality content, robots meta rules that disallow indexing, and site design that makes indexing difficult. Low quality is one of three.
• Meeting the rules guarantees nothing. Google’s Search Essentials says a page that meets the technical requirements and best practices is still not guaranteed to be crawled, indexed or served.
• You should not expect every URL to be indexed. The report help says not to expect every URL on your site to be indexed, only the canonical pages, and that the key pages are what matter. Non-indexed URLs can be fine, for example duplicates.

So there is no switch to flip. The report is a list of URLs to sort, not a score to get to zero. The neighbouring statuses are easy to mix up:

If most of your list says Discovered rather than Crawled, the questions are about crawling, not about whether the pages are good enough.

Step zero: sort the list before you fix anything

A count of 300 means nothing until you know which 300.

Split the report by sitemap. The Page indexing report can be filtered by All known pages, All submitted pages, Unsubmitted pages only, or one specific sitemap. A URL counts as submitted if it is in a sitemap you have submitted, even if Google also found it by following a link.

This is useful on Shopify because Shopify generates the sitemap, and Shopify’s help centre says it contains your products, primary product images, pages, collections and blog posts. On a Shopify demo store (os2-demo.myshopify.com) on 30 October 2026, the collections sitemap listed 57 collection URLs and none had a tag or other path added, and the products sitemap listed no /collections/ addresses. So:

• All submitted pages shows the URLs Shopify itself offers as the pages that matter. A URL here is one you presumably want indexed. Take this list seriously first.
• Unsubmitted pages only shows URLs that are not in a sitemap you submitted. Tag-filtered collections and other addresses Shopify leaves out of its sitemap show up here if Google found them another way.

This only works if you have submitted your sitemap. Shopify’s SEO overview tells you to add its address to Search Console, so do that first if you have not.

Mind the 1,000-row limit. Google says the examples table for each status does not necessarily show every URL with that issue and is limited to 1,000 rows. On a bigger store, work one sitemap at a time.

Group the URLs by type in a spreadsheet: product, collection, tag-filtered collection, paginated collection, blog post, page, localised version, other. You are looking for the pattern. “Mostly one type” is a very different story from “scattered across everything”.

Then decide, per group, whether you want it indexed. This is my rule of thumb, not Google’s:

1. Does the page answer something a buyer would search for that no other page on your store answers?
2. Can a shopper reach it through normal navigation, not only through the sitemap?
3. Is it meaningfully different from its nearest neighbour?

If the answer to all three is no, the page probably does not need to be in Google, and the right move is to consolidate it or leave it alone. If the first answer is yes and the page still is not indexed, that page is worth work.

The Shopify page types worth checking first

I am not claiming every URL of these types ends up in the bucket. Plenty are indexed without trouble. These are the types to look at first, why each is a candidate, and what to check.

Tag-filtered collection URLs

Shopify’s tag filtering adds a tag to a collection address, so /collections/skincare can also be reached at /collections/skincare/vitamin-c, and several tags can be joined with a plus sign. Shopify’s developer documentation describes the mechanism. The page I read does not address how these URLs should be treated for SEO.

On that demo store on 30 October 2026, a single-tag URL such as /collections/all/handbag returned a normal page with a canonical tag pointing to itself, not to the main collection, and it was not in the sitemap. The store’s robots.txt blocked sorted URLs, URLs with a plus sign (or its encoded forms) and URLs with two filter parameters, but none of those rules matched a single-tag URL. So a single-tag page is crawlable, shows a subset of its parent collection’s products, and claims to be its own canonical page. That is a good description of a page Google may crawl and then decline to index.

Two cautions. This is one demo store on one day, so check how yours behaves. And Shopify’s help centre lists a shorter set of default robots.txt rules than that store served, a reminder that defaults change. Read your own file at yourstore.com/robots.txt.

What I check: how many tag URLs exist, whether any has its own search demand, and whether menus, filters or apps link to them. What I do: if a tag is a real search term (say, “vitamin c serum”) and the page has a reason to exist, turn it into a proper collection with its own title, copy and products chosen on purpose. If not, leave it. The collection side is covered in our Shopify collection page SEO guide and the canonical side in the guide to duplicate content and canonical URLs.

An honest point: if you add a noindex tag to these pages, the report will not go to zero. Google lists a separate status for pages with a noindex directive. You have moved the URLs from “Google chose not to” to “you told Google not to”. That is a legitimate decision, but it is a relabel, not a fix.

Thin and overlapping collections

A collection can be thin (a handful of products, no introduction, nothing the parent collection does not already offer) or overlapping (two collections chasing the same search with mostly the same products). Seasonal and sale collections re-created each year at a new address are one version to watch for.

Google’s helpful content guidance supplies the questions. Does the page add something original or restate what is elsewhere? Does it cover the topic with insight beyond the obvious? Is it something a reader might bookmark or share? Those are about what the page offers, not its length.

On length there is a mild contradiction worth knowing. Shopify’s help centre says every page should have at least 250 words of descriptive text. Google’s helpful content page says it has no preferred word count. Treat 250 as Shopify’s rule of thumb, not a threshold Google applies. A 90-word introduction that says what the collection is, who it is for and how to choose beats 400 words of padding.

What I check: product count, whether the products are mostly a subset of another collection’s, whether it is in the main navigation or only in the sitemap, and whether its title and introduction differ from its neighbours. What I do: merge overlapping collections with a 301 redirect, give each survivor a distinct purpose, and write the introduction a shopper would want. Category pages are the highest-leverage SEO asset on most Shopify stores, so this group is usually where the effort pays.

Near-duplicate products

Three common sources: colour or size split into separate products with the same description instead of one product with variants; supplier descriptions pasted as supplied, so the text matches every other retailer; and bundles that repeat the contents of the products inside them.

Google’s “How Search works” page says it groups pages with similar content, picks one representative from each group, and treats the rest as alternates. A near-duplicate product can be crawled and then treated as the alternate.

Shopify variants are a separate case. On the demo store, a ?variant= URL had a canonical pointing to the plain product URL, so that case was handled there.

What I check: URL Inspection on the product, comparing the canonical you declared with the one Google selected. If Google picked a different product page, the problem is duplication, and extra copy on this page will not help until it is clearly different from the one Google chose. What I do: combine true variants into one product, rewrite descriptions on products that should stand alone, and redirect the ones that should not exist. Our product page SEO checklist covers what a product page needs to stand on its own.

Collection-path product URLs and paginated pages

Some themes link to a product through its collection, at an address like /collections/skincare/products/vitamin-c-serum. On the demo store, a request for that kind of address got a 301 redirect to the plain /products/ URL. I did not find this described in the Shopify documentation I read, so test one on your own store: if the address bar changes, yours redirects too. Either way, internal links, canonical tags and the sitemap should all name the same URL.

Page 2, 3 and beyond of a large collection are rarely worth indexing as landing pages, so seeing some in this report is not alarming. The real risk is products that can only be reached through those pages or a “load more” button. Google’s pagination documentation says its crawlers generally do not click buttons or trigger JavaScript that needs a user action. My reading is that products loaded only by a “load more” button or infinite scroll may be missed. The same page says not to use the first page of a sequence as the canonical for the others. On the demo store, ?page=2 had a self-referencing canonical, which matches that advice.

What I check: can a not-indexed product be reached by plain links from a page that is indexed? What I do: make sure important products appear on the first page of a relevant collection, link to them from elsewhere, and leave the deep pages alone.

Localised versions of the same page

If you sell into more than one country with Shopify Markets, each market can have its own URL for a page. Shopify says canonical URLs are set automatically, each market version has a self-referencing canonical, and hreflang tags are generated from your market and language settings. When two markets share a language and nearly identical content, such as an Australian store with a US subfolder, the pages are similar, and Google groups similar pages.

What I check: which version Google selected as canonical, using URL Inspection on both. What I do: if the content is truly the same, accept that Google may index one. If the markets genuinely differ (currency, shipping, range), make each page say so.

Blog posts and standalone pages

A blog is not exempt. Posts that restate common advice or were written only to hit a keyword can fall under the low-quality reason Google lists. The same questions apply, including who wrote it, how it was produced and why it exists. Improve it, merge it into a better post or retire it.

The order I check things in

This is the order I work through when I open a store’s Page indexing report. The early steps are quick and technical and the last is a judgement call. Skipping straight to rewriting content risks longer pages that are still not indexed.

1. Read the indexed version in URL Inspection

Paste a representative URL into the Search Console search bar. The indexed view shows Google’s stored version, not the live page. It covers how Google discovered the URL, the last crawl, whether crawling and indexing were allowed, the referring sitemaps and pages, and the canonical selection. Read three things:

• Discovery. Found through a sitemap, links, or both? A URL found only through the sitemap, with no referring pages, may have no internal links.
• Indexing allowed. A robots meta tag that disallows indexing is on Google’s own list of reasons a page is left out. If an app or theme setting added one, that is a quick win.
• Declared versus Google-selected canonical. If they differ, you have a duplicate problem. Fix that first.

2. Run the live test

Test live URL fetches and examines the page in real time. It tells you whether the page is reachable and indexable now, and the tested page view shows the rendered page and a screenshot. If the screenshot is missing content a shopper sees, resources your theme depends on may be blocked or failing, which matters for any page that loads its main content or reviews through an app.

Read the limits too. Google says the live test does not check sitemaps, referring pages, duplicates, canonical selection, manual actions or quality, and a positive result does not guarantee indexing. A pass means nothing technical is blocking the page. It does not mean the page deserves to be indexed.

3. Check the internal links

Google says every page you care about should be linked from at least one other page on your site, using a standard anchor element with a link address so Google can follow it. I compare the sitemap with what a crawl of the store finds by following links. Pages in the sitemap that the crawl never reaches are orphans. Common Shopify causes are products not assigned to any collection, collections not in any menu, and links built with scripts instead of plain links. Two or three links from relevant collections and related products is a cheap test of whether links were the missing piece.

4. Find the indexed twin

It costs nothing. Pick a not-indexed URL, then find a page of the same type on the same store that is indexed. Put them side by side: original or supplier copy, number of products, where each is linked from, canonical, age. The difference is often the answer, and it tells you which fix to try. If every page of a type is not indexed and none has an indexed twin, suspect something sitewide: a template, a setting, or something that applies to the whole type.

5. Only then, judge the page itself

If the page passes the technical checks, has links and is the canonical version, the content is the next suspect. Use the three questions from step zero and Google’s helpful content questions: original value, real expertise, clear authorship and a reason to exist that is about the reader.

Be careful what “improve” means. Google says adding or removing content just to seem fresh does not help, and that changing a page’s date without substantial changes is a warning sign. Improving a page means making it more useful: a clear buying guide on a collection, original photos and measurements on a product, real answers to what customers ask.

6. Decide per group: improve, consolidate, noindex or leave

• Improve when the page has a reason to exist and is weak.
• Consolidate when two pages do the same job. Google calls redirects and rel canonical strong signals for choosing a canonical URL, and a sitemap entry a weak one.
• Noindex when the page helps shoppers but has no search value. Noindex only works if the page is not blocked in robots.txt, because Google has to crawl the page to see the rule.
• Leave it when the URL is a harmless variant.

What does not work, and why

• Resubmitting the URL over and over. Google’s status text says there is no need to resubmit a Crawled URL. Its URL Inspection help says Request indexing adds the page to a queue after a quick check, has a daily limit, and does not guarantee the page will appear in the index. Use it after a real change, not as a repeat button.
• Resubmitting the sitemap. Google says a sitemap helps it discover URLs but does not guarantee they will be crawled and indexed. Google already crawled this URL, so discovery is not the problem.
• Adding words for the sake of it. Google has no preferred word count. A longer duplicate is still a duplicate.
• Blocking in robots.txt and adding noindex. Block and noindex together and Google never sees the noindex. Shopify also treats editing robots.txt as an unsupported customisation, so changes need care. See our Shopify robots.txt guide.
• Noindexing product pages to “tidy up”. If a product is the canonical version you want to rank, noindex removes it from search.
• Mass-publishing pages and hoping. Hundreds of near-identical filter or tag pages can add to this problem and will not cure it. We wrote about where that goes wrong in the programmatic SEO trap on Shopify.

A worked example (illustrative numbers)

These numbers are illustrative, not from a real store. Say a store has 120 products and 25 collections, and the report lists 210 URLs as Crawled - currently not indexed. After sorting:

The 110 tag URLs shrink to 8 jobs and the 28 paginated pages need nothing. If someone had said “add more content to all 210”, most of that effort would have been wasted.

After you make changes: validate and measure

When a group is fixed, open the status’s detail page and use Validate fix. Google’s process is to fix all instances first, start validation once, and not click it again until it succeeds or fails. Google says validation typically takes up to about two weeks but can take much longer. That is how long Google takes to check your fix, not how long a page takes to be indexed, and Google makes no promise that any page will be.

While you wait, measure what matters. By group: how many URLs in each group are indexed, using the sitemap filter. By page: impressions and clicks in the Performance report, filtered to the pages you worked on. By revenue: whether those pages bring orders over time. A product that is indexed and never visited is still a leak. Our Shopify SEO guide covers how this fits into the rest of your search work.

When to leave it alone

Not every row needs work. I would leave the report alone when:

• the not-indexed URLs are mostly tag, parameter or paginated variants and your important products and collections are indexed;
• the count has been steady for months and the pages that earn revenue are not in it; or
• the URLs are new. Fix links first, then give Google time without chasing a deadline.

I would act when pages that should earn revenue are stuck: a product you sell, a collection a buyer would search for, a post that should bring in customers.

Key takeaways

• “Crawled - currently not indexed” means Google fetched the page and did not add it to its index. Google says it may or may not be indexed later and offers no guaranteed fix.
• Google does not name a single cause. Its documentation lists low-quality content as one of three common reasons a page is not indexed.
• Sort the list first: use the sitemap filters to separate pages Shopify submits from everything else, then group by URL type.
• Check first: tag-filtered collections, thin and overlapping collections, near-duplicate products, deep paginated pages, localised duplicates and weak blog posts.
• Check in this order: indexed version, live test, internal links, an indexed twin, then the content.
• If the canonical you declared differs from the one Google selected, you have a duplicate problem, and more words will not fix it.
• Do not resubmit repeatedly, add words for their own sake, or block and noindex the same URL.
• The goal is not a zero count. It is that the pages that sell are indexed and the rest are a decision.

FAQs

What does “Crawled - currently not indexed” mean in Search Console?

Google fetched the page and did not add it to its index. Google’s help says the page may or may not be indexed in future and that you do not need to resubmit it for crawling. The status does not say why, and it is not a penalty.

How long does it take for a Crawled - currently not indexed page to be indexed?

Nobody can say, and Google does not give a timeframe. If you make a fix, Google says validation typically takes up to about two weeks but can take much longer. That is the time to check the fix, not a promise the page will be indexed.

Is Crawled - currently not indexed bad for my Shopify store?

Not on its own. Google says not to expect every URL on a site to be indexed. It matters when the URLs are pages that should earn revenue, such as products or collections buyers search for. If the list is mostly tag, parameter or paginated URLs, Google may simply be declining pages you did not need indexed.

Should I use Request indexing on these URLs?

Only after a real change, and not repeatedly. Google’s status text says you do not need to resubmit a Crawled URL, and the URL Inspection help says Request indexing does not guarantee indexing and has a daily limit.

Is it a content problem or a technical problem?

It can be either, or both. Google lists low-quality content, robots rules that disallow indexing, and site design that makes indexing difficult as common issues. That is why the order matters: check the quick technical things first, then judge the content.

Will adding more content to a collection page fix it?

Sometimes, if the page was thin and the new content makes it more useful. Not if the page is a near-duplicate of another or nothing links to it. Google says it has no preferred word count, and Shopify’s 250-word suggestion is Shopify’s guidance, not a Google threshold.

Should I noindex pages that are Crawled - currently not indexed?

Only if you have decided the page has no search value but still helps shoppers. Noindex relabels the URL in the report; it does not fix it. And never block the same URL in robots.txt, or Google will not see the noindex.

Is your Search Console report hiding a problem worth fixing?

Sorting this report is part of the indexation work in the technical audit of our Shopify SEO service. The hard part is not reading the status. It is knowing which URLs are costing you sales and which are noise, and that depends on your catalogue, your theme and your apps.

If you would like a second pair of eyes, book a free 30-minute diagnostic or tell us about your store. We look at your store before we recommend anything, and we tell you honestly if SEO isn’t the right move. No pitch.