This guide sets up a WooCommerce store so AI systems can find it, read it, and quote it. It covers the work in the order that matters: let the crawlers in, fix the product facts, check the structured data, add the files that describe your store, then publish content worth citing. It does not cover running ads, and it does not promise a citation or a recommendation. No vendor publishes a formula for what gets cited, and no setup step on WooCommerce changes that.
WooCommerce runs on WordPress, and that gives you more control than a hosted platform, and more ways to break things. You control the theme, the robots file, the structured data, the plugins, and the server. Keep a backup before you change anything, and test code changes on a staging copy where you have one. Screens and menu names change, so check the vendor docs in Sources for the current path before relying on a menu name or click path in this guide.
Who does which step
Two people may be involved, and the split matters. The marketer uses the WordPress admin dashboard, the product editor, and plugin settings to edit titles and descriptions, set prices and stock, write blog posts, and configure an SEO plugin. The developer uses theme code, editing theme files or a child theme directly, or using version control where the store already has it, and edits theme templates and structured data. If you are both people, keep the split in mind anyway, because a code edit made like a dashboard edit is how stores break their theme.
Step 1. Let the AI crawlers in
Start by reading the live robots.txt file. Open your store domain followed by robots.txt in a browser and read it top to bottom. WordPress generates this file dynamically rather than storing it as a physical file by default, and an SEO plugin can add an editor for it inside the admin. If you see a rule that blocks GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot, or Google-Extended, that rule is the first thing to fix.
The marketer can usually fix a robots.txt rule through the SEO plugin's editor, where one is installed. The developer fixes it where the file is managed at the server or host level. Keep the rules narrow. Allow the crawlers you want, and keep the blocks on the paths that should stay out: the admin, the cart, the checkout, and the account pages.
Do not stop at robots.txt. A security plugin or a firewall can block a crawler that robots.txt allows. After any change, check the live robots.txt file again to confirm the change actually appears, and check your server logs for the crawlers you want: OAI-SearchBot for ChatGPT search, PerplexityBot for Perplexity, and the others named in our robots.txt guide. OpenAI says it can take about 24 hours from a robots.txt update for its systems to adjust for search, and Perplexity says it may take up to 24 hours for its systems to reflect changes. Wait for that window before you conclude a fix did not work.
Step 2. Fix the product data in the editor
A product page is the unit an AI system reads, quotes, and links to. Before you add any file or plugin, make the pages themselves worth reading. The marketer does this part in the WooCommerce product editor.
WooCommerce documents the product editor as the place where every product can be edited at any time to update pricing, description, and imagery. The editor holds the product name, the product description, the short description, and the product data panel, where the majority of the important data about a product lives. Write a product name that names the product plainly, and a description that states what it is, what it is for, what it is made of, and the limits a buyer needs to know. Use the short description for the summary near the price, and the main description for the detail. Put the price, the options, and the stock status where a reader can see them without clicking. Keep the price current.
Set the inventory honestly. WooCommerce lets you manage stock at the product level or at the variation level. For a variable product, each variation can have its own price, stock status, and image, so set the stock for each variation, not only for the product as a whole. When a product sells out, update the stock status the same day. When a product is discontinued, say so on the page.
Work through your best sellers first. They are the products an assistant is most likely to be asked about. Fix the pages that earn the questions, then work down the list.
Check for conflicts. If the same product shows a different price in your store, in a marketplace listing, and in a review roundup, an AI system has three answers and no reason to trust any of them. Fix the source of the conflict so they agree.
Step 3. Check the structured data, and keep one source
WooCommerce outputs some basic product markup on its own, and an SEO plugin can make it far more complete. Pick one source and keep it. Do not run two schema-generating plugins at the same time, or you can end up with duplicate, conflicting markup. The marketer configures the single SEO plugin from the admin. The developer checks the theme output, because a theme can also inject its own block, and reconciles the two before anything is published.
Check what is actually there. The developer opens a live product page, views the page source, and searches for the structured data block. Confirm it states the product name, price, currency, and availability, and that it matches what the visible page says. Then run a sample of product pages through a structured data validation tool. If the output is missing or wrong, fix it in the one place that owns it, and test before publishing.
Google says structured data is not required for its generative AI features, and there is no special schema markup you need to add for them. It also says structured data helps with rich results and helps Google understand price, discount, and shipping costs on a page. Other engines use it to verify what a page claims. Treat schema as the confirmation of the facts on the page, not as a ticket into an answer.
Pay attention to variable products. WooCommerce documents that a variable product lets you offer a set of different options, with control over prices, stock, and images for each variation. Make sure the markup reflects that. A page that shows one price for the product and different prices per variation, without marking up the variations, gives an agent a single answer to a question that has several.
Step 4. Add llms.txt and a clean sitemap
An llms.txt file is a short markdown briefing at your site root that tells models what you sell, who it is for, and where the key pages are. It is written for models generally. Google Search does not use llms.txt, and Google says so directly, but other assistants can read it. Keep the file short: name your brand, state what you sell, and link to your best category pages, guides, and shipping and returns pages. Do not paste your whole catalog into it.
WordPress does not publish llms.txt by default, so this is a step to plan, not a setting to toggle. The marketer writes the content of the file: the brand description, the audience, and the links. The developer publishes it at the site root and confirms it loads at your store domain followed by llms.txt. Read our llms.txt guide for the file format and a complete sample.
Check your sitemap while you are here. Your SEO plugin should generate one listing your product pages, category pages, and guides. Submit it in Google Search Console. A stale sitemap makes new and changed pages harder to find.
Step 5. Publish content worth citing
A store with good product pages and no other content gives an AI system facts but no answers. Publish the guides and comparisons your customers actually ask for: how to choose between two of your products, how to use the product, and how to fix the common problem. The marketer writes these in the WordPress post editor. Open with a direct answer, then give the detail, then state the limits. Use your own first-hand experience, because Google says a first-hand review provides a unique perspective based on personal experience, while a summary of existing content simply restates information already available elsewhere.
Do not create a separate page for every possible phrasing of the same question. Google warns against creating separate content for every possible variation to manipulate rankings, since that can violate its scaled content abuse spam policy. One good guide per real question, kept current, beats ten thin pages.
Use the post settings your SEO plugin provides. Keep the author real, and keep the author page honest. A fabricated author profile makes a page untrustworthy.
Step 6. Check the store the way an assistant would
After the setup steps, test the store as an outsider. Ask the assistants themselves what they say about your brand, using the questions your customers ask. If they cannot name your products or state your prices correctly, look at what they cite instead. The gap is usually in the facts: a missing price, a missing size, a blocked crawler, or a page that never states the use case.
Run the free scan as well. It checks whether AI crawlers can read your store today. Fix the failures in the order in this guide: access first, product facts second, markup third, content fourth. A store that is blocked at the edge is invisible no matter how good its content is.
The fundamentals
These mechanics are shared across every engine and covered in full in their own guides:
- •The llms.txt format and a complete sample, see our guide to writing a good llms.txt file
- •The markup AI systems read to verify facts, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
Say you run a loose-leaf tea merchant on WooCommerce
Say you run a loose-leaf tea merchant on WooCommerce, selling black, green, and herbal teas in three bag sizes. The marketer rewrites the product pages in the product editor, so each tea states the origin, the caffeine level, the brewing temperature and time, the bag sizes, and the price for each size in plain text. The developer checks the theme output, finds two plugins both injecting Product schema, removes one, and confirms the remaining block matches the visible page. The developer also finds a security plugin blocking PerplexityBot, allows it, and confirms the crawler arrives in the logs. The marketer writes one guide, how to brew green tea without bitterness, opening with a direct answer and showing the actual steeping times tested in the shop. A shopper asks an assistant for a green tea that brews well at a lower temperature under a set budget. The assistant can check your temperature, your price, and your stock, and it cites your guide for the brewing advice.
What this guide does not cover
This guide covers the AI SEO setup for a WooCommerce store. It does not cover the full technical audit that checks every crawler and every page, the transaction layer that lets an agent complete a purchase, or the per-engine playbooks for getting each assistant to find you. Those are separate jobs, and this guide is the map, not the whole trip.
Check your own store now
Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan
Run the free scanSources
- WooCommerce, Variable Products documentation (specific): https://woocommerce.com/document/variable-product/
- WooCommerce, Product Editor settings documentation (specific): https://woocommerce.com/document/managing-products/product-editor-settings/
- OpenAI, Overview of OpenAI crawlers (specific): https://platform.openai.com/docs/bots
- Perplexity, Perplexity crawlers (specific): https://docs.perplexity.ai/guides/bots
- Google Search Central, Optimizing your website for generative AI features on Google Search (specific): https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Google Search Central, Share your product data with Google (specific): https://developers.google.com/search/docs/specialty/ecommerce/share-your-product-data-with-google
- Schema.org, Product type (specific): https://schema.org/Product
- llms.txt proposal (specific): https://llmstxt.org
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.
