Shopify SEO — working with the platform's constraints, not against them

Shopify makes a set of decisions for you that you cannot fully override, and most Shopify SEO problems are those decisions meeting a catalogue they were not designed for. This page is about the platform’s specific constraints — what you can change, what you have to work around, and what is not worth fighting.

The URL structures Shopify imposes

Shopify generates several addresses for the same product, and the duplication is structural rather than accidental:

• /products/handle — the canonical product URL.
• /collections/x/products/handle — the same product reached through a collection. Shopify canonicalises these to /products/, which is correct, but internal links and sitemaps do not always agree with the canonical, and that inconsistency is what leaks crawl budget.
• Variant parameters — ?variant= multiplies addresses for one product page.
• /collections/all and automated collections, which can reproduce most of the catalogue under a second set of paths.

The work is not “remove duplicates” — you cannot. It is making the canonical signal, the internal link graph and the sitemap all name the same address, so the platform’s own canonicals are reinforced rather than contradicted.

Faceted navigation and tag filters

Shopify’s filtering commonly produces crawlable parameter URLs — by size, colour, price, availability. A modest catalogue generates thousands of combinations, nearly all of them thin and near-identical, and a store can quietly end up with more filter URLs than products.

The decision is per facet, not global: a facet with genuine search demand and distinct inventory can deserve an indexable landing page; a facet that only permutes an existing set should not be indexable at all. Getting this wrong in the permissive direction is the single most common cause of a Shopify store with a large “crawled – currently not indexed” count.

Collections are the ranking surface — and are usually empty

For most category-level commercial queries the collection page is what competes, not the product. Yet the default Shopify collection is a grid with a title and no text, because the theme has nowhere obvious to put any. Adding useful content above or below the grid — what the category covers, how to choose between the options, what varies — is usually the highest-value on-page change available in a Shopify build, and it is a theme edit, not a plugin.

Product pages

Supplier descriptions duplicated across every retailer selling the item are the norm, and the reason many product pages never rank. Specifications, genuine use guidance, and honest fit-and-limitation notes are what differentiate them. Where a catalogue is too large to rewrite, prioritise by revenue and by search demand rather than attempting all of it.

Theme, apps and performance

Shopify’s hosting is fast; Shopify themes frequently are not. Performance problems here are usually accumulated app injections — review widgets, upsell scripts, chat, analytics, each adding render-blocking work to every template. Because apps inject globally, the fix is usually an audit of what is loaded where, not a single optimisation. Removing two unused apps regularly beats every micro-optimisation available in the theme.

Structured data on Shopify

Most themes ship some Product markup and many ship it incompletely — missing availability, price currency, or a review aggregate that does not correspond to visible reviews. Marking up reviews the page does not display is a policy violation, not an optimisation. We validate what the theme actually emits rather than what its documentation claims.

What we do on a Shopify engagement

1. Index inventory. Establish which of the platform’s generated URL families are indexable, which are indexed, and which should be neither.
2. Canonical and internal-link agreement. Make links, sitemap and canonical name one address per product.
3. Facet policy. Decide indexability facet by facet against real demand.
4. Collection content. Give the pages that carry category queries something to rank with.
5. Product differentiation, by priority. Revenue and demand first.
6. App and theme performance audit. Attribute cost to specific injections.
7. Structured data validation against visible content.
8. Measurement by URL family, so collection, product and filter performance are visible separately.

What is not worth fighting

Shopify does not give you server-level control of everything. /collections/x/products/ paths will keep being generated; the platform canonicalises them and that is sufficient. Trying to eliminate them, or replicating a WordPress-shaped architecture on Shopify, wastes budget that belongs on collection content and facet policy.

Shopify or WooCommerce?

They fail differently. Shopify’s constraints are fixed and its defaults are mostly sane — you work within a known shape. WooCommerce gives you full control and therefore full responsibility: its problems are usually plugin interactions and configuration drift rather than platform structure. If you are on Shopify, this is your page; the WooCommerce work is genuinely different and we do not run the same checklist on both.

Broader category work sits on ecommerce SEO, and platform-independent crawl and indexation work on technical SEO.