Discussion starter: an ecommerce SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- eCommerce SEO
- Indexing
- Shopify SEO
Shopify’s collection-scoped product URLs: did fixing theme links to point at canonical product URLs change anything you could measure?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
Pointing theme links at the canonical
/products/URL does change things you can measure, but mostly crawl and indexing housekeeping rather than rankings. The signals that move reliably are internal-link consistency (immediately), the share of Googlebot requests hitting/collections/.../products/...URLs (over weeks), the count of URLs reported as “Alternate page with proper canonical tag” (slowly, over months) and, where it was happening, Google choosing a collection-scoped URL as canonical. A traffic or revenue uplift you can attribute to the fix is much less common, because Shopify already canonicalises those URLs and Google usually honours that.The fix tends to matter more on large catalogues where products sit in many collections, where Google has been choosing non-canonical URLs, or where new products are slow to be crawled. On a few-hundred-product store with clean canonicals, expect a tidier crawl and not much else. It is still worth doing, because it is cheap and removes a conflicting signal, but it should not be sold internally as a growth project.
What Shopify is doing with these URLs
Every collection a product belongs to gives it another address:
/collections/{collection}/products/{product}. Themes create these links with the Liquidwithinfilter, which Shopify’s reference describes in one line: “Generates a product URL within the context of the provided collection.” Shopify’s own documentation carries the warning: “Because a standard product page and a product page in the context of a collection have the same content on separate URLs, you should consider the SEO implications of using thewithinfilter.”Automated collections make this multiply quickly. A product that sits in eight collections (plus the catch-all
/collections/all) has around ten addresses for one page. Shopify’s default canonical tag points each of them at/products/{product}, and the generated sitemap lists only the/products/versions. The conflict comes from the theme: every collection grid links to the scoped version, so internal links (often thousands across a store) point one way while the canonical and sitemap point the other.Think of a shop with a sign saying “all enquiries at the front counter” while every arrow on the floor points to a side door. Most people still end up at the counter, but you have given them a reason to hesitate. Technically, Google treats rel=canonical as a strong hint rather than a directive and weighs it against other signals, including internal links. Usually the canonical wins. Sometimes, especially where the scoped URL has external links or far more internal links, Google picks the scoped URL instead.
Dawn, Shopify’s reference theme for several years before Horizon became the default in 2025, links product cards to the plain product URL, so the problem mostly lives in older themes, some third-party themes and custom sections. Check the card snippet in whatever theme you run rather than assuming. Apps are a common leftover source: related products, quick view, recently viewed and search widgets can all output scoped links after the theme is fixed.
What the public evidence says
Very little of it is measured. Amsive’s 2019 write-up reported seeing collection-scoped URLs rank despite being canonicalised, showed the theme edit (replacing
product.url | within: collectionwithproduct.url), and cautioned that rankings might dip temporarily while Google reassesses. It did not publish before-and-after data. That is typical: plenty of how-to guidance, very few datasets. So the honest position is that the crawl and canonical effects are predictable from the mechanism, while ranking effects are store-specific and need to be measured rather than assumed.What you can measure, and roughly when
The timings below are rough expectations based on how recrawling works, not benchmarks.
Metric Where to see it Expected change Rough timing What a surprise would mean Internal links to scoped URLs A site crawl before and after Near zero from the theme Immediately Leftover links from apps, search results, breadcrumbs or recommendation widgets Googlebot requests to scoped URLs Crawl stats report (totals and example URLs); logs only if you have your own proxy or CDN layer A declining share of requests Weeks No decline after two months: external links, feeds or apps still reference them “Alternate page with proper canonical tag” Page indexing report Slow decline, may plateau Months A plateau is normal; Google remembers URLs it has seen Google-selected canonical URL Inspection on a product sample; “Duplicate, Google chose different canonical than user” Mismatches resolve to /products/Weeks to months Persistent mismatches: check external links, redirects or content differences Impressions attributed to scoped URLs Performance report, page filter containing /collections/and/products/Falls towards zero, shifting to /products/URLsWeeks Scoped URLs still earning impressions means Google still treats some as canonical Product page clicks and impressions Performance report, treatment versus comparison groups (below) Little on clean stores; gains where mismatches existed One to three months Broad gains across all products usually mean something else changed too Time for new products to be crawled URL Inspection “last crawl” on new launches Faster on large catalogues if crawl was stretched Months No change: crawl was never the constraint Watch for this:
Shopify does not give merchants raw server logs, so the cleanest crawl evidence is usually unavailable. Search Console’s Crawl stats report shows totals and example URLs, not a full breakdown by path. Plan to rely on URL Inspection samples and the Performance report page filter, and set expectations accordingly.
Designing the before-and-after so the result means something
A theme link change is sitewide, so a clean split test is not possible. You can still build comparison groups that make the result more than a before-and-after chart.
- Take a baseline first. Crawl the site, export internal link counts to scoped URLs, and use URL Inspection (or its API) to record the Google-selected canonical for your top products and a random sample of the rest. Capture four to eight weeks of Performance data by page.
- Build a dose-response comparison. Group products by how many collections they belong to. Products in one or two collections had little duplication; products in eight or more had a lot. If the fix matters, gains should concentrate in the many-collection group.
- Flag the products where Google chose a scoped URL. These are where a ranking effect is most plausible, because consolidation actually changes which URL holds the signals.
- Deploy in one release and annotate it. Search Console’s custom annotations make the date visible to everyone reading the report later.
- Log confounders. Core updates (Google completed a March 2026 and a May 2026 core update), sales events, collection restructures, new apps and theme releases can all land in the same window.
Hypothetical example:
A store has 4,000 products, and tag-based automated collections put the average product in six collections, so there are roughly 24,000 scoped addresses for 4,000 real pages. URL Inspection on the top 200 products shows 11 where Google selected a scoped URL as canonical. After the fix, crawl examples shift towards
/products/URLs within a few weeks, and nine of the 11 mismatches resolve within two months.The useful reading: watch those 11 products and the many-collection group against the few-collection group. If only the mismatched products gain, the fix worked where it had something to fix. If every product gains equally, look for another cause before crediting the theme edit.
The trade-off: losing collection context
Scoped URLs exist for a reason. Themes use the collection context for breadcrumbs, “back to collection” links, previous and next navigation within a collection, and collection-specific product templates. Removing
withinremoves that context from the URL, which can hurt navigation on stores where people browse deep collections.You can usually keep the user experience without the URL. Common approaches are a breadcrumb built from a primary-collection metafield, a back link that uses browser history, or storing the last-viewed collection client-side while keeping the link itself pointed at
/products/. Check add-to-cart rate from collection pages before and after, because a crawl win that costs conversion is not a win.Two things not to do. Do not block scoped URLs in robots.txt: Google then cannot see their canonical tags, and any external links to them stop consolidating. And do not expect to redirect them: Shopify’s URL redirects only apply when the old path no longer resolves, and these paths always resolve.
A practical position
If this were my store, I would make the change, because it costs a theme edit and removes a signal that contradicts your own canonical tags. I would measure it as a crawl and canonicalisation fix first: scoped internal links at zero, scoped URLs fading from Crawl stats examples and the Performance report, and Google-selected canonicals matching yours. I would only claim a traffic effect if the products that were actually affected (many collections, or a scoped URL chosen as canonical) outperform the products that were not. If canonicals were already being honoured everywhere, a flat traffic line is the expected result, not a failed fix.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.