Shopify Agency and SEO
Shopify removes the servers, not the decisions. Which theme, which apps, how collections are organised, what the templates output and what the checkout will not let you change all decide whether a store ranks and converts. We build and optimise Shopify stores, and we will tell you when it is the wrong platform.
What is included
- A platform check first: whether Shopify fits the catalogue, the checkout needs and the way you sell
- A theme or custom theme build, configured around your product data rather than the demo store
- An app review that keeps what earns its place and replaces or removes the rest
- Collection, navigation and URL rules written down before the catalogue is loaded
- Product, Offer and breadcrumb markup checked in the theme and validated
On this page
- What does a Shopify agency do, and who actually needs one?
- Should you use a Shopify theme or have a custom theme built?
- Should a Shopify feature be an app or custom code?
- Is Shopify good for SEO?
- What are Shopify's structural SEO limits, and how do you work around them?
- How do Shopify collections, tags and filters create duplicate content?
- How do Liquid templates and structured data affect Shopify SEO?
- What makes a Shopify store slow, and how do you fix it?
- How do you migrate a store onto Shopify without losing rankings?
- What can you not change about the Shopify checkout?
- When is Shopify the wrong platform?
- How do you choose a Shopify agency or a Shopify SEO agency?
- What drives the cost of Shopify development and SEO?
What does a Shopify agency do, and who actually needs one?
A Shopify agency builds, rebuilds and improves online stores on the Shopify platform. That means choosing or building the theme, deciding which apps belong, structuring collections and URLs for search, moving a store across from another platform, and fixing whatever slows it down or stops it converting. It is for retailers who have chosen Shopify or are about to.
Plenty of stores do not need one. A small catalogue on an unmodified theme, managed by someone comfortable in the Shopify admin, can trade for years without outside help. The point at which an agency earns its fee is usually one of four: the theme has stopped fitting the business, apps have piled up and the store has slowed, the catalogue has outgrown its collections, or the store is about to be replatformed.
We do this work as part of our wider e-commerce development practice, which also builds on WooCommerce and custom. That is the reason to ask us rather than an agency that only works on one platform: our advice about whether to use Shopify does not depend on whether we get paid to build on it. The platform-neutral search work sits on the e-commerce SEO page.
Should you use a Shopify theme or have a custom theme built?
Use a configured theme when your catalogue and brand fit one with modest changes, and build a custom theme when the changes would touch most of the templates. A theme is cheaper to build and easier to keep updated; custom is a larger invoice and a larger maintenance responsibility. The table sets out where each route fits.
| Route | What it is | Choose it if | Watch for |
|---|---|---|---|
| Configured theme | A theme from Shopify's theme store, set up with your sections, navigation, metafields and brand, without editing its code. | The catalogue is straightforward, the layout the theme gives you is close to what you want, and you want updates from the theme's author to keep flowing. | Every store on the same theme looks and performs similarly, and settings you cannot change are settings you live with. |
| Customised theme | A theme whose code has been edited: new sections, changed templates, altered markup, added features. | Most of the theme is right but a handful of templates need to behave differently, such as product pages with unusual data. | Once the code is edited, theme updates have to be merged by hand, and the edits need documenting or the next developer inherits a puzzle. |
| Custom theme | A theme built to your design and your product data, using Liquid and Online Store 2.0 sections, with only the code the store needs. | Your product data needs layouts no theme provides, performance matters, or customising a stock theme would mean rewriting most of it anyway. | A larger build and a permanent maintenance responsibility. It only pays back if the store has needs a theme cannot meet. |
| Headless storefront | A separate front end drawing on Shopify as the commerce engine. Our website development service covers headless builds in general. | The storefront has to do things Shopify's own theme system cannot, and you accept the cost of building and running two systems. | Server rendering, search markup, cart behaviour and apps that expect a theme all become your problem. Justified less often than it is sold. |
Should a Shopify feature be an app or custom code?
Use an app when the function is mature, isolated and light, such as reviews or subscriptions. Write custom code when an app would add weight to every page, duplicate markup the theme already outputs, or charge a monthly fee for something small. The decision is made feature by feature, not as a policy.
| Feature | Usually better as | Why |
|---|---|---|
| Product reviews and ratings | An app, with its markup checked | Collecting, moderating and showing reviews is real functionality. The risk is the app adding its own Product markup beside the theme's, so the two disagree. |
| Subscriptions and recurring orders | An app | Failed payments, pauses and changes are fiddly to get right, and the checkout limits what custom code can do here. |
| Currency, language and market switching | Shopify's own tools first, an app only to fill a gap | These touch every URL and every price. A plan for international search comes before choosing the tool. |
| Product badges, labels and simple banners | Custom code in the theme | A small piece of Liquid and CSS does the job. An app does it with its own script on every page and a recurring charge. |
| Product filtering and search | Shopify's native filtering, then an app if the catalogue needs more | Filtering decides which URLs exist, so choose it with search in mind. An app that rewrites filter URLs can undo your rules. |
| Redirect management | Shopify's own redirects, with an app for bulk work | The native tool is enough for a handful. A migration with thousands of redirects needs bulk handling and a clean import. |
| Structured data and SEO fields | The theme | Markup belongs in the template. An app layering a second set on top is the most common cause of duplicate or conflicting product markup. |
| Tracking pixels and marketing tags | A single tag manager, kept tidy | Each tag added directly to the theme is another script on every page, including the ones behind paid campaigns. |
Is Shopify good for SEO?
Mostly, yes. Shopify provides hosting, an automatic XML sitemap, canonical tags, SSL, mobile-friendly themes and editable titles, descriptions and redirects without any plugin or server work. A well-configured Shopify store can rank as well as one on any other platform. What decides the outcome is the structure and the theme, not the platform.
The strengths are real. Stores are served from infrastructure Shopify runs, so slow servers, expired certificates and unpatched software are not your problem. The sitemap updates itself as products and collections change. Pages are rendered on the server, so the content is in the HTML a crawler receives. And the admin lets a non-technical owner edit the fields that matter without touching code.
The limits are structural, and they are the subject of the next few sections. Shopify decides the shape of your URLs, lets one product be reached by several paths, and generates collection views you did not plan. None of that stops a store ranking. It means the work is configuration and template discipline, which is what we mean by technical SEO on a store, not a case of installing an app and hoping.
The point
The limits are structural, and they are the subject of the next few sections.
What are Shopify's structural SEO limits, and how do you work around them?
Shopify fixes its URL prefixes, serves a product on more than one path, generates collection views from tags and filters, and limits direct control of the sitemap and robots rules. Each can be managed in the theme or the structure. The table lists the limit, what it causes, and the usual remedy.
| Limit | What it causes | Usual remedy |
|---|---|---|
| Fixed URL prefixes: /products/, /collections/, /pages/ and /blogs/ | You cannot shorten or remove them, so URLs carry a prefix whether or not it helps. | Accept the prefix and put the effort into the handle, which you can control. Keep handles short, readable and stable once set. |
| A product reachable at /products/handle and under each collection it belongs to | The same page exists at several addresses, and internal links pointing to the longer path can dilute signals. | Themes normally set a canonical tag to the /products/ address. Check yours does, and link internally to the canonical path. |
| Tag-filtered collection views | Every tag can produce a collection URL with the same products as the parent in a different subset. | Decide which tags earn a page. Stop the rest being linked, and check how your theme sets canonical and noindex on them. |
| Filter and sort parameters in the URL | Filtering and sorting create parameter URLs that multiply with every combination. | Control crawling and indexing of parameter URLs through the theme, canonical tags and robots rules written to the real pattern. |
| Built-in system collections and pages, such as all-products and vendor views | Pages that exist because the platform makes them, whether or not you wanted them. | Decide whether each should be indexed, redirected or kept out of search, then apply that consistently. |
| An automatic sitemap you cannot edit directly | You cannot hand-pick URLs for the sitemap file. | Fix the underlying pages instead: noindex or remove what should not be there, so the sitemap reflects the right set. |
| Robots rules edited through a theme template | Changes sit in theme code, so they can be lost or overwritten if the theme is replaced. | Keep the customised file documented, test it after every theme change, and use it sparingly. |
| A basic blog structure | Limited categorisation and few built-in content tools compared with a content-led platform. | Use collections, internal links and clear article structure. If content is the engine of the business, weigh WordPress for content-led sites. |
How do Liquid templates and structured data affect Shopify SEO?
Shopify themes are written in Liquid, and the theme templates decide what appears in the HTML: the title tag, the headings, the canonical link, the breadcrumbs and the Product markup. If the template outputs the wrong thing, every page using it is wrong. That is why Shopify SEO is largely theme work.
Many themes output Product and Offer structured data themselves, drawing price, currency and availability from the same product record as the visible page, which keeps the two in agreement. The usual fault is duplication: a review app adds its own Product markup, a second app adds another, and the page ends up with competing descriptions of the same product. The fix is to choose one source, normally the theme, and make the others stand down.
Check three things on any store. First, view the rendered page and confirm there is one Product block, not three. Second, confirm the price and availability in the markup match what a shopper sees, including for a sale item, a multi-variant product and one that is sold out. Third, confirm the title and heading templates pull from fields you can edit. A store whose crawl and indexation have been reviewed once by someone who reads theme code is in a very different position from one that was only checked in a browser.
The point
First, view the rendered page and confirm there is one Product block, not three.
What makes a Shopify store slow, and how do you fix it?
Apps, theme scripts, unoptimised images and third-party tags make a Shopify store slow. Shopify's servers rarely do. Fixing it means measuring which scripts load on which pages, removing what does not earn its place, and correcting images and fonts. Most of the cost is added after launch, one app at a time.
- Apps load code on every page. Even an app used on one template can inject scripts and styles across the whole store. Audit what each app loads, and where it loads it.
- Uninstalling an app does not always remove its code. Leftover snippets in the theme can keep loading after the app is gone. Search the theme files for them after removal.
- Tracking and marketing tags pile up. Chat, consent, heatmaps and advertising pixels all compete for the same main thread, which hurts how quickly the store responds to a tap. Keep them in one tag manager and prune it.
- Images are usually the heaviest asset. Serve correctly sized images in modern formats with set dimensions, load those below the fold lazily, and never lazy-load the first large image on a page.
- Fonts and sliders cost more than they look. Fewer font files and a single static hero image often beat a slider that loads every slide up front.
- Measure what real visitors experience. Core Web Vitals field data in Search Console shows what customers get, which a single lab test on a fast laptop does not. What the Core Web Vitals measure explains the targets.
- Speed is a conversion issue first. It decides whether someone sees the product at all.
How do you migrate a store onto Shopify without losing rankings?
Write the URL map first, before anything moves. Every product, collection, page and article gets an old address and a new one, with a 301 redirect for each. Then move and reconcile the data, test on a development store with real products, and watch indexation afterwards. Moving without redirects is what causes lasting damage.
- Map every URL. Shopify's /products/, /collections/, /pages/ and /blogs/ prefixes will not match the old platform, so almost every address changes. Export the old URLs from the live site, the sitemap and Search Console, not from memory.
- Redirect all of them, including the low-traffic ones. Shopify's redirect tool takes a bulk import. Test the redirects on staging and again at launch. The wider method is in the SEO migration checklist.
- Rebuild the structure deliberately. Do not copy the old category tree if it does not suit Shopify's collection model. Decide what each collection targets and what happens to old tags and filters.
- Move the data and reconcile it. Products, variants, images, customers, orders and reviews should be exported, cleaned, imported and counted against the source. Customers generally have to set a new password, so tell them before launch.
- Check what the reviews are stored in. If reviews sit in an app, confirm they can be exported and what the new markup will show. Review stars in search results are slow to rebuild.
- Keep the content that was ranking. A redesign tempts you to trim the copy. Compare what the old pages said with what the new templates will say, and carry across whatever was earning.
- Keep watching after launch. Check indexation, errors in Search Console and revenue against the baseline. A short dip is normal; a lasting fall means something in the map was missed.
- Moving from WooCommerce is a common case, and whether to move at all is a separate question worth settling first.
What can you not change about the Shopify checkout?
Much less than you can on a self-hosted platform. Shopify controls the checkout, and how far it can be customised depends on your plan and on Shopify's current checkout framework, which has changed over the years. Branding and some added features are possible. Rebuilding the flow, or changing the order of its steps, generally is not.
That is a deliberate trade. Shopify takes responsibility for payment security and for a checkout it has tested heavily, and in exchange you accept its limits. For most retailers that is the right bargain. It becomes a problem when the business depends on something the checkout does not do: quote-based ordering, per-customer pricing and credit terms, configurable products with dependencies, or a payment flow that does not fit its model.
Because the rules shift, do not rely on what any agency remembers. Write down what the checkout must do, then check it against Shopify's documentation for your plan on the day you decide. If the requirement is at the edge, it is often cheaper to learn that before the build. For the checkout as a conversion problem rather than a platform one, see our conversion work.
The point
Write down what the checkout must do, then check it against Shopify's documentation for your plan on the day you decide.
When is Shopify the wrong platform?
Shopify is the wrong platform when your commerce logic is unusual enough that you would fight it, when content drives the business and you want to own the code, or when platform and transaction fees at your volume outweigh the maintenance Shopify saves. For most retailers with standard needs it is a sensible default.
- Complex B2B or trade pricing. Customer-specific prices, credit terms, minimum order quantities and quote requests depend on your plan and on apps, and can be awkward. A platform built around these may fit better.
- Configurable or made-to-order products. Products with options that depend on each other, or that change the price in complicated ways, push against Shopify's product model and its limits on options and variants.
- Content as the main engine. If the business is mostly articles, guides and community with a shop attached, a content-led WordPress site with WooCommerce may serve better.
- Deep integration with a production or stock system. When the store is the front of a larger operation, you may be commissioning a bespoke software project with a shop on it, not a shop.
- Fee-sensitive volume. At higher order volume, platform subscription, transaction fees where a third-party gateway is used and app charges become a real annual cost. Do the arithmetic against the cost of running a self-hosted store.
- Ownership requirements. Shopify is hosted software. You own your products and customers, but not the platform. If owning the code outright matters, that is a reason to choose another route.
- A very small catalogue with no plans to grow. A simple site with a payment link may do the job, and how we think about online retail starts from that honesty.
How do you choose a Shopify agency or a Shopify SEO agency?
Ask who changes the theme code, how they decide which collections and filtered views are indexed, what they do about apps, and how they protect rankings in a migration. Ask to see the written output, not a slide of logos. An agency that cannot answer in specifics is selling the platform, not the work.
- Who edits the theme? SEO findings on Shopify only matter if somebody can change the Liquid templates that cause them. Find out whether the agency writes theme code or hands a list to your developer.
- How do they decide what gets indexed? A good answer starts with how people search and ends with a rule per collection and filter. “We block everything” and “we index everything” are both wrong.
- What is their attitude to apps? You want someone prepared to remove an app, or replace it with a few lines of code, not someone who answers every problem with a subscription.
- Will they say if Shopify is wrong for you? Ask directly. An agency that has only ever built on one platform has a reason to say yes.
- How do they run a migration? Look for the URL map before the build, a redirect for every old address and an indexation check afterwards.
- What will you own at the end? Your store account, domain, theme files and data should be in your name. Ask what is transferred on handover.
- What have they actually built? Our own delivery record is international rather than UK-based, and the projects we have built show what we have made, not rankings we cannot promise. Weigh a freelancer, an agency and an in-house hire honestly with this comparison.
- A shortlist question for SEO specifically: how to choose an ecommerce SEO agency lists the rest.
What drives the cost of Shopify development and SEO?
Five things: whether you use a configured or custom theme, the size and cleanliness of the catalogue, the number of apps and integrations, whether a migration is involved, and how much is bespoke. Shopify's subscription, any transaction fees and app charges are separate running costs. We publish no prices; the build is scoped after we look at the store.
The biggest swing is usually the theme decision. A configured theme with a clean catalogue is a modest piece of work. A custom theme, a large catalogue with messy data, or a migration with thousands of redirects each add real effort, and they add it in different places. For the broader picture, our ecommerce website cost guide sets out the drivers across platforms.
Running costs deserve as much attention as the build. Monthly platform fees, app subscriptions and payment processing continue for as long as the store trades, and apps are the line that grows without anyone deciding it should. If you want to talk through a particular store, send us the details and we will tell you whether Shopify is the right place to build it.
The point
Monthly platform fees, app subscriptions and payment processing continue for as long as the store trades, and apps are the line that grows without anyone deciding it should.
What Shopify Agency and SEO covers
Not a menu to pick from. Most projects use some of this and ignore the rest, and the scope conversation is mostly about working out which half you actually need.
Theme selection and setup
Choosing a theme for the catalogue you actually have, then configuring it properly: sections, navigation, metafields and the template outputs that search engines read.
Custom theme development
A theme built to your design and your product data where a stock theme would need so many changes that building to purpose is cleaner.
Apps or custom code
A decision made feature by feature: an app where it is mature and light, custom code where an app would add weight, duplicate markup or a subscription for one small function.
Collection and URL structure
Collections, handles, navigation and tags planned so the pages that earn money are the strongest pages in the store, within the URL pattern Shopify imposes.
Liquid templates and structured data
Product and Offer markup, breadcrumbs and canonical tags checked in the theme code and corrected there, not layered on top by a second app.
Speed and app audit
Finding which apps, scripts, fonts and images slow the storefront, removing leftover code from apps that were uninstalled, and fixing what remains.
Migration onto Shopify
A URL map, redirect plan and data reconciliation for moving a store from another platform without discarding what the old store earned.
Shopify SEO audit
A written, prioritised review of how a Shopify store is crawled, indexed and presented, with changes specified at the level of the theme file.
Why this is worth doing properly
Advice that can end in “not Shopify”
An agency that only builds on one platform will always find a reason to recommend it. We also build on WooCommerce and custom, so if Shopify is wrong for you we say so before you pay for the build.
Fixes made in the theme, not stacked on top
Most Shopify SEO problems are template problems. Because we write theme code, a finding becomes a change to the file that produces the page rather than another app that patches over it.
Fewer apps, each one chosen
Every app adds code to every page and often a monthly fee. We keep the ones that do real work and write or remove the rest, so the store stays quick and the running costs stay legible.
Migrations with the URL map first
Every product, collection, page and article is mapped from old address to new before anything moves, so what the old store earned is carried across instead of discarded.
Honest about what the platform will not do
Shopify fixes its URL prefixes and limits what the checkout can be made to do. We state those limits at the start and design around them, rather than discovering them mid-build.
What you are handed, and who this suits
Deliverables
- A written platform recommendation with the trade-offs stated
- A configured theme or a custom theme, built on a store you can review
- An app review: what stays, what is replaced by code, what is removed
- Collection, handle and navigation rules covering what is indexed and what is not
- Validated Product, Offer and breadcrumb markup in the theme templates
- A URL map and 301 redirect plan where a migration is involved
- Data export, cleaning, import and reconciliation against the source
- A prioritised Shopify SEO audit with changes specified at theme-file level
Everything on that list is yours on final payment, in your own company's accounts — the handover is written into the contract, not offered as a favour at the end.
Usually a fit for
- Retailers on Shopify whose store has slowed down as apps have piled up
- Stores whose collections, tags and filters have produced pages nobody planned
- Businesses moving to Shopify from WooCommerce or another platform who cannot afford to lose rankings
- Shops running a stock theme that no longer fits the catalogue or the brand
- Owners deciding between Shopify and another platform who want a view that is not selling one
- Merchants holding a Shopify SEO audit that nobody has turned into theme changes
Built with
- Shopify
- Liquid theme templates
- Online Store 2.0 sections and metafields
- REST and GraphQL APIs for integrations
- Schema.org Product and Offer markup
- JSON-LD structured data
- Google Search Console
- Google Analytics 4
- XML sitemaps and robots.txt
- 301 redirect mapping
Chosen per project, not per fashion. If your team already runs something else and can maintain it, that usually wins.
Ask what this would involve for youFour gates, and you sign off at each one
Every stage ends with something you can read and approve — review and recommendation, structure and url rules, build and configure, launch and measure. Nothing moves to the next stage until you say so.
- 01
Review and recommendation
We look at the catalogue, the checkout you need, the apps you run and how you sell, then say whether Shopify fits and what a theme, a custom build or another platform would each mean.
- 02
Structure and URL rules
Collections, handles, navigation, tags and filters are agreed in writing before products are loaded, including which collection pages are meant to rank and which filtered views are not.
- 03
Build and configure
The theme, the apps and any custom code are built on a development store you can look at throughout, with the markup, redirects and speed checked as part of the build.
- 04
Launch and measure
We launch with redirects live and tracking configured, then check indexation, crawl behaviour and conversions against the baseline, and change what the data shows is not working.
Explore Related Services
Frequently Asked Questions
What does a Shopify agency do?
A Shopify agency builds and improves stores on the platform: choosing or building the theme, deciding which apps belong, structuring collections and URLs for search, migrating from another platform, and fixing speed and conversion problems. A good one also tells you when your requirements do not suit Shopify, before you spend on the build.
Is Shopify good for SEO?
Mostly, yes. It handles hosting, sitemaps, canonical tags and mobile layouts by default, and lets you edit titles, descriptions and redirects. Its limits are structural: fixed URL prefixes, products reachable on more than one path, and collections that generate near-duplicate views. A well-configured store ranks fine; a careless one does not.
What should a Shopify SEO agency actually change?
Theme code and store structure: collection and navigation design, canonical and noindex behaviour for filtered views, product and breadcrumb markup, app-injected duplicates, redirects and page speed. If an agency's output is only a list of keywords and meta descriptions, it has left the part that matters on Shopify untouched. Our e-commerce SEO service covers the platform-neutral work.
Should I use a Shopify theme or have a custom theme built?
Start with a theme if your catalogue and brand fit it with modest changes; that is cheaper to build and easier to keep updated. Build custom when changes would touch most of the templates, or when your product data needs layouts no theme provides. Custom is a larger invoice and a larger maintenance responsibility.
How many apps is too many on a Shopify store?
There is no safe number. The test is what each app adds: most inject scripts and styles into every page, some add their own structured data, and many bill monthly. If you cannot say what an app earns, or it duplicates something the theme already does, remove it and check that no leftover code stays behind.
Can you move my store to Shopify without losing rankings?
Yes, with a complete URL map and a 301 redirect for every old address written before the move, and the products, customers and reviews reconciled against the source. Expect a dip while the new store is re-crawled. What causes lasting damage is moving without redirects. See our website migration SEO service.
Can the Shopify checkout be customised?
Only within limits Shopify sets, which depend on your plan and on Shopify's current checkout framework, and which have changed over the years. Branding and some added features are possible; rebuilding the checkout flow is not. Check what you need against Shopify's present documentation before committing to the platform for a complex requirement.
What decides the cost of Shopify development?
Whether you use a configured theme or a custom one, how many products and how clean their data is, how many apps or integrations are needed, whether a migration is involved, and how much is bespoke. Shopify's subscription, transaction fees and app charges sit outside the build. The ecommerce website cost guide covers the pattern.
When should I not use Shopify?
When your pricing, quoting or checkout logic is unusual enough that you would fight the platform; when content is the main engine of the business and you would rather own the code; or when platform fees at your volume outweigh the maintenance Shopify saves. Our Shopify, WooCommerce or custom comparison sets out the arithmetic.
Let's Build Something That Matters.
Tell us what you're trying to achieve and we'll help you find the right solution.
