Most Shopify SEO is theme tweaks and review apps.
Your collection pages decide your revenue.

The fundamentals are identical — collection-page architecture, PDP schema, theme performance, app audit, internal linking — but Shopify Plus unlocks structural capabilities that change the SEO playbook materially. Plus stores get multi-store / expansion-store architecture (you can run a US store and an AU store on separate domains with shared catalog), Shopify Scripts for checkout customization, more granular Liquid template control, B2B / wholesale channels, the Markets feature for international SEO with proper hreflang and currency handling, and access to checkout extensibility. Mid-market brands ($5M+) on basic Shopify routinely hit ceilings — multi-currency tax handling, B2B catalog gating, advanced redirect rules, custom checkout flows — and the cost of a Plus migration is usually paid back inside a year by the SEO and conversion-rate gains alone. We audit whether the Plus upgrade is justified before recommending it; the platform fee is significant and not every brand needs it.

A Shopify app audit is a systematic review of every app installed on the store, scoring each one on: page weight added (KB of JavaScript and CSS injected into the storefront), render-blocking impact on LCP and INP, schema conflicts (multiple apps fighting to inject Product schema, often with conflicting data), DOM mutations that break crawlability, and overlap with other apps doing the same job. The reason it matters: every app installed adds technical debt, and the cumulative drag on Core Web Vitals is the single biggest hidden SEO problem we see on Shopify stores. We have audited stores with 40+ active apps where 30-60% of organic potential was being throttled by cumulative app load. The intervention is unglamorous — uninstall, replace, consolidate, defer — but the ranking lift is often visible in 4-8 weeks because it removes a constant headwind. Most agencies do not run this audit because their playbook does not include it; ours starts with it.

It depends on the theme age, build quality, and how much custom Liquid has been layered on top. Themes built before mid-2023 generally pre-date the Online Store 2.0 architecture and miss out on sections-everywhere, JSON templates, and the metafield-driven content patterns that make modern Shopify SEO efficient. Older themes also tend to ship with mediocre schema (or none), poor image handling, render-blocking JavaScript, and inflexible collection-page templates. The migration call is: if your theme is OS 2.0 native, well-built (Dawn, Sense, Ride, or a reputable third-party), and your custom work is metafield-driven, optimize in place. If it is a heavily customized older theme with hardcoded content, render-blocking apps stitched into the head, and limited collection-page flexibility, migration usually pays back faster than incremental optimization. We do migration audits as a discrete engagement because the answer is different for every store.

B2B Shopify is its own discipline because the catalog is often partially or fully gated (logged-in pricing, account-required checkout, tiered customer pricing) which creates a tension between SEO visibility (you need crawlable content) and commercial protection (you do not want public pricing on every SKU). The right pattern is a hybrid: indexable category and product information pages with educational content, specifications, use cases, and application context — but pricing and 'add to cart' behind the customer-account login. Schema markup uses Product without Offer (or with priceSpecification omitted) on public pages. We build B2B Shopify SEO around three buyer behaviors: the procurement researcher who needs spec sheets and compatibility info, the existing customer logging in for reorder, and the new prospect comparing your product to incumbents. Each gets a different content tier. Shopify Plus B2B (the dedicated B2B channel) makes this dramatically easier than basic Shopify with workarounds.

Yes — Shopify Plus allows up to 9 expansion stores under one organization, and the multi-store SEO playbook is well-defined. The most common patterns are geographic (US store on .com, AU store on .com.au, UK store on .co.uk) and audience (B2C on the brand domain, B2B on a separate domain). The SEO requirements: proper hreflang implementation across all stores, distinct canonical strategies per market, currency and tax handling that does not block crawlers, and a content-localization plan that goes beyond machine-translated PDPs. Shopify Markets (the alternative to expansion stores) handles some of this at the URL level with subfolder localization (/en-au/, /en-gb/) and is the right call for smaller markets. Expansion stores are right for markets large enough to justify a fully localized commercial presence. We audit which model fits the brand before recommending; the cost difference and SEO implications are significant.

Material amounts. Out of the box, Shopify themes ship with serviceable but not exceptional SEO — schema is incomplete or generic, collection-page templates lack content sections, PDP variant URL handling defaults to the simplest behavior, breadcrumbs may be visual-only without schema, and JSON-LD coverage is uneven. Liquid template work is where the platform-specific SEO leverage actually lives: enriching Product schema with brand, GTIN, MPN, AggregateRating, and Offer fields pulled from metafields and review apps; adding ItemList schema to collection pages with proper position and URL fields; injecting BreadcrumbList schema everywhere it is missing; adding FAQ schema sections to high-priority collection pages and PDPs; controlling canonical behavior on faceted collection pages; building pagination handling that does not generate near-duplicate content. We work alongside Shopify developers to specify and ship these template changes, or we ship them ourselves on theme files we have access to.

Shopify Markets is Shopify's native solution for selling to multiple countries from one store, with localized URLs (subfolder-based: /en-au/, /en-gb/, /fr/), automatic hreflang generation, market-specific pricing and currency, geographic redirects, and localized payment methods. For SEO, the wins are: proper hreflang at scale (which is genuinely difficult to get right manually), market-specific canonicals, URL-level localization that search engines treat as distinct ranking surfaces, and the ability to serve different content per market (different product mix, different copy, different metafield values) without running separate stores. The limits: Markets is less powerful than full expansion stores for large markets that need genuinely distinct catalogs, payment processors, fulfillment, or B2B configuration. The decision criteria: Markets is right for 80% of international expansion scenarios; expansion stores are right when a single market is large enough to justify a fully separated commercial operation. We audit market revenue and growth before recommending the architecture.

Leaving Shopify makes sense in three scenarios. First, when catalog complexity exceeds Shopify Plus capacity — brands with 100,000+ SKUs, complex configurable products with deep variant hierarchies, or industrial B2B catalogs with custom product configurators sometimes outgrow even Plus. Second, when checkout or product experience requirements demand control Shopify cannot deliver — multi-vendor marketplace functionality, complex subscription billing logic that goes beyond Recharge or Skio, deeply customized cart behavior, or experiences that need backend logic Shopify Functions cannot reach. Third, when the brand is heading toward a headless / composable architecture where Shopify is one component (the commerce backend) but the storefront moves to Next.js, Hydrogen, Remix, or another framework — this is not 'leaving Shopify' so much as decoupling the storefront for performance and content flexibility, and Shopify's headless story is now strong enough that this is a viable path. For most brands $500K-$50M, Shopify or Shopify Plus is the right answer; the platforms underneath (BigCommerce, Magento / Adobe Commerce, custom builds) win on specific use cases but lose on velocity, ecosystem, and platform stability. We have shipped on every major commerce platform and our recommendation is platform-agnostic.