On WooCommerce the buy check starts from a different place than on a hosted platform, because you control the whole stack and the markup comes from more than one place. WooCommerce core emits only basic markup, your SEO plugin generates the fuller Product block, and your theme may emit one of its own. The check below is therefore sharper on the two places WooCommerce stores actually fail: duplicate markup from two sources, and a checkout or a crawl path that a plugin or a theme setting quietly blocks.
Platform screens change over time. If a menu name in this guide does not match what you see, check the vendor docs linked in Sources for the current path.
Why WooCommerce is different
Three things are specific to the platform. First, the markup layer is a plugin, not the platform. In practice you install an SEO plugin such as Yoast SEO or Rank Math, and the plugin generates a Product block for every product page automatically. Second, there is no single owner of the markup. Your theme, your SEO plugin, and WooCommerce core can each emit structured data, so a store that installs a plugin without checking often ends up with two Product blocks on the same page. Third, the crawl file is virtual. WordPress generates robots.txt dynamically rather than reading a physical file from the server root, so the way you edit it depends on whether you use a plugin editor or a physical file, and the two routes behave differently.
The check, in order
1. Check what already exists, and keep exactly one markup source
Open a live product page, view the page source, and search for application/ld+json. Identify which blocks the SEO plugin emits and whether the theme emits its own. Check your theme's documentation for built-in schema support before you configure anything. If the theme outputs Product schema and the plugin does too, disable one of them. Most themes with built-in schema have a setting to turn it off, and both Yoast and Rank Math let you disable their schema output per content type. Two competing blocks with different prices is worse than one incomplete block.
2. Compare the markup with the visible page, variant by variant
Check a variable product with mixed stock, an out-of-stock product, and a product with reviews. The availability in the markup must match the actual stock for the variant shown, and the price must match the price a shopper sees. Fill in GTIN, UPC, or MPN fields on your products where you have them, since identifiers help engines match your product across sites. The default plugin output does not always set availability per variant, so view the source of a specific variant URL and confirm each variant's availability value matches the actual stock status. If it does not, this is a developer job: a small custom plugin or code snippet can correct the availability value per variation. A marketer should not edit theme or plugin code alone.
3. Check robots.txt, and know which route edits it
Open your robots.txt file at [yourdomain.com]/robots.txt, replacing yourdomain.com with your actual domain, and confirm it allows OAI-SearchBot, Googlebot, PerplexityBot, and ClaudeBot. WordPress generates this file dynamically, and WooCommerce itself adds no entries to it, so the base WordPress rules apply unless a plugin or a physical file changes them. The marketer route is the file editor inside your SEO plugin, for example Yoast SEO or Rank Math, which writes the rules for you from the WordPress admin. The developer route is a physical robots.txt file uploaded to the server root, which WordPress defers to entirely. If you use the plugin route, confirm the live file afterwards at your robots.txt URL, since a physical file left over from an earlier setup will override the plugin. Do not block the cart, checkout, or account pages with robots.txt. Those pages should be kept out of search results with a noindex setting instead, so a crawler can still read the page and see the noindex instruction.
4. Check the sitemap, and confirm products are in it
WordPress generates a basic XML sitemap automatically, and most SEO plugins replace it with a fuller sitemap index that links to separate sitemaps for posts, pages, products, categories, and tags. Open your sitemap index, usually at [yourdomain.com]/sitemap_index.xml, replacing yourdomain.com with your actual domain, and confirm your products are listed. Pages set to noindex should not appear in the sitemap, which is how the cart, checkout, and account pages are kept out. If a product is missing, check that it is published and visible in the catalog, not hidden by a draft status or a visibility setting.
5. Walk the checkout as a guest
Add a product to the cart and go to checkout without logging in. Confirm shipping options, tax, and a total appear before any payment step, and that your shipping zones and payment gateway cover the address and method you test with. If the store forces an account before showing shipping, that is a fail for an agent with no account. Confirm your shipping and returns policies are published pages with working links, and that a support contact is listed. An agent that cannot compute a total cannot complete the order, no matter how good the markup is.
6. Check the protocol paths, and confirm their current status
Two protocol paths can let an agent buy without leaving its own interface. The first is Google's Universal Commerce Protocol, which needs a Merchant Center account in good standing with approved products, return policies and support information set in Merchant Center, and the checkout eligibility attribute set on the products you want to offer. The second is OpenAI's Agentic Commerce Protocol, which is an approved-partner path, not a switch that works for every store. For both paths, confirm the current availability for your store with the platform before you build against them. A WooCommerce store that has not set up either path can still be bought from by an agent that browses like a human and checks out on the site, provided the markup and the guest checkout pass the steps above.
7. Test with a real prompt, and read the result carefully
Ask an assistant for one of your products by name, then ask for its price and whether it is in stock. Note what it cites and whether the price and stock match your site. Then ask it to buy the product and watch where it stops. A real abort is an agent genuinely attempting a purchase and failing, for example because it cannot verify the price or the checkout blocks it. Friction alone, such as a slow page or an extra click, is not an abort. Do not claim a measured walkthrough rate from one test. One prompt tells you where this product fails today. Repeat the test across products and assistants to find the pattern.
The fundamentals
- •The complete JSON-LD reference this check builds on, see our product schema guide
- •How to add product schema on WooCommerce, see our WooCommerce product schema guide
- •Whether AI crawlers can reach your pages at all, see our robots.txt guide
Say you run a skincare store on WooCommerce
You pick your best-selling moisturizer, which comes in three sizes, and run the check. The page source shows two Product blocks: the theme emits a thin block with just name and price, while Rank Math emits a fuller one with availability and ratings. Your robots.txt allows the search crawlers, and the sitemap index lists the product. Guest checkout shows shipping before payment. The fix is not a third block. You turn off the theme's schema output, keep Rank Math, fill in the GTIN fields on your best sellers, and spot-check the size variant that is out of stock to confirm the markup says OutOfStock. One source, complete identifiers, availability you can trust, is what turns a blind buy into a verified one.
What this guide does not cover
This covers checking whether an agent can buy from your WooCommerce store today. It does not cover building a protocol checkout integration, which is engineering work with the platform, or the monitoring work of keeping prices and availability accurate as inventory changes. It also does not cover your own brand agent, which sells from the fixed data this check verifies.
Check your own brand now
Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your product pages today: aizii.ai/aeo-scan
Run the free scanSources
- WooCommerce documentation, core products (general docs): https://woocommerce.com/documentation/woocommerce/core-products/
- WooCommerce documentation, Rich Snippets and Schema Markup (general docs): https://woocommerce.com/document/rich-snippets/
- Yoast help, editing robots.txt through Yoast SEO (general docs): https://yoast.com/help/how-to-edit-robots-txt-through-yoast-seo/
- Rank Math knowledge base, blocking web crawlers (general docs): https://rankmath.com/kb/how-to-block-web-crawlers/
- OpenAI bots documentation (specific): https://platform.openai.com/docs/bots
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Google Universal Commerce Protocol, prepare your Merchant Center account (specific): https://developers.google.com/merchant/ucp/guides/overview/merchant-center
- Schema.org, Product type (general standard): https://schema.org/Product
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
