Collection strategy
Which collections should exist, be indexable and be linked, since collection pages carry most store revenue and duplication starts here.
What Shopify decides for you
Shopify enforces its URL structure — products under /products/, collections under /collections/ — and generates a product URL for every collection it appears in. It also limits server-level control, so redirects, headers and rendering behave differently from a self-hosted stack. None of that is negotiable.
The collection duplication is the most consequential of these. A product appearing in four collections generates four crawlable paths to the same item. Shopify canonicalises to the primary product URL by default, which mostly works, but link equity and crawl budget still spread across paths that were never intended to exist as separate pages.
The URL structure itself is fixed in a way that surprises teams migrating from other platforms. You cannot remove the /products/ or /collections/ segments, and attempting to work around it with proxies or redirects usually creates more problems than the shallower URLs were worth. Accepting it is the correct answer.
Apps are where most Shopify performance problems actually originate. Each installed app typically injects scripts into every page, and a store that has accumulated fifteen over three years is carrying most of that weight on every request — including from apps nobody uses any more but nobody removed.
The compensating advantage is that Shopify handles a great deal correctly by default. Hosting, security, mobile rendering and structured data basics are largely sound out of the box, which means the work concentrates on content, collection strategy and app hygiene rather than on infrastructure you would otherwise be rebuilding.
What the engagement covers
The engagement covers collection strategy and duplication control, an app audit measuring what each one costs, theme-level template fixes, structured data corrections, content work on collection and product pages, and a realistic assessment of which platform constraints simply have to be accepted.
Duplication control
Canonical behaviour across collection paths, tag pages and filtered views, so crawl budget concentrates on the URLs you actually want ranking.
App audit
What each installed app costs in performance and whether anyone still uses it. Usually the largest available win and rarely owned by anyone.
Theme template fixes
Heading structure, internal linking, image handling and markup corrected in the theme, so every product and collection inherits the fix.
Structured data corrections
Product and breadcrumb markup validated against what the theme actually renders, since theme updates frequently break it silently.
Constraint assessment
Which of your problems are Shopify decisions rather than mistakes, so effort is not spent trying to remove limitations that cannot be removed.
How the engagement runs
The engagement audits the store first, separating genuinely fixable problems from platform constraints. It then addresses collection strategy and duplication, audits the installed apps for their performance cost, and corrects theme-level templates so that every generated page inherits the improvement.
- 01
Separate fixable from fixed
Which problems are genuine mistakes and which are Shopify decisions. This distinction saves the most time, because teams routinely spend months on the second category.
→ An audit separating fixable from fixed
- 02
Sort out collections
Which collections exist, which are indexable, how products are assigned. Collections carry most store revenue and are where duplication originates.
→ A collection strategy, implemented
- 03
Audit the apps
Measure what each installed app costs on a real page load and whether it is still in use. Removing three unused apps routinely beats every other speed fix combined.
→ An app inventory with removal recommendations
- 04
Fix at theme level
Headings, internal linking, image handling and markup corrected in the theme so every product and collection page inherits it rather than being edited individually.
→ Theme-level corrections deployed
- 05
Validate and monitor
Structured data validated against rendered output, with a check after theme updates, since those routinely break markup without any warning.
→ Validated markup and an update check
What you can change and what you cannot
Knowing the difference is the single most useful thing about working on this platform. Teams migrating from more flexible stacks routinely spend months trying to remove constraints that are architectural, when the productive work sits entirely in the other column.
| Fixed by the platform | Genuinely fixable |
|---|---|
| /products/ and /collections/ URL segments | Which collections exist and are indexable |
| A product URL per collection it appears in | How products are assigned across collections |
| Limited server and header control | App weight and script load |
| Checkout structure on most plans | Theme templates, headings and internal links |
| Some redirect handling behaviour | Structured data accuracy |
Signals you need this now
You need this when your store is slow and nobody has audited the installed apps, when collections have multiplied without a strategy, when a theme update broke structured data, or when someone is proposing to fix the URL structure rather than work with it.
- The store is slow and nobody has audited installed apps
- Collections have multiplied without any strategy
- A theme update silently broke your structured data
- Someone is proposing to change the URL structure
- Products appear at several crawlable paths
- Collection pages are a product grid with no other content
- Apps remain installed that nobody in the business uses
What clients see
App removal usually produces the fastest visible improvement, since it reduces weight on every page at once. Collection strategy takes longer and matters more commercially, because collection pages target the terms with genuine demand and carry most of a store's organic revenue.
Where this fits
Related SEO services
Common in these sectors
The adjacent disciplines
Deciding between options
Questions about Shopify SEO
Each answer is written to stand alone in 40 to 60 words — the shape an AI Overview or Perplexity citation lifts. Ships with FAQPage schema.
Can we remove /collections/ from our URLs?
No. It is architectural rather than configurable, and workarounds through proxies or redirects create more problems than shallower URLs are worth. Teams migrating from flexible platforms routinely spend months on this before accepting it, which is time better spent elsewhere.
Why is our Shopify store slow?
Almost always apps. Each one typically injects scripts into every page, and a store carrying fifteen accumulated over several years is loading all of that on every request — frequently including apps nobody uses any more but nobody removed.
Do products appearing in several collections cause duplicate content?
Shopify canonicalises to the primary product URL by default, so the duplication is mostly handled. What is not handled is crawl budget and link equity spreading across paths that were never meant to exist as separate pages, which is worth controlling deliberately.
Should we move off Shopify for SEO reasons?
Rarely. The constraints are real and mostly cosmetic, while the platform handles hosting, security and rendering well by default. A replatform carries genuine migration risk, and we would want a much stronger reason than URL structure before recommending one.
Why did our structured data break?
Theme updates are the usual cause. Product and breadcrumb markup lives in theme templates, so an update can change or remove it silently. This is why we validate against rendered output and add a check that runs after theme changes.
Do collection or product pages matter more?
Collections, for most stores. They target the terms with real search demand while product pages capture high-intent long-tail. Most Shopify stores invest the reverse of that, which makes collection strategy the usual location of the largest available gain.
Find out whether this is your constraint.
Thirty minutes with a senior strategist. We pull your live visibility while we talk and tell you plainly whether a Shopify SEO is what you need — or whether your problem sits somewhere else.