Shopify allows product access via both /products/handle and /collections/collection-handle/products/handle. While canonical tags help SEO, indexed collection-scoped URLs require true 301 redirects—but Shopify’s native redirect system ignores these dynamic paths, and Liquid/JS cannot issue real 301s.
Visit: domain/collections/collection-name/products/product-handle → page loads with 200 OK
In Shopify Admin → Online Store → Navigation → URL Redirects, add:
a. Redirect from: /collections/collection-name/products/product-handle
b. Redirect to: /products/product-handle
c. Type: 301
Save and reload the old URL → no redirect occurs (still 200 OK)
Try JS/Liquid redirect → works for users but still returns 200, not 301
Additional info
Theme: Confirmed canonical tag is present:
Goal: Prevent duplicate content & preserve SEO equity from backlinks to collection URLs
Workarounds tried:
JS redirect in theme.liquid → user-friendly but not SEO-safe
robots.txt block (Disallow: /collections//products/) → helps long-term but doesn’t redirect
Shopify limitation: Dynamic routes like /collections//products/* are not real pages, so native redirects don’t apply
Question: Is there any server-side or edge-based method (without heavy apps) to force real 301s?
Shopify redirects do not work if original URL can be rendered/shown.
The only way to (maybe) avoid these collection-aware links from being crawled is to not generate them. So basically, have only canonical product URLs output on collection pages – some themes have a setting in the theme for this.
You can go headless or maybe implement some kind of logic with Cloudflare services.
Shopify doesn’t support or allow you to create nested url structure, and redirects are limited to pages that don’t exist. Sounds like you need to go through your theme code and get rid of unsupported site structure.
Shopify’s online sales channel does NOT have this feature.
Merchants that want control over a shopify-stores URL structure need to go headless with storefront SDK, or hydrogen, etc and be their own host.
READ: $$$$
@deenajacob These are some of the many time & money wasting habits new merchants make don’t make a habit of it:
Don’t bury the lead in communications, open with the question UPFRONT.
This isn’t a bar no need to be coy. ib4: no, don’t just rely on the title for the ask
Avoid self-prescribing a solution with an inexperienced diagnosis , e.g. https://xyproblem.info/
What is the actual goal, redirects aren’t a goal they are an implementation you self prescribed ignoring your own listed goal:
“Prevent duplicate content & preserve SEO equity from backlinks to collection URLs”
which is just canonical urls, don’t overcomplicate things before talking to an expert first.
that’s because you can only redirect pages that return a 404 page with shopify’s native functionality of setting up 301 redirects. if your aim is to go beyond that functionality, you might have to use Shopify redirect apps that allow you to redirect active (webpages that return 200 OK) pages.
and I am personally not aware of any server-side tweaks that you can make. at the most, i feel you will have to use an app to solve your issue.
Yes, I haven’t removed or deactivated those URLs—they still exist and return a 200 OK status (since Shopify treats /collections/x/products/y as a valid product page).
What I have done is stop generating new links to them by removing | within: collection from all product card links. So going forward, internal navigation only uses the canonical /products/y URLs.
I understand Shopify’s native redirects only work for 404s, and I’ve also read that most redirect apps use client-side (JavaScript/meta refresh) redirects for active pages—which don’t pass SEO equity like true 301s.
Given that Shopify already sets the correct canonical tag on all product pages (always pointing to /products/y, even when accessed via a collection), my current plan is to rely on canonicalization + clean internal linking and let search engines handle the rest over time—unless there’s a server-side method I’m missing.
Just to clarify: the /collections/x/products/y URLs aren’t something I added via theme code — they’re Shopify’s default behavior when a product is viewed from within a collection. The platform fully supports (and generates) these URLs natively.
My goal isn’t to “fix” an unsupported structure, but to avoid duplicate content, since both /products/y and /collections/x/products/y return the same product (with the same canonical tag pointing to /products/y).
I’ve already updated the theme to stop linking to the collection-scoped URLs (by removing | within: collection), so new links won’t be created. Now I’m just confirming whether further action (like redirects) is needed — or if relying on Shopify’s canonical tags is sufficient.
Thanks, @tim_tairli — that’s a really clear summary.
Just to confirm: I’ve already updated the theme to stop generating collection-scoped product URLs on collection pages (removed | within: collection from all product card links), so going forward, only the canonical /products/y URLs are being linked internally.
My remaining question is about the already-existing/collections/x/products/y URLs:
They’re still accessible (return 200),
They were likely crawled/indexed in the past,
But Shopify correctly sets the canonical tag to /products/y.
Given that, is it safe to rely solely on canonicalization (plus clean sitemaps), or would you still recommend exploring Cloudflare/edge logic or headless for true 301s?
My instinct is that for most stores, canonicals are sufficient — but I’d love your take!
The URL structure /collections/x/products/yisn’t something I created manually or imported. It’s actually Shopify’s built-in behavior:
When you visit a product from within a collection page, Shopify automatically serves the product at /collections/{collection-handle}/products/{product-handle}.
This is not a nested collection (like /collections/mens/shoes), but a collection-scoped product URL — and it’s fully supported by Shopify.
Example:
On any Shopify store (even demo stores), go to a collection → click a product → the URL will be: https://yourstore.com/collections/hoodies/products/winter-pullover
…even though the canonical tag on that page points to: https://yourstore.com/products/winter-pullover
You can’t disable this routing in the Shopify Admin — it’s part of how the platform works.
As you rightly said: as long as the canonical tag is correct (which Shopify handles automatically), duplicate content isn’t an SEO issue. I’ve just been double-checking whether redirects are needed — but consensus (and Shopify docs) say they’re not.
Hope that clears it up! Happy to share a live example if helpful.
Glad we cleared that up. We’re talking about the same thing: content-aware url. Completely normal behavior. Maybe a little strange if you’re not used to it. So you don’t need to do anything. Should be all good… No need for seo worries.
I tend to think that canonicals should be ok doing their job.
The only problem with huge amount of URLs is crawl budget.
People freak out when they go to Google search console and see, say 200 000 “Alternate page with proper canonical tag” and try to “Fix” it, but in fact there is nothing to fix.
It means Google already learned that those URLs lead to the pages which are already indexed. Would Google continue re-crawling those? That’s the question.
Yes, preventing this would probably be the right thing to do, but if they are already crawled there is not much we can do.
You may try blocking those with robots.txt or “noindex” meta, but as far as I know, those are not strong enough.
Unfortunately, we can’t do proper 404/301 at will and headless/Cloudflare solutions would cost serious money which IMO can be spent elsewhere with better ROI.
Also – I’d rather amend the “Related Products” URLs as well as they are known to generate tons of URLs.
(However, I am not a SEO strategist, rather a theme dev).
@tim_tairli
Totally agree — and thanks for highlighting the crawl budget angle. That’s the only real concern here, not duplicate content (since canonicals are solid).
I’ve also seen those “Alternate page with proper canonical tag” reports in GSC and initially panicked too — but you’re right: it just means Google understands the relationship and has already indexed the canonical.
Good point about Related Products — we’ve already updated those sections to use only canonical product URLs (no | within: collection anywhere), so we’re not adding to the issue going forward.
And yes, blocking via robots.txt or noindex isn’t ideal:
robots.txt blocks crawling but not indexing,
noindex on collection-scoped pages could conflict with canonical signals.
So for now, we’re sticking with: Clean internal links (canonical-only), Trusting Shopify’s canonical tags, Letting Google naturally deprioritize the collection-scoped versions over time.
And absolutely — headless or Cloudflare redirects aren’t worth the ROI for this. Better to focus energy on content, speed, or conversion.
These URL params are used to fine-tune your recommendations, so stripping them may affect recommendations precision, but obviously there is a huge potential to exhaust your crawl budget.
I’ve written about this here – Removing URL parameters - Recommended Products Section
The idea was to move URL params to the data attribute on the link so that href points to the canonical URL, but when clicked, JS code will pull these parameters from the data attribute and redirect visitors to full URL.
This way crawler sees only canonicals but recommended products fine-tuning works too.
Example:
— but you’re right: it just means Google understands the relationship and has already indexed the canonical.
Clean internal links (canonical-only),