# Shopify Plus SEO for multi-store, multi-market brands Source: https://www.smartecomseo.com/shopify-plus-seo/ Updated: 2026-09-29 Plus gives you more stores, more markets, B2B and headless options. Each one adds ways to split authority, duplicate content or break things at launch. We keep the SEO side of a Plus organization under control. ## What goes wrong on Shopify Plus ### Expansion stores competing The UK store and the US store publish the same English copy and outrank each other in both countries. ### Hreflang between stores Shopify creates hreflang inside one store’s Markets. Across separate expansion stores, someone has to build and maintain it. ### B2B and retail overlap A wholesale store duplicating retail product content, or trade catalogs hidden behind login walls Google can’t pass. ### Headless builds missing basics Hydrogen or custom front ends launched without full sitemaps, canonicals, redirects or server-rendered meta. ### Too many hands on the theme Several agencies, apps and internal teams pushing changes. Nobody checks what each release does to indexing. ### Checkout changes that break tracking The move to checkout extensibility and the end of Shopify Scripts broke conversion tracking and attribution on some stores. ## Many stores, one search strategy ## Liquid theme vs Hydrogen: who handles the SEO basics? | | Liquid theme | Hydrogen (headless) | |---|---|---| | Sitemap | Generated by Shopify | Sitemap routes in the template; must be kept current | | robots.txt | Default, editable via robots.txt.liquid | Route in the template; team maintains it | | Meta tags and canonicals | Theme and Shopify defaults | Set per route, e.g. with getSeoMeta | | Admin URL redirects | Applied automatically | Handled in the app code (storefrontRedirect); keep it wired in | | Structured data | Theme Liquid | JSON-LD per route | | Rendering | Server-rendered HTML | Server-rendered by default; check every route | ## How we run SEO for a Plus organization 1. **Organization audit**: Every store, market, domain and B2B setup crawled together, with overlaps and gaps mapped. 2. **Architecture decisions**: Which markets live in Markets subfolders, which justify expansion stores, and how they cross-reference. 3. **Release checks**: An SEO checklist for theme deployments, new apps and headless releases: indexability, canonicals, hreflang, schema, redirects. 4. **Launch governance**: For new stores, markets and migrations: redirect maps, staging crawls and a go/no-go check before DNS changes. 5. **Ongoing growth**: Collection pages, content, internal links and reporting per store, the same way we work on any Shopify store. ## What Plus clients get ### Store and market architecture plan ### Hreflang across expansion stores ### B2B indexability and duplication review ### Headless SEO requirements for your developers ### Release and launch SEO checklist ### Tracking checks after checkout changes ### Per-store and per-market reporting ### Collection, content and internal link work across stores ## Results from structure and execution ## SEO decisions specific to Shopify Plus ### Expansion stores vs Markets Plus includes your main store plus up to nine expansion stores. Markets can handle many countries from one store with subfolders or domains, and Shopify adds hreflang for those automatically. Expansion stores are fully separate: their own catalog, apps, settings and authority. We recommend them only when a region needs something Markets can't do well. The trade-offs are covered in our [international SEO](/shopify-seo-services/international-seo/) service. ### Multi-store hreflang Once you run separate stores, hreflang between them is your job. Every page needs to reference its equivalents on the other stores, each annotation needs a return link, and product handles must be mapped where they differ. We build that mapping from product data so it stays accurate as catalogs change. ### B2B on Plus Core B2B features came to all Shopify plans in April 2026. Plus still adds unlimited catalogs and company-specific pricing, which is why most larger wholesale operations stay on it. The SEO rule is the same either way: keep product pages public and put the price behind login. See [B2B SEO](/shopify-seo-services/b2b-seo/). ### Checkout extensibility and Shopify Functions Shopify Scripts stopped running on June 30, 2026, and checkout.liquid is gone. Discount, shipping and payment logic now runs through Shopify Functions, and checkout changes through UI extensions. Checkout pages aren't indexed, so this isn't a ranking issue. It is a measurement issue: if purchase events break, your SEO revenue reporting breaks with them. We check tracking after every checkout change. ### Headless and Hydrogen Hydrogen ships with sitemap and robots routes and SEO utilities, but a headless build still depends on your developers getting canonicals, redirects, structured data and pagination right on every route. We write the SEO requirements, review staging and crawl before launch. ### Launch and migration governance Plus brands often have several agencies touching one store. We act as the SEO gate: nothing that changes URLs, templates or indexing goes live without a check. For platform moves, see [Shopify Plus migration](/shopify-migration-seo/shopify-plus-migration/). ## Shopify Plus SEO questions ## Related services ## Running several stores or markets on Plus? We will audit your stores together and show where they compete, where hreflang breaks and what to fix first. [Get a free audit](/free-audit/) ## Frequently asked questions ### Does Shopify Plus rank better than standard Shopify? No. Plus stores use the same storefront, URL structure and SEO settings as other plans, and robots.txt.liquid can be edited on every plan. Plus changes what you can build around SEO: expansion stores, larger B2B setups, checkout customization and more API capacity for headless. Those create opportunities and new ways to make mistakes. ### Should we use Markets or expansion stores? Start with Markets unless a region truly needs its own catalog, apps, pricing logic or team. Markets keeps authority on one domain and Shopify handles hreflang for you. Expansion stores make sense for very different product ranges or legal setups, but each store builds its own authority and hreflang across stores has to be maintained manually. ### Is Hydrogen bad for SEO? No, but it moves responsibility to your developers. Hydrogen includes sitemap and robots routes and helpers for meta tags, and it renders on the server. Canonicals, redirects, structured data, pagination and error handling still need to be built correctly on every route. We write those requirements and crawl staging before launch. ### Can you work alongside our development agency? Yes, and on Plus that is common. We act as the SEO owner: we write requirements, review staging, check releases that touch URLs, templates or indexing, and flag problems before launch. Your developers keep building. Clear sign-off steps prevent the most expensive mistakes, like a release that noindexes a template. ### How do you handle hreflang across expansion stores? We map equivalent pages across stores, usually by product handle or SKU, and output hreflang on each store that references the others, with return links and an x-default. Because catalogs change, the mapping comes from product data rather than a static list. We then crawl each store to confirm every annotation resolves to an indexable page.