WooCommerce Schema Markup for ChatGPT: 12-Field Audit

WooCommerce auto-generates 5 of the 12 schema fields AI shopping assistants use to recommend products: name, description, image, SKU, and basic price. The 7 it omits — BuyAction, GTIN, MPN, itemCondition, FAQPage, Organization, and complete Offer data — are the fields ChatGPT weights most. Here's the full audit checklist and how to close each gap.

You've heard schema markup matters for AI search. You're running WooCommerce. You assume it's handled — after all, WooCommerce is a mature platform. In AgentReadyHQ's audit of 30 live WooCommerce stores, 73% were missing product schema entirely — and 100% failed the AI checkout signals check, which requires the BuyAction field WooCommerce never outputs. The stores that do have basic product schema are still missing the fields that matter most.

Does WooCommerce Automatically Generate Product Schema Markup?

WooCommerce does automatically generate Product schema markup in JSON-LD format. It outputs the core @type: "Product" block with name, description, image, SKU, and basic price. However, it stops there. The fields that AI search engines actively use for product recommendations — BuyAction, GTIN, MPN, condition, and policy links — are not generated by default.

You can verify WooCommerce's auto-output in two minutes: open any product page, right-click → View Page Source, and search for "@type":"Product". You'll see the JSON-LD block WooCommerce generates. Alternatively, paste a product page URL into Google's Rich Results Test — the "Detected Items" section shows exactly what WooCommerce outputs.

What you'll typically see: name, description, image, SKU, price, currency. What you won't see: BuyAction, GTIN, MPN, itemCondition, FAQPage, Organization. Those are the gaps this post closes.

The WooCommerce Schema Markup Audit Checklist (12 Fields)

Schema markup is code — typically JSON-LD format — that tells search engines and AI systems the precise meaning of your page content. For WooCommerce product pages, 12 distinct schema fields determine whether your products appear in AI-generated recommendations. WooCommerce covers 5 of them automatically; the other 7 require a plugin or manual addition.

The five auto-generated fields tell ChatGPT what a product is called, what it looks like, and roughly what it costs. The seven missing fields tell it whether the product is available, whether it's new or used, what its canonical identifier is across retail databases, and whether the page is a place where a purchase can actually be completed.

What Schema Markup Does ChatGPT Use for WooCommerce Product Recommendations?

ChatGPT and other AI shopping assistants prioritize schema fields that confirm a product is available, purchasable, and fully identified. The most important fields are BuyAction (signals direct purchase intent), gtin or gtin13 (unique product identifier used across retailer databases), mpn, itemCondition, and a complete Offer block with availability and url.

Why BuyAction matters: BuyAction is a schema.org type nested inside the Offer block's potentialAction property. It tells AI systems that a user can take a buy action on this URL — not just browse a product listing, but complete a purchase. Without BuyAction, an AI system can identify your product but cannot confirm it's a transactional page. AI assistants are looking for pages where buyers can act, not just learn.

Why GTIN matters: AI systems and Google's Shopping Graph use GTIN to reconcile your product against canonical product databases. When a buyer asks ChatGPT "find me a Nike Air Max 270 in size 10," ChatGPT matches that query against GTINs. Without a GTIN, your product is harder to match to a specific query even if your product page has all the right text. If your products have GTINs in your inventory system, getting them into your schema is high-leverage — GTIN connects your product to AI systems' product knowledge graphs.

WooCommerce store operators often know GTIN and MPN from Google Merchant Center work. These are the same fields. Schema markup is another delivery mechanism for the same data.

How to Add BuyAction and JSON-LD Product Schema to WooCommerce

The fastest way to add complete JSON-LD product schema to WooCommerce — including BuyAction, GTIN, MPN, and itemCondition — is with a dedicated schema plugin. Without one, you'll need to manually inject a JSON-LD block via a hook in your child theme's functions.php. Here's the exact structure for a complete WooCommerce product schema block.

Complete JSON-LD template with BuyAction:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "{{product.name}}",
  "image": "{{product.image_url}}",
  "description": "{{product.short_description}}",
  "sku": "{{product.sku}}",
  "gtin13": "{{product.gtin}}",
  "mpn": "{{product.mpn}}",
  "itemCondition": "https://schema.org/NewCondition",
  "brand": {
    "@type": "Brand",
    "name": "{{product.brand}}"
  },
  "offers": {
    "@type": "Offer",
    "url": "{{product.url}}",
    "priceCurrency": "USD",
    "price": "{{product.price}}",
    "availability": "https://schema.org/InStock",
    "potentialAction": {
      "@type": "BuyAction",
      "target": "{{product.url}}"
    }
  }
}

To inject this via functions.php:

add_action('woocommerce_single_product_summary', function() {
  if (!is_product()) return;
  global $product;
  // Build your JSON-LD array using $product->get_*() methods
  // Then: echo '<script type="application/ld+json">' . json_encode($schema) . '</script>';
}, 5);

You'll need get_post_meta($product->get_id(), '_gtin', true) or equivalent to pull GTIN/MPN values from product meta. Adjust the meta key to match your GTIN plugin's storage field.

The limitation of manual injection: it doesn't scale across hundreds of products unless you've built a complete dynamic template. For stores with more than 20–30 products, a plugin is the right path — it handles the mapping and keeps schema current as prices and availability change.

Yoast vs. Schema Pro vs. AgentReadyHQ — Which Covers WooCommerce Schema for AI Search?

For WooCommerce schema in 2026, two plugins and one diagnostic tool cover the AI citation gap differently: Yoast SEO Premium handles basic Product and BreadcrumbList schema; Schema Pro extends to BuyAction and custom field mapping for GTIN/MPN; AgentReadyHQ is a platform-agnostic AEO diagnostic that audits your live store for missing AI-critical schema and generates llms.txt. AgentReadyHQ is not a WooCommerce plugin — it's an external site-level tool that works on any platform and complements rather than replaces a schema plugin.

The practical recommendation:

• Yoast SEO Premium if you're already in the Yoast ecosystem — you get basic Product schema without switching plugins. You'll still need Schema Pro or manual JSON-LD for BuyAction and GTIN/MPN.
• Schema Pro for maximum control over field mapping without custom code — the strongest mid-ground for operators willing to configure manually.
• AgentReadyHQ as the diagnostic layer regardless of which schema plugin you choose — it surfaces exactly which of the 12 fields are missing on your live store, and generates llms.txt that no WooCommerce plugin currently handles.

How to Test and Verify Your WooCommerce Schema Markup

After adding or modifying WooCommerce schema markup, verify output with three tools: Google's Rich Results Test (confirms valid JSON-LD and eligibility for rich snippets), Schema.org Validator (checks structural correctness), and Google Search Console's Rich Results report (shows live index status). For AI-specific fields, run the AgentReadyHQ free diagnostic for a structured citation-readiness score.

1. Visit a WooCommerce product page.
2. Open Google Rich Results Test — paste the URL — verify Product type appears and check for errors or warnings.
3. Copy the raw JSON-LD from View Page Source and paste into Schema.org Validator — confirm no missing required properties.
4. In Google Search Console → Enhancements → Products: check for crawl-level warnings affecting your product pages.
5. Run AgentReadyHQ free diagnostic — review the "schema completeness" sub-score for AI-specific fields including BuyAction, GTIN, and FAQPage.

One important distinction: Google's Rich Results Test checks eligibility for rich snippets — a narrow set of fields. AI citation readiness is broader and includes BuyAction, GTIN, and FAQPage, which Google's test may not flag as missing (they're not required for rich snippets). The AgentReadyHQ diagnostic checks for AI citation-relevant fields specifically.

Frequently Asked Questions

Conclusion

WooCommerce's auto-generated schema gets you roughly 40% of the way to AI citation readiness. The fields it generates tell AI systems what your products are called and roughly what they cost. The fields it omits are the ones AI shopping assistants use to confirm products are purchasable, identifiable across databases, and worth recommending.

The fastest path to complete coverage: (1) run the free AgentReadyHQ diagnostic to see exactly which of the 12 fields are missing on your live store, (2) install Schema Pro — or use manual JSON-LD if you prefer control — to add BuyAction, GTIN/MPN, and itemCondition, (3) verify with Rich Results Test. That workflow takes under 30 minutes for a store that already has GTIN/MPN data in its product records.

One caveat: if your products don't have GTINs yet, that's a separate task. GTINs come from manufacturers or from registering with GS1. It's worth the effort — GTIN is the field that connects your products to AI systems' product knowledge graphs, and without it your products are harder to surface in shopping recommendations regardless of how good your other schema is.