| Topic | Website readiness for AI search |
|---|---|
| Best for | Site owners, marketers and agencies |
| Format | Checklist of 20 items |
| Related tool | Search Readiness Auditor |
| Reading time | 4 minutes |
Most websites that are invisible to AI assistants are not invisible for a mysterious reason. They have a handful of fixable problems, usually in access, clarity or structure. This checklist works through them in the order that tends to matter. Tick through it for your most important pages first, then the rest of the site.
Access: can systems reach your pages?
- The page returns a normal success response and loads reliably.
- The page is not blocked by a noindex tag or header.
- Your robots.txt does not block the search and user-request crawlers you care about. See robots.txt for AI crawlers.
- Your firewall, CDN or security plugin does not silently block legitimate bots.
- A sitemap exists and is referenced in robots.txt.
- Key content is present in the HTML and does not depend entirely on scripts that crawlers may not run.
On-page basics
- Each page has a unique title that says what the page is.
- Each page has a meta description that summarises it accurately.
- Each page has one clear main heading and logical subheadings.
- A canonical tag points to the preferred version of the page.
- The site works properly on a phone.
- Images have meaningful alt text.
Identity and structure
- Your business name, address, phone number and description are consistent across the site and external listings.
- Organisation or local business markup is present on the home page.
- Authors and practitioners are named and, where relevant, marked up as people. See structured data for AI search.
- Breadcrumbs or clear navigation show how pages relate.
Answer-ready content
- Important pages open each section with a direct answer.
- Headings use the language customers use, including questions.
- Pages show author, reviewer where needed, and a current date.
- Claims are specific and sourced, with no invented statistics.
How to use the checklist
Do not try to fix everything at once. Work in order, because access problems make every later improvement pointless. After each batch of fixes, recheck the page and then see whether assistants describe you differently over the following weeks.
The Search Readiness Auditor tests most of these items automatically for a single URL and scores the page, listing what to fix and what to improve. To measure the outcome in generated answers rather than on the page, follow up with the method for checking whether ChatGPT recommends your business.
Prioritising what you find
After a first pass you will probably have a long list. Sort it by two questions: how much does this item affect whether the page can be found and understood, and how hard is it to fix? Start with high impact and low effort items, which are often a stray noindex tag, a missing title, an overly strict robots rule or an absent organisation markup block. Then plan the heavier items, such as rewriting thin pages or fixing inconsistent listings, as scheduled projects.
Assign each item an owner and a date. A checklist that nobody owns stays a checklist.
Pages to check first
You do not need to audit every page at once. Start with the pages that matter most to revenue: your home page, your main service or product pages, your location or contact page, and your best-performing articles. These are the pages customers see first and the ones assistants are most likely to read. Once those are in good shape, work outwards through the rest of the site.
Re-testing after fixes
Rerun the checks on each page you changed, to confirm the fix worked and nothing else broke. Then, after a few weeks, rerun your fixed question set and compare it with the baseline. Record what changed, even if the answer is nothing, because a null result is information too. Over several months this loop of check, fix and measure is what turns a one-time cleanup into a durable advantage.
What a checklist cannot do
Passing every item does not guarantee citations. These are the foundations, and they remove avoidable obstacles. What earns recommendations beyond that is the quality of what you publish and the way the wider web describes you. Treat the checklist as a floor, then build on it with content worth quoting.
Frequently asked questions
How often should I run through this checklist?
Check your key pages at launch, after any redesign or migration, and then at least twice a year.
Which items matter most?
Access items come first, because nothing else matters if pages cannot be reached. After that, identity, structured data and answer-ready content do most of the work.
Can I do this without a developer?
Many items, such as titles, headings and content, are editable in your content system. Robots rules, firewall settings and templates may need a developer or your hosting provider.
Does the auditor check every item?
It covers access, on-page, structured data and answer-readiness signals that can be read from a page. Items about external listings and content quality need a human review.