Agent standards in every report, and stricter price and stock checks
Reports now list the agent standards a site publishes, and a price or stock level counts only when the scan can show it on the product page.
- Agent standards. A new section in each report lists the files, headers and protocols that tell an AI agent what a site offers: llms.txt and Markdown for agents, MCP server cards, Agent Skills, API catalogs, WebMCP tools, A2A agent cards, agentic checkout and payment protocols such as ACP, UCP, AP2 and x402, and more. A level from 0 to 3 sums it up. It is there for information and does not change the Axidort Score. A file counts only when it has the fields its specification requires, and a request the site refuses shows as "couldn’t verify", not as missing.
- Stricter price and stock checks. A price or stock level now counts only when it appears on the product page, next to the product’s name. A promotion such as "$10 off" is never taken for a price, and a price the agent reports must be on the page it was reading. A rating or a size is not taken for a price, and "Available in 3 colours" is not stock. A barrier the agent reports, such as a login wall or a bot check, counts only when the page shows it. Some sites will score differently than before. The methodology page explains the rules.
- Fairer discoverability. Discoverability now counts how quickly an agent reaches the page, through site search or through the site’s links: a product one click from the home page scores as well as one a search returns. A report says "no site search" only when the site has none.
- Better site detection. The scan now reads your home page as a browser shows it, with its menu links, so sites built with JavaScript and sites that offer a free tool alongside paid plans are recognised correctly. A page that only writes about carts or checkouts is no longer treated as a shop, and a sign-up that only offers "Continue with Google" counts as reaching sign-up.
- A fairer measure of what agents need. Product data now counts what agent shopping feeds ask for: description, image and brand, and whether shipping cost and returns are stated. On a product page, the buy button must be a real button with a name an agent can read. robots.txt is checked for AI search crawlers and the agents that browse for a person; blocking AI training crawlers is your choice and no longer counts. A file the site refused to send shows as "couldn’t verify" instead of missing, and every report says which language the site answered in, and how much scores usually move between scans.
- Information sites. A site that sells nothing is scored on whether agents can find and read it, labelled that way, and no longer ranked against the stores in the Axidort Index.
- Checkout is judged only when it was tried. If the agent runs out of steps before it can try to buy, checkout is left out of the score instead of counting against your site.
- Plan buttons on subscription sites. On a site that sells plans, our safety rules stop the agent at a plan’s buy button, such as "Subscribe to Growth". That now counts as reaching the purchase step and scores 75, because the steps after it were not tested. It no longer counts against your site.
- Clearer purchase blockers on stores. When the agent stops on a product page without trying to buy, the scan now uses that page’s buy button once, so the report names what really stands in the way, such as a wallet or account wall. The safety rules are unchanged: the agent never pays, places an order or signs in.
- Email when your report is ready. Axidort can email you a link when a report is ready: tick or untick "Email me when a report is ready" on the scan screen or in My reports. We also confirm Contact us messages and privacy or legal requests, and tell you if there is a problem with your plan. Service emails only: no newsletters or marketing.
- Terms and Privacy Policy updated. On October 24 and 25, 2026: Amazon SES is named as the service that delivers our emails, with how long we keep them, and the ?ref= code of the link that brought you is kept with your scans and new account. On November 3, 2026: the Privacy Policy notes that your browser remembers the last announcement you saw, so it is shown once. You do not need to accept them again.
- Security and reliability fixes. Scans are more dependable and better protected.