The result is blazing-fast, infinitely customisable shopping experiences, but it introduces a question every engineering and SEO team eventually asks: Does Google actually index all of this JavaScript-rendered content correctly?
The short answer is yes, but with important nuances. In this deep dive, we break down exactly how Google crawls, renders and indexes headless storefronts, what the risks are and what Commerce Engine teams should do to ensure maximum search visibility.
How Google's Rendering Pipeline Works
Google's indexing process is not instantaneous. It happens in three distinct phases:
Crawling: Googlebot fetches the raw HTML of your page
Rendering: Google's Web Rendering Service (WRS) executes JavaScript using a headless Chromium instance
Indexing: The rendered DOM is parsed, content is extracted and the page is added to Google's index
The critical insight here is the gap between crawling and rendering. In most cases, rendering follows the crawl within seconds or minutes. But for large sites with thousands of product pages, some pages may wait hours before rendering occurs. During that window, your content is not indexed.
Key insight: Google uses an up-to-date version of Chromium for rendering. Modern JavaScript features, including ES modules, async/await and React Server Components are fully supported.
Rendering Strategies and Their SEO Impact
Not all rendering approaches are equal from Google's perspective. Here is how the most common strategies compare for headless commerce:
For most headless commerce sites built on Commerce Engine APIs, a hybrid approach works best: SSG or ISR for product listing pages (PLPs) and category pages, SSR for product detail pages (PDPs) where inventory and pricing change frequently.a
The JavaScript SEO Myths Holding Commerce Teams Back
Myth 1: Google Cannot Index JavaScript-Rendered Content
This was true before 2015. Today, Google renders JavaScript on virtually 100% of HTML pages it crawls. Studies analysing over 100,000 Googlebot fetches have confirmed that even complex React applications with dynamic API calls are fully rendered and indexed.
Myth 2: Client-Side Navigation Hurts Crawling
Google discovers links whether they appear in the initial HTML or after rendering. However, server-rendered links in the initial response do have a slight discovery advantage. For headless storefronts, using proper <a href> tags rather than JavaScript-based navigation ensures Googlebot can follow them reliably.
Myth 3: A Rendering Queue Means Days of Delay
In reality, 50% of pages are rendered within 10 seconds of crawling, and 75% within 26 seconds. Only the 99th percentile of pages sees delays up to 18 hours. For most headless commerce pages, the rendering queue is not a practical SEO concern.
Critical SEO Configurations for Headless Commerce
1. Server-Render Your Critical Meta Tags
noindex tags, canonical URLs, Open Graph tags, and structured data (Product schema, BreadcrumbList) must be present in the initial HTML response — not injected by client-side JavaScript. Google does not execute client-side changes to noindex tags.
2. Structured Data for Product Pages
Commerce Engine APIs return rich product data — use it. Implement Product schema (name, price, availability, sku, brand) via server-rendered JSON-LD on every PDP. This enables rich results in Google Search, including price, availability badges, and star ratings.
3. Ensure API Endpoints Are Not Blocked
If your storefront fetches product data from Commerce Engine APIs at render time, ensure those API endpoints are not blocked in robots.txt. Google's Web Rendering Service must be able to fetch all resources needed to render your pages.
4. Keep Your XML Sitemap Updated
For large catalogues, an up-to-date sitemap eliminates most page discovery delays regardless of rendering strategy. Use the lastmod tag to signal content freshness and ensure Googlebot prioritises recently updated pages.
Commerce Engine-Specific Recommendations
Use ISR with a short revalidation window (60-300 seconds) for PDPs to balance content freshness with crawl efficiency
Implement Commerce Engine's product availability and pricing data in server-rendered JSON-LD — never rely on client-side injection
Paginate large category pages and provide explicit pagination signals (rel=next/prev or load-more with canonical tags)
Monitor Google Search Console's URL Inspection Tool regularly to verify how Googlebot renders your key landing pages
Conclusion
Headless commerce and SEO are fully compatible — but only when your rendering strategy is intentional. Google can render modern JavaScript storefronts with high reliability. The real SEO risks in headless commerce are not about whether Google can render your JavaScript; they are about ensuring critical content like meta tags, structured data, and internal links appear in the initial server response.
Commerce Engine gives you the API infrastructure to build storefronts that are both richly dynamic for users and reliably crawlable for search engines. The rendering strategy is yours to control — and with the right configuration, headless can outperform traditional monolithic commerce platforms in organic search.