--- title: "Salesforce Commerce: agent-ready recipes | Agent Ready Checklist" description: "Every agent-ready recipe for Salesforce Commerce: 31 rows of the checklist, the version read, the date and the vendor documentation each step came from." canonical: https://agentreadychecklist.com/platforms/salesforce-commerce-cloud site: "Agent Ready Checklist" last_updated: 2026-11-05 section: "Platforms" --- # Salesforce Commerce: agent-ready recipes | Agent Ready Checklist > Every agent-ready recipe for Salesforce Commerce: 31 rows of the checklist, the version read, the date and the vendor documentation each step came from. Source: https://agentreadychecklist.com/platforms/salesforce-commerce-cloud 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). # Salesforce Commerce: agent-ready recipes Salesforce B2C Commerce (SFRA and PWA Kit / Composable Storefront): 31 recipes against the 31 checklist rows, read on 2026-11-04. Salesforce B2C Commerce: 13 are direct, 17 are workarounds and 1 says plainly that the platform cannot do it, with the workaround. Version read for Salesforce B2C Commerce: Hosted SaaS. ## Version and documentation read Version Hosted SaaS (B2C Commerce help release 264.0.0); PWA Kit retail-react-app 10.3.0 and pwa-kit-runtime 3.21.0 on npm, read 2026-11-04 Read on 2026-11-04 Recipes 13 direct, 17 workaround, 1 not possible on the platform robots.txt [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?id=cc.b2c_generating_a_robots_txt_file.htm&type=5). Merchant Tools > Site > SEO & Discoverability > Robots; instance-specific or custom definition, up to 50,000 characters; the custom sample includes AI crawler user-agent entries since B2C Commerce 26.1. Sitemap [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html). Generate in Business Manager (sitemap\_index.xml); for PWA Kit serve it from ssr.js and add it to robots.txt. Page is 403 to plain curl; read through a browser fetch. Structured data No first-party doc: No structured data guide reached on 2026-11-04 (developer.salesforce.com answered 403 to curl). Workaround: render JSON-LD in PWA Kit page components with react-helmet, or in SFRA ISML templates. Status codes No first-party doc: No status-code guide reached. PWA Kit runs an Express server on Managed Runtime, so set res.status(404) in the not-found route; verify with curl. Headers and redirects [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?language=en_US&id=cc.b2c_seo_overview.htm&type=5). SEO overview covers URL rules and redirects in Business Manager; response headers for PWA Kit are set in ssr.js. Content negotiation No first-party doc: No markdown support documented for storefronts. Workaround: an eCDN or Cloudflare Worker that converts HTML for Accept: text/markdown. llms.txt No first-party doc: No llms.txt feature documented. Workaround: serve static/llms.txt from ssr.js the same way the sitemap guide serves sitemap\_index.xml. OpenAPI No first-party doc: Storefront sites do not publish an OpenAPI file; SCAPI specs live on developer.salesforce.com. Workaround: serve your own openapi.json through ssr.js if you expose an API. [The checklist table for Salesforce B2C Commerce (SFRA and PWA Kit / Composable Storefront)](https://agentreadychecklist.com/platform/salesforce-commerce-cloud/checklist/) shows every row with its first step. ## Verify with Ora Salesforce B2C Commerce (SFRA and PWA Kit / Composable Storefront) has a direct recipe for 13 rows, and Ora's catalogue (read 2026-11-05) names a matching check for 10 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 ``` 16 rows that Ora checks are a workaround or not possible on Salesforce Commerce: [AR-FIND-04](https://agentreadychecklist.com/checklist/ar-find-04/) (ai-catalog-published, workaround); [AR-READ-02](https://agentreadychecklist.com/checklist/ar-read-02/) (redirect-hygiene, 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 Business Manager: Merchant Tools > Site > SEO & Discoverability > Robots > Define an instance type-specific robots.txt > All spiders are allowed (Production) or Custom with AI crawler entries uncommented to Allow. Click Apply, then invalidate the static content cache. Read 2026-11-04. [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?id=cc.b2c_generating_a_robots_txt_file.htm&type=5) ### [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 Generate the sitemap in Business Manager (sitemap\_index.xml), add Sitemap: https://example.com/sitemap\_index.xml to robots.txt. PWA Kit: app.get('/sitemap\_index.xml', runtime.serveStaticFile('static/sitemap\_index.xml')) in ssr.js and add 'static/sitemap\_index.xml' to ssrShared in config/default.js. Read 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [AR-FIND-04](https://agentreadychecklist.com/checklist/ar-find-04/): AI Catalog at .well-knownworkaround No catalog feature. PWA Kit: add static/.well-known/ai-catalog.json to ssrShared and app.get('/.well-known/ai-catalog.json', runtime.serveStaticFile('static/.well-known/ai-catalog.json')) in ssr.js, following the sitemap pattern. Read 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [AR-READ-01](https://agentreadychecklist.com/checklist/ar-read-01/): Answer in the initial HTMLrecipe PWA Kit server-side renders each page on Managed Runtime; SFRA renders ISML on the server. Make sure product and category data is fetched in the server render, not only after hydration. Read 2026-11-04. [developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html) ### [AR-READ-02](https://agentreadychecklist.com/checklist/ar-read-02/): Real HTTP status codesworkaround Set a real 404 status in the not-found route of the PWA Kit Express app (res.status(404)) and test it with curl; for SFRA check the error page pipeline. 429 handling sits in eCDN rate limiting. Read 2026-11-04. [developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html) ### [AR-READ-03](https://agentreadychecklist.com/checklist/ar-read-03/): Home page with real linksrecipe Keep header and footer navigation as server-rendered links to category, product and help pages; avoid menus loaded only by client fetch. Read 2026-11-04. [developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html) ### [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; use a docs platform for developer docs. Read 2026-11-04. [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?language=en_US&id=cc.b2c_seo_overview.htm&type=5) ### [AR-READ-06](https://agentreadychecklist.com/checklist/ar-read-06/): Link the discovery filesworkaround Add footer links to /llms.txt and other discovery files in the footer component or content asset; files served through ssr.js as in the sitemap guide. Read 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [AR-READ-07](https://agentreadychecklist.com/checklist/ar-read-07/): Ship llms.txtworkaround Write static/llms.txt (H1, summary, links to key categories, shipping and returns pages) and serve it with app.get('/llms.txt', runtime.serveStaticFile('static/llms.txt')); add it to ssrShared. Read 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [AR-READ-08](https://agentreadychecklist.com/checklist/ar-read-08/): JSON-LD on key pagesworkaround No documented setting reached. Render Product and Organization JSON-LD in the PDP and home components (react-helmet in PWA Kit) or ISML templates in SFRA. Read 2026-11-04. [developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html) ### [AR-READ-09](https://agentreadychecklist.com/checklist/ar-read-09/): Advertise a markdown mirrorworkaround No markdown mirror. Put a Cloudflare zone or Worker in front and enable Markdown for Agents; it adds the markdown variant at the edge. 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 on server-side PDP and PLP pages; keep the price in text in the initial HTML rather than fetched after load. Read 2026-11-04. [developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html) ### [AR-ACT-01](https://agentreadychecklist.com/checklist/ar-act-01/): Auth an agent can finishrecipe Use SLAS, the Shopper Login and API Access Service, which is B2C Commerce's own authorization server. Its access-token requests use grant types defined by OAuth 2.1, and the grant depends on whether the SLAS client is public or private and on how the shopper signs in. There is no authorization server to build. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html) 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 Storefronts have no OpenAPI file by default; if you expose an API, serve openapi.json through ssr.js and link it. Read 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [AR-ACT-03](https://agentreadychecklist.com/checklist/ar-act-03/): MCP over Streamable HTTPworkaround PWA Kit adds routes in ssr.js with app.get. Add a route for /mcp in ssr.js that returns the MCP server over Streamable HTTP (a POST answered with JSON or an event stream), or run it as a separate service on a subdomain or API domain you control. Keep a docs MCP public and gate a product MCP with OAuth and PKCE. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md) ### [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/salesforce-commerce-cloud/#ar-find-04): add the file to ssrShared and an app.get route for /.well-known/mcp/server-card.json in ssr.js. Publish it only if you run an MCP server. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) 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 An MCP Apps view is a ui:// resource listed by resources/list on your MCP server. Add it to the server built for AR-ACT-03 (/platforms/salesforce-commerce-cloud/#ar-act-03); the platform adds no step of its own. Publish it only if the product has a UI to hand back. 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-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//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 The PWA Kit storefront is a React app built from components, so register tools from a component after feature-detecting document.modelContext, one tool per real action. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/retail-react-app.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/retail-react-app.html) and [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 PWA Kit adds routes in ssr.js with app.get. Add a route for /paid in ssr.js that returns HTTP 402 with a payment payload on the paid path only (x402 or MPP), or a checkout handler, or run it as a separate service on a subdomain or API domain you control. Put no CAPTCHA in front of a verified agent. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) and [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 PWA Kit adds routes in ssr.js with app.get. Add a route for /ask in ssr.js that returns schema.org-shaped JSON for the query parameter, or run it as a separate service on a subdomain or API domain you control. Mirror the same ask tool over MCP. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) and [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/salesforce-commerce-cloud/#ar-act-06). An MCP server also meets it; how Salesforce B2C Commerce hosts one is in the AR-ACT-03 recipe (/platforms/salesforce-commerce-cloud/#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 the Custom robots.txt definition in Business Manager. Read 2026-11-04. [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?id=cc.b2c_generating_a_robots_txt_file.htm&type=5) ### [CF-MARKDOWN-NEGOTIATION](https://agentreadychecklist.com/checklist/cf-markdown-negotiation/): Markdown by Acceptworkaround Use Cloudflare Markdown for Agents or a Worker in front of the storefront; Salesforce documents no native negotiation. 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 Salesforce B2C Commerce 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 Salesforce B2C Commerce 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 B2C Commerce already has an authorization server, SLAS, whose token requests use grant types defined by OAuth 2.1, so you run none. To publish RFC 8414 metadata for it at your own domain's /.well-known path, serve a static file through ssr.js with the app.get pattern; the SLAS page does not say whether SLAS publishes discovery metadata of its own. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html) and [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [CF-AGENT-SKILLS](https://agentreadychecklist.com/checklist/cf-agent-skills/): Agent Skills indexworkaround Serve static/.well-known/agent-skills/index.json through ssr.js with the sitemap pattern. Read 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) ### [VERCEL-NEGOTIATION-HEADERS](https://agentreadychecklist.com/checklist/vercel-negotiation-headers/): Markdown headersworkaround If a Worker serves markdown, set Content-Type: text/markdown; charset=utf-8 and Vary: Accept on that response; Cloudflare Markdown for Agents does this for you. Read 2026-11-04. [developers.cloudflare.com/fundamentals/reference/markdown-for-agents/](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/) ### [VERCEL-ROBOTS-EXCLUSIONS](https://agentreadychecklist.com/checklist/vercel-robots-exclusions/): Robots exclusionsrecipe Open the robots.txt that your PWA Kit storefront serves and read every Disallow; each one must have a reason you can state. The PWA Kit sitemap guide says to keep the sitemap line and the crawl directives in the robots.txt file of the PWA Kit or headless site. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) 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 - [Salesforce Commerce Cloud](https://agentreadychecklist.com/vendors/salesforce-commerce-cloud/)Commerce platform, 0 of 5 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 - [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?id=cc.b2c_generating_a_robots_txt_file.htm&type=5)read 2026-11-04 - [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html)read 2026-11-04 - [help.salesforce.com/s/articleView](https://help.salesforce.com/s/articleView?language=en_US&id=cc.b2c_seo_overview.htm&type=5)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 - [developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/pwa-kit-overview.html)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.salesforce.com/docs/commerce/commerce-api/guide/slas.html](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html)read 2026-11-04 - [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/retail-react-app.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/retail-react-app.html)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 - [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 --min-score ` [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.