Limited time: Try B12 for $1 for 7 days.Sign up now

Agent-ready website: what it means and how to check yours

Published ·SEO
Agent-ready website: what it means and how to check yours

An agent-ready website is one that AI agents can find, read, and use. When someone asks ChatGPT or Claude to look up your prices or compare you with someone else, the agent visits your site for them. If your pages load for it and your key facts are in plain text, it can answer from your site.

Why this is coming up now

People increasingly hand small research jobs to an AI assistant, like "find a dog groomer near me that's open Sundays and tell me what a bath costs." The assistant opens real websites to answer.

That's why a group of companies, including ora.ai, Vercel, Stripe, Auth0, Mintlify, Tavily, and Google, launched AgentReady.org, an open standard for what a site or product should offer so agents can use it.

What agents actually do on your site

Vercel and the ora.ai research lab watched 1,033 AI agent runs across 25 websites between June and August 2026 (study). A few findings are useful for anyone with a website:

  • The homepage came up in 69% of runs, and it was the agent's first stop in 92% of those.
  • 82.5% of answers traced back to a page the agent fetched on the site.
  • Only two setups stopped agents from getting an answer: putting it only inside JavaScript, and blocking the agent with a 403 error.

The short version: agents read the same pages people do. The basics matter more than any new file.

A checklist for an agent-ready website

  1. Keep public pages reachable. If a security setting shows every visitor a "verify you're human" check, agents get stuck there. Only block them on purpose.
  2. Put the answer on the page as text. Prices, hours, services, and contact details belong in the page itself, not only in an image, a PDF, or a widget that loads later.
  3. Make your homepage a good front door. Agents usually start there, so give it real links to your pricing, services, and contact pages.
  4. Add an llms.txt file. It's a short, plain-text list of your most important pages at yoursite.com/llms.txt. In the study, agents found it through links 86% of the time, so link to it from your footer. It helps point agents in the right direction, but it doesn't replace good pages.
  5. Return honest errors. If someone opens yoursite.com/old-page and sees "page not found," your site should also send a real 404 error. Otherwise search engines and agents treat that empty page like a real one.
  6. Add structured data where it's accurate. JSON-LD helps search engines, but the study didn't find it changed agent answers, so keep the same facts in visible text too.
  7. Decide whether agents need to act. Booking, buying, or logging in on someone's behalf needs things like an API or an MCP server. Most portfolios, blogs, and local service sites don't need this yet.

How to check your website

Scanners give you a quick read:

  • is-agentic.com, built by ora.ai with Vercel, scores the essentials for content sites.
  • isitagentready.com runs 23 checks and gives your site a level from 0 to 5.

Treat any score as a snapshot. Many checks, like agent payments or OAuth, are meant for software products, so a strong local service site can score low and still be in good shape.

For a real-world test, ask an AI assistant a question only your site can answer, like "What does [your name or site] charge for a consultation?" If it answers from your site, you're in good shape.

Making your B12 website agent-ready

You can handle most of this by chatting with the AI Agent. A few prompts to try:

  • "Add an llms.txt file that lists my services, pricing, and contact pages."
  • "Put my opening hours and prices on the homepage as text, not in an image."
  • "Add a link to my llms.txt file in the footer."

Once the file exists, you can fine-tune it yourself in code mode. If you install the agent-browser skill, the AI Agent can also click through your published site and post screenshots of what it saw, so you catch broken pages and forms before a visitor or an agent does.

That's it. Your site's probably doing most of this already, and the checklist closes the gaps. The same fixes help people and search engines too, so none of it goes to waste.

Frequently asked questions

What is an agent-ready website?

A website AI agents can reach, read, and use on someone's behalf. Its public pages load without being blocked, its key facts are in the page text, and its homepage links to the pages that matter.

Do I need an llms.txt file?

It helps, but good pages matter more. An llms.txt file is a short list of your key pages that points agents in the right direction. Link it from your footer, since agents mostly find it through links.

Should I block AI bots on my website?

Only if you mean to. Search crawlers like OAI-SearchBot, Claude-SearchBot, and PerplexityBot fetch pages for AI answers, so blocking them can keep you out. Blocking training crawlers like GPTBot or ClaudeBot doesn't affect whether you show up in AI search.

How do I check if my website is ready for AI agents?

Run it through a scanner like is-agentic.com or isitagentready.com, then ask an AI assistant a question only your site can answer and see where the answer comes from.

Is an agent-ready website the same as AEO?

They're related. Answer engine optimization is about getting cited in AI answers. Being agent-ready is about whether agents can reach and use your site at all, which AEO depends on.

Build a website, store, or web app by chatting.

Describe your idea and B12's AI builds it: pages, copy, and the working parts like logins, payments, and bookings. Get a solid first draft, then make it yours.

Executive coaching website
Expense tracking app
Online jewelry store
Lifestyle blog
Architecture portfolio
Invoice generator
Website with animations
Join the 4M+ websites created by B12 · Free to build. No credit card.

Related posts

SEO for AI websites: 2026 checklist & tools
SEO for AI websites: 2026 checklist & tools