How To Appoint A Shopify SEO Agency

The agencies we've followed on SEO contracts for Shopify stores started with keyword research and moved straight into a content plan. That sequence is wrong.

Shopify's architecture creates technical constraints that directly affect whether content work lands. Duplicate product URLs, canonical handling that doesn't work out of the box, crawl budget wasted on faceted navigation, JavaScript rendering on modern Dawn-based themes affecting how Googlebot indexes pages, page speed problems inherited from an accumulated app stack. These are platform-structural problems. They don't yield to a better blog post or a refreshed content calendar.

If they're not resolved before content work begins, everything built on top of them inherits the same structural fault. More content doesn't fix the technical foundation. It buries it and makes the real problem harder to diagnose later.

Shopify's architecture out-of-the-box creates SEO problems that content can't fix

Shopify generates two valid URLs for every product by default: one at /products/[handle] and one at /collections/[handle]/products/[handle]. Without correct canonical configuration at the theme level, Google treats both as real pages and can split ranking signals between them, diluting the authority of the URL you actually want to rank.

Collection pages create a different problem. Faceted navigation — filtering by size or colour — generates parameter-based URL variants that Googlebot will crawl. Most of those pages carry near-identical content with minimal ranking value, but they consume crawl budget. Google spends that resource on thin pages instead of the collection and product pages that need to rank.

Modern Shopify themes built on Dawn use JavaScript rendering to display content. Googlebot handles JavaScript, but not as efficiently or as quickly as it handles static HTML. The pages most important to your architecture may be the last ones properly indexed or may not be indexed correctly at all, depending on how the theme was implemented.

Lastly, there's the app stack. Every app loading on the storefront adds page weight and HTTP requests. The cumulative effect on LCP and INP is often significant, and it compounds as the app stack grows.

All of these problems share a characteristic: they're structural, and they require codebase access to fix. A better content calendar won't resolve duplicate product URLs.

Content-first SEO on Shopify can compound problems rather than solve them

When the technical foundation is broken, adding content doesn't help — it creates more of the same problem at greater scale.

Google's crawler is finite. For stores with large catalogs and active faceted navigation, this can mean several thousand parameter-based URLs consuming crawl budget instead of the collection and product pages you want to rank. New content joins the crawl queue, but the structural noise is already competing for the same resource. The crawler doesn't prioritise well on a site where crawl path signals are muddled.

Every piece of new content also inherits the canonical and URL issues already present in the store. If internal links to products are split between /products/ and /collections/[handle]/products/ URLs, the link equity that should consolidate on one canonical is distributed across two. You're building on a foundation that leaks authority in the wrong direction.

If LCP is slow because of a heavy hero image and third-party app scripts, another blog post doesn't change it.

What this looks like in practice: organic rankings appear, sometimes early, but traffic from those rankings doesn't convert at the rate it should. Or content output stays consistent for six months and organic performance is flat — not because the content is weak, but because structural issues are suppressing indexation and diluting authority across the wrong URLs.

What the technical audit should cover before content begins

A pre-content audit on a Shopify site isn't a generic technical SEO checklist. The platform creates specific constraints that need specific checks.

Start with URL structure and canonical configuration. Shopify's product URL duplication needs to be resolved in the theme code. That means looking at how the theme handles canonical tags, not just running a crawler over the site.

Crawl path analysis comes next. How does Googlebot actually move through the site? Which pages get crawled, and which get ignored? Sites with large collections and active faceted navigation often have a significant crawl budget problem that isn't visible until you pull the data.

Duplicate content runs wider than the product URL issue. Parameter variants from filters and sorting, paginated collection pages, product variants generating separate URLs — each needs to be assessed for its actual impact on crawl and indexation, not just flagged as potential duplication.

Core Web Vitals need to be measured in the field, not just in Lighthouse, as lab scores don't reflect real-user experience. The audit should identify which Shopify-specific factors are moving LCP, CLS, and INP: app scripts, image handling in the theme, layout shift from dynamic content loading.

Shopify sites often have misconfigured or missing structured data, particularly after theme updates. The audit should confirm whether product schema, review signals, and pricing data are being communicated correctly to search engines.

Internal linking patterns need checking too. Are links pointing to canonical URLs, or split across /products/ and /collections/ paths? Is link equity flowing to the pages that actually need to rank?

Page speed at the codebase level goes beyond what Lighthouse reports. Which apps are loading scripts on pages that don't need them? Are images sized and formatted correctly? What does LCP look like under real network conditions, not just in a lab environment?

The consistent point across all of this: the findings require codebase access to action. When an agency produces an audit document and hands it to you to pass to a developer, that's not the same as an agency that can fix what it finds.

Shopify SEO agencies should never skip the technical stage

Starting with a technical audit feels slower. Month one doesn't have a keyword report or a content calendar to show. There's no link outreach to report on. What exists is a codebase review and a set of findings that require development work to action — harder to present as visible progress to a client who's watching the first month closely.

It's also harder to scope and bill cleanly. Technical SEO work on Shopify requires development time, and development time sits outside what a pure-SEO agency does. If the agency can't fix canonical issues in the theme or address Core Web Vitals at the codebase level, it's writing recommendations for someone else to implement, and there's no guarantee that happens, or happens on any particular timeline.

Pure-SEO agencies can sometimes lack development capability. They're effective at keyword research, content strategy, and link building. What they can't do is open the theme and rewrite the canonical tag logic. So the audit gets written, the findings sit in a document, and content work starts anyway because there's nothing else to start.

The incentive structure produces the wrong order.

Keyword research and a content plan show activity immediately — rankings can appear within weeks, giving the client something to point to. An unresolved canonical issue or crawl budget problem shows up much later, when organic growth plateaus and no one can explain why.

How to tell if the sequence was wrong from the start

If you're already in an SEO engagement, or you've been through one that didn't deliver, some indicators point to whether the sequence was wrong.

The most direct: the agency started with keyword research.

If month one was keyword mapping and a content calendar, the technical foundation wasn't checked first. Content work can still rank pages — the issue is that unresolved structural problems suppress what those rankings deliver.

A technical audit exists, but nothing in it was actioned.

This is common when the agency that produced it didn't have the development capability to implement the findings. The document describes the problem accurately; the codebase hasn't changed.

Content output has been consistent for six months.

And organic performance hasn't moved materially. The content may be good. The structural issues mean it's not getting indexed or ranking as it should.

Some pages rank, but the traffic doesn't convert.

This sometimes means the wrong pages are ranking — not the intended targets, but near-duplicate or low-intent URLs that Googlebot settled on because canonical configuration wasn't correct.

If you're evaluating a Shopify SEO agency now, start with the pre-content work.

What do you audit before starting content work, and how long does that take?

An agency that answers specifically — crawl paths and canonical configuration — understands the sequence. An agency that describes keyword research and competitor analysis hasn't answered the question.

Do you have access to the codebase, or do you work from crawler exports?

A Screaming Frog crawl is useful, but it doesn't tell you how the theme handles canonicals. The answer separates agencies that can fix what they find from agencies that can only identify it.

Who actions technical recommendations — you, or a separate developer?

If the answer is a separate developer, the findings go into a document that may or may not get implemented, on a timeline you don't control, by someone who wasn't part of the audit. That's the same gap as skipping the technical stage.

What a Shopify SEO agency should do first — and what makes that possible

The right sequence is technical first, content second. But the sequence only works if the agency can actually fix what the technical audit finds.

Resolving Shopify's canonical URL duplication requires changing how the theme generates canonical tags, which is a (simple!) code change in the theme. Core Web Vitals improvements come from development work: image handling in the theme and third-party app script load. Crawl path issues, where they involve the store's architecture, how collections are structured, which URLs get indexed and how internal links flow, require decisions that touch the platform itself.

These aren't tasks an SEO agency can hand off and mark resolved. They require development capability alongside SEO capability, managed within the same engagement.

Strawberry manages Shopify SEO as part of the same engagement that covers platform work and development. When the technical audit identifies a canonical URL problem, it gets fixed at the theme level. When Core Web Vitals need improving, that work sits with the same team that understands the codebase, not a third party working from a Lighthouse report.

FAQs

What is technical SEO for Shopify?

Technical SEO on Shopify covers the configuration and codebase factors that determine how search engines crawl and index your site — URL structure and canonical handling (particularly Shopify's product URL duplication), crawl path analysis, Core Web Vitals, structured data, internal linking, and page speed.

It's distinct from content SEO, and on Shopify it's more often the limiting factor than missing content or weak copy.

Do I need a technical SEO audit before starting content SEO?

Yes. On Shopify, the platform's architecture creates specific constraints that affect whether content work performs. Canonical issues mean ranking signals may be split across duplicate URLs. Crawl budget problems mean new content may not get indexed efficiently. Building content before the technical foundation is resolved means building on a broken base.

The audit comes first; content scales on top of it.

Why does Shopify create duplicate content problems?

Shopify generates two valid URLs for every product: one under /products/ and one under /collections/[handle]/products/[handle]. Without correct canonical configuration at the theme level, search engines treat both as real pages and can split ranking signals between them, diluting the authority of the URLs you want to rank.

This needs to be fixed in the theme code — flagging it in an audit document isn't the same as resolving it.

What should a Shopify SEO agency do in the first 30 days?

Audit the codebase and site architecture — URL structure, crawl paths, canonical configuration, Core Web Vitals baseline, structured data — before touching content. An agency that opens month one with keyword research and a content plan has the sequence wrong. Agencies lead with content because it shows visible progress in month one.

The ones that produce material organic performance lead with a technical audit and the development capability to action it.

What should Shopify SEO services include?

Shopify SEO services should start with a technical audit before any content work, covering URL structure and canonical handling, crawl path analysis, Core Web Vitals, and structured data. Shopify's architecture creates specific constraints that content can't fix until they're resolved at the codebase level.

Services that include development capability alongside SEO can action those findings directly, rather than producing a document for someone else to implement.

How do I find Shopify SEO experts who work at the technical level?

Ask whether they audit the codebase before starting content work, and whether they have development capability to action technical findings directly. If the answer to the second question is "we produce a recommendations document for your developer to implement," the findings will stay as findings.

The Shopify SEO experts who move organic performance are the ones who can fix what they identify, not just describe it.