---
title: "Adobe Commerce: agent-ready recipes | Agent Ready Checklist"
description: "Every agent-ready recipe for Adobe Commerce: 31 rows of the checklist, the version read, the date and the vendor documentation each step came from."
canonical: https://agentreadychecklist.com/platforms/adobe-commerce
site: "Agent Ready Checklist"
last_updated: 2026-11-05
section: "Platforms"
---

# Adobe Commerce: agent-ready recipes | Agent Ready Checklist

> Every agent-ready recipe for Adobe Commerce: 31 rows of the checklist, the version read, the date and the vendor documentation each step came from.

Source: https://agentreadychecklist.com/platforms/adobe-commerce
Site: Agent Ready Checklist
Last reviewed: 2026-11-05
Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search)
Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free).

# Adobe Commerce: agent-ready recipes

Adobe Commerce and Magento Open Source: 31 recipes against the 31 checklist rows, read on 2026-11-04. Adobe Commerce and Magento Open Source: 14 are direct, 16 are workarounds and 1 says plainly that the platform cannot do it, with the workaround. Version read for Adobe Commerce and Magento Open Source: 2.4.9.

## Version and documentation read

Version

2.4.9 (GitHub tag published 2026-05-12; 2.4.10-alpha1 tagged 2026-10-13); release notes read 2026-11-04

Read on

2026-11-04

Recipes

14 direct, 16 workaround, 1 not possible on the platform

robots.txt

[experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview). Content > Design > Configuration > Global > Search Engine Robots: Default Robots and Edit custom instruction of robots.txt File. robots.txt is generated by a controller when no physical file exists.

Sitemap

[experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/sitemap-xml](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/sitemap-xml). Marketing > SEO & Search > Site Map to generate; Stores > Configuration > Catalog > XML Sitemap with Enable Submission to Robots.txt = Yes.

Structured data

No first-party doc: No JSON-LD guide in the admin docs; add a head block through layout XML in the theme (frontend layout guide).

Status codes

[experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages](https://experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages). CMS pages include the 404 Not Found page used as the CMS No Route Page; Luma returns status 404 for unknown routes.

Headers and redirects

[experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/url-rewrites/url-rewrite](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/url-rewrites/url-rewrite). URL rewrites with 301 or 302 in Marketing > SEO & Search > URL Rewrites; response headers on cloud through Fastly custom VCL snippets.

Content negotiation

No first-party doc: No markdown output documented. Workaround: Fastly VCL or Cloudflare Markdown for Agents in front.

llms.txt

No first-party doc: No llms.txt feature documented. Workaround: place a static llms.txt in pub/ (on-premise) or serve it through a Fastly snippet on cloud.

OpenAPI

[developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/). Swagger UI at /swagger (Developer mode only since 2.4.4) and JSON schema at /rest/<store\_code>/schema?services=all with an admin token.

[The checklist table for Adobe Commerce and Magento Open Source](https://agentreadychecklist.com/platform/adobe-commerce/checklist/) shows every row with its first step.

## Verify with Ora

Adobe Commerce and Magento Open Source has a direct recipe for 14 rows, and Ora's catalogue (read 2026-11-05) names a matching check for 11 of them, among them AR-FIND-01, AR-FIND-03, AR-READ-01. After the steps are live, one audit shows which of those fixes the score picks up.

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

15 rows that Ora checks are a workaround or not possible on Adobe Commerce: [AR-FIND-04](https://agentreadychecklist.com/checklist/ar-find-04/) (ai-catalog-published, workaround); [AR-READ-05](https://agentreadychecklist.com/checklist/ar-read-05/) (code-fence-validity, not possible); [AR-READ-07](https://agentreadychecklist.com/checklist/ar-read-07/) (llms-txt-exists, workaround); [AR-READ-08](https://agentreadychecklist.com/checklist/ar-read-08/) (json-ld, workaround); [AR-READ-09](https://agentreadychecklist.com/checklist/ar-read-09/) (markdown-link-alternate, workaround); [AR-ACT-02](https://agentreadychecklist.com/checklist/ar-act-02/) (openapi-spec, workaround); [AR-ACT-03](https://agentreadychecklist.com/checklist/ar-act-03/) (mcp-server, workaround); [AR-ACT-04](https://agentreadychecklist.com/checklist/ar-act-04/) (mcp-server-card, workaround); [AR-ACT-05](https://agentreadychecklist.com/checklist/ar-act-05/) (mcp-app-registry, workaround); [AR-ACT-08](https://agentreadychecklist.com/checklist/ar-act-08/) (x402-support, workaround); [AR-ACT-09](https://agentreadychecklist.com/checklist/ar-act-09/) (nlweb-ask, workaround); [CF-MARKDOWN-NEGOTIATION](https://agentreadychecklist.com/checklist/cf-markdown-negotiation/) (markdown-negotiation-vary, workaround); [CF-OAUTH-DISCOVERY](https://agentreadychecklist.com/checklist/cf-oauth-discovery/) (oauth-protected-resource, workaround); [CF-AGENT-SKILLS](https://agentreadychecklist.com/checklist/cf-agent-skills/) (agent-skills-index-v2, workaround); [VERCEL-NEGOTIATION-HEADERS](https://agentreadychecklist.com/checklist/vercel-negotiation-headers/) (markdown-negotiation-vary, workaround). Ora scores the site as it stands, so a row the platform cannot satisfy stays open until the workaround is in place.

Run it again with `--force` after a deploy, so the audit skips Ora's cache. [Gate deploys on it in CI](https://agentreadychecklist.com/guides/gate-deploys-on-agent-readiness-in-ci/), [why this site recommends Ora](https://agentreadychecklist.com/verify-with-ora/), [the crosswalk of rows and checks](https://agentreadychecklist.com/checklist/ora-checks/).

## Recipes, row by row

### [AR-FIND-01](https://agentreadychecklist.com/checklist/ar-find-01/): Do not block agentsrecipe

Admin: Content > Design > Configuration > Global > Edit > Search Engine Robots. Set Default Robots to INDEX, FOLLOW and keep custom instructions free of Disallow: / for AI crawlers. Save, then flush cache. On cloud, also check Fastly and WAF rules.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview)

### [AR-FIND-02](https://agentreadychecklist.com/checklist/ar-find-02/): Answers on one first-party pagerecipe

Publish each answer once, as a page on your own domain. Put the fact (price, limit, version) in the page text, give the page one stable address, and link it from the home page and from llms.txt. Keep the page current: a second, older copy elsewhere on the site is the usual way an agent cites the wrong figure.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-FIND-03](https://agentreadychecklist.com/checklist/ar-find-03/): Sitemap listed in robots.txtrecipe

Marketing > SEO & Search > Site Map > Add Sitemap, Save & Generate. Stores > Settings > Configuration > Catalog > XML Sitemap > Search Engine Submission Settings > Enable Submission to Robots.txt = Yes. On cloud, write the file to the /media/ path.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/sitemap-xml](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/sitemap-xml)

### [AR-FIND-04](https://agentreadychecklist.com/checklist/ar-find-04/): AI Catalog at .well-knownworkaround

No catalog feature. On-premise, place pub/.well-known/ai-catalog.json if the web server serves it; on cloud, serve it with a Fastly custom VCL snippet (synthetic response).

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets](https://experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets)

### [AR-READ-01](https://agentreadychecklist.com/checklist/ar-read-01/): Answer in the initial HTMLrecipe

The Luma theme renders category, product and CMS pages server-side in PHP; keep prices and descriptions in templates rather than KnockoutJS-only blocks. Headless (PWA Studio or other) storefronts need SSR.

Read 2026-11-04. [developer.adobe.com/commerce/frontend-core/guide/layouts/](https://developer.adobe.com/commerce/frontend-core/guide/layouts/)

### [AR-READ-02](https://agentreadychecklist.com/checklist/ar-read-02/): Real HTTP status codesrecipe

Unknown routes go to the CMS No Route Page with a 404 status; keep that page as a CMS page and do not redirect it to the homepage. Add 301 URL rewrites for retired products.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/url-rewrites/url-rewrite](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/url-rewrites/url-rewrite)

### [AR-READ-03](https://agentreadychecklist.com/checklist/ar-read-03/): Home page with real linksrecipe

Keep the top menu and footer links (category tree, CMS pages for shipping, returns, pricing) in server-rendered blocks.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages](https://experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages)

### [AR-READ-04](https://agentreadychecklist.com/checklist/ar-read-04/): Docs that answer agent tasksrecipe

For each of your top five agent tasks, write a page that holds the steps as text, in order, with the exact names of the buttons, fields and settings. Steps that exist only in an image, a video or a script-built widget are not in the response a plain fetch receives. Fetch the page with curl and grep for the step.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-READ-05](https://agentreadychecklist.com/checklist/ar-read-05/): Fenced, language-tagged codenot possible

Not applicable to a storefront with no code samples; keep developer docs on a docs platform.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview)

### [AR-READ-06](https://agentreadychecklist.com/checklist/ar-read-06/): Link the discovery filesworkaround

Add footer links to /llms.txt in a CMS block and a <link> in the head through layout XML (default\_head\_blocks.xml).

Read 2026-11-04. [developer.adobe.com/commerce/frontend-core/guide/layouts/](https://developer.adobe.com/commerce/frontend-core/guide/layouts/)

### [AR-READ-07](https://agentreadychecklist.com/checklist/ar-read-07/): Ship llms.txtworkaround

Write llms.txt and place it in the pub/ document root (on-premise) or serve it through a Fastly snippet on cloud.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets](https://experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets)

### [AR-READ-08](https://agentreadychecklist.com/checklist/ar-read-08/): JSON-LD on key pagesworkaround

Add a template block to the head via layout XML in your theme that prints Product, Offer and Organization JSON-LD; keep the same facts in visible text.

Read 2026-11-04. [developer.adobe.com/commerce/frontend-core/guide/layouts/](https://developer.adobe.com/commerce/frontend-core/guide/layouts/)

### [AR-READ-09](https://agentreadychecklist.com/checklist/ar-read-09/): Advertise a markdown mirrorworkaround

No markdown mirror. Use Cloudflare Markdown for Agents in front, or a Fastly snippet that adds a Link header to a markdown endpoint you host.

Read 2026-11-04. [developers.cloudflare.com/fundamentals/reference/markdown-for-agents/](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/)

### [AR-READ-11](https://agentreadychecklist.com/checklist/ar-read-11/): Pricing as first-party HTMLrecipe

Prices render server-side on product and category pages; for B2B or quote-only catalogs publish a CMS page with plan or tier pricing in text.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages](https://experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages)

### [AR-ACT-01](https://agentreadychecklist.com/checklist/ar-act-01/): Auth an agent can finishrecipe

Register an integration in the Admin: it defines which API resources the application can reach, all of them or a chosen subset, and it issues the credentials. That covers self-serve credentials with documented scopes. Adobe's flow is OAuth 1.0a, so OAuth 2.0 delegation to an agent needs outside help. Workaround: put an OAuth 2.0 authorization server in front and publish its metadata (the CF-OAUTH-DISCOVERY recipe, /platforms/adobe-commerce/#cf-oauth-discovery).

Derived from Adobe Commerce and Magento Open Source's documentation read on 2026-11-04. [developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-oauth](https://developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-oauth) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-02](https://agentreadychecklist.com/checklist/ar-act-02/): OpenAPI contractworkaround

Export the schema with GET /rest/default/schema?services=all (admin token) and publish the result as a static openapi.json; /swagger works only in Developer mode.

Read 2026-11-04. [developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/)

### [AR-ACT-03](https://agentreadychecklist.com/checklist/ar-act-03/): MCP over Streamable HTTPworkaround

No MCP server in core 2.4.9. Workaround: build one on the REST or GraphQL API and host it at /mcp on a separate service.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9](https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9)

### [AR-ACT-04](https://agentreadychecklist.com/checklist/ar-act-04/): MCP server cardworkaround

Serve the card the way the AR-FIND-04 recipe serves the catalog (/platforms/adobe-commerce/#ar-find-04), at /.well-known/mcp/server-card.json. The Adobe Commerce 2.4.9 release notes read list no MCP server, so the card describes a server you host elsewhere.

Derived from Adobe Commerce and Magento Open Source's documentation read on 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9](https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-05](https://agentreadychecklist.com/checklist/ar-act-05/): MCP Apps viewworkaround

The Adobe Commerce 2.4.9 release notes read list no MCP server. Not possible on this platform without outside help. Workaround: serve the ui:// resource from an MCP server you run on a subdomain or API domain you control (the AR-ACT-03 recipe, /platforms/adobe-commerce/#ar-act-03).

Derived from Adobe Commerce and Magento Open Source's documentation read on 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9](https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-06](https://agentreadychecklist.com/checklist/ar-act-06/): SDKs and a CLIrecipe

Publish the SDK and the CLI from the product's own repository to npm or PyPI; the website platform is not involved. Then show the install command and a first call on a page of your own site so that agents reading the site find them. Verify with curl -s https://registry.npmjs.org/<cli-name>/latest.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-07](https://agentreadychecklist.com/checklist/ar-act-07/): WebMCP toolsrecipe

Add the script through a head or footer block in the theme layout, feature-detect document.modelContext and register one tool per real action, such as a catalogue search.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-08](https://agentreadychecklist.com/checklist/ar-act-08/): Agent paymentsworkaround

The documentation read lists no built-in feature for this row. Not possible on this platform without outside help. Workaround: run the paid endpoint on a subdomain or API domain you control, returning HTTP 402 with a payment payload on the paid path only (x402 or MPP), or a checkout handler, and link it from the site. Put no CAPTCHA in front of a verified agent.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-09](https://agentreadychecklist.com/checklist/ar-act-09/): NLWeb /ask endpointworkaround

The documentation read lists no built-in feature for this row. Not possible on this platform without outside help. Workaround: run the /ask endpoint on a subdomain or API domain you control, returning schema.org-shaped JSON for the query parameter, and link it from the site. Mirror the same ask tool over MCP.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [AR-ACT-10](https://agentreadychecklist.com/checklist/ar-act-10/): An MCP server or a CLIrecipe

A CLI meets AR-ACT-10 on any platform: publish it as described in the AR-ACT-06 recipe (/platforms/adobe-commerce/#ar-act-06). An MCP server also meets it; how Adobe Commerce and Magento Open Source hosts one is in the AR-ACT-03 recipe (/platforms/adobe-commerce/#ar-act-03). Do not ship an empty surface to tick the box.

Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)

### [CF-CONTENT-SIGNALS](https://agentreadychecklist.com/checklist/cf-content-signals/): Content-Signal linerecipe

Add Content-Signal: ai-train=no, search=yes, ai-input=yes under User-agent: \* in Edit custom instruction of robots.txt File.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview)

### [CF-MARKDOWN-NEGOTIATION](https://agentreadychecklist.com/checklist/cf-markdown-negotiation/): Markdown by Acceptworkaround

Put Cloudflare Markdown for Agents in front, or implement a Fastly VCL branch on Accept: text/markdown that routes to a converter.

Read 2026-11-04. [developers.cloudflare.com/fundamentals/reference/markdown-for-agents/](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/)

### [CF-PAY-PER-CRAWL](https://agentreadychecklist.com/checklist/cf-pay-per-crawl/): Pay per crawl, HTTP 402workaround

Pay per crawl is a feature of Cloudflare AI Crawl Control, set per Cloudflare zone and in closed beta on 2026-11-04, so Adobe Commerce and Magento Open Source does not set it, and a crawler is answered 402 only on a zone that has it. Not possible on this platform without outside help. Workaround: put the domain on a Cloudflare zone, where Adobe Commerce and Magento Open Source allows a proxy or custom DNS in front, and set the price there. Test with curl -A "GPTBot/1.0".

Derived from Cloudflare's pay per crawl documentation read on 2026-11-04. [developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/](https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) and [developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/](https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/)

### [CF-OAUTH-DISCOVERY](https://agentreadychecklist.com/checklist/cf-oauth-discovery/): OAuth discovery filesworkaround

Adobe Commerce integrations authenticate with OAuth 1.0a, so Commerce itself publishes no OAuth 2.0 authorization server metadata. Workaround: run an OAuth 2.0 authorization server in front, such as an identity provider, and serve its RFC 8414 metadata the way the AR-FIND-04 recipe serves the catalog (/platforms/adobe-commerce/#ar-find-04).

Derived from Adobe Commerce and Magento Open Source's documentation read on 2026-11-04. [developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-oauth](https://developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-oauth) and [isitagentready.com/.well-known/agent-skills/oauth-discovery/SKILL.md](https://isitagentready.com/.well-known/agent-skills/oauth-discovery/SKILL.md)

### [CF-AGENT-SKILLS](https://agentreadychecklist.com/checklist/cf-agent-skills/): Agent Skills indexworkaround

Serve /.well-known/agent-skills/index.json as a static file in pub/ or as a Fastly synthetic response.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets](https://experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets)

### [VERCEL-NEGOTIATION-HEADERS](https://agentreadychecklist.com/checklist/vercel-negotiation-headers/): Markdown headersworkaround

Whatever serves markdown must set Content-Type: text/markdown; charset=utf-8 and Vary: Accept; on cloud add Vary in a Fastly snippet so cached HTML is not served to markdown requests.

Read 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/fastly](https://experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/fastly)

### [VERCEL-ROBOTS-EXCLUSIONS](https://agentreadychecklist.com/checklist/vercel-robots-exclusions/): Robots exclusionsrecipe

Open the robots.txt that Adobe Commerce and Magento Open Source serves for your site and read every Disallow; each one must have a reason you can state. How the file is produced here: Content > Design > Configuration > Global > Search Engine Robots: Default Robots and Edit custom instruction of robots.txt File. robots.txt is generated by a controller when no physical file exists.

Derived from Adobe Commerce and Magento Open Source's documentation read on 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview) and [vercel.com/kb/guide/make-your-site-readable-by-ai-agents](https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents)

## Vendors on this platform

-   [Adobe Commerce](https://agentreadychecklist.com/vendors/adobe-commerce/)Commerce platform, 0 of 6 checklist rows read met by default

## Sources

-   [ora.ai/api/checks, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=platform)read 2026-11-05
-   [registry.npmjs.org/ax, the ax README](https://registry.npmjs.org/ax)read 2026-11-05
-   [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/seo-overview)read 2026-11-04
-   [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/sitemap-xml](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/sitemap-xml)read 2026-11-04
-   [experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages](https://experienceleague.adobe.com/en/docs/commerce-admin/content-design/elements/pages/pages)read 2026-11-04
-   [experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/url-rewrites/url-rewrite](https://experienceleague.adobe.com/en/docs/commerce-admin/marketing/seo/url-rewrites/url-rewrite)read 2026-11-04
-   [developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/)read 2026-11-04
-   [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)read 2026-11-04
-   [experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets](https://experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets)read 2026-11-04
-   [developer.adobe.com/commerce/frontend-core/guide/layouts/](https://developer.adobe.com/commerce/frontend-core/guide/layouts/)read 2026-11-04
-   [developers.cloudflare.com/fundamentals/reference/markdown-for-agents/](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/)read 2026-11-04
-   [developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-oauth](https://developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-oauth)read 2026-11-04
-   [experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9](https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9)read 2026-11-04
-   [developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/](https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/)read 2026-11-04
-   [isitagentready.com/.well-known/agent-skills/oauth-discovery/SKILL.md](https://isitagentready.com/.well-known/agent-skills/oauth-discovery/SKILL.md)read 2026-11-04
-   [experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/fastly](https://experienceleague.adobe.com/en/docs/commerce-on-cloud/user-guide/cdn/fastly)read 2026-11-04
-   [vercel.com/kb/guide/make-your-site-readable-by-ai-agents](https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents)read 2026-11-04

Edition

Data

2026-11-04

Reviewed

2026-11-05

Spec

AgentReady v2.0, 273d2d7

Crawl

13,071 rows, 2026-11-04

Ora

132 checks, contract 1.38.0, 2026-11-05

Verify with Ora

The scanner this site recommends for the whole checklist. 132 checks, a score out of 100, no account.

`npx ax@0.10 audit <url> --min-score <n>`

[Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/)

Method

-   [How rows, commands and rates are made](https://agentreadychecklist.com/method/)
-   [How an Ora check is matched to a row](https://agentreadychecklist.com/checklist/ora-checks/)
-   [Pass rates by rank band](https://agentreadychecklist.com/data/by-rank/)

Sources and read dates sit at the foot of the page.

Last reviewed 2026-11-05. AgentReady v2.0, read 2026-11-04.
