About ReadyforAI

What is ReadyforAI?

ReadyforAI is a website audit tool that shows how AI systems see your site — and whether it can be discovered, understood, and recommended by models like ChatGPT, Perplexity, Gemini, and Claude.

How it works

We evaluate your website in two tracks, AI Visibility and AI Capability, with 60 checks in total (30 each), and summarise the results in three dimensions: content access, content discovery and task use.

Content access

Can AI read it?

AI crawlers and assistants may be unable to read or trust this content.

Content discovery

Can AI find it?

Pages may be missed, indexed under the wrong address, or never surface in AI answers.

Task use

Can AI act on it?

Agents cannot reliably search, sign up or call your API on a user's behalf.

AI Visibility

Measures how easily AI systems can find, interpret, and recommend your content — including structure, content quality, trust signals, and crawler accessibility.

AI Capability

Measures how well AI agents can interact with your site programmatically — including API availability, authentication, documentation, and agent-friendly standards.

AI recommendations & roadmap

For each website, ReadyforAI uses large models to deeply understand your content and generate actionable recommendations.

You'll get:

  • A clear summary of your current AI readiness
  • Key issues with prioritized fixes
  • Quick wins you can implement immediately
  • A practical 30-day roadmap to improve step by step

All recommendations can be copied and directly used with AI tools to generate improved content or implementations.

What the scanner does

The scanner identifies itself as AIFriendlyBot/1.0. It follows your robots.txt, requests only public web addresses, and never logs in. It creates and changes nothing on your site: besides reading pages, it only sends OPTIONS requests and the standard MCP initialize handshake, which asks a server to introduce itself.

A scan makes at most 60 requests and stops after two minutes, with at least one second between requests to your host. To keep the scanner out of a page, disallow AIFriendlyBot in robots.txt. Checks that needed that page are then shown as could not verify, not as problems. If your robots.txt cannot be read (a server error), the scanner does not request your pages.

What we keep

Detailed results of each scan are kept for 90 days, and a site's latest scan is kept until a newer one replaces it. We do not store page content, only short pieces of evidence for each finding.

How are checks judged?