Guides / Headless WooCommerce
Headless WooCommerce & the Public Product API
Headless commerce promises speed and flexibility — a modern front end on a proven WooCommerce back end. But decoupling the storefront changes how product data reaches search engines and AI. Here’s how to go headless without going invisible.
What “headless” actually means
In a headless setup, WordPress and WooCommerce stay as the back end — managing products, inventory, orders, and content — while a separate front end (Next.js, Astro, Nuxt, or similar) renders the storefront and fetches data through an API. The presentation layer is decoupled from the commerce engine.
The SEO risk of going headless
The danger is rendering. If your headless front end builds product pages entirely in the browser with JavaScript, crawlers and AI engines that don’t execute JS see empty shells. The fix is to render product content on the server or at build time:
| Rendering | Crawler sees | Verdict |
|---|---|---|
| Client-side only (CSR) | Empty shell | Risky |
| Server-side (SSR) | Full HTML per request | Good |
| Static generation (SSG) | Pre-rendered HTML | Great |
Two different APIs for two different jobs
A headless store actually needs two kinds of data access, and conflating them causes both security and SEO problems:
- Authenticated operations — cart, checkout, account — need the WooCommerce REST API or a secure GraphQL layer with credentials.
- Public product discovery — what crawlers, feeds, and AI agents read — is best served by a public, read-only product API that exposes only catalog data, no keys required.
Using authenticated APIs for public discovery means either exposing credentials or leaving crawlers with nothing. See REST API vs. public endpoints.
Keep structured data in the picture
Headless front ends sometimes drop the Product schema that plugins inject into a traditional theme. Make sure your decoupled pages still emit complete Product JSON-LD — ideally from the same source of truth as your rendered content, so they can’t drift apart.
Don’t forget feeds and llms.txt
Shopping feeds and llms.txt don’t care whether you’re headless — they read your catalog data directly. A public product API that serves JSON/XML feeds gives your headless store the same discovery surface as a traditional one.
A clean headless discovery stack
- WooCommerce as the catalog back end.
- SSR or SSG front end so product HTML is crawlable.
- Complete Product schema rendered server-side.
- A public, read-only product API for crawlers, feeds, and AI agents.
- Authenticated APIs reserved for cart and checkout only.
Easy Woo API provides that public, read-only layer —
schema, feeds, and llms.txt — so a headless WooCommerce store
stays fully discoverable without exposing anything private.