A checklist for being read by AI assistants

The litetile team

An AI assistant beside a checklist, four items ticked.

How AI assistants find and recommend small businesses explains where assistants get their facts and why it matters. This post is the practical companion: twelve checks you can run against your own site in an afternoon, so that when an assistant reads it, it reads the right things.

None of this guarantees that an assistant will mention you. It makes sure that when one looks, it finds clear and correct facts, and repeats them correctly.

Say it in text, not in images

Assistants read words. A menu photographed on a blackboard, opening hours inside a banner image, a price list as a scanned PDF: each is harder to read and easier to get wrong.

Open each page of your site and look for facts that live only in pictures or attached files. Services, prices, the area you serve, hours, how to book: each should be written in the page as text. Keep the photo of the blackboard if it looks good, and write the menu beside it.

Images that carry meaning also need a short description, the alt text, which tells people who cannot see the image what it shows, and tells assistants too. Image descriptions (alt text): what to write and why covers what to write.

Answer the questions people ask

An assistant is answering someone's question, so a page that already holds the answer is the easiest to use. A questions-and-answers section on your site does exactly that.

Collect the questions from real life: what people ask on the phone, at the counter and in messages before they buy. Parking, payment, whether you work on Saturdays, how long a job takes, which areas you cover, what to bring to a first appointment.

Then write each answer so it starts with the answer itself. "Yes, we open on Saturdays from 9 to 1" is easy to quote. "We understand that many of our customers have busy weeks, which is why..." is not. Add the detail after the first sentence.

One fact, one wording, everywhere

When your site says "Mon to Fri, 8 to 6" and a directory says "weekdays until 5", the assistant has to guess, or it reports both. The fix is dull and it works.

Write down your facts once: business name, address, phone, email, hours, the area you serve, and the names and prices of your main services. Then search for your business name and go through every place it appears, starting with your own site, your Google Business Profile, social accounts and the directories that list you. Correct anything that does not match.

Check your own site against itself too. If the services page calls it "sports massage" and the prices page calls it "deep tissue treatment", a reader cannot tell whether that is one service or two.

Business details in a standard form

Search engines and assistants read business details more reliably when the page also states them in a shared vocabulary called schema.org. It is a short block in the page code that says, in effect: this is the business name, this is the address, these are the opening hours. Questions and answers and blog posts can be marked up the same way.

Your website tool should write this for you. To check that it is there, paste a page address into a free checker such as Google's Rich Results Test or the Schema Markup Validator. You do not need to read the code; look for your name, address and hours in the results, and fix the source if one is wrong.

Keep pages light and reachable

An automated reader can only use a page it can reach and read. Some fetch a page without running its scripts, so text that only appears after a script runs may never be seen.

  • Make sure the text of each page is there without a login, a pop-up or a button that must be clicked first.
  • Link every page you want read from your menu or from another page. A page nothing links to is hard to find.
  • List your pages in a sitemap, the file that tells readers which pages exist. Most website tools write it for you.

The plain-text copies and the llms.txt file described in the companion post go a step further: they give assistants the words of each page without the layout.

Decide who may read: allow, no training, block

Your site has a file called robots.txt that tells automated readers what they may do. Open yours in a browser by adding /robots.txt to your address, and read it. It is short.

The companies behind assistants publish the names of their readers, and some keep separate ones for separate uses. OpenAI, for example, names GPTBot for collecting training data and OAI-SearchBot for its search. Google uses a name called Google-Extended to let sites decline the use of their pages for its AI models, separately from its ordinary search reader.

Choose what suits you and check that the file says it:

  • Allow: assistants may read your pages to answer questions and to train.
  • No training: they may read to answer questions, but you ask them not to train on your words. The newer Content-Signal convention lets the same file state this preference.
  • Block: they may not read your pages at all.

Check what an assistant says about you

The simplest test is to ask. Once a month, put a few questions to two or three assistants:

  • "What are the opening hours of [your business] in [your town]?"
  • "Who does [your service] in [your town] on Saturdays?"
  • "How much does [your business] charge for [your main service]?"

Write down the date, each answer and the sources it names. When something is wrong, do not argue with the assistant. Find where the wrong fact comes from, often an old directory listing or an unclear sentence on your own site, and fix it there. Answers change from day to day, so look for patterns over a few months rather than reacting to one reply.

Update when things change

New hours, a price rise, a move, a service you no longer offer: each one needs updating everywhere on the same day. Start with your website, then your Google Business Profile, then the directories and social accounts on your list. Assistants and search engines read again on their own schedule, so the sooner every source agrees, the sooner the old fact fades.

The twelve checks

  1. Every fact a customer needs is written as text on a page, not only in an image or a file.
  2. Every image that carries meaning has a short description.
  3. A questions-and-answers section covers what customers ask before they get in touch.
  4. Each answer starts with the answer itself, in one sentence.
  5. Name, address, phone and hours are worded the same on your site, your profile and every directory.
  6. Each service has one name and one price wherever it appears.
  7. Your business details are in the standard form, and a free checker shows them correctly.
  8. Every page shows its text without a login, a pop-up or a click in the way.
  9. Every page you want read is linked from another page and listed in your sitemap.
  10. You have chosen allow, no training or block, and your robots.txt says so.
  11. Once a month, you ask assistants about your business and note what they get wrong.
  12. When something changes, you update the site, the profile and the directories on the same day.

litetile writes your business details, questions and answers and posts in the standard form, a sitemap, an llms.txt file and a plain-text copy of each page on every publish, and its AI crawlers setting lets you allow assistants, ask them not to train, or block them. See what is included.

Related reading: How AI assistants find and recommend small businesses and Image descriptions (alt text): what to write and why.