# WooCommerce AI agent readiness What WordPress and WooCommerce do for AI agents out of the box, where variable products, policies and plugins get in the way, and the routes to agent checkout, each with its status label. By Valerii Checha, 3 Nov 2026 Is a WooCommerce store ready for AI agents? Partly, and it depends on your plugins. A stock install lets AI agents in, keeps guest checkout on and has no CAPTCHA, and its product structured data covers the basics. The gaps are in variable products, shipping and return terms, and agent checkout, which WooCommerce offers only through a plugin that is off by default. WooCommerce says it "powers more than 4 million stores", and once a store adds plugins it is no longer a stock install: an SEO plugin, a security plugin or a CAPTCHA plugin can each change what an agent meets. This guide starts from what WordPress and WooCommerce do on their own, read from their source code and docs on 3 November 2026, then covers the plugins that can change it. Each item maps to the [check](https://storewalk.ai/checks) in our scan that reads it. Storewalk is ours: we build it, and this blog is part of its site. Where we explain something in plain words, the explanation is ours. [The hub article](https://storewalk.ai/blog/why-agents-cant-buy) sets out the five walls between an agent and a finished purchase. This page is the WooCommerce view of them. ## What does WooCommerce already do for AI agents? 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](https://storewalk.ai/checks/DISC-004) asks for. What WooCommerce ships, against what an agent needs. - robots.txt lets AI agents in: Fine by default. Core and WooCommerce name no AI agent. The admin and add-to-cart lines apply to everyone, so our DISC-001 reports WARN. Checks: [DISC-001 robots.txt allows AI agents](https://storewalk.ai/checks/DISC-001). Sources: [WordPress: do_robots()](https://developer.wordpress.org/reference/functions/do_robots/) and [WooCommerce source: class-woocommerce.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-woocommerce.php). - Cart and checkout out of search results: Fine by default. Done with a noindex robots meta tag, not a robots.txt block, so an agent may still open them. Checks: [TRX-010 A path to buy exists](https://storewalk.ai/checks/TRX-010). Source: [WooCommerce source: wc-template-functions.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/wc-template-functions.php). - Product JSON-LD: Fine by default. Core prints name, sku, gtin when it is valid, mpn, offers with price, currency and availability, and ratings, in the footer of product pages. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004), [EVAL-003 Price transparency](https://storewalk.ai/checks/EVAL-003) and [EVAL-004 Availability explicit](https://storewalk.ai/checks/EVAL-004). Source: [WooCommerce source: class-wc-structured-data.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-wc-structured-data.php). - Variable products: Gap by default. When variations differ in price, one AggregateOffer with lowPrice, highPrice and offerCount, and no list of variants. Our DISC-004 counts that as a missing offers.price. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004) and [EVAL-005 Variant data structured](https://storewalk.ai/checks/EVAL-005). Source: [WooCommerce source: class-wc-structured-data.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-wc-structured-data.php). - Brand and shipping in JSON-LD: Gap by default. Neither brand nor shippingDetails is in the product data core prints. Checks: [EVAL-001 Shipping cost and terms machine-readable](https://storewalk.ai/checks/EVAL-001). Source: [WooCommerce source: class-wc-structured-data.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-wc-structured-data.php). - Return policy in JSON-LD: Gap by default. WooCommerce 11.3, scheduled for the week of 9 November 2026, adds a MerchantReturnPolicy link, printed on the refund and returns page. Checks: [EVAL-002 Return policy machine-readable](https://storewalk.ai/checks/EVAL-002). Sources: [WooCommerce developer blog: 11.3 pre-release (26 October 2026)](https://developer.woocommerce.com/2026/10/26/woocommerce-11-3-pre-release/) and [WooCommerce source: class-wc-structured-data.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-wc-structured-data.php). - Guest checkout: Fine by default. On in the code by default, labelled “(recommended)”. Checks: [TRX-001 Guest checkout available](https://storewalk.ai/checks/TRX-001). Source: [WooCommerce source: class-wc-settings-accounts.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/admin/settings/class-wc-settings-accounts.php). - No CAPTCHA before payment: Fine by default. Core has none. A plugin can add one, on the forms you choose. Checks: [TRX-002 No CAPTCHA before the payment step](https://storewalk.ai/checks/TRX-002). Sources: [WooCommerce developer docs: Store API rate limiting](https://developer.woocommerce.com/docs/apis/store-api/rate-limiting/) and [WordPress.org: Simple Cloudflare Turnstile](https://wordpress.org/plugins/simple-cloudflare-turnstile/). - llms.txt and Markdown: Yours to set. Neither is in core. Yoast can write llms.txt; Cloudflare’s Markdown for Agents works in front of any site on its Pro, Business and Enterprise plans. Checks: [DISC-002 llms.txt present and non-trivial](https://storewalk.ai/checks/DISC-002) and [DISC-009 Pages served as Markdown on request](https://storewalk.ai/checks/DISC-009). Sources: [Yoast help: Enable llms.txt](https://yoast.com/help/enable-llmstxt/) and [Cloudflare docs: Markdown for Agents](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/). - UCP agent checkout: Yours to set. Through the WooCommerce AI plugin, off by default. WooCommerce’s own agentic commerce page still labels UCP “Coming soon”. Checks: [DISC-018 UCP profile passes schema validation](https://storewalk.ai/checks/DISC-018) and [TRX-004 Agent checkout endpoint present](https://storewalk.ai/checks/TRX-004). Sources: [WooCommerce docs: WooCommerce AI](https://woocommerce.com/document/woocommerce-ai/) and [WooCommerce: Agentic commerce](https://woocommerce.com/agentic-commerce/). - WooCommerce MCP: Not stated or not shipped. For admins, not shoppers: it reads products and orders. The developer docs say “developer preview”; the marketing page says “Beta”. Checks: [DISC-012 MCP server card published](https://storewalk.ai/checks/DISC-012). Sources: [WooCommerce developer docs: MCP](https://developer.woocommerce.com/docs/features/mcp/) and [WooCommerce: Agentic commerce](https://woocommerce.com/agentic-commerce/). - Stripe agentic checkout: Not stated or not shipped. The Stripe extension’s page says “Agentic checkout is coming to Stripe for WooCommerce.” Its changelog already lists agentic commerce code. Checks: [TRX-003 PSP supports agent payment tokens](https://storewalk.ai/checks/TRX-003). Source: [WooCommerce Marketplace: Stripe](https://woocommerce.com/products/stripe/). Statuses are ours, read from each source’s own words. “Not stated or not shipped” means the platform’s pages do not say, or the feature is announced but not something you can switch on. ## Where do the WooCommerce settings live? Seven places decide most of what an agent meets, and three of them belong to plugins. Where each WooCommerce setting lives, and what it defaults to. 1. Guest checkout. Where: WooCommerce > Settings > Accounts and Privacy. Default: Yes in the code, where the label reads “(recommended)”. The help page states no default. In its words: “Enable guest checkout (recommended)” What to do (our advice): Leave it ticked. Subscriptions still need an account, so a subscription product will ask for one. Checks: [TRX-001 Guest checkout available](https://storewalk.ai/checks/TRX-001). Sources: [WooCommerce source: class-wc-settings-accounts.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/admin/settings/class-wc-settings-accounts.php) and [WooCommerce docs: Accounts and Privacy settings](https://woocommerce.com/document/configuring-woocommerce-settings/accounts-and-privacy/). 2. robots.txt. Where: No core screen: WordPress serves a virtual file; SEO plugins add an editor. Default: User-agent: \* with the admin folder, WooCommerce’s upload folders and add-to-cart links disallowed. No AI agent named. What to do (our advice): Read /robots.txt on your live site. If you use Yoast’s bot toggles (Yoast SEO > Settings > Advanced > Crawl optimization), decide bot by bot rather than switching them all on. Checks: [DISC-001 robots.txt allows AI agents](https://storewalk.ai/checks/DISC-001) and [VER-004 Content Signals / AI usage preferences declared](https://storewalk.ai/checks/VER-004). Sources: [WordPress: do_robots()](https://developer.wordpress.org/reference/functions/do_robots/), [WooCommerce source: class-woocommerce.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-woocommerce.php) and [Yoast help: Block unwanted bots](https://yoast.com/help/block-unwanted-bots-with-yoast-seo/). 3. Refund and Returns Policy page. Where: Pages: the draft “Refund and Returns Policy”. Default: Created as a draft on install, so not public until you publish it. What to do (our advice): Edit and publish it, and add a shipping page of your own. WooCommerce 11.3 adds structured data that links to the selected policy page. Checks: [EVAL-002 Return policy machine-readable](https://storewalk.ai/checks/EVAL-002) and [EVAL-001 Shipping cost and terms machine-readable](https://storewalk.ai/checks/EVAL-001). Sources: [WooCommerce docs: Refund policy page](https://woocommerce.com/document/refund-policy-page-guidelines/) and [WooCommerce developer blog: 11.3 pre-release (26 October 2026)](https://developer.woocommerce.com/2026/10/26/woocommerce-11-3-pre-release/). 4. Checkout rate limiting. Where: WooCommerce > Settings > Advanced > Features: Rate limiting Checkout block and Store API. Default: Off. In its words: “This is optional and disabled by default.” What to do (our advice): Turn it on if card-testing bots are a problem. Once on, it allows 3 requests per 60 seconds, and nobody has to solve a puzzle. Checks: [VER-003 Checkout has stricter controls than the product page](https://storewalk.ai/checks/VER-003) and [SAFE-105 Checkout automation controls](https://storewalk.ai/checks/SAFE-105). Source: [WooCommerce developer docs: Store API rate limiting](https://developer.woocommerce.com/docs/apis/store-api/rate-limiting/). 5. CAPTCHA plugin. Where: The plugin’s own settings (Simple Cloudflare Turnstile, for example). Default: Core has no CAPTCHA. With a plugin, you choose the forms. What to do (our advice): Keep it on login, registration and contact forms, and leave checkout off the list. Checks: [TRX-002 No CAPTCHA before the payment step](https://storewalk.ai/checks/TRX-002). Source: [WordPress.org: Simple Cloudflare Turnstile](https://wordpress.org/plugins/simple-cloudflare-turnstile/). 6. Agentic commerce (WooCommerce AI). Where: WooCommerce > Settings > WooCommerce AI: Enable agentic commerce. Default: Off. In its words: “It is off by default.” What to do (our advice): Turning it on makes the plugin’s UCP checkout services available. It needs a WordPress.com connection, and the plugin advertises UCP version 2026-04-08. Checks: [DISC-018 UCP profile passes schema validation](https://storewalk.ai/checks/DISC-018), [DISC-019 UCP version is a known release](https://storewalk.ai/checks/DISC-019) and [TRX-004 Agent checkout endpoint present](https://storewalk.ai/checks/TRX-004). Sources: [WooCommerce docs: WooCommerce AI](https://woocommerce.com/document/woocommerce-ai/) and [WooCommerce docs: WooCommerce AI UCP REST API](https://woocommerce.com/document/woocommerce-ai/ucp-rest-api/). 7. llms.txt. Where: Yoast SEO > Settings > Site features > AI tools > LLMS.txt. Default: Not in WordPress or WooCommerce core. What to do (our advice): Yoast can write one for you. It is not available on multisite. Checks: [DISC-002 llms.txt present and non-trivial](https://storewalk.ai/checks/DISC-002). Source: [Yoast help: Enable llms.txt](https://yoast.com/help/enable-llmstxt/). 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](https://storewalk.ai/checks/EVAL-001) and [returns](https://storewalk.ai/checks/EVAL-002) 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". ## What is off or missing by default? 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](https://storewalk.ai/checks/EVAL-005) 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](https://storewalk.ai/blog/agentic-commerce-glossary#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](https://storewalk.ai/checks/DISC-002) and [Markdown](https://storewalk.ai/checks/DISC-009) checks will fail a stock install until a plugin or your CDN adds them. ## How do you fix the common failures? Start with the plugins you already have: on a stock install, WooCommerce itself blocks very little. If our [robots.txt check](https://storewalk.ai/checks/DISC-001) 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](https://storewalk.ai/blog/bots-crawlers-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. The robots.txt a WooCommerce install serves, and what a bot block changes. WordPress builds robots.txt on the fly; there is no file on disk unless you add one. Below is what core and WooCommerce write together, with the standard uploads folder. Default install. No AI agent is named, and cart and checkout are not disallowed: WooCommerce marks them noindex instead, in a robots meta tag on the page. By the rule of our DISC-001, this file is WARN: no agent is fully blocked, but each inherits some Disallow lines, such as cart or checkout. That is normal for a store and costs little. ```text 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= ``` | Path | GPTBot under “Default install” | | ------------------------------------- | ---------------------------------------- | | A product page: /product/linen-shirt/ | Allowed | | The cart: /cart/ | Allowed | | Checkout: /checkout/ | Allowed | | An add-to-cart link: /?add-to-cart=42 | Blocked, by Disallow: /\*?\*add-to-cart= | | Site search: /?s=linen | Allowed | | The admin: /wp-admin/ | Blocked, by Disallow: /wp-admin/ | With GPTBot and CCBot blocked. Our own illustration of what blocking two bots looks like. Yoast Premium can block both, and we have not checked the exact lines it writes. By the rule of our DISC-001, this file is WARN: only training crawlers and tokens are fully blocked, so search and shopping agents can still read the store. A fair choice, though some assistants may know less about you. ```text 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: / ``` | Path | GPTBot under “With GPTBot and CCBot blocked” | | ------------------------------------- | -------------------------------------------- | | A product page: /product/linen-shirt/ | Blocked, by Disallow: / | | The cart: /cart/ | Blocked, by Disallow: / | | Checkout: /checkout/ | Blocked, by Disallow: / | | An add-to-cart link: /?add-to-cart=42 | Blocked, by Disallow: / | | Site search: /?s=linen | Blocked, by Disallow: / | | The admin: /wp-admin/ | Blocked, by Disallow: / | Sources: [WordPress: do_robots()](https://developer.wordpress.org/reference/functions/do_robots/), [WooCommerce source: class-woocommerce.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-woocommerce.php) and [WooCommerce source: wc-template-functions.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/wc-template-functions.php). 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](https://storewalk.ai/checks/TRX-002) and our check for [stricter controls at checkout](https://storewalk.ai/checks/VER-003) 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](https://storewalk.ai/blog/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". ## Can a WooCommerce store take agent checkout? 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](https://storewalk.ai/checks/DISC-018), [DISC-019](https://storewalk.ai/checks/DISC-019)) and the [agent checkout check](https://storewalk.ai/checks/TRX-004) 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](https://storewalk.ai/blog/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. ## WooCommerce agent readiness checklist Tick as you go. Ticks are saved in this browser, and unlike a draft refund page they need no publishing. Your WooCommerce checklist, saved in this browser. - \[ ] Guest checkout is ticked (WooCommerce > Settings > Accounts and Privacy). Checks: [TRX-001 Guest checkout available](https://storewalk.ai/checks/TRX-001). - \[ ] /robots.txt blocks only the bots you chose to block. Checks: [DISC-001 robots.txt allows AI agents](https://storewalk.ai/checks/DISC-001). - \[ ] The Refund and Returns Policy page is published, and a shipping page exists. Checks: [EVAL-001 Shipping cost and terms machine-readable](https://storewalk.ai/checks/EVAL-001) and [EVAL-002 Return policy machine-readable](https://storewalk.ai/checks/EVAL-002). - \[ ] Variable products print an offer per variant, through a plugin or the woocommerce_structured_data_product filter. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004) and [EVAL-005 Variant data structured](https://storewalk.ai/checks/EVAL-005). - \[ ] Products have a valid GTIN where they have one. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004). - \[ ] No CAPTCHA on checkout; rate limiting instead if you need it (WooCommerce > Settings > Advanced > Features). Checks: [TRX-002 No CAPTCHA before the payment step](https://storewalk.ai/checks/TRX-002) and [VER-003 Checkout has stricter controls than the product page](https://storewalk.ai/checks/VER-003). - \[ ] An llms.txt, if you want one (Yoast SEO > Settings > Site features > AI tools). Checks: [DISC-002 llms.txt present and non-trivial](https://storewalk.ai/checks/DISC-002). - \[ ] Decided whether to enable agentic commerce in WooCommerce AI (WooCommerce > Settings > WooCommerce AI). Checks: [TRX-004 Agent checkout endpoint present](https://storewalk.ai/checks/TRX-004). ## Frequently asked questions ### 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. ## Sources - [WordPress: do_robots()](https://developer.wordpress.org/reference/functions/do_robots/) - [WooCommerce source: class-woocommerce.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-woocommerce.php) - [WooCommerce source: wc-template-functions.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/wc-template-functions.php) - [WooCommerce source: class-wc-structured-data.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/class-wc-structured-data.php) - [WooCommerce source: class-wc-settings-accounts.php](https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/plugins/woocommerce/includes/admin/settings/class-wc-settings-accounts.php) - [WooCommerce docs: Accounts and Privacy settings](https://woocommerce.com/document/configuring-woocommerce-settings/accounts-and-privacy/) - [WooCommerce developer blog: 11.3 pre-release (26 October 2026)](https://developer.woocommerce.com/2026/10/26/woocommerce-11-3-pre-release/) - [WooCommerce docs: Refund policy page](https://woocommerce.com/document/refund-policy-page-guidelines/) - [WooCommerce developer docs: Store API rate limiting](https://developer.woocommerce.com/docs/apis/store-api/rate-limiting/) - [WordPress.org: Simple Cloudflare Turnstile](https://wordpress.org/plugins/simple-cloudflare-turnstile/) - [Yoast help: Block unwanted bots](https://yoast.com/help/block-unwanted-bots-with-yoast-seo/) - [Yoast help: Enable llms.txt](https://yoast.com/help/enable-llmstxt/) - [Cloudflare docs: Markdown for Agents](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/) - [WooCommerce docs: WooCommerce AI](https://woocommerce.com/document/woocommerce-ai/) - [WooCommerce docs: WooCommerce AI UCP REST API](https://woocommerce.com/document/woocommerce-ai/ucp-rest-api/) - [WooCommerce: Agentic commerce](https://woocommerce.com/agentic-commerce/) - [WooCommerce developer docs: MCP](https://developer.woocommerce.com/docs/features/mcp/) - [WooCommerce: Stripe Agentic Commerce Suite (11 December 2025)](https://woocommerce.com/posts/stripe-agentic-commerce-suite-for-woocommerce/) - [WooCommerce Marketplace: Stripe](https://woocommerce.com/products/stripe/) - [Stripe for WooCommerce changelog](https://raw.githubusercontent.com/woocommerce/woocommerce-gateway-stripe/develop/changelog.txt) - [WooCommerce.com](https://woocommerce.com/) Last checked 4 Nov 2026