How do AI search engines like ChatGPT find products?

AI answer engines rely on web crawls, structured data, and (increasingly) machine-readable feeds. Most do not execute JavaScript, so they read your server-rendered HTML, JSON-LD structured data, sitemaps, and discovery files like llms.txt. Clean, crawlable, well-structured product data is what makes a store citable.

What is llms.txt and do I need it for ecommerce?

llms.txt is a plain-text file at your site root that points AI agents to your most important, machine-readable resources. For ecommerce it can link to your product feeds and catalog endpoints, giving answer engines a clean map of your catalog instead of forcing them to scrape rendered pages.

Should I block AI crawlers like GPTBot and ClaudeBot?

If you want your products to appear in AI answers, allow them. Blocking GPTBot, ClaudeBot, PerplexityBot, or Google-Extended in robots.txt removes your catalog from those systems. Allow the crawlers you want to be discovered by, and expose only public catalog data, never customer or order information.

Guides / AI search visibility

How to Make Your WooCommerce Store Visible to ChatGPT & AI Search

A growing share of buying journeys now start with a question to ChatGPT, Perplexity, or Google’s AI Overviews instead of a search box. If those systems can’t read your catalog, your products simply don’t exist in the answer. This is answer engine optimization (AEO) — here’s how it works for WooCommerce.

How answer engines actually read your store

AI search differs from classic SEO in one decisive way: most AI crawlers do not run JavaScript. They fetch your raw HTML, parse any structured data, follow your sitemap, and look for machine-readable resources. If your product data only appears after a React or AJAX render, the answer engine sees an empty shell.

What they can read well:

Server-rendered HTML with real product content
Product JSON-LD structured data (price, availability, brand, GTIN)
sitemap.xml and clean, crawlable URLs
Discovery files: robots.txt, llms.txt, and JSON/XML product feeds

Step 1 — Let the right crawlers in

Check your robots.txt. To appear in AI answers you need to allow the agents that power them. Blocking them is the single most common reason a store is invisible to AI search:

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Allow discovery, but only expose public catalog data. Never let crawlers reach customer accounts, orders, or checkout. This is exactly the read-only boundary Easy Woo API is built around.

Step 2 — Give them structured product data

Structured data is the language answer engines trust most, because it is unambiguous. A product with complete Product schema — name, brand, GTIN, price, availability, rating — is far more likely to be cited accurately than one described only in prose. If you haven’t done this yet, start with adding rich Product schema to WooCommerce.

Step 3 — Publish an llms.txt and product feeds

llms.txt is an emerging convention: a plain-text file at your domain root that hands AI agents a curated map of your machine-readable resources, instead of making them guess. For a store, it points to your catalog feeds and endpoints:

# llms.txt — https://yourstore.com/llms.txt
# Public, read-only product data for AI agents and answer engines.

## Product feeds
- Catalog (JSON): https://yourstore.com/api/products.json
- Catalog (XML):  https://yourstore.com/api/products.xml

## Single product
- By SKU:  https://yourstore.com/api/products/{sku}.json
- By slug: https://yourstore.com/api/products/by-slug/{slug}.json

Pair that with a structured product feed (JSON and XML) so an agent can ingest your entire catalog in one request rather than scraping thousands of pages. This is the difference between being partially scraped and being fully understood.

Step 4 — Make sure content is in the HTML, not just the JS

If your storefront or landing pages render content client-side, add a server-rendered or pre-rendered fallback so non-JavaScript crawlers see the real text. Test by fetching a page with JavaScript disabled, or with curl, and confirming the product details are present in the raw HTML.

How Easy Woo API fits

Easy Woo API automates steps 2–3: it publishes complete Product schema, generates an llms.txt, and exposes JSON and XML catalog feeds plus per-product endpoints — all public and read-only, with private store data never exposed. It’s the discovery layer WooCommerce doesn’t ship on its own. See how it works or browse the documentation.

Related: ready to also list in Google Shopping? Read How to create a Google Merchant Center feed from WooCommerce.