Agent readiness on Adobe Commerce and Magento

Commerce generates robots.txt. Add rules under Content › Design › Configuration, in the "Custom instruction of robots.txt" field. If search engine indexing is turned off, custom rules aren't applied, so check the live /robots.txt after any change.

AgentScore checks: robots.txt lets AI assistants and search agents in

Adobe's cloud includes a Fastly firewall; bot management is a separate Advanced Security add-on, and Adobe says bot protection is the merchant's responsibility. Whoever runs your rules should allow verified AI agents and avoid challenges at the cart and checkout.

AgentScore checks: Bot protection lets AI agents through, No CAPTCHA or challenge on arrival, AI agents aren't blocked or shown a CAPTCHA at the cart and checkout

Allow Guest Checkout lives under Stores › Settings › Configuration › Sales › Checkout, and is on by default. Check nobody has turned it off for your store view.

AgentScore checks: Shoppers can check out without an account

The Luma theme includes only basic product microdata, and themes differ. View a product page's source and check for one Product with price, currency and availability; many stores add it with an extension or in the theme.

AgentScore checks: Structured data describes your business and products, Product pages give price and stock in a form agents can read

Luma's checkout is built with JavaScript, and headless storefronts may build whole pages in the browser. Check product pages carry their content in the HTML, and that every checkout field has a label agents can read.

AgentScore checks: Content loads without JavaScript, Cart and checkout fields are labelled for agents

On a self-hosted store, a developer can place an llms.txt file in the web root. On Adobe's cloud, ask your agency where static files are served from.

AgentScore checks: llms.txt guide for AI