Agent-readiness check · free
No login, no credit card. We only read your site.
9 technical checks against your live domain, across four pillars: Retrievable, Explainable, Actionable, Distributed.
Result in under 60 seconds. No login, no setup, free.
A score from 0 to 100 plus one concrete next step per area — and an honest "we could not verify this" where the answer is not visible from outside.
21 domains scanned
9 areas · 4 pillars · 100 points
Can an AI agent fetch and read your pages at all?
We parse your robots.txt and additionally fetch your homepage with the real user agents of GPTBot, ClaudeBot and PerplexityBot. If the status codes differ from a browser request, something is blocking you — usually a bot rule in a CDN or firewall.
Why it matters: Whoever gets locked out does not appear in AI answers. That is the single most expensive mistake on this list.
We measure the visible text on your homepage without JavaScript, and how much of the delivered HTML is executable script code. Under 1,500 characters without JavaScript is critical.
Why it matters: AI crawlers do not execute JavaScript. Anything that only appears in a browser does not exist for them.
sitemap.xml, rel="canonical", a findable route to legal notice and contact, homepage response time under 3 seconds.
Why it matters: The homework. Without it, the rest only gets you so far.
We look for Google Search Console and Bing Webmaster verification in your DNS TXT records and your homepage meta tags, and check whether robots.txt declares a sitemap that actually resolves.
Why it matters: Verified domains get crawled sooner and deeper — and the Bing index is what Microsoft Copilot answers from. Note the honest limit: verification by file upload or Tag Manager is invisible from outside, so we report "could not verify", never "not registered".
Once it has your pages, can it state facts about you instead of guessing?
We check whether /llms.txt really answers with 200, serves text, and is not an HTML soft 404 in disguise. /llms-full.txt earns bonus points.
Why it matters: Your llms.txt is the curated short version: product, value, pricing, links — written for models rather than for people.
We read every JSON-LD block in your HTML and look at which @types appear — Organization, Product, Offer, FAQPage — and whether prices are stored as numbers.
Why it matters: Structured data is the difference between a model interpreting you and a model quoting you.
For every product object in your JSON-LD we check the six fields agents rely on: name, price, currency, availability, identifier (GTIN/SKU/MPN) and image — plus whether return and shipping terms are machine-readable.
Why it matters: "What does it cost, is it in stock, can I send it back?" are the questions that decide a purchase. An agent will not answer them from prose.
Can it do more than describe you — can it act on your offering?
We detect your shop platform and look for references to an agent-callable checkout in your HTML, robots.txt and llms.txt.
Why it matters: Reading about your product is not buying it. This is a heuristic and we label it as one — there is no standard way to discover a checkout endpoint from the outside.
Are your products ready for the catalogues agents shop from?
Whether your product data meets the preconditions for merchant catalogues: identifiers on every product, price and availability together, and a verified domain.
Why it matters: We check prerequisites, not listings. Whether you are actually in Google Merchant Center or the ChatGPT merchant catalogue cannot be queried from outside, so we do not claim to know.
0–39
AI agents get no reliable picture of you. Usually there is either blocking or an empty HTML shell behind this.
40–69
The fundamentals are in place, the rest is missing. Typical case: crawlers get through, but there is neither an llms.txt nor structured data.
70–100
You are agent-ready. From here it is no longer the technology that decides, but what is written about you.
Full detail: How it works
FAQ
AgentReady Monitor