WooCommerce guide
Can AI agents shop a WooCommerce store?
Often yes, since WordPress's own robots.txt only blocks /wp-admin/ and WooCommerce prints product markup, but agents commonly hit security or CDN rules that turn automated visitors away, price ranges on variable products, and delivery costs hidden until an address is entered.
A WooCommerce store is WordPress plus your theme, plugins and hosting, so what an agent sees depends on all of them: an SEO plugin may write robots.txt, a security plugin or CDN decides who gets through, and the theme renders the product page.
Reviewed 21 October 2026 against official documentation. 22 sources
Common problems
An illustrative store, not a real result. Your own result shows only what is really on your store.
WooCommerce at a glance
- robots.txt
- Virtual, made by WordPress, unless a physical file exists. SEO plugins edit it.
- Structured data
- WooCommerce core: Product with price and stock. Variable products get one price range.
- Bot protection
- Whatever your host, CDN and security plugin do. Cloudflare now sets AI bot policies per domain.
- Agent checkout
- WooCommerce lists Stripe's Agentic Commerce Suite and Google's UCP as coming soon.
What usually breaks on WooCommerce
WooCommerce itself rarely blocks agents. The layers around it do: plugins, hosting and the CDN in front of your store.
- 01
A CDN or security plugin turns agents away
Since 15 September 2026, new Cloudflare domains start from a preset: sites without ads allow Search, Agent and Training; ad-funded sites disallow AI training and block agents on pages with ads. In Wordfence, rate limiting and advanced blocking is on by default with every rule set to Unlimited; verified Google crawlers are never limited, so once you set a limit, other crawlers, AI ones included, can be throttled.[7][20][21]
- 02
A robots.txt rule written years ago
WordPress's own file disallows only /wp-admin/. Copied 'hardening' rules often add Disallow: /wp-content/ or /wp-includes/, which stops crawlers loading the images and theme files a page needs, and an SEO plugin's bot blocker can add AI crawler blocks you never noticed. A physical robots.txt in the web root overrides all of it.[1][4]
- 03
Variable products show a range, not a price
Until a shopper picks every option, a variable product shows its price range, and the matching variation's price, image and stock load with JavaScript. WooCommerce's structured data holds one AggregateOffer with the lowest and highest price, so an agent can't quote the size it was asked about.[8][10]
- 04
Delivery cost waits for an address
Shipping zones are matched to the customer's address, so rates appear in the cart after 'Calculate shipping' or in checkout once an address is entered. Agents stop before cart and checkout, so a shipping page with real rates is the only place they can find them.[11]
- 05
The returns page is still a draft
WooCommerce creates a Refund and Returns Policy page as a draft with sample text. Left unpublished, or published with the sample, it gives agents nothing true to quote, and core product markup carries no shipping or return details.[8][12]
How to fix it on WooCommerce
Start at the edge of your stack and work inwards: CDN, robots.txt, then product data. The snippets go in a small custom plugin or your child theme's functions.php.
- 1
Set your CDN's AI bot policies on purpose
On Cloudflare, open Security settings and configure AI bot policies: Search, Agent and Training each take Allow, Block, or Block on pages with ads. Allow Search and Agent if you want shoppers' assistants to reach you. Bot Fight Mode on the Free plan can't be bypassed with WAF rules, so check whether it challenges the agents you want.[21][22]
- 2
Find out which robots.txt is live, then edit that one
Open yourstore.com/robots.txt. A physical file in the web root wins over WordPress's virtual one. Otherwise edit it in Yoast SEO > Tools > File editor, or in Rank Math > General Settings > Edit robots.txt with Advanced Mode on. Remove Disallow lines for /wp-content/ and /wp-includes/. To decide per AI crawler in code, use the robots_txt filter.[2][3][6]
wp-content/plugins/ai-crawler-rules.php (example)<?php /** * Plugin Name: AI crawler rules */ add_filter( 'robots_txt', function ( $output, $public ) { if ( ! $public ) { return $output; } // Opt out of model training. OAI-SearchBot, ChatGPT-User, // Claude-User and PerplexityBot keep following the * group. foreach ( array( 'GPTBot', 'Google-Extended', 'CCBot' ) as $bot ) { $output .= "\nUser-agent: {$bot}\nDisallow: /\n"; } return $output; }, 10, 2 ); - 3
Give each variation an address with its own price
When every variation attribute is in the address and exactly one variation matches, WooCommerce outputs a single Offer for that variation instead of the price range. Link sizes and colours that way from size guides and comparison tables, and keep a short table of variation prices in the description.[8]
A variation linkhttps://yourstore.com/product/rain-jacket/?attribute_pa_size=m&attribute_pa_color=blue - 4
Add shipping and returns to product markup
WooCommerce's structured data filters let you add shipping details and a return policy to every offer. WooCommerce 11.3 will add a link-only return policy on your refund and returns page (OnlineStore markup), not on products; it's merged but not in a stable release yet (11.2.1 is the latest). For product-level terms, add them yourself.[8][9]
functions.php (example values, use your own)add_filter( 'woocommerce_structured_data_product_offer', function ( $offer, $product ) { $offer['shippingDetails'] = array( '@type' => 'OfferShippingDetails', 'shippingRate' => array( '@type' => 'MonetaryAmount', 'value' => '4.95', 'currency' => 'USD' ), 'shippingDestination' => array( '@type' => 'DefinedRegion', 'addressCountry' => 'US' ), ); $offer['hasMerchantReturnPolicy'] = array( '@type' => 'MerchantReturnPolicy', 'applicableCountry' => 'US', 'returnPolicyCategory' => 'https://schema.org/MerchantReturnFiniteReturnWindow', 'merchantReturnDays' => 30, ); return $offer; }, 10, 2 );
What WooCommerce has announced for AI agents
WooCommerce's agent work so far is developer tools and payments partnerships. Here is what has been announced, newest last.
- Oct 2025Roadmap: AI and agentic commerce in WooCommerceWooCommerce said it was working with Stripe on the Agentic Commerce Protocol and experimenting with OpenAI's product feed spec.[13]
- Oct 2025WooCommerce MCP, developer previewWooCommerce 10.3 added an MCP integration for store management: AI tools can query and update products and orders. It's a developer preview that needs the MCP Adapter plugin and signs in with a WordPress user and an Application Password. It isn't for shoppers.[15]
- Dec 2025Stripe Agentic Commerce Suite, with WooCommerce among the platformsStripe announced a suite for selling through AI agents, listing WooCommerce among the platforms it will be rolling out through, with a waitlist. WooCommerce says it will come via the Stripe for WooCommerce extension.[16][17]
- Apr 2026Stripe extends the suite to WooCommerceAt Stripe Sessions, Stripe previewed extending the Agentic Commerce Suite to platforms including WooCommerce, Wix and BigCommerce.[18]
- Oct 2026Agent checkout still listed as coming soonWooCommerce's agentic commerce page lists MCP and the WordPress Abilities API as available, and Google's UCP and Stripe's protocol as coming soon.[19]
What Aiscovery checks on WooCommerce
From the outside, the way an agent sees your store. Nothing to install, and agents stop before login, cart, checkout and payment.
- What your live robots.txt declares for each AI crawler, whether it comes from WordPress, an SEO plugin or a physical file.
- Whether robots.txt blocks /wp-content/, /wp-includes/ or other paths pages need.
- Whether pages answer our identified checker or fail for automated visitors. We never pretend to be an AI crawler, so firewall rules for their user agents aren't tested.
- Page basics and JSON-LD syntax, and llms.txt if your SEO plugin makes one.
- GPT-6 Luna and Gemini try to find a variation's price, stock, delivery cost and your returns terms, stopping before cart and checkout.
Questions about WooCommerce and AI agents
Does WooCommerce block ChatGPT or GPTBot?
No. WordPress's built-in robots.txt only disallows /wp-admin/, and WooCommerce adds no AI crawler rules. Blocks usually come from somewhere else: an SEO plugin's bot blocker, a hand-written robots.txt file, a security plugin, or your CDN, such as Cloudflare's AI bot policies.
How do I edit robots.txt on WooCommerce?
If a robots.txt file sits in your web root, edit that file. Otherwise use Yoast SEO > Tools > File editor, Rank Math > General Settings > Edit robots.txt (with Advanced Mode on), or WordPress's robots_txt filter in a small plugin.
Can ChatGPT check out on a WooCommerce store?
Not as a built-in feature yet. WooCommerce lists Stripe's Agentic Commerce Suite and Google's Universal Commerce Protocol as coming soon. Agents that browse can still read your product pages, and they need prices, delivery and returns there either way.
Does WooCommerce have an MCP server for AI agents?
Yes, for store management rather than shoppers. Since WooCommerce 10.3 a developer preview lets AI tools query and update products and orders through the WordPress MCP Adapter plugin, signed in as a WordPress user with an Application Password; WooCommerce recommends a dedicated user with the fewest permissions. Shopper-facing data lives in the public, unauthenticated Store API, where writes need a nonce.
Does Yoast's llms.txt help agents shop?
It helps them find your key pages: Yoast has generated llms.txt for free since June 2025 and refreshes it weekly. It doesn't put prices, delivery or returns on your product pages, so the fixes above still matter.
Do I need a WordPress plugin to use Aiscovery?
No. Aiscovery tests your store from the outside, the way an agent sees it, so there is nothing to install in WordPress.
Sources
Official documentation and announcements, checked on 21 October 2026. Platforms change often, so check the source before you change settings.
- 1.do_robots()WordPress developer reference
- 2.robots_txt filterWordPress developer reference
- 3.How to edit robots.txt through Yoast SEOYoast
- 4.Block unwanted bots with Yoast SEOYoast
- 5.Yoast SEO release: llms.txtYoast, 10 June 2025
- 6.How to edit robots.txt with Rank MathRank Math
- 7.Wordfence Security (plugin and its rate limiting settings)WordPress.org plugin directory
- 8.class-wc-structured-data.phpWooCommerce on GitHub
- 9.Add return policy page selection and OnlineStore markup (#69002)WooCommerce on GitHub, 30 September 2026
- 10.Variable productWooCommerce docs
- 11.Setting up shipping zonesWooCommerce docs
- 12.Refund policy page guidelinesWooCommerce docs
- 13.AI and agentic commerce in WooCommerceWooCommerce developer blog, 3 October 2025
- 14.Store APIWooCommerce developer docs
- 15.WooCommerce MCPWooCommerce developer docs
- 16.Introducing the Agentic Commerce SuiteStripe, 11 December 2025
- 17.Stripe Agentic Commerce Suite for WooCommerceWooCommerce, 11 December 2025
- 18.Stripe Sessions 2026 announcementsStripe, 29 April 2026
- 19.Agentic commerceWooCommerce
- 20.Cloudflare changes how AI crawlers scrape the internetCloudflare, 1 July 2025
- 21.AI bot policiesCloudflare docs
- 22.Bot Fight ModeCloudflare docs
Related guides
- Can AI agents shop a Shopify store?Read the guide
- Can AI agents shop a Magento store?Read the guide
- Can AI agents shop a custom-built store?Read the guide
Platform names and logos belong to their owners. Aiscovery is not affiliated with them; we test any store from the outside.
See what agents see on WooCommerce.
Tell us your store and we'll show you, on a short call, what AI agents could and couldn't find there, and the fix for each.
Have a real workflow to test now? Apply as a launch partner