A Shopify store I audited had 659 tag pages indexed.
Not products. Not collections. Tag pages: the URLs Shopify generates automatically when you tag a product, of the form /collections/something/tag-name. Nobody had created them on purpose. Nobody knew they existed. They outnumbered the store’s real commercial pages several times over.
What Shopify is doing when you tag a product
Tags are an organisational feature. You add them so you can filter your own admin, drive collection rules, and let customers narrow a collection down.
The side effect is that Shopify will serve a crawlable, indexable URL for the tag. Tag ten products with “waterproof” and you have a /waterproof variant of that collection, live, linkable and eligible for the index.
Do that across a catalogue with a normal number of attributes, colour, material, size, use case, season and brand, and the count multiplies fast. It is a combinatorial problem, and it grows quietly because nothing about adding a tag feels like publishing a page.
That is how you get to 659 without anyone making a decision.
Why it is a problem, stated precisely
I want to be careful here, because this topic attracts overstatement.
It is not a penalty. Nobody is going to action a store for having tag pages. Google is generally competent at working out which of several similar URLs it wants, and much of the time it will simply pick one and ignore the rest.
It is not primarily a crawl budget problem either. Crawl budget matters at a scale most stores never reach. If you have a few thousand URLs, Google is not struggling to get round them.
The actual cost is more specific and less dramatic.
You have handed Google a choice you did not want it to make. For a query like “waterproof jackets”, your store now offers a properly built collection page with a description, curated products and internal links pointing at it, and also a bare tag page listing the same products with no copy and nothing linking to it. Those compete. Sometimes the tag page wins, and the customer lands on the thinner of your two options.
They are thin by construction. A tag page is a product grid with a heading. There is no description, no buying guidance, no reason for it to be the best result. Enough of them and you have a store where a large fraction of indexable URLs are pages you would be embarrassed to send a customer to.
They dilute internal linking. Whatever authority flows around the store gets spread across URLs that were never meant to receive it.
On this store the third point was the one that mattered. The tag pages outnumbered the collections. The signal about which pages the business actually cared about was buried.
What I would do about it
In order.
- Work out how many you have.
site:yourstore.com inurl:/tag/will give you a rough count, and Search Console’s page indexing report will show you what has actually been indexed. Do this before deciding anything. Plenty of stores have twelve, and twelve does not matter. - Decide which ones you actually want. This is the part people skip. Some tag pages are genuinely useful and deserve to be real pages: if “waterproof jackets” is something customers search and you have thirty of them, that should be a proper collection with a description, not a tag page and not nothing.
- Noindex the rest. In
theme.liquid, conditionally output anoindexmeta tag when the template is a tag-filtered collection. This is the standard fix and it is a few lines. Leave them crawlable. You want Google to see the tag so it drops the URL, and blocking in robots.txt prevents exactly that. - Do not canonical them to the parent collection and consider it solved. Shopify already sets a canonical on tag pages pointing at the parent collection. That is a hint, and Google will disregard it when the pages differ enough. If canonicals were sufficient, this store would not have had 659 of them indexed.
- Then look at whether the collection pages are worth ranking. Removing a thin competitor only helps if the page that survives is good. On most stores I audit, the collection pages have a title and a product grid and nothing else.
The wider version of the same problem
Tag pages are the Shopify-flavoured instance of something you see on every ecommerce platform: the store generates URLs faster than anyone decides to publish pages.
WordPress does it with tag and author archives. Faceted navigation does it with parameters. Shopify does it with tags and with the /collections/all/product duplication of every product URL.
The common failure is not that these URLs exist. It is that nobody has ever gone and looked at how many there are. In the audits I have done, the number is almost always higher than the owner expects, and the first useful thing I do is simply count.
For a sense of how many stores this is true of: HTTP Archive’s 2025 Web Almanac found ecommerce software on 19.2% of mobile sites, with Shopify accounting for 25.3% of those. Roughly one site in twenty on the mobile web is a Shopify store, and every one of them mints a tag URL the moment somebody types a word into the tags field. The 659 I found were not a misconfiguration by a careless store owner. They were the platform doing exactly what it was built to do.
The short version
- One Shopify store, 659 indexed tag pages that nobody had created deliberately.
- Shopify serves an indexable URL for every tag on a collection. Tag combinations multiply fast.
- It is not a penalty and it is rarely crawl budget. It is competition between your good page and your thin one, and dilution of the internal links pointing at what you sell.
- Count them first. Promote the few worth having into real collections. Noindex the rest in
theme.liquid: crawlable, not blocked. - Shopify’s own canonical is a hint, not a fix. Those 659 were indexed with canonicals already in place.
If a site should be ranking and it isn’t, that’s the work I do. Shopify SEO covers the defaults that create this kind of problem, and Ecommerce SEO covers architecture at catalogue scale.
