WooCommerce and AI shopping: get your store ready in one afternoon

WooCommerce gives you full control over your store. That is a strength, and it is also why WooCommerce stores so often block AI assistants by accident. Between your hosting, your CDN and your plugins, there are many places where a bot can get turned away.

This checklist fits in one afternoon. You do not need to write code.

Why WooCommerce stores get skipped

An AI assistant recommends stores it can read, understand and trust. On WooCommerce, the usual problems are:

• A security plugin or hosting firewall that blocks anything that looks like a bot.
• Cloudflare rules that block AI agents. Cloudflare changed its defaults on September 15, 2026.
• Two SEO plugins that output two different Product blocks.
• Prices built by plugins (bundles, dynamic pricing) that never reach the structured data.
• No product feed, so assistants only see what they happen to crawl.

Step 1: open the door (30 minutes)

Check robots.txt

WordPress generates a virtual robots.txt. Yoast and Rank Math let you edit it from the dashboard. Open yourstore.com/robots.txt and make sure there is no Disallow: / under GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot or PerplexityBot.

Check the firewall

robots.txt is a request. A firewall is a wall. Test a product page with a bot user agent:

curl -s -o /dev/null -w "%{http_code}\n" -A "Mozilla/5.0 (compatible; GPTBot/1.1; +https://openai.com/gptbot)" https://yourstore.com/product/your-product/

You want a 200. A 403 or 503 means Wordfence, your host or Cloudflare blocked it. Our post on whether Cloudflare blocks ChatGPT explains the Cloudflare side step by step.

Step 2: one clean Product block (1 hour)

WooCommerce core already adds Product structured data to product pages. Yoast WooCommerce SEO and Rank Math can extend it with brand, GTIN and more. That is good. Two outputs at once are not.

1. Open a product page and run it through Google's Rich Results Test.
2. Count the Product items. You want exactly one.
3. Check it has name, image, description, and an Offer with price, priceCurrency and availability.
4. If your SEO plugin supports it, add brand and GTIN. They help assistants match your product with the same item elsewhere.

For the full field list and an example, see product schema for AI shopping agents.

Step 3: prices and stock that match (30 minutes)

Pick three products: a simple one, a variable one, and one on sale. For each, compare the visible price with the price in the markup. Check the currency is right (USD, GBP, EUR). Check that out of stock items say OutOfStock. Dynamic pricing and currency switcher plugins are the usual cause of mismatches.

Step 4: send a feed (1 hour)

Install Google for WooCommerce and connect Google Merchant Center. It is free and it pushes your full catalog with current prices and stock. Free product listings in Google come from this feed.

If you sell in the US, OpenAI and Perplexity also run merchant feed programs. ChatGPT finds products through those feeds and sends shoppers to your site to buy.

Step 5: the small files (15 minutes)

llms.txt

A short text file at your root that lists your key pages with one line each. Google has said it ignores it, so it will not lift your rankings. It is cheap, and some AI agents read it. The free plugin Website LLMs.txt has around 30,000 active installs, or you can make one with our llms.txt generator and upload it.

agents.md

A plain file that tells AI agents who you are and what they can do on your store. Our agents.md generator fills it in from five fields.

Step 6: trust pages (30 minutes)

Assistants answer questions like "do they ship to Canada?" and "what is the return window?". Make those answers easy to find:

• Shipping page with countries, costs and delivery times in numbers.
• Returns page with the window in days and who pays return shipping.
• Contact details in the footer.
• An About page with your business name.

Plugin conflicts to watch for

Most WooCommerce problems with AI bots come from plugins that work fine for humans:

• Security plugins. Wordfence and similar tools can rate limit or block unknown crawlers. Check their live traffic log for blocked GPTBot or ClaudeBot requests, and allow them if needed.
• Caching plugins. Some serve a different page to bots, sometimes an old one with old prices. Test with curl and compare the price you get with the live page.
• Age gates and cookie walls. If a popup must be clicked before the product shows, a bot may only see the popup.
• Maintenance mode leftovers. A coming soon plugin that still answers bots with a 503 after launch.

After every plugin change, run the curl test again. It takes ten seconds.

What to expect after

Be realistic. AI referred traffic was 0.89% of ecommerce visits in May 2026, per Similarweb. It is growing quickly, and Adobe found those visitors convert better than average. You are not chasing a flood. You are fixing a few things once, so you are in the answer when the shopper asks.

The same work prepares you for agent checkout. It is live in the US through specific programs and not yet open in most other markets. Clean data is what every one of those programs asks for.

Check your work

Run the free AISaysYes scan before and after. It checks robots.txt rules for each AI bot, product data, prices and the small files, then gives you a 0 to 100 score with each issue explained. The guide goes deeper on every fix, and the ranking shows how other stores score.

Stores that already passed the scan