Demo evaluation
Working on it...
We're checking how well your agent can understand and act on the website.
Demo activity is being simulated while the backend connection is unavailable.
Blocked
AI assistants can't get into your site.
www.amazon.com turned our checker away (bot challenge page (HTTP 202), from AWS WAF). ChatGPT, Claude and other AI assistants visiting for your customers are most likely turned away the same way, so they can't read your pages or do anything for your customers.
We only score what AI assistants can actually see, so there's no score until they can get in.
How to let AI assistants in
Your site is protected by AWS WAF. These are settings in your AWS WAF account; send this page to whoever looks after your website if that isn't you.
In your AWS WAF web ACL, check the Bot Control rule group: its AI and HTTP-library categories may be set to block.
To let our checker in, add a higher-priority rule that allow requests whose user agent contains "AgentReady".
What AI assistants can still read
robots.txt also tells these AI agents to stay out: ClaudeBot, Claude-User, Claude-SearchBot, GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, Google-Extended.Blocks AI
llms.txt isn't published. It's a short guide to your site written for AI assistants.Missing
Sitemap wasn't found, so agents have to guess which pages exist.Missing
Own this site? Let our checker in for your full score
Our checker says who it is: every request's user agent contains AgentReady. We never pretend to be ChatGPT or Claude, so allowing them doesn't let us in. Add the rule from the steps above, then check again.
Mozilla/5.0 (compatible; AgentReady/1.0; +https://github.com/leoi137/agent-ready)Anyone can send that user agent, so remove the rule after your check unless you're happy to leave it.