---
title: "AI Ready and the schema detector for WooCommerce"
url: "https://aeoultimate.com/docs/woocommerce/ai-ready-schema-detector/"
description: "Make your WooCommerce store readable to AI: clean Markdown pages, llms.txt, a knowledge bundle and content signals, plus a detector for missing schema."
author: "David Chamberlain"
published: "2026-10-14T17:56:17+00:00"
modified: "2026-10-15T15:50:04+00:00"
language: "en-US"
site: "AEO Ultimate"
---

Source: https://aeoultimate.com/docs/woocommerce/ai-ready-schema-detector/

AEO Ultimate for WooCommerce

# Make your store readable to AI

AI agents and crawlers read your store differently from people. AI Ready gives them clean versions of your pages, files that describe the whole store, and a clear statement of how AI may use your content. The Schema Detector then finds pages that should carry schema but do not. Watch the walkthrough, or read the guide below.

AI Ready and the schema detector on a real WooCommerce store.

Read the transcript

**0:00 Readable by AI agents**
AI Ready makes your store readable to AI agents and crawlers: clean versions of your pages, files that describe the whole store, and a clear statement of how AI may use your content.

**0:14 Clean Markdown for agents**
When an agent asks for Markdown, it gets a clean version of the page instead of the HTML: fewer tokens, less noise. On a product, it opens with the facts an agent needs, price, stock, SKU and options, taken from the same source as your product schema.

**0:36 llms.txt**
llms.txt is a short guide to your store for AI models: your pages, your biggest categories, and your collections, with a note on how many more there are, never a list that silently stops.

**0:52 A knowledge bundle**
The knowledge bundle publishes the whole store as Markdown files an AI can read without crawling: your organization, every product and category, and your policies, each with a header it can parse.

**1:08 How AI may use your content**
Content signals tell AI companies what they may do with your content: train on it, index it for search, or use it to answer a question. They're sent with every page and written into robots.txt.

**1:22 Pages stay open to crawlers**
The rate limit protects only the agent API endpoints. Your pages and products are never rate-limited, because crawlers reading your store are the point. To keep one crawler out entirely, block it.

**1:38 The schema detector**
The Schema Detector looks through your pages and posts for content that should carry schema but doesn't, like a list of questions with no FAQ markup, or a contact page with no address. Conflicts finds schema left behind by other SEO plugins. On this store, there's nothing to fix.

**1:58 Next: the RAG Engine**
That's AI Ready: your store, in a form AI can read. Next, the RAG Engine, which matches your product documents to your product pages.

## Where is AI Ready in AEO Ultimate for WooCommerce?

Open **AEO Ultimate → Discovery → AI Ready**. Each feature has its own switch and a note on what it does; the header shows how many are on.

[Image: AI Ready screen in AEO Ultimate for WooCommerce showing 9 of 10 features active and the Markdown Content Negotiation feature switched on, with the ?aeo_format=markdown URL fallback ticked]

AI Ready: what AI agents and crawlers get from your store, one switch per feature.

## What does an AI agent see when it asks for Markdown?

When an agent asks for a page with an `Accept: text/markdown` header, it gets a clean Markdown version instead of the HTML: fewer tokens, less noise. With the URL fallback on, adding `?aeo_format=markdown` to any page does the same, for CDNs that strip the header. On a product, the Markdown opens with the facts an agent needs (price, stock, SKU and options) taken from the same source as your product schema, so the two cannot disagree.

[Image: The Hoodie product page served as Markdown: source URL, then a Facts list with product type, SKU woo-hoodie, price 42.00 to 45.00 USD, availability in stock, colour and logo options, then the description]

A product as an agent receives it: the facts first, from the same source as the product schema.

## What is llms.txt?

`/llms.txt` is a short guide to your store for AI models: your pages, your biggest categories and your collections. Where there are more than it lists, it says how many more, rather than a list that silently stops.

[Image: The store's llms.txt: store name and address, a link to the knowledge bundle at /okf/, a Pages section and a Products section listing the shop and its product categories]

llms.txt: a short guide to the store for AI models.

## What is the knowledge bundle?

The knowledge bundle at `/okf/` publishes the whole store as Markdown files an AI can read without crawling: your organization, every product and category, and your policies. Each file starts with a header an AI can parse: what it is, where it lives, and when it was generated.

[Image: A product file from the knowledge bundle: a header with type Product, title, description, resource URL, status and when it was generated, followed by the product description and its facts]

One file per product in the knowledge bundle, each with a header an AI can parse.

## How do I tell AI companies how they may use my content?

**Content signals** state three separate permissions: whether AI may train on your content, index it for search, or use it as input to answer a question. You can say yes to one and no to another. They are sent as a header with every page and written into `robots.txt`.

[Image: Content-Signal Headers and robots.txt settings: AI training set to do not train, AI search indexing allowed, AI input allowed, giving the directive Content-Signal: ai-train=no, search=yes, ai-input=yes]

Three separate permissions: training, search indexing, and use as input to an answer.

## Does the rate limit block crawlers from my pages?

No. The rate limit protects only the agent API endpoints (Agent Search and MCP), 60 requests per address per hour by default. Your pages and products are never rate-limited, because crawlers reading your store are the point. To keep one crawler out entirely, set it to **Block** under Per-Bot Controls: that writes a Disallow rule into `robots.txt` and refuses its requests.

[Image: Rate Limiting set to 60 agent API requests per address per hour, with the note that pages and products are never rate-limited, above the Per-Bot Controls table listing GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot and others, each set to Allow]

The limit covers the agent API only. To keep one crawler out, block it.

## What does the Schema Detector find?

Open **AEO Ultimate → Discovery → Schema Detector**. It looks through your pages and posts for content that should carry schema but does not. The **FAQ** tab finds question-and-answer content with no FAQ markup, whether it was built with FAQ blocks, accordions or question headings. The **Contact** tab checks contact pages for an address and contact details in their schema.

[Image: Schema Detector FAQ tab with 0 pages with FAQ content, 0 missing FAQPage schema and 0 with FAQPage schema present, and the six detection methods it uses]

The FAQ check and the six ways it recognises question-and-answer content.

**Conflicts** finds schema data left in your database by other SEO plugins, such as Yoast SEO, Rank Math and All in One SEO, and can clear it. It does not uninstall anything. On this store there was nothing to fix.

[Image: Schema Detector Conflicts tab: Delete SEO Plugin Schema Data, with Yoast SEO, Rank Math, All in One SEO and Schema & Structured Data for WP & AMP each inactive and no data found]

Schema left behind by other SEO plugins. On this store there was none.

## What should I set up next?

Next is the RAG Engine, which matches your product documents to your product pages.

## All WooCommerce tutorials

1. [Getting started](https://aeoultimate.com/docs/woocommerce/getting-started/)
2. [Product schema](https://aeoultimate.com/docs/woocommerce/product-schema/)
3. [Agent Ready](https://aeoultimate.com/docs/woocommerce/agent-ready/)
4. [Agentic checkout](https://aeoultimate.com/docs/woocommerce/agentic-checkout/)
5. [Merchant Center](https://aeoultimate.com/docs/woocommerce/merchant-center/)
6. [Meta descriptions and AI enrichment](https://aeoultimate.com/docs/woocommerce/meta-descriptions-ai-enrichment/)
7. [Store trust and reviews](https://aeoultimate.com/docs/woocommerce/store-trust-reviews/)
8. [Local Store](https://aeoultimate.com/docs/woocommerce/local-store/)
9. [Smart Collections](https://aeoultimate.com/docs/woocommerce/smart-collections/)
10. [Promotions and price rules](https://aeoultimate.com/docs/woocommerce/promotions/)
11. [AI citations and the crawler log](https://aeoultimate.com/docs/woocommerce/ai-citations-crawler-log/)
12. **AI Ready and the schema detector**
13. The RAG Engine (coming soon)

← Previous: [AI citations and the crawler log](https://aeoultimate.com/docs/woocommerce/ai-citations-crawler-log/)

Next: The RAG Engine (coming soon) →