Shopify Agency UK: Fixing the SEO Problems Shopify Creates by Default

Shopify decides several things for you that other platforms leave open, and each decision has an SEO consequence. Shopify gives every product two live addresses, one under /products/ and one under each collection it sits in. Shopify builds your sitemap automatically, so you cannot simply delete an entry you do not want indexed. Shopify turns filters into new URLs. And your theme, written in a language called Liquid, decides where your category text actually appears in the page code. Fixing any of these means editing Liquid, not just rewriting page titles.

Shopify publishes every product at /products/your-product, and again at /collections/your-collection/products/your-product for each collection the product belongs to. A product in five collections is therefore reachable at six addresses showing identical content. Google treats near-identical pages as a set and picks one itself unless you tell it which to prefer, and it warns that crawling duplicate versions uses time it could spend on new or updated pages instead. The fix is a correct canonical tag in your Liquid theme pointing every collection-scoped copy back to the single /products/ address.

Mostly, but not always. Shopify exposes a Liquid object called canonical_url that returns the canonical address for the current page, and well-built themes print it in the head of every template. Problems appear when a theme was heavily customised, when a page-builder app injects its own head markup, or when a developer removed the tag while fixing something unrelated. We check the rendered head of a product page, a collection page, a filtered collection page and a paginated page, because those four behave differently and a theme can get one right and the others wrong.

They can. Selecting a variant adds a query string such as ?variant=123456 to the product address. Every variant therefore has its own crawlable URL showing essentially the same product page with a different price or swatch selected. On a store where products carry many sizes and colours this multiplies quickly. We make sure variant URLs carry a canonical tag pointing at the clean product address, keep them out of the sitemap, and check Search Console to see how many have already been crawled before deciding whether anything more aggressive is needed.

Shopify covers the basics well. You get editable page titles and meta descriptions, an automatic sitemap, a redirect manager, and alt text fields on product images. Shopify does not decide your canonical strategy for filtered and variant URLs, does not stop filter pages eating crawl capacity, does not write category text, does not add structured data beyond basic product markup, and does not make your theme fast. Those all sit in the theme code or in your content plan. Shopify native SEO is necessary and genuinely useful. It is not sufficient on a store with a large catalogue.

The principles are identical but Plus removes some ceilings. Plus gives you deeper control of the checkout, more room in URL and redirect handling, and Shopify Markets for running several countries from one store. For UK Plus brands the work usually shifts towards scale problems: crawl capacity on catalogues in the tens of thousands of products, a separate business-to-business storefront that needs its own indexing rules, and hreflang if you sell outside the UK. Plus engagements are larger because the stores are larger, not because the method changes.

Faceted navigation is the filter panel on a category page: colour, size, price, brand. On Shopify each filter click produces a new address such as /collections/trainers?filter.p.m.colour=red. Google warns that filter systems built on URL parameters can generate effectively unlimited numbers of addresses, which spends crawl capacity on thin combinations instead of your real pages. We audit which filter URLs Google has already fetched, point them back at the parent collection with a canonical, and build a proper page only where a filter combination has genuine UK search demand behind it.

Collection pages carry the commercial searches, so they get the most attention. We edit the collection Liquid template so that a content block renders in the page code above the product grid rather than being pushed underneath it. That block holds one H1 carrying the category phrase, a short piece of writing specific to that category, and a small set of questions real buyers ask. We add breadcrumb structured data, check that pagination is crawlable, and confirm the collection appears in the sitemap. Each collection gets its own brief so no two read the same.

Because most themes put it there. A common Liquid pattern prints the product grid first and the collection description afterwards, sometimes inside a collapsed panel or a tab. A reader may never scroll to it and a crawler sees it as the least prominent text on the page. Moving it is a template edit, not a settings change: you relocate the description output so it renders before the grid in the page code, then confirm by viewing the raw source rather than the rendered page, because a tab can hide text that is technically present.

Most Shopify apps add JavaScript to every page whether that page uses the app or not. Review widgets, pop-ups, currency switchers, upsell tools and analytics tags each add requests and processing time. The result is a store where the theme is fine and the page still feels slow. We list every script the store loads, match each one to an installed app, and separate the ones that earn their weight from the ones nobody remembers installing. Removing a dead app is usually the single fastest speed improvement available on a Shopify store.

Google publishes three thresholds. Largest Contentful Paint should happen within the first 2.5 seconds of the page starting to load. Interaction to Next Paint should stay under 200 milliseconds. Cumulative Layout Shift should stay under 0.1. Google says achieving good Core Web Vitals aligns with what its core ranking systems seek to reward, which is a real signal but not a switch that lifts you up the results on its own. On Shopify the usual culprits are an unprioritised hero image, web fonts loading late, and app scripts.

The largest element on a Shopify collection or product page is almost always the hero or first product image, so we make the browser fetch it first. That means marking it as high priority in the Liquid template, letting it load normally rather than lazily, and serving it at a sensible size instead of a full-resolution original scaled down in the browser. We also set width and height on the image so the browser reserves the space before the file arrives, which stops the page jumping and helps Cumulative Layout Shift at the same time.

Four types as standard, all written into the theme rather than added by an app. Product markup with price and availability on product pages. Breadcrumb markup on collection and product pages so the site hierarchy shows correctly. Question and answer markup where a collection page carries a real, visible set of questions. Organisation markup on the homepage. Two rules we do not bend: the markup must describe something a visitor can actually see on the page, and we do not add review markup unless real reviews are displayed. Invented ratings are a manual action waiting to happen.

Large collections split across numbered pages, and each page gets its own address ending ?page=2 and so on. The old rel next and prev instructions are no longer used by Google, so the job now is simply making sure the paginated pages are reachable through real links, that each one canonicalises to itself rather than back to page one, and that the products on later pages are not orphaned. Pointing every paginated page at page one is a common mistake: it hides most of your catalogue from being crawled at all.

Only indirectly, which surprises people. Shopify generates sitemap.xml automatically from your published products, collections, pages and blog posts, and you cannot hand-edit it. The way to keep something out is to change its status rather than the file: unpublish it, remove it from the sales channel, or apply a no-index instruction in the theme head for the templates concerned. Filter and variant URLs are not listed in the sitemap anyway, so those are handled with canonical tags and internal linking rather than sitemap edits.

Month one is the audit and the quick wins. We crawl the store, pull your Search Console data covering impressions, clicks, coverage and Core Web Vitals, and read your sitemap. From that we produce a list of what is actually wrong, ordered by what will move first: duplicate and filter URLs and how many there are, collection pages with no text above the grid, missing or wrong canonical tags, structured data gaps, and searches where you already appear but nobody clicks. Then we start implementing rather than handing over a document.

Technical fixes tend to show first, usually six to eight weeks after they go live, because Google has to recrawl and reprocess the pages you changed before anything can move. Adding real text to collection pages usually takes two to three months to settle. Competitive category searches take longer and depend heavily on where you start and who you are up against. Anyone who gives you a firmer date than that is guessing. What we can promise is that you will see what changed each month and why.

Monthly, on organic revenue first and positions second, because a good position that sells nothing is not a result. Each report covers organic sessions and organic revenue from Search Console and your analytics, movement on the category and product searches we are working on, Core Web Vitals on your main templates, what we fixed during the month, and what is planned next with the reasoning. There is a call to walk through it. If something odd shows up in Search Console between reports, such as a coverage drop, we tell you then rather than waiting.

By treating redirects as part of the build rather than something to sort out afterwards. Before anything moves we take a full inventory of every address currently indexed and every address currently earning clicks. We map each one to its new Shopify address, implement those redirects as permanent single-hop redirects, and test them before launch rather than after. Then we watch Search Console coverage daily for the first fortnight, because that is when a missed pattern shows up and is still cheap to fix.

Three shapes, depending on what you need. A one-off technical audit if you have a developer and want to know what to tell them. A fixed-price block of milestones if you have a defined list of problems and want them fixed and finished. Or a monthly retainer if you want continuing work across technical fixes, collection content and reporting. Every engagement starts with the audit, because scoping work on a Shopify store without reading its theme and its Search Console data is guesswork. Everything is month to month with no annual lock-in.

Yes, and this is the main practical difference between us and a general SEO agency. Most of the fixes on this page are Liquid template edits: moving a description above a grid, correcting a canonical tag, adding structured data, changing how an image loads. An agency without Shopify developers can only write those down and hope your developer implements them correctly. We work on a duplicate of your theme, show you the change on a preview link, and publish only once you have looked at it.

Three things. Staff access to the Shopify admin with theme permissions, so we can read the Liquid templates and work on a duplicate theme rather than the live one. Access to your Google Search Console property, because that is where the real crawl and coverage evidence lives. And a short conversation about which categories actually make you money, since the highest-traffic collection and the most profitable collection are frequently not the same page and we would rather work on the second one.

A canonical tag is a line in the hidden part of a web page that says which address is the real one for this content. When the same product is reachable at six addresses, the canonical tag on all six points at the one you want in search results. Google describes it as a way to consolidate signals, meaning links and other evidence pointing at any of the copies get credited to the single preferred address instead of being split six ways. It is a strong hint rather than an instruction, so it needs to be consistent to be believed.

Crawl budget is the amount of fetching Google will do on your site in a given period. Small stores rarely have a problem. It starts to matter when the number of crawlable addresses is far larger than the number of real pages, which is exactly what filters, variants and collection-scoped product copies produce. The symptom to look for in Search Console is a large count of pages found and not indexed, or crawled and not indexed, alongside new products taking a long time to appear. That pattern is worth investigating; a low count is not.

Ecommerce SEO is the strategy: which categories to target, how to structure the site, what content earns links, how organic search fits alongside your paid channels. It applies whatever platform you are on. Shopify SEO is the platform layer underneath it: the specific technical behaviour of Shopify around duplicate addresses, filters, Liquid templates, apps and sitemaps. You need both. This page covers the Shopify layer in detail. Our ecommerce SEO page covers the strategy layer for stores on any platform, including Shopify.