WooCommerce AI agent readiness

The defaults are friendly to agents, mostly because nobody set out to stop them.

WordPress serves robots.txt itself; there is no file on disk unless you add one. Core writes one group for every crawler, disallows the admin folder and allows admin-ajax.php. WooCommerce adds its own lines to that group, which in the words of its source code "Tell bots not to index some WooCommerce-created directories": its log and upload folders, plus links that add a product to the cart. No AI agent is named anywhere, and the cart and checkout pages are not disallowed.

Those pages are kept out of search results a different way. Since WooCommerce 5.0, the cart, checkout and My account pages carry a noindex robots meta tag. An agent may still open them, which is what you want when it is buying.

Guest checkout is on. WooCommerce's settings page shows the box as "Enable guest checkout (recommended)", and its default in the code is yes. Core has no CAPTCHA at all, so nothing asks an agent to pick out traffic lights before it pays.

Product pages print JSON-LD in the footer: name, URL, description, image, SKU, a GTIN when the stored one is valid, MPN, an offer with price, currency and availability (in stock, on backorder or out of stock), and the average rating with up to five reviews. That covers most of what our product structured data check asks for.

Seven places decide most of what an agent meets, and three of them belong to plugins.

The refund page is the one you can get wrong without touching anything. On installation WooCommerce adds a draft "Refund and Returns Policy" page, and a draft is invisible to everyone, agents included. Publish it with your return window in days, and write a shipping page too: WooCommerce does not create one. Our shipping and returns checks read those pages when there is no structured data, and pass on plain terms such as "free delivery over €50" or "30 days from delivery".

Four things, two of them in the structured data.

Variable products lose their prices. When a product's variations have different prices, WooCommerce prints one AggregateOffer with lowPrice, highPrice and offerCount, and no list of the variations themselves. An agent learns that a shirt costs between €30 and €45, not which size costs what. Our DISC-004 counts an AggregateOffer with no individual offers as a missing offers.price, so variable products fail it, and our variant check has nothing structured to read. When all variations share one price, WooCommerce prints a plain Offer with that price, and the problem goes away.

Brand and shipping are not in the product data at all. The source has no brand and no shippingDetails.

The return policy is not in structured data yet. WooCommerce 11.3 is, in its developer blog's words, "scheduled for the week of November 9, 2026", and "For discoverability, WooCommerce adds structured data linking to the selected policy page". In the source, that is a MerchantReturnPolicy with a merchantReturnLink, printed on the refund and returns page. Until you update, the HTML page is what agents read.

Agent checkout is off. WooCommerce's route to UCP is the WooCommerce AI plugin, whose "Enable agentic commerce" setting "enables the plugin's UCP checkout services. It is off by default." We come back to it below.

There is no llms.txt or Markdown version of pages in core either. Our llms.txt and Markdown checks will fail a stock install until a plugin or your CDN adds them.

Start with the plugins you already have: on a stock install, WooCommerce itself blocks very little.

If our robots.txt check fails or warns, look at your SEO plugin first. Yoast has "Block unwanted bots" toggles under Yoast SEO > Settings > Advanced > Crawl optimization. Its help page says "If you're using Yoast SEO free, you can only block Google AdsBot", while Premium can also block Gemini, Vertex AI, GPTBot and Common Crawl's CCBot. Blocking a training crawler is a fair choice; just make it bot by bot, knowing which agents you are turning away. Our check gives a block on training crawlers alone a warning, and keeps the failure for a block on a search bot or an assistant fetching for a shopper. Bots, crawlers and agents explains who each one is. With the stock file our check reports WARN rather than PASS, which is expected: every agent inherits the admin and add-to-cart lines.

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=

User-agent: GPTBot
Disallow: /

User-agent: CCBot
Disallow: /

If a CAPTCHA plugin is on checkout, take it off. A plugin such as Simple Cloudflare Turnstile asks you to "Select which forms Turnstile should be added to", so you can keep it on login, registration and contact forms and leave checkout out. If card-testing bots are the reason it went on, WooCommerce has its own answer: rate limiting for the Checkout block and Store API, under WooCommerce > Settings > Advanced > Features. "This is optional and disabled by default." Once on, it allows "a maximum of 3 requests per 60 seconds", and nobody has to solve anything. Our CAPTCHA check and our check for stricter controls at checkout both like that trade.

If variable products fail DISC-004, give them an offer per variation. WooCommerce exposes the woocommerce_structured_data_product and woocommerce_structured_data_product_offer filters for this, or a structured data plugin can do it. Whichever you use, check one variable product page afterwards for a second Product block: two of them is its own mess. Add a valid GTIN to each product while you are there. WooCommerce prints it only when it is 8, 12, 13 or 14 digits.

If our policy checks fail, publish the refund page and a shipping page, and state numbers rather than promises. How agents read a page has examples.

If you want an llms.txt, Yoast can write one: Yoast SEO > Settings > Site features > AI tools > LLMS.txt. It is not available on multisite. For Markdown, Cloudflare's Markdown for Agents works in front of any origin, and "Markdown for Agents is available to Pro, Business and Enterprise plans".

Through a plugin, and the labels depend on which WooCommerce page you read.

The WooCommerce AI plugin is the route to UCP. Turn on "Enable agentic commerce" under WooCommerce > Settings > WooCommerce AI; it needs a WordPress.com connection. Its docs say the feature "shipped in WooCommerce AI 0.8.0", that "The plugin advertises UCP version 2026-04-08", and that "WordPress.com proxy mode is enabled by default". Our UCP checks (DISC-018, DISC-019) and the agent checkout check read the profile it publishes. Meanwhile WooCommerce's own agentic commerce page still labels UCP and ACP "Coming soon". Both pages are live; we describe it as UCP through the WooCommerce AI plugin, not as a native feature.

WooCommerce MCP is a different thing: a tool for store admins. The marketing page sums it up as "AI assistants can read your store's products and orders". It connects through the WordPress MCP Adapter plugin with a WordPress username and an Application Password. The developer docs call it "developer preview"; the marketing page calls it "Beta". Either way it is not for shoppers' agents, so it does not move our checkout checks. WooCommerce 11.3 also removes the older /wp-json/woocommerce/mcp endpoint.

Stripe's agentic checkout is the third route, through the official Stripe extension. Its product page says "Agentic checkout is coming to Stripe for WooCommerce." WooCommerce's December 2025 post asks merchants to "join the waitlist". The extension's own changelog already lists agentic code, from "Add the base CSV feed for agentic commerce" in 10.5.0 to showing "the originating AI agent in the WooCommerce order Origin column" in 11.1.0. Whether every merchant can switch it on today, we could not confirm. How agents pay covers the payment side.

You will also find third-party "agentic commerce" plugins on wordpress.org. They are not WooCommerce's, so read their pages as you would any plugin's.

Tick as you go. Ticks are saved in this browser, and unlike a draft refund page they need no publishing.

Does WooCommerce block AI agents by default?

No. WordPress core and WooCommerce write one robots.txt group for every crawler and name no AI agent. They disallow the admin, WooCommerce's upload folders and add-to-cart links. If your store does block an agent, look at your SEO or security plugin first.

Does WooCommerce allow guest checkout by default?

Yes. The setting under WooCommerce > Settings > Accounts and Privacy reads "Enable guest checkout (recommended)", and its default in the code is yes. Subscriptions still need an account.

Why do my variable products fail product structured data checks?

When variations differ in price, WooCommerce prints one AggregateOffer with a low and a high price and no individual offers. Tools that want a price on each offer, ours included, report it missing. A plugin or the structured data filters can add an offer per variation.

Does WooCommerce support UCP?

Through the WooCommerce AI plugin, whose "Enable agentic commerce" setting is off by default and advertises UCP version 2026-04-08 when on. WooCommerce's marketing page still labels UCP "Coming soon".

Is WooCommerce MCP for shopping agents?

No. It lets the owner's AI assistant work with the store's products and orders. WooCommerce's developer docs call it "developer preview" and its marketing page calls it "Beta".

The sources below were last checked on the date shown.