Writing a website that AI assistants can read

Search used to mean ten blue links and a visit. Increasingly it means a paragraph written by an AI assistant that has read your site, or tried to. If your pages are vague, the answer will be vague, or about someone else. The good news is that what helps an assistant is mostly what helps a person in a hurry.

Say what you are in one plain sentence

"We craft bespoke digital experiences" tells a model nothing it can repeat. "A creative studio in Sofia that does branding, websites, events and marketing" does. Put that sentence near the top of the homepage, in text, not in an image.

One topic per page

A long homepage that covers every service gives an assistant one blurry document. A page per service, each with its own heading, scope and price, gives it something precise to quote when someone asks about that service.

Answer real questions in full sentences

Questions and answers work well because that is the shape of the request. Write the question as people ask it and make the answer complete on its own, without "see above".

Describe the site to machines

• Structured data. Schema markup states who the organisation is, what it offers and how the pages relate, in a format built for software.
• llms.txt. A short Markdown file at the root of the site that summarises it and links every important page. Ours is at /llms.txt.
• robots.txt. Many sites block AI crawlers by accident through a blanket rule. Decide deliberately which ones you allow.

Do not claim what you cannot show

Assistants repeat what they find. Invented statistics and reviews that do not exist are a risk for you once they are quoted back to a customer. We left review markup off this site because we would rather have none than pretend.

None of this replaces having something worth saying. It makes sure that when you do, it is understood. This kind of structure is part of every site we build under website design and of the content work in end-to-end marketing.