Your AI assistant doesn’t know what a good website looks like.
AI names those it was able to find, read and understand.
An illustration based on this site’s home page: first it sits among other pages in search, then it appears without design — only the headings remain, in order — then the Schema.org markup and the llms.txt file appear next to it.
It searches the same way people do.
- Speed
- People close a slow page before it loads. Google takes speed into account when it decides whom to show higher.
- Maps listing
- For “near me” searches, Google relies on the business profile. We fill it in so that the address, hours and services match the site.
It reads the page’s code.
- Text in HTML
- All the text is in the code from the start. Some AI systems never see what appears only after a script runs.
- Headings in order
- One main heading with sections under it. An outline like this shows what the page is about and where the answer is.
It understands what is said directly.
- Schema.org markup
- Structured markup tells machines who you are, what you do and what your services cost. Nothing has to be guessed from the design.
- The llms.txt file
- A short brief about you for AI: who you are, what you do, prices and contacts — in a single file.
- Answer pages
- The client’s question as the heading, the answer in the first two sentences. An answer like that is easy to quote.