How it works

A free technical scan across 9 areas, with an agent-readiness score from 0 to 100. No login, no setup, free.

In three steps

1. Enter a domain. example.com is enough — we ignore protocol and path.
2. Wait. We fetch your homepage, robots.txt, llms.txt, llms-full.txt and sitemap.xml, look up your public DNS TXT records for search-index verification, and additionally test the homepage with the user agents of GPTBot, ClaudeBot and PerplexityBot. Every request has a timeout; nothing is retried more than once.
3. Read the result. A score from 0 to 100 across 9 areas in four pillars, with plain-language findings and one concrete next step each.

The 9 checks in detail

R — Retrievable (51 points)

Can an AI agent fetch and read your pages at all?

AI crawler access — 18 points

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, a CDN or firewall rule may be treating crawlers differently.

Why it matters: Crawler access lets an AI service retrieve your pages. A block can prevent that service from using your content directly.

JavaScript dependency — 14 points

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: Crawlers that skip JavaScript miss content loaded only in the browser. Server-rendered text gives them something to read.

Agent basics — 10 points

sitemap.xml, rel="canonical", a findable route to legal notice and contact, homepage response time under 3 seconds.

Why it matters: A sitemap and canonical URLs help crawlers find and identify your pages. Contact details help establish who runs the site.

Search index verification — 9 points

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: Public verification signals show that a domain has been connected to a search webmaster service. Verification by file upload or Tag Manager is outside this scan, so missing signals are reported as unverified.

E — Explainable (37 points)

Can an agent extract accurate facts about your business?

llms.txt — 14 points

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: An llms.txt file gives agents a short overview of your offering with links to details and prices.

Structured data — 14 points

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: JSON-LD gives models explicit fields for company details, products and prices.

Feed & product data — 9 points

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: Explicit product fields help agents compare prices, availability and return terms.

A — Actionable (7 points)

Can an agent use your offering through a checkout or API?

Agentic buyability — 7 points

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: This check looks for signs of an agent-callable checkout. It is a heuristic; it does not test a purchase or guarantee that an agent can complete one.

D — Distributed (5 points)

Are your products ready for the catalogues agents shop from?

Catalog prerequisites — 5 points

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: Complete product data supports catalogue submissions. The scan cannot confirm an actual listing in Google Merchant Center or the ChatGPT merchant catalogue.

How the score is calculated

The 9 areas are worth 100 points in total. The score is not a plain sum of those points, though — it is a percentage of the points that actually apply to your domain:

score = round(100 × points earned ÷ points applicable)

Two rules decide what "applicable" means, and both exist for the same reason: we would rather tell you nothing than tell you something false about your own site.

An area that does not apply is removed from the calculation. A blog has no checkout an agent could use and no product catalogue to be listed in. Scoring those areas zero would not be a measurement, it would be a penalty for being a blog. So they leave both sides of the fraction, and the remaining areas are scaled back up to 100.

An area we cannot see counts as half. Some things are genuinely invisible from the outside. If you verified your domain in Google Search Console by uploading an HTML file, or through Google Tag Manager, or your hosting provider did it for you automatically, there is no DNS record and no meta tag for us to find. We will say "we could not verify this", never "you are not registered" — and score it as half rather than zero, so a false negative cannot cost you the full points and doing nothing cannot earn you them either.

This is why two sites can both score 70 while a different number of areas were measured. The result page names the areas that were left out and why.

• 0–39 (red): The scan found substantial technical gaps. Check crawler access and whether your HTML contains readable content first.
• 40–69 (yellow): Some technical foundations are in place. Review the individual findings for remaining gaps, such as missing structured data or an llms.txt file.
• 70–100 (green): Your site passes most applicable technical checks. Review the remaining findings; this score does not measure whether AI recommends your business.

What we do NOT do

• We write nothing on your site and submit no forms.
• We register nothing on your behalf — no Search Console, no Bing, no IndexNow ping.
• We call no authenticated API and read nothing that is not public.
• We execute no JavaScript — exactly like the AI crawlers we simulate.
• We do not crawl your site in full. It is at most eleven requests, less than a single browser visit.
• We do not claim to know whether you are listed in a product catalogue. That cannot be queried from outside, so we check the prerequisites and say so.

What we store

Domain, score and check results are stored anonymously and feed the aggregated market data at /api/v1/stats. We only store an email address if you enter one yourself, and we never publish it.

After that

Does AI recommend your business? AgentReady Monitor asks buying questions each month and records how AI models describe and recommend your business. → https://ai-agent-ready.com

---

A product by The Autopilot — https://the-autopilot.com