The agent-readiness package files, explained

Our agent-readiness files help AI agents that land on your website find and understand your business without changing your theme, existing plugins, or server code, and without a new backend.

The exact package is driven by published standards, working-group proposals, and documented conventions, sized to your site's profile (typically 13 files). Every file below links to a plain-English education page with its origin, who defines or maintains it, and where adoption stands today.

Files are grouped by the four Agent Readiness Score dimensions from your free Pre-Check and dashboard: Discoverability, Content Understanding, Agentic Capabilities, and Permissions and Governance.

Discoverability

Content Understanding

Agentic Capabilities

Permissions and Governance

Never clobbered: your existing files are safe

Three of these files may already exist on your site, and we treat them with an augment-if-present, create-if-absent, never-clobber rule: `robots.txt` is upserted onto your existing rules, `sitemap.xml` is generated only if you have none, and `schema.jsonld` is merged with your existing structured data. An existing customer file is preserved and built upon, never silently overwritten.

Important boundary

AgentReadyWebsite delivers static files and installation guidance. We do not modify your theme, existing plugins, or server code, create live server-side MCP/A2A/NLWeb/WebMCP endpoints, host your website, rewrite your site's accessibility tree or layout stability, or guarantee traffic and revenue lift. For WordPress websites, our free installer plugin installs your agent-readiness package from WordPress admin after you upload the delivery zip (no FTP required). On other platforms you upload the zip.

How this relates to Google AI Search

Google's guidance on AI features in Search says special AI files, AI-only markup, or llms.txt are not required to appear in AI Overviews or AI Mode, yet that’s what we deliver in our agent-readiness package.

The reason we deliver these files is we leave AI Mode placement and SEO rankings alone. We help AI agents that have already reached your website understand your business and accurately answer questions about what you offer.

See the FAQ for how generative AI search visibility differs from agentic browsing, which is the job we focus on.

How this relates to Google's Chrome Lighthouse Agentic Browsing

Google Chrome's Lighthouse Agentic Browsing category groups four areas: llms.txt presence, WebMCP integration, accessibility tree integrity, and layout stability. The WebMCP area itself has multiple named audits; Lighthouse's expected install pattern is live tool registration on the page, not a static file alone.

Covered today: llms.txt

Our package includes the root-level llms.txt file Chrome's audit looks for.

Shipped, not yet counted: WebMCP

We include an experimental static webmcp-registration.js wrapper, but do not count WebMCP toward Lighthouse coverage until live registration (declarative form attributes or the browser API) is verified against Chrome's audits.

Customer-site dependent: accessibility

Accessibility tree integrity depends on your site's existing HTML, labels, and interactive elements.

Customer-site dependent: layout stability

Cumulative Layout Shift depends on your site's CSS, scripts, images, fonts, and rendering behavior.

See which of these files your site has today

The free Pre-Check inventories your agent-readiness files and returns your Agent Readiness Score in seconds.

Run My Free Pre-Check