Rendering is where headless wins or loses.
We check the HTML every crawler receives, not only what a browser shows. Moving an existing store to headless? Pair this with our migration SEO plan.
Headless & custom commerce SEO
Headless commerce that search engines can actually read.
Fast, flexible storefronts often ship empty HTML, broken canonicals and no sitemap. We fix rendering, routing and data so Google and AI crawlers see every product.
Free 30-minute call. We compare what your store shows people with what crawlers receive.
- 31 five-star reviews
- Month-to-month, no lock-in
- Prices published
Client-renderedServer-renderedIllustrative
view-source: yourstore.com/products/oud-noir
- Googlebotrenders later✓ reads it
- AI crawlersempty page✓ reads it
- Product rich resultsnot eligible✓ eligible
Trusted by teams at
- Hyland
- Nuxeo
- Ledger
- Mihomu
- Kunoji
- Microsoft
- OpenSea
- 7yrsRunning SEO programmes
- 50M+Organic visits generated for clients
- +150%Traffic after Hyland’s 500-page migration
- 31Five-star client reviews
Where headless stores lose traffic
Great for people. Sometimes invisible to crawlers.
A headless build moves SEO from the platform to your code. Nothing is automatic any more, and these six gaps are the most common.
- 01
Client-side rendering
Product details that only appear after JavaScript runs. Google renders later; most AI crawlers do not run JavaScript at all.
- 02
Routing and canonicals
Trailing slashes, uppercase paths, query strings and locale prefixes that each create a duplicate.
- 03
No sitemap, or a stale one
The old platform generated it. The new build forgot, or it lists products that no longer exist.
- 04
Structured data left behind
Product and Offer markup that the theme used to print, missing from the new components.
- 05
Heavy hydration
Large JavaScript bundles that slow interaction on phones and hurt Core Web Vitals.
- 06
Previews indexed
Preview and staging deployments on public URLs, competing with the live store.
What’s included
Headless ecommerce SEO, built into the code.
We work with your developers in the repository, with SEO requirements written as tickets and checked in pull requests.
- 01
Rendering audit
What people see versus what Googlebot and AI crawlers receive, template by template.
- 02
Rendering strategy
Server rendering, static generation or revalidation, chosen per template.
- 03
Routing and canonicals
One URL per page, with redirects and canonicals handled in middleware.
- 04
Sitemaps and feeds
Sitemaps generated from the catalogue, plus feeds for Merchant Center.
- 05
Structured data components
Product, Offer, Breadcrumb and Organization markup built into reusable components.
- 06
Faceted search rules
Which filter URLs exist, which are indexable and how they are linked.
- 07
Core Web Vitals
Bundle size, images, fonts and hydration tuned for real phones.
- 08
CMS fields for SEO
Titles, descriptions, copy and FAQs editable by your team, not only developers.
Rendering options
Choose rendering per template, not per project.
A headless store can mix methods. This is how each one looks to search engines and AI crawlers, and where it fits.
| Method | What Google gets | What AI crawlers get | Best for |
|---|---|---|---|
| 01Client-side (CSR) | Renders it later, not always completely | Often an empty page | ✓Accounts, cart, checkout |
| 02Server-side (SSR) | Full HTML on the first request | Full HTML | ✓Products and categories with live stock |
| 03Static (SSG) | Full HTML, very fast | Full HTML | ✓Guides, brand and content pages |
| 04Static + revalidation | Full HTML, refreshed as data changes | Full HTML | ✓Large catalogues |
Why Qube
SEO that speaks developer.
We write requirements your developers can build and test, and we review the result in code.
Next.js, Hydrogen, Nuxt or custom.
The principles are the same on every stack. We have worked with composable setups and with large Magento stores moving to headless front ends.
Choosing a headless SEO partner.
Ask anyone advising on SEO for your headless build these four questions.
- Do they check raw HTML?Rendered screenshots hide what AI crawlers miss.
- Can they write tickets?Requirements your developers can build and test.
- Do they review pull requests?SEO regressions are easiest to catch before merge.
- Do they cover AI crawlers?Most do not run JavaScript. Your products must be in the HTML.
How it runs
Best before launch. Fixable after it.
Ideally we join during the build. For stores already live, we start with a rendering audit.
- Week 1
Rendering audit
Raw HTML, rendered HTML and crawler access compared.
- Weeks 2–3
SEO requirements
Tickets for rendering, routing, sitemaps and schema.
- Month 2
Build and review
Pull requests checked against the requirements.
- Month 3+
Growth
Categories, content and AI shopping visibility on the new stack.
Headless SEO is part of our ecommerce SEO services. Why AI crawlers matter for stores: read AI shopping visibility. Not sure what is broken? Book an ecommerce SEO audit.
Results
Organic growth that shows up in revenue.
We measure SEO success on what your finance team cares about: non-brand traffic, leads and revenue from organic search, measured in your own analytics.
Enterprise software
“+150% organic traffic after migrating 500+ pages.”
Site migration planned and shipped without the usual traffic dip, then grown past the old baseline.
HylandRead story →
SaaS platform“A full-year commercial content strategy, built from zero.”
Keyword research, topical map and a revenue-first publishing calendar for a content-management platform.
NuxeoRead story →
Your business“Your growth story, next.”
Book a free 30-minute call. We’ll show you where you rank, where AI leaves you out, and what to fix first.
YouBook your free call →
“We’ve been working with Qube for 2 years now and the results are amazing: +300% in organic qualified traffic. They see through to revenue and make sure the whole strategy is aligned with our goals.”
Jason YannickEcommerce owner, Mihomu“We trusted Qube for our migration and we are completely satisfied. Their framework makes things easier for every stakeholder, and the delivery is impeccable.”
Laure LineMarketing Growth, KalipsoFAQ
Headless SEO questions.
Still unsure? Ask us directly on a free 30-minute call. No pitch deck.
Book your free strategy callIs headless commerce bad for SEO?
No. It can be excellent for SEO because you control every detail. The risk is that the platform no longer handles rendering, sitemaps, canonicals and structured data for you, so they have to be built deliberately.
Does Google render JavaScript?
Yes, Google renders JavaScript, but it can happen later than the first crawl and is less reliable at scale. Most AI crawlers do not render JavaScript, so product content should be in the server-rendered HTML.
Which rendering method is best for ecommerce SEO?
Server rendering or static generation with revalidation for product and category pages, so the full HTML is there on the first request. Client-side rendering is fine for accounts, carts and other pages that should not rank.
Do you work with Shopify Hydrogen?
Yes, as well as Next.js, Nuxt and custom front ends on platforms such as Shopify, BigCommerce and Magento.
How much does headless ecommerce SEO cost?
A rendering audit is quoted as a fixed fee. Ongoing work runs inside our monthly plans, which start at AED 12,850 a month, or as a custom scope for large builds.
When should SEO join a headless project?
Before the first template is built. Rendering and routing decisions are far cheaper to get right early than to change after launch.
Free strategy call
Find out where you rank, and where AI leaves you out.
A free 30-minute call. We review your site, your competitors and your AI visibility live. No pitch deck. You keep the notes.
Book your free strategy call →Call agenda30 min
- 00:00Your goals and current numbers
- 05:00Live site and competitor review
- 15:00AI visibility spot-check
- 25:00Quick wins and a realistic plan
