Headless Shopify or a separate content system?
If the problem is content, you may not need to rebuild the store. Compare what each option replaces, the SEO work headless hands back to you, and the questions any proposal should answer.
01What each option replaces
Going headless replaces the whole Shopify storefront. Product pages, collections, cart and content are rebuilt in a custom front end, for example with Shopify's Hydrogen. Adding a separate content system replaces only the content. The theme keeps selling, and articles and guides come from another system on the same domain.
| Area | Headless storefront | Theme + separate content system |
|---|---|---|
| Product and collection pages | Rebuilt in your code | Unchanged theme pages |
| Apps that render in the theme (reviews, upsells, pop-ups) | Need another integration in the custom front end | Keep working on store pages |
| Meta tags, canonical, sitemap, robots.txt | Your code is responsible. Hydrogen provides helpers and template routes [1] | Shopify handles store pages. The content system handles its own pages |
| Hosting and releases | Your app, for example on Oxygen. Every release can affect the store | Content releases are separate from the store |
| Team you need | Front-end developers who know the Storefront API | An owner for content templates and routing rules |
| Blast radius of an outage | Potentially the whole storefront | Only the content folder. Products and checkout stay on Shopify |
02The SEO work a headless storefront hands back to you
Shopify's Hydrogen SEO guide lists what a custom storefront must provide [1]. Each item is work that a theme already does on product and collection pages.
| Item | What Hydrogen gives you | What you still decide |
|---|---|---|
| Title, description, Open Graph | The getSeoMeta helper, per route. The most specific route wins | The actual text for every route type, with fallbacks to product SEO fields |
| Canonical URL | Query parameters are stripped by default | Pages where a parameter really changes the content must override it |
sitemap.xml, robots.txt | Routes in the base template, cached for 24 hours by default. The sitemap updates within a day | Whether custom routes, such as content pages, appear in them |
| Structured data | JSON-LD support in the helper | What each route outputs, such as Product, Offer and Breadcrumb |
| Preview deployments | Non-production Oxygen deployments get a disallow-all robots.txt | Keep shared preview links private anyway |
None of this is difficult for an experienced team. A rebuild undertaken "for SEO" should still name the specific limit the theme cannot solve, because the rebuild also has to recreate everything the theme already does.
03Match the option to the reason you started
| Reason given | Better fit | Check first |
|---|---|---|
| "We need more guides, comparisons and languages" | Separate content system | Whether the native blog's limits really apply |
| "Editors need their own workflow and approvals" | Separate content system | Who owns routing and templates after launch |
| "The product configurator can't be built in a theme" | Headless | Whether a theme app extension or custom section would do |
| "The store is slow" | Usually neither, at first | App scripts, image weight and theme code. Prune before rebuilding |
| "We want one codebase for app and web" | Headless | Whether the team will maintain the storefront long term |
| "Headless is better for SEO" | Neither, by that reason alone | Name the ranking or indexing problem and its evidence |
ShopXN.net is an example of the second column. The Shopify theme sells. A bilingual reference library lives in a folder on the same domain, served by a separate system through CDN routing. The routing options and launch checks are in Shopify blog in a subfolder.
04What to ask about cost and ownership
- Who maintains the storefront after launch, and what does a month of that cost?
- Which installed apps need replacing or rebuilding in a headless front end?
- What is the rollback if the new storefront has a serious bug on a sales day?
- Which SEO items in section 02 are in the acceptance criteria, and who tests them?
A proposal that cannot answer these is pricing the build, not the ownership.
05Copy these SEO acceptance criteria into any rebuild
SEO acceptance criteria for a storefront or content rebuild
URL inventory: every currently indexed URL is mapped to [same URL / redirect target] before launch Titles and descriptions: match the approved list for [n] key templates; no route falls back to a generic title Canonical: products, collections, articles self-canonical; parameter pages point to [rule] Structured data: Product + Offer on product pages; BreadcrumbList on [templates]; tested in Rich Results Test sitemap.xml: lists [products, collections, pages, articles, content folder]; no preview or parameter URLs robots.txt: matches the approved rules; no disallow-all on the production domain hreflang: [languages/markets] reciprocal on [templates] Status codes: removed URLs return 301 or 410, never a 200 "not found" page Checkout and cart: untouched paths verified on [date] Owner after launch: [name], recheck in Search Console on [date + 2 and + 6 weeks]
06Questions
Is headless Shopify better for SEO?
Not automatically. A headless store can be fast and well structured. It can also lose canonical tags, sitemaps and structured data that the theme used to provide. Treat SEO as part of the rebuild's acceptance tests.
Can I use a headless CMS without going headless on the store?
Yes. A headless CMS can feed content pages served on your domain beside the Shopify theme. The store itself stays a normal theme.
Does headless cost more?
Usually. You add custom development, hosting operations and ongoing maintenance of front-end code that a theme would otherwise cover.
Sources and what still needs a direct check
- Shopify, Search Engine Optimization for Hydrogen.
getSeoMeta, canonical defaults, sitemap and robots routes, caching, Oxygen preview behavior. Checked October 14, 2026.
Still to check yourself
- Which of your installed apps render through the theme, and whether they offer a headless integration.
- Current Hydrogen and Oxygen plan availability in your Shopify admin.
- Your theme's actual performance bottleneck, measured before any rebuild decision.
Next: write down the one limitation that started the discussion. If it is about content, compare the options on our content hub page. If it is about the storefront, put the criteria above into the headless plan. Our architecture page shows how we assign each path to a system before anything is rebuilt.