Skip to content

Agent readiness report · example

Can AI agents find, read and use aiseo.ai?

A scan of the files, headers and protocols AI agents look for before they read a page, call an API or complete a task on your site.

Site aiseo.aiScanned September 28, 202620 checks in 5 categories
27/100

Agent readiness score

Level 1 · Basic Web Presence

4 of 15 scored checks pass

Next level

Level 2 · Bot-Aware

One change gets you there: Content Signals.

Level 0Level 5

Breakdown

Readiness by category.

Commerce is reported for every site but does not count toward the score.

Discoverability

2/4

Can agents find your crawl rules, sitemap, discovery headers and DNS records?

  • robots.txtrobots.txt exists with valid formatPass
  • Sitemapsitemap.xml exists with valid structurePass
  • Link headersLink headers present but no agent-useful relation types foundFail
  • DNS for AI DiscoveryDNS for AI Discovery (DNS-AID) well-known entrypoint records not foundFail

Content

0/1

Can agents read a clean, machine-readable version of your pages?

  • Markdown negotiationSite does not support Markdown for AgentsFail

Bot access

1/2

Do your bot rules state clearly what AI agents may do?

  • AI bot rulesNo AI-specific bot rules; wildcard rules apply to all crawlers including AI botsPass
  • Content SignalsNo Content Signals found in robots.txtFail
  • Web Bot AuthWeb Bot Auth directory not found (informational only)Info

API, auth and MCP

1/8

Can agents find and call your APIs, sign in and use your tools?

  • API catalogAPI Catalog not foundFail
  • OAuth discoveryOAuth 2.0 (RFC 8414) discovery metadata foundPass
  • OAuth Protected ResourceNo OAuth Protected Resource Metadata foundFail
  • auth.mdauth.md not foundFail
  • MCP Server CardMCP Server Card not foundFail
  • Agent SkillsAgent Skills index not foundFail
  • WebMCPNo WebMCP tools detected on page loadFail
  • ARD manifestARD capability manifest not foundFail

Commerce

0/4

Can agents pay or check out through open protocols? Not counted in the score.

  • x402x402 payment protocol not detectedFail
  • MPPMPP payment discovery not detectedFail
  • UCPUCP profile not foundFail
  • ACPACP discovery document not foundFail

Fixes

What to fix first.

Ordered by what unlocks the next level, then by checks that count toward the score.

01

Content Signals

· Bot accessUnlocks level 2

No Content Signals found in robots.txt

How to fix

Add Content-Signal directives to robots.txt that declare preferences for ai-train, search and ai-input, for example: Content-Signal: ai-train=no, search=yes, ai-input=no

Fix with SEO Agentcontentsignals.org spec
02

Link headers

· Discoverability

Link headers present but no agent-useful relation types found

How to fix

Add Link response headers to your homepage that point agents to useful resources, for example rel="api-catalog" or rel="service-doc" (RFC 8288).

Fix with SEO AgentRFC 8288 spec
03

DNS for AI Discovery

· Discoverability

DNS for AI Discovery (DNS-AID) well-known entrypoint records not found

How to fix

Publish DNS-AID records under your domain, for example _index._agents.example.com, using ServiceMode SVCB/HTTPS records with alpn and endpoint parameters, and sign the zone with DNSSEC.

Fix with SEO AgentDNS-AID draft spec

10 more fixes, ready for SEO Agent

SEO Agent turns each finding into a fix you can ship, without a ticket queue.

Fix with SEO Agent

Source: Cloudflare Agent Readiness Scanner (isitagentready.com), all default checks. A2A Agent Card and AP2 are excluded by the scanner's default configuration.

Fix it with SEO Agent.

This scan is the free part of SEO Agent. The agent audits your site, turns findings like these into fixes, and ships them.

Run SEO AgentSign up free, then SEO Agent opens on your site