AGENTREADY CHECK · FREE

Can AI read your website?

Find what stops AI agents from reading, understanding and using your site. Get a free technical score and a concrete next step for every area.

Free, with no login. The scan reads public pages.

615 domains scanned

RRetrievable
EExplainable
AActionable
DDistributed

A next step for each of the 9 checks.

9 areas · 4 pillars · 100 points

What we measure

RRetrievable

51 pts

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

01

AI crawler access

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.

18 pts
02

JavaScript dependency

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.

14 pts
03

Agent basics

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.

10 pts
04

Search index verification

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.

9 pts

EExplainable

37 pts

Can an agent extract accurate facts about your business?

05

llms.txt

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.

14 pts
06

Structured data

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.

14 pts
07

Feed & product data

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.

9 pts

AActionable

7 pts

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

08

Agentic buyability

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.

7 pts

DDistributed

5 pts

Are your products ready for the catalogues agents shop from?

09

Catalog prerequisites

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.

5 pts

0–39

The scan found substantial technical gaps. Check crawler access and whether your HTML contains readable content first.

40–69

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

Your site passes most applicable technical checks. Review the remaining findings; this score does not measure whether AI recommends your business.

Full detail: How it works

FAQ

Frequently asked

What exactly does the check measure?
9 technical areas across four pillars (Retrievable, Explainable, Actionable, Distributed), worth 100 points in total: AI crawler access (18), JavaScript dependency (14), Agent basics (10), Search index verification (9), llms.txt (14), Structured data (14), Feed & product data (9), Agentic buyability (7), Catalog prerequisites (5). The scan checks public signals on your domain and labels results it cannot verify.
How can an area be worth nothing?
Some areas do not apply to every site. For example, a blog may have no checkout. Those areas are excluded, and the score is calculated from the applicable points. An applicable signal that cannot be verified from outside receives half its points.
What does it cost?
Nothing. The check is permanently free, with no login and no credit card. 3 of the 9 areas are visible immediately, the remaining 6 after you enter your email address.
Why do I have to give my email for 6 of the checks?
We email you the full report with all 9 areas and a next step for each. You can forward it to your engineers. You also join our newsletter and can unsubscribe with one click.
How long does a scan take?
Usually under 60 seconds. Every individual check has a 10-second timeout; a check that fails is left out of the score rather than counted as zero, and never aborts the scan.
Does the scan change anything on my website?
The scan is read-only. It fetches publicly available URLs: your homepage, robots.txt, llms.txt, llms-full.txt and sitemap.xml. We additionally look up your public DNS TXT records to check for search-index verification.
What happens to my data?
The domain, score and check results are stored anonymously and feed the aggregated market data at /api/v1/stats. Your email address is stored separately and is never published alongside a specific scan.
Is the result public?
The result page is shareable and indexable by default. On the page itself you can switch it to noindex with one click.
Is there an API?
Yes. POST /api/v1/scans starts a scan, GET /api/v1/scans/{id} returns the result, GET /api/v1/stats returns aggregated market data. The OpenAPI spec lives at /api/v1/openapi.json.
How is this different from AgentReady Monitor?
The check measures technology: can agents reach your content at all? The Monitor measures effect: do ChatGPT, Claude and Perplexity actually recommend you, and in what words?

AgentReady Monitor

Does AI recommend your business?
AgentReady Monitor asks buying questions each month and records how AI models describe and recommend your business.

See AgentReady Monitor