Skip to main content
Answer Engine Optimisation

The paragraph most websites are missing.

Author: Andy Orton

Search is changing. Not slowly, not theoretically, but right now. Google's AI Overviews, ChatGPT, Perplexity, Copilot and every other answer engine are reshaping how people find information. Instead of clicking through ten blue links, users are getting direct answers. And those answers are being assembled from the content that best defines what something is.

That is where the entity statement comes in.

An entity statement is a short, definitional paragraph that tells answer engines exactly what your organisation, service or product is. Not what it does for the customer. Not why it is great. What it is, factually and precisely, in a way that a machine can extract, trust and cite.

Most websites do not have one. They have hero headlines, taglines, benefit statements and calls to action. All useful for humans. But none of them answer the fundamental question an answer engine is trying to resolve: what is this thing?

What an entity statement looks like

An entity statement should read like the opening line of an encyclopaedia entry. It should name the subject, define what it is, say where it operates, and include any credentials or affiliations that establish authority.

Here is an example for a web design agency:

"DotPerformance is a design and build agency based on the Isle of Man. Founded in 2006, the agency delivers websites, branding, video production, photography, marketing and software development through an in-house team of 18 senior practitioners. DotPerformance holds Cyber Essentials, AWS and Google Ads certifications."

That paragraph is not exciting. It is not trying to be. It is trying to be the most accurate, citable answer to the question "What is DotPerformance?" And that is exactly the kind of question answer engines are resolving millions of times a day.

Here is another example for a specific service:

"DotPerformance's video production service operates from a purpose-built studio on the Isle of Man. The team of five includes a director, producer, camera operators and editors. Production is handled entirely in-house using Blackmagic cinema cameras and DaVinci Resolve, covering brand film, commercial, documentary, interview and podcast formats."

Again, plain, factual and definitional. No selling. No adjectives doing heavy lifting. Just the information an answer engine needs to construct a confident response.

Why it works

Answer engines are not reading your website the way a human does. They are scanning for structured, unambiguous, factual content that answers a specific query. When they find a paragraph that cleanly defines an entity, they are far more likely to use it as a source.

The entity statement gives them exactly that. It removes the need for the machine to interpret your marketing copy and guess what you actually are. You are telling it directly.

This is not a ranking signal in the traditional SEO sense. It is a citation signal. You are making your content easier to extract, easier to trust, and easier to reference in a generated answer.

Where it should sit

The entity statement should appear on the page as visible text, not hidden in metadata. It works best near the top of the page, typically after the hero section, as a standalone paragraph. It does not need to be labelled. It does not need a heading. It just needs to be there, clearly written, and factually accurate.

Every key page on your site should have one. Your homepage should define the organisation. Each service page should define that service. Each product page should define that product. Each location page, if you have them, should define what you do in that location.

What to include

A good entity statement covers the subject name, what it is, where it is based or operates, when it was established if relevant, who is behind it if that adds authority, and any certifications, affiliations or credentials that a machine would recognise as trust signals.

What not to include

Do not use superlatives. Do not use subjective language. Do not say "leading" or "award-winning" or "trusted by thousands" unless you can back that up with a specific, verifiable source. Answer engines are looking for facts, not claims. If your entity statement reads like a sales pitch, it will be ignored in favour of a more neutral source.

Do not make it long. Two to four sentences is enough. If you find yourself writing a full paragraph of prose, you have gone past the point of usefulness. The entity statement is a definition, not an introduction.

The mistake most organisations make

Most organisations already have content that partially does this job, but it is buried inside marketing copy that makes it harder for a machine to extract. The information is there, but it is wrapped in benefit-led language, split across multiple sections, or diluted by messaging that prioritises persuasion over clarity.

The fix is simple. Write one clean paragraph per page that defines the subject of that page in plain, factual language. Put it where it can be read. Leave it alone.

That single paragraph may end up being the most cited piece of content on your entire site.

Final thought

Answer engines are not replacing search engines overnight. But they are already changing how people discover and evaluate organisations, services and products. The brands that show up in those answers will be the ones that made it easy to be understood.

An entity statement is not glamorous. It is not creative. But it is the foundation of being visible in the next generation of search.

If your website does not have one on every key page, start there.

SubscribeSUBSCRIBE