# Agent readiness vs SEO: what's different for ecommerce

> Agent readiness builds on ecommerce SEO but goes further. Both need crawlable pages, sitemaps, server-rendered content and Product structured data. Agent readiness adds robots and WAF rules for AI bots, pages browsing agents can operate, and machine interfaces such as UCP profiles, MCP endpoints, Markdown pages, llms.txt and checkout permalinks.

- Source: https://is-agentic-storefront.com/guides/agent-readiness-vs-seo
- Updated: 2026-10-15

## How is agent readiness different from SEO?

Agent readiness and SEO answer different questions. SEO asks whether a search engine can crawl, index and rank your pages. Agent readiness asks whether an AI agent can reach your store, read product facts, operate the page and, ideally, buy through an API on a shopper's behalf. For ecommerce stores, the two share a foundation of crawlable, server-rendered pages with good structured data. Agent readiness then adds bot policy, page operability and commerce protocols that search engines don't care about.

## What do agent readiness and SEO have in common?

Ecommerce SEO and agent readiness overlap on four technical foundations. If your SEO is in good shape, you already pass much of the [product data](https://is-agentic-storefront.com/guides/agent-ready-ecommerce#product-data-25-can-ai-agents-read-your-products) and [discovery](https://is-agentic-storefront.com/guides/agent-ready-ecommerce#discovery-15-can-ai-agents-find-your-catalog) categories.

- **Sitemaps.** Both search engines and AI agents use [XML sitemaps](https://www.sitemaps.org/protocol.html) to list your catalog. The [sitemap check](https://is-agentic-storefront.com/checks/sitemap) also confirms that product URLs in it return `200`.
- **Structured data.** [Product and Offer JSON-LD](https://developers.google.com/search/docs/appearance/structured-data/merchant-listing) powers merchant listings in Google. OpenAI says ChatGPT shopping uses "structured metadata from first-party and third-party providers" ([OpenAI](https://help.openai.com/en/articles/11128490-shopping-with-chatgpt-search)). See [Product JSON-LD](https://is-agentic-storefront.com/checks/product-json-ld), [variants](https://is-agentic-storefront.com/checks/product-variants) and [return and shipping data](https://is-agentic-storefront.com/checks/return-shipping-data).
- **Server-side rendering.** Googlebot renders JavaScript, but a Vercel log study found that GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot and PerplexityBot did not ([Vercel](https://vercel.com/blog/the-rise-of-the-ai-crawler)). SSR matters more for agents than for Google. See [product facts in server HTML](https://is-agentic-storefront.com/checks/ssr-product-facts).
- **Canonicals and status codes.** [Canonical URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) and real `404`s instead of [soft 404s](https://developers.google.com/search/docs/crawling-indexing/troubleshoot-crawling-errors#soft-404-errors) stop both search engines and agents from treating dead products as live. See [canonical and status codes](https://is-agentic-storefront.com/checks/canonical-status).

## What does agent readiness add on top of SEO?

Agent readiness adds requirements that an SEO audit doesn't check, because search engines don't shop.

### Robots and WAF policy for AI bots

SEO usually only checks `Googlebot` and `Bingbot`. Agent readiness checks more than 20 AI user agents and treats them differently: blocking training crawlers is fine, blocking AI search bots and user-initiated agents is not. WAFs and CDNs also block AI user agents even when robots.txt allows them. See [AI crawler and agent user agents](https://is-agentic-storefront.com/guides/ai-user-agents), [robots.txt](https://is-agentic-storefront.com/checks/robots-txt) and [agent access](https://is-agentic-storefront.com/checks/agent-access).

### Operability for browsing agents

Browsing agents click your buttons and fill your forms. Google's Lighthouse notes that "Agents rely on the accessibility tree as their primary data model" ([Chrome](https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents)). SEO doesn't care whether add to cart is a `<button>` or a `<div>`, but an agent does. See [add to cart](https://is-agentic-storefront.com/checks/add-to-cart), [variant controls](https://is-agentic-storefront.com/checks/variant-controls), [accessible names](https://is-agentic-storefront.com/checks/accessible-names) and [no CAPTCHA](https://is-agentic-storefront.com/checks/no-captcha).

### Commerce protocols (UCP and MCP)

The [Universal Commerce Protocol](https://ucp.dev/latest/specification/overview/) lets a store publish its capabilities at `/.well-known/ucp`, usually with an [MCP](https://modelcontextprotocol.io/) endpoint agents can call to search, build carts and start checkout. Search engines don't use these. See [UCP profile](https://is-agentic-storefront.com/checks/ucp-profile), [live agent endpoint](https://is-agentic-storefront.com/checks/agent-endpoint) and [agentic commerce protocols](https://is-agentic-storefront.com/guides/agentic-commerce-protocols).

### Markdown pages and llms.txt

[Markdown for Agents](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents) serves a Markdown version of a page for `Accept: text/markdown`, and [llms.txt](https://llmstxt.org/) is a curated Markdown map of a site. Both reduce tokens for agents. Google says Google Search doesn't use them ([Google](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)), so they're Low weight here. See [Markdown alternative](https://is-agentic-storefront.com/checks/markdown-alternative) and [llms.txt](https://is-agentic-storefront.com/checks/llms-txt).

### Checkout permalinks

A [checkout permalink](https://ucp.dev/2026-08-25/specification/permalink/) is a URL that builds a cart and redirects to checkout, for example `/buy/{variant_id}:{qty}` in the UCP format. An agent can hand it to the shopper to finish payment. No search engine needs this. See [checkout permalinks](https://is-agentic-storefront.com/checks/checkout-permalinks).

## How do agent readiness and SEO compare side by side?

| Signal                                          | Ecommerce SEO                  | Agent readiness                          |
| ----------------------------------------------- | ------------------------------ | ---------------------------------------- |
| XML sitemap with product URLs                   | Yes                            | Yes, declared in robots.txt              |
| Product JSON-LD (price, availability)           | Yes, for rich results          | Yes, plus a match with the visible price |
| `ProductGroup` variants                         | Yes                            | Yes                                      |
| Return policy and shipping structured data      | Recommended                    | Yes                                      |
| Server-side rendering                           | Helpful (Googlebot renders JS) | Required (most AI bots don't run JS)     |
| Canonical URLs, no soft 404s                    | Yes                            | Yes                                      |
| robots.txt rules                                | Googlebot, Bingbot             | 20+ AI search, user and training tokens  |
| WAF and bot-challenge behavior                  | Rarely checked                 | Core check                               |
| CAPTCHA on shopping pages                       | Not relevant                   | Hard stop for agents                     |
| Real buttons, labelled inputs, variant controls | Not ranked                     | Core check                               |
| GET search URL                                  | Not relevant                   | Core check                               |
| Markdown pages, `llms.txt`                      | Not used by Google Search      | Low weight                               |
| UCP profile, MCP endpoint, OAuth discovery      | Not relevant                   | Agentic commerce category                |
| Checkout permalinks                             | Not relevant                   | Agentic commerce category                |

## Where does GEO fit in?

GEO, or generative engine optimization, sits between SEO and agent readiness. GEO is about getting your pages read and cited by AI answer engines such as ChatGPT search, Perplexity, Claude and Google AI Mode. For an ecommerce store, the GEO requirements are mostly agent-readiness basics:

- **Let AI search bots in.** `OAI-SearchBot`, `Claude-SearchBot`, `PerplexityBot` and similar bots must reach product pages, in robots.txt and at the WAF.
- **Put answers in the HTML.** Prices, availability, sizes and policies should be in server-rendered text and structured data, not only in JavaScript.
- **Keep facts consistent.** If JSON-LD and the visible page disagree on price, an AI answer may quote the wrong one.
- **Publish policies.** AI answers to "does this store offer free returns?" can only cite a returns page that agents can find. See [policy links](https://is-agentic-storefront.com/checks/policy-links).

Google's guidance says you don't need new machine-readable files, AI text files or Markdown for its AI features ([Google](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)). Other assistants run their own crawlers, which is why the robots and access checks matter beyond Google.

## Should I prioritize SEO or agent readiness?

Prioritize the overlap first, since it pays off for both: SSR product facts, complete Product JSON-LD, a sitemap and real `404`s. Then fix the agent-only issues that cost the most: unblock AI search bots and user agents, remove CAPTCHAs from shopping pages, and make add to cart and variant selectors real controls. Protocols like UCP come last. The order and weights are in [agent-ready ecommerce](https://is-agentic-storefront.com/guides/agent-ready-ecommerce#where-should-i-start-making-my-store-agent-ready) and the [scoring methodology](https://is-agentic-storefront.com/guides/scoring-methodology).

[Scan your store](https://is-agentic-storefront.com/) to see where it stands, or browse the [glossary](https://is-agentic-storefront.com/glossary) for terms like UCP, MCP and soft 404.

## Frequently asked questions

### If my store has good SEO, is it agent-ready?

Partly. Good SEO usually means sitemaps, canonical URLs, server-rendered pages and Product JSON-LD, which cover much of the product data and discovery categories. It says nothing about whether AI bots are blocked by your WAF, whether browsing agents can use your add-to-cart button, or whether agents can buy through a protocol like UCP.

### Does Google use llms.txt or Markdown pages for AI search?

No. Google says Google Search doesn't use AI text files or Markdown versions and that you don't need to create them. They're aimed at other agents, and the scorer gives them Low weight.

### What is GEO in ecommerce?

GEO (generative engine optimization) means making content easy for AI answer engines like ChatGPT, Perplexity and Google AI Mode to find, read and cite. For a store, that means allowing AI search bots, server-rendering product facts and publishing accurate structured data.

### Is structured data still worth adding for AI agents?

Yes. Google says structured data isn't required for its AI features, but OpenAI says ChatGPT shopping uses structured metadata, and AI agents that don't run JavaScript can only read JSON-LD that is in the server HTML.

## Run your store on a platform built for agentic commerce

Medusa is open-source, headless commerce with a full Store API agents can call and storefronts you control end to end.

### Deploy on Medusa Cloud

Open-source commerce with a full Store API, hosted and scaled for you. Your storefront, your data model.

- [Deploy on Medusa Cloud](https://cloud.medusajs.com?utm_source=agent-friendly-scorer&utm_medium=referral&utm_campaign=markdown-cta&utm_content=%2Fguides%2Fagent-readiness-vs-seo)
- [Medusa Cloud docs](https://docs.medusajs.com/cloud?utm_source=agent-friendly-scorer&utm_medium=referral&utm_campaign=markdown-cta&utm_content=%2Fguides%2Fagent-readiness-vs-seo)

### Storefront skills for coding agents

Teach Claude Code, Cursor or Codex to build storefronts with the patterns these checks look for.

```bash
npx skills add medusajs/medusa-agent-skills
```

[View the skill on GitHub](https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/ecommerce-storefront/skills/storefront-best-practices)

---

Scan your store for free at https://is-agentic-storefront.com/