Is Your Site Agent-Ready? icon

Is Your Site Agent-Ready?

Is Your Site Agent-Ready? scans websites for AI-agent-facing signals such as robots.txt, sitemap headers, markdown negotiation, MCP-related discovery, and commerce protocols. It helps site owners check whether their sites are discoverable and usable by agents, and where they may need fixes.

Is Your Site Agent-Ready?

Overview

Is Your Site Agent-Ready? is a website scanner that evaluates whether a site exposes signals and standards that AI agents can use. The product centers on emerging agent-facing conventions such as robots.txt, sitemap and link headers, markdown negotiation, AI bot rules, Web Bot Auth, MCP-related discovery, agent cards, and commerce protocols.

The interface lets you scan a URL, choose a site type, and customize which checks to run. The goal is to show which agent-readiness signals are present and to point site owners toward practical improvements, starting with basic discoverability and bot-rule setup.

What it checks

Discoverability checks

Checks whether a site exposes signals that help agents find and understand it, including robots.txt, sitemap, link headers, and DNS for AI Discovery (DNS-AID).

Content accessibility checks

Looks for content delivery patterns such as Markdown negotiation and other signals that make site content easier for agents to consume.

Bot access control checks

Checks for AI bot rules in robots.txt, Content Signals, and Web Bot Auth so site owners can define how bots may interact with the site.

Protocol discovery checks

Looks for protocol and discovery surfaces such as MCP Server Card, Agent Skills, WebMCP, API Catalog, OAuth discovery, OAuth Protected Resource, Auth.md, A2A Agent Card, and related signals.

Commerce checks

Covers commerce-oriented standards including x402, MPP, UCP, and ACP for sites that need agent-friendly transaction flows.

Custom scan options

Lets the user customize which checks run and choose a site type such as All Checks, Content Site, or API / Application.

Common ways to use it

  • Audit a public website

    Run a scan on a public marketing site to see whether robots.txt, sitemap, headers, and other discovery signals are present for AI agents.

  • Review content accessibility

    Check a content site for Markdown negotiation, bot rules, and related signals that affect how agents can read and access pages.

  • Assess an application surface

    Validate an API or application site for protocol discovery cues such as MCP-related cards, API catalog entries, and OAuth discovery signals.

  • Turn findings into fixes

    Use the scan output as a checklist for improving the site, then copy the provided instructions into a coding agent to implement changes.

  • Diagnose scan blocks

    Test whether a site is reachable by the scanner itself; if it returns 403, the issue may be blocking rules, bot detection, or IP restrictions.

Pros and Cons

Pros

  • Covers a broad set of emerging agent-readiness standards in one scan.
  • Includes both discovery and access-control checks, not just surface-level crawlability.
  • Provides customizable scan scope and site-type selection.
  • Offers guidance on easy wins for improving the score, such as valid robots.txt directives and discovery metadata.
  • References further documentation through Cloudflare Agents resources.

Cons

  • The source does not show a detailed explanation of scoring, thresholds, or how results are weighted.
  • The pricing page shows that some URLs may be blocked by bot detection or WAF rules, which prevents a scan from completing.

FAQ

What does Is Your Site Agent-Ready check?

It scans a website against emerging agent-facing standards, including robots.txt, sitemap and discovery headers, markdown negotiation, AI bot rules, Web Bot Auth, MCP-related signals, and agent commerce protocols.

How do you use the scan?

The source does not describe a required setup flow. The page presents a URL scan with options to customize which checks run and to choose a site type.

Who is this for?

The page is aimed at websites that want to see whether they expose enough discovery, access-control, protocol, and commerce signals for AI agents to work with them.

What happens if the site blocks the scanner?

The pricing page shows a scan attempt for the pricing URL but reports that the site returned 403 Forbidden, with error code 1003, and says the site is blocking the scanner.

Does it provide guidance for improving a site?

The source mentions a way to copy instructions into a coding agent such as Cursor, Claude Code, Windsurf, or Copilot to improve site readiness, but it does not describe the exact output format in detail.

Quick Facts

Category
Website scanner
Primary use
Agent-readiness assessment for websites
Scan focus
Discovery, access control, protocol discovery, and commerce signals
Site type options
All Checks, Content Site, API / Application
Source domain
isitagentready.com
Pricing signal
Pricing page is present, but no public prices are shown in the provided source

Alternatives à Is Your Site Agent-Ready?