How to Fix Duplicate Content on Shopify Collections

By the Lenoretech SEO Strategy Team · Reviewed by a senior SEO strategist · Last updated: June 2026

Shopify duplicate content on collections happens because the same product is reachable at /products/handle and at /collections/x/products/handle, and because filter and sort parameters spin up endless near-identical collection URLs. Shopify already adds a self-referencing canonical that points product URLs back to the clean /products/handle, so the real work is fixing collection pagination, filtered and sorted URLs, and the cases where your theme or apps break that default canonical. Below is the exact order I fix it in for client stores.

Why Shopify generates duplicate collection URLs in the first place

Shopify's URL architecture is convenient for merchandising and hostile to crawlers. When you assign a product to a collection, Shopify lets that product render under the collection path. A single t-shirt in five collections can be served at six different URLs. Add Shopify's native filtering (?filter.v.price.gte=), sorting (?sort_by=best-selling), and pagination (?page=2), and one collection of 200 products can expose several thousand crawlable URL combinations. Google does not see "one collection" - it sees a sprawl of pages with the same product grid in a slightly different order.

This matters because crawl budget on mid-size stores is finite. In audits I routinely see 70-80% of Googlebot hits landing on filtered or sorted parameter URLs that should never be indexed, while genuinely new products wait days to get crawled. The symptom in Search Console is "Duplicate, Google chose a different canonical than user" or "Crawled - currently not indexed" piling up on collection variants. If your store is showing those exact reports, work through the broader Shopify SEO guide to ranking on Google alongside this fix - duplicate content is only one of the technical blockers that keep stores from ranking.

Step 1: Confirm your product canonical is actually correct

Before changing anything, verify what Shopify is already doing. Open a product through a collection - for example yourstore.com/collections/sale/products/blue-tee - then view source and search for rel="canonical". On a clean theme it should read:

• <link rel="canonical" href="https://yourstore.com/products/blue-tee">

If it points to the /collections/.../products/... version instead, your theme or an app has overridden the default and that is your duplicate-content source. The fix lives in theme.liquid. Shopify outputs the canonical through the canonical_url object inside {{ content_for_header }}, so do not hardcode a second one - instead make sure no app or custom code is injecting a competing tag. If you genuinely need to force the clean product URL, the correct override is:

• {%- if template contains 'product' -%}
•   <link rel="canonical" href="{{ canonical_url }}">
• {%- endif -%}

Because canonical_url already resolves to /products/handle regardless of the collection path, this guarantees every collection-nested product points home. Remove any plugin that writes its own <link rel="canonical"> on product templates - two canonicals cancel each other out and Google ignores both. SEO apps that "manage canonicals" are the most common culprit I find on broken stores, so audit your installed apps before you blame the theme.

Step 2: Stop linking to /collections/x/products/y internally

Canonicals are a hint, not a command. The strongest signal you control is internal linking. If your collection grid links to /collections/sale/products/blue-tee, you are voting for the duplicate. Most Shopify themes use within: collection in the product loop, which is what generates the nested URL. Open your collection template (often product-grid-item.liquid or card-product.liquid) and find the link:

• Change <a href="{{ product.url | within: collection }}">
• To <a href="{{ product.url }}">

Dropping within: collection makes every product link resolve to the canonical /products/handle. You lose Shopify's "back to collection" breadcrumb behaviour in some themes, but you can rebuild that with a proper breadcrumb that uses the collection from the product's collections array. This one change removes the largest block of duplicate URLs on most stores and is the single highest-ROI edit in this guide. While you are in those template files, fix your overall link structure too - a clean internal linking strategy sends crawl equity to the canonical product and collection pages instead of leaking it into parameter sludge.

Step 3: Handle filtered and sorted collection URLs

Shopify's filter and sort parameters create the second wave of duplicates. A filtered view like /collections/shoes?filter.v.option.color=black is useful for shoppers but is thin, near-duplicate content for search. Your goals: let Google crawl the clean collection, ignore the parameter variants, and keep the parameter pages out of the index without nofollowing them to death.

The cleanest approach in 2026 is robots.txt disallow plus a self-referencing canonical. Shopify lets you edit robots through robots.txt.liquid (create it under your theme's templates if it does not exist). Add rules to block the parameter crawl paths:

• {%- for rule in robots.default_groups[0].rules -%}{{ rule }}{%- endfor -%} (keep Shopify's defaults)
• Then append: Disallow: /collections/*?filter*
• Disallow: /collections/*sort_by*
• Disallow: /collections/*?*q=*

Do not blanket-disallow /collections/*?page=* - paginated pages need to be crawled so deep products get discovered. For pagination, rely on the self-referencing canonical Shopify outputs on ?page=2 (it canonicalises each page to itself, which is correct modern behaviour) and ensure your <link rel="next"> is not the only discovery path. Internal links from the blog and parent categories should reach deep products directly.

Step 4: Decide which filtered pages deserve to rank

Blanket-blocking every filtered URL is a mistake when a filter maps to real search demand. "Black running shoes" or "men's leather wallets under ₹2,000" are queries people actually type. For those, do not rely on a parameter URL - build a dedicated collection with its own clean handle (/collections/black-running-shoes), unique intro copy, and a curated product set. That page is indexable, canonical to itself, and can outrank a competitor's parameter sludge.

The rule I give clients: if a filter combination has its own keyword and conversion intent, promote it to a hand-built collection with 150 or more words of genuine copy. If it is just a shopper convenience (sort by price, in-stock toggle), keep it out of the index via the robots rules above. This split is the difference between faceted navigation that earns rankings and faceted navigation that drowns your store. If you want to scale this into hundreds of demand-mapped collections systematically, the same logic underpins a sound programmatic SEO approach - just make sure every generated page clears the unique-content bar before it goes live.

Step 5: Add Product and CollectionPage schema to reinforce the canonical

Structured data does not fix duplicate content on its own, but it strengthens which URL Google treats as the entity. On product templates, output a Product schema whose url and @id use {{ canonical_url }}, never the collection-nested path. On collection templates, use CollectionPage with an ItemList of product canonicals. When your JSON-LD, your rel="canonical", and your internal links all name the same clean URL, Google has zero ambiguity about which page is the original. Mismatched schema URLs are a quiet way to undo everything you fixed in Steps 1 to 3 - I have seen a single hardcoded collection URL in a schema app re-trigger "Google chose a different canonical" reports. If you are unsure which types to emit, our breakdown of schema markup examples for ecommerce shows the exact Product and breadcrumb structures to copy.

Step 6: Validate and monitor in Search Console

Changes to canonicals and robots take days to weeks to reflect in the index, so do not judge by checking one URL the next morning. Use the URL Inspection tool on a collection-nested product URL and confirm the "User-declared canonical" and "Google-selected canonical" both resolve to /products/handle. Then watch the Pages report: the count under "Duplicate, Google chose a different canonical than user" and "Crawled - currently not indexed" should trend down over four to eight weeks as the parameter URLs drop out and crawl budget shifts to real products.

Two checks I run on every store after deployment. First, in Search Console's Crawl Stats, confirm the share of requests hitting ?filter and ?sort_by paths is falling - that is direct proof the robots rules are working. Second, fetch yourstore.com/robots.txt in a browser and verify your appended rules render correctly below Shopify's defaults; a Liquid typo in robots.txt.liquid can silently wipe out the whole file. Re-run a full crawl with Screaming Frog a month later and the duplicate clusters that started this project should be gone.

Putting it together

Fixing Shopify duplicate content is not one switch - it is removing within: collection from internal links, keeping the default product canonical clean, disallowing filter and sort parameters in robots.txt.liquid, promoting high-intent filters to real collections, aligning your schema URLs, and then verifying in Search Console. Do those six steps in order and you consolidate crawl signals onto the URLs that actually convert. For the wider technical and on-page items - speed, metadata, collection copy and image SEO - work through our Shopify SEO checklist for 2026 next. If you would rather hand the whole crawl-and-fix to a senior team, that is exactly what our Shopify SEO agency does for stores across India, the US and the UK.