Magento and Adobe Commerce
Is your Magento store agent-ready? Check it free
A Magento store runs on your own server, so every pillar is reachable: robots.txt, structured data and llms.txt are files or settings you own, and /.well-known/poppy.json can be served, or proxied from a hosted Company, by the web server.
What the check usually finds on Magento and Adobe Commerce
- Found
- Content → Design → Configuration → Search Engine Robots controls robots.txt; defaults allow the assistants.
- Understood
- Product JSON-LD depends on the theme or an extension; Organization is often missing from the home page.
- Usable
- No poppy.json unless you publish or proxy it. No Magento extension implements the protocol that we know of.
- Trusted
- Nothing to score until there is agent sign-in.
What you can do
- 1
Describe the business and what it sells in schema.org
Add Organization JSON-LD to the home page through the theme or a structured-data extension. The check looks for an Organization, LocalBusiness or Store entity, and Product/Offer or Service entities, as JSON-LD on the home page.
- 2
Let assistants in through robots.txt
Content → Design → Configuration → Search Engine Robots. Allow ChatGPT-User, Claude-User and Perplexity-User (they fetch a page only when a person asks) and the AI search bots (OAI-SearchBot, Claude-SearchBot, PerplexityBot). Blocking training crawlers such as GPTBot or CCBot is a separate choice and costs no points.
- 3
Publish llms.txt
A short Markdown page at /llms.txt naming the business, what it sells, its delivery and returns policies, and the pages that matter. Most platforms can serve a plain-text file at the root; where one cannot, a redirect to a page you host elsewhere works.
- 4
The protocol part: a hosted Company
Your nginx or Apache config can proxy /.well-known/poppy.json from the hosted Company in a few lines, so it is served on your own domain (a redirect to the provider's host doesn't count). Agent Adapt is building a hosted Company for sites that cannot run its WordPress plugin: it publishes poppy.json, runs the sign-in and the customer API, and the document is served on the site's own domain through a small proxy (the spec stopped allowing a redirect to the provider's host on 16 October 2026). It is not yet on sale.
Ask for early access
Common questions
›Could I run the protocol myself on Magento?
Yes, in principle: the spec is open and the plugin repo's design is public. It is an OAuth server with sender-bound tokens, a sign-in flow and a scope-enforced API, so it is a project, not a setting.
›Does the check reach the admin or any private page?
No. It reads only public documents: robots.txt, the home page, llms.txt, /.well-known/poppy.json and the issuer's metadata.
In depth: Magento and Adobe Commerce with personal agents on getagentadapt.com.