Built for your kind of site
AIScan fetches your site the way ChatGPT, Claude, Perplexity and shopping agents do, then grades what they find across five dimensions. It reads robots.txt for explicit AI bot rules and Content Signals, follows your XML sitemap, asks for Markdown and /llms.txt, checks for a single H1 and JSON-LD in the server-rendered HTML, and looks for agent endpoints such as an API catalog, an MCP server card and, for stores, UCP and machine-readable pricing.
The pages below turn those checks into a plan for one kind of site. Playbooks are for whoever runs the stack: the WordPress admin, the Shopify store owner, the Next.js or Lovable developer. Each one says which checks that platform usually fails and where the fix lives. Stories are for the business owner: a clinic, a plumber, a restaurant, a studio. Each one names the question a customer asks an AI assistant and the checks that decide whether your site can answer it.
Every page ends with a free scan of your own URL, so you see your score and the failing checks before you change anything. No account needed.
Start from your platform
How your site is built decides where the fix lives. Each playbook shows live averages and the checks that platform fails most often, computed from our own public scans.
Three plugins fighting over robots.txt, and a theme that hides the answer in a tab.
Great structured data out of the box, and a locked-down root that hides the rest.
Server components render beautifully, and the file an agent asks for first does not exist.
The best-rendered HTML we see, and almost nothing at the capability layer.
Shipped in an afternoon, indexed like a single-page app.
A beautiful page built in a canvas, where the root of the domain is not yours to edit.
No detector fired, which means no platform defaults are helping you either.
Start from your business
What an AI agent needs differs by business. Each story names a real moment, the way it currently fails, and the dimensions that decide it. Showing 5 of 40.
Food, travel & hospitality
5Hours, menus, availability — the facts an assistant is asked for by name.
The menu is a PDF, the hours are in a footer image, and dinner is in two hours.
Also covers: restaurant, cafe, coffee shop, bistro, pizzeria, takeaway
The aggregator answers for you, because the aggregator publishes facts and you publish mood.
Also covers: hotel, guest house, bed and breakfast, boutique hotel, inn, hostel
Capacity, dates and hire fee — the three things every enquiry asks and the page never says.
Also covers: event venue, wedding venue, conference centre, meeting rooms, coworking space, exhibition hall
Trip planning is the flagship use case for assistants. Most operators are unreadable.
Also covers: travel agency, tour operator, guided tours, walking holidays, adventure travel, cycling tours
The aggregator takes a third of the order. The assistant could send it direct.
Also covers: takeaway, food delivery, pizzeria, curry house, chinese takeaway, kebab shop
Scan your site and see where you actually stand
Free, no account, about twenty seconds. The report names every failing check by ID, shows the evidence we found, and gives the fix for your platform — plus a hand-off prompt you can paste straight into Claude Code or Cursor.
npx aiscan-cli yoursite.comPrefer to read first? Browse every check we run or the guide library.