Shopify Product Tags and SEO: What Tags Do, What They Don't, and How to Clean Them Up

Most Shopify stores collect product tags the way a garage collects boxes. A supplier import adds fifty, an app adds a few more, someone on the team tags products by season, and two years later the store has 3,000 tags that nobody can explain. The usual question at that point is whether all those tags help SEO. The short answer is no, and in some setups they quietly hurt it.

This guide covers what product tags actually do on Shopify, why tag-filtered collection URLs cause indexing problems, where tags are genuinely useful (automated collections and filters), and how to clean up a tag list without breaking anything.

What product tags are in Shopify

A product tag is a short internal label attached to a product. You add tags on the product page in the admin under Product organization > Tags. Each product can hold up to 250 tags (Shopify Plus stores have no cap), and each tag can be up to 255 characters, although Shopify recommends keeping them short. Shopify also recommends using only ordinary letters, numbers and hyphens, because accented characters and symbols can be ignored or treated as the same tag.

Tags do not appear on the storefront by default. They show up only where your theme or an app uses them. The common places are:

• Automated collections, using the condition "Product tag includes".
• Storefront filters in the Search and Discovery app, where a tag filter lists tag values as checkboxes.
• Theme logic, such as a "Sale" badge or a size chart that only appears on products tagged a certain way.
• Apps that read tags to decide shipping rules, bundles, reviews widgets or feed exclusions.
• Tag-filtered collection URLs such as /collections/shirts/blue, which older themes link to from a tag list in the sidebar.

For the full list of Shopify's tag rules, see the Shopify Help Center article on tag formats.

Do product tags help SEO?

No, not directly. Google does not read the tag field on a Shopify product. Tags are not printed into the page as a meta keywords tag, and even if a theme did print them, Google has ignored the meta keywords tag for ranking for many years. Shopify's own help article on tag formats says plainly that tags should not be used for SEO.

What tags can do is shape the pages that search engines see. That influence runs in both directions:

So the useful way to think about tags is as plumbing. They route products into collections and filters. The collections are what you optimize for search. If you want a page to rank for "linen summer dresses", build and optimize that collection page; do not expect a tag called linen-summer-dress to do the work. Our guide to Shopify collections SEO covers how to make those pages rank.

The tag page indexing problem

Shopify supports URLs that filter a collection by tag. If the "Shirts" collection has products tagged blue, the URL /collections/shirts/blue shows only the blue shirts. The same works on the catch-all collection, so /collections/all/blue shows every blue product in the store. Combining tags with a plus sign, such as /collections/shirts/blue+cotton, narrows it further.

Here is why that becomes an SEO problem:

• They multiply fast. Ten collections with 80 tags each is up to 800 extra URLs, before combinations.
• They look like duplicates. Most themes print the same collection title, description, H1 and meta description on the tag URL as on the main collection. Only the product grid changes.
• They can carry a self-referencing canonical. Themes usually output {{ canonical_url }} in the head, and on a tag page that value is the tag URL itself, so the page tells Google it is its own original.
• They waste crawling. On a large store, Googlebot can spend time on hundreds of tag pages instead of new products.

Shopify's default robots.txt already blocks some of this. It disallows collection URLs containing a plus sign (the combined tags), sort_by parameters and URLs with more than one storefront filter. It does not block single-tag URLs like /collections/shirts/blue. Those stay crawlable unless you change something.

Newer themes built on Online Store 2.0 and the Horizon family use the Search and Discovery filters instead of tag URLs. Those filters add parameters like ?filter.p.tag=blue to the collection URL. A single filter is crawlable, while two or more filters match the default disallow rule. If your store has run more than one theme over the years, you may have both kinds of URLs in Google's index.

How to check whether tag pages are indexed

1. Search Google for site:yourstore.com inurl:/collections/ and scan for URLs with an extra segment after the collection handle.
2. In Google Search Console, open Indexing > Pages. Check the "Duplicate, Google chose different canonical than user", "Crawled, currently not indexed" and "Indexed" groups for tag URLs.
3. Run a site crawler and filter for URLs matching /collections/*/* that are not product URLs.
4. Open a few tag URLs and view the source. Note what the canonical tag and the meta robots tag say.

If you find a handful of tag pages and none of them get traffic, the fix is simple. If some of them already get search clicks (check the Search Console Performance report filtered by page), treat those differently, as covered below.

Fix option 1: noindex tag pages

The cleanest general fix is to tell search engines not to index any collection view filtered by tag, while still letting them follow the product links. In your theme code, open layout/theme.liquid and add this inside the <head>:

{% if current_tags %}<meta name="robots" content="noindex, follow">{% endif %}

The current_tags object is only populated when a collection or blog is being viewed through a tag, so normal collection pages are unaffected. Duplicate your theme before editing, and check that no app already outputs a robots meta tag on those pages.

Fix option 2: canonicalize to the parent collection

Some stores prefer to point the canonical tag of each tag page to the main collection. In the same head section, replace the standard canonical line with logic that outputs {{ shop.url }}{{ collection.url }} as the canonical when current_tags exists, and {{ canonical_url }} otherwise. A canonical is a hint, not a directive, so Google may still index a tag page it considers different enough. Noindex is the more reliable signal for thin tag pages.

Fix option 3: block crawling in robots.txt

You can edit robots.txt.liquid in your theme to disallow tag paths. Use this carefully. A robots.txt block stops crawling but does not remove pages that are already indexed, and it also prevents Google from ever seeing a noindex tag on those pages. If tag pages are already in the index, add noindex first, wait for them to drop out, and only then consider blocking. If you want to draft a rules file before touching your theme, the robots.txt generator can help you build and check the syntax.

When a tag page deserves to rank, make it a collection

Sometimes a tag page does get clicks, because it matches a real search like "blue linen shirts". The answer is not to keep the tag page. Build a proper collection for that query, then redirect the tag URL to it.

1. Go to Products > Collections > Create collection.
2. Give it a title that matches the search, such as "Blue Linen Shirts".
3. Under collection type, choose automated and add conditions, for example "Product tag includes blue" and "Product type is equal to Shirt", set to match all conditions.
4. Write a short, unique collection description (a few useful sentences on fit, fabric and care is enough) and fill in the search engine listing with a unique title and meta description.
5. Add the collection to your navigation or link it from the parent collection description so it gets internal links.
6. Noindex the old tag URL and replace any internal links to it with links to the new collection. Shopify URL redirects (under Content > Menus > View URL redirects) only work from URLs that return a 404, and a tag URL on a live collection still loads, so a redirect is usually not an option here.

Automated collections can hold up to 60 conditions, so you can build fairly precise groupings from tags, product type, vendor, price and metafields.

Using tags for filtering and automated collections

This is where tags earn their place. Two uses matter most.

Storefront filters

In the Search and Discovery app, go to Apps > Search and Discovery > Filters > Add filter and choose "Tags" as the source. Shoppers then see a filter group listing tag values on collection and search pages. A few limits worth knowing:

• A store can have up to 25 filters.
• Each filter shows up to 100 values on the storefront, and tag filters support up to 5,000 unique tag values.
• Filters are hidden on collections with more than 5,000 products.
• Tag filter values are not translated, so a multilingual store shows them in the default language only.

Because the tag text itself becomes the label shoppers read, a tag filter exposes every messy tag you have. If your tags include supplier codes, internal notes or three spellings of "cotton", shoppers will see all of them. For attributes like color, size and material, product options or metafields usually make better filter sources, since their values are structured and can be translated. Keep tag filters for simple groupings that do not fit elsewhere, like "Gift idea" or "Vegan".

Automated collections

Tags are the most flexible way to feed automated collections because you can add them to any product regardless of type or vendor. A new product tagged summer-edit appears in the Summer Edit collection the moment it is saved. That saves real time for stores that change merchandising every season.

How to clean up Shopify product tags

A tag clean-up is mostly careful bookkeeping. Before deleting anything, find out what depends on each tag, because removing a tag can silently empty a collection or switch off an app rule.

1. Export your products. Go to Products > Export, choose all products and a CSV format. The Tags column lists every product's tags separated by commas.
2. Build a tag inventory. Split the Tags column in a spreadsheet and count how many products use each tag. Sort by count.
3. Map dependencies. List every automated collection's conditions under Products > Collections. Check theme code for tag references (search the code editor for product.tags) and check app settings for tag-based rules.
4. Mark each tag. Keep, merge (for example Cotton, cotton and 100-cotton into one), or delete (supplier codes, one-off tags, tags on zero or one product with no dependency).
5. Add the new tags first. Select the affected products in the product list, then use More actions > Add tags. Update collection conditions to the new tag.
6. Remove old tags. Select the products again and use More actions > Remove tags. Tags that no product uses stop appearing in the admin tag list.
7. Check the storefront. Open each affected collection and filter, confirm the product counts look right, and recheck any theme badges or app rules.

For very large catalogs, re-importing a corrected CSV is faster than bulk actions, but it carries more risk: with overwrite turned on, blank non-required columns overwrite existing values. Our Shopify CSV import guide covers how to update only the columns you intend to.

A tag naming system that scales

Once the list is clean, write down rules so it stays clean. A simple convention is enough for most stores:

A few rules keep it from drifting:

• Lowercase, hyphen-separated, no spaces or symbols.
• One tag per concept. Decide once whether it is tshirt or t-shirt.
• Internal and operational tags use a prefix, so they are easy to exclude from a shopper-facing tag filter.
• No keyword stuffing. Tags are not SEO fields, so tags like best-cheap-shirts-usa add nothing.
• Review tags added by imports. Supplier and marketplace imports often bring their own tags. Strip or rename them during import.

With tags doing their proper job, put your SEO effort where it counts: product titles, descriptions, collection pages and technical hygiene. Our guides to writing Shopify SEO titles and meta descriptions and running a Shopify SEO audit are good next steps.