Methodology · v1.0

How we score agent-readiness.

A transparent breakdown of every check we run, why it matters, and what we deliberately leave out. Update cadence: monthly. Last revision: May 2026.

← Back to scanner

What we check

5 categories. 26 checks. Each category is weighted by how material it is to an agent's ability to find, understand, and transact with your store.

Discoverability

Weight: 15%

robots.txt, sitemap, AI bot rules

robots.txt presentSitemap referencedAI user-agent rulesllms.txt manifestCanonical hostnames

Content Accessibility

Weight: 20%

JS-less rendering, semantic HTML, markdown negotiation

Renders without JavaScriptSemantic landmarksHeadings hierarchyMarkdown content negotiationReading order matches DOM order

Catalog Quality

Weight: 25%

Feed presence, schema.org Product, GTIN coverage

Product feed (GMC/feed.xml)schema.org/Product on PDPGTIN / MPN coveragePrice + currency in schemaAvailability stateVariant relationships

Checkout Readiness

Weight: 25%

ACP / UCP advertisement, capability endpoints

ACP capability advertisementUCP manifestMCP server announcedCart API discoverableGuest checkout supported

Trust & Policy

Weight: 15%

Returns, shipping, identity signals

Returns policy reachableReturns policy structuredShipping policy structuredBusiness identity verifiedPrivacy & data handling

Why it matters now

AI agents — ChatGPT's commerce surface, Google's Gemini for shopping, Perplexity's Comet, and a growing list of vertical agents — are starting to make purchase decisions on behalf of users. The signals those agents read are still settling. Sites that meet ACP, UCP, MCP, and schema.org conventions today will be discoverable, comparable, and transactable when those agents scale. Sites that don't will be invisible.

None of this is a crystal ball. ACP and UCP are early specifications and may change. We follow them as they evolve and update this methodology monthly.

How scoring works

Each check returns pass, partial, or fail. Partial credits 0.5. Each category is normalized to 0–100 and combined into the headline score using the weights above. Tier bands:

0–39 Hostile Fundamental signals are missing. Agents struggle to read or trust the store.
40–59 Visible Agents can find the store but not yet transact through it.
60–79 Ready Most signals are in place. Closing a few gaps would make it agent-native.
80–100 Native Built for the agentic web. The signals agents need are present and machine-readable.

What we don't check

Synthetic checkout, login-walled content, page performance, and qualitative UX. We measure the agent-readable surface, not the buying experience. We also don't follow links offsite, scrape the full catalog, or hold any data after the scan finishes — see the privacy notice for details.

Who built this

KODLY is an enterprise eCommerce + AI consultancy based in Lisbon. We work with European retailers on agent-readiness, structured commerce, and platform migrations. This tool is free because we want a baseline that's transparent and shared.

Feedback

See something we got wrong, or a check we should add? Email hello@kodly.io. The methodology updates monthly; large enough corrections cut a fresh version.