☀ AEO · be recognised

Become a thing engines recognise.

Modern search and AI engines don't reason about keywords — they reason about entities: known people, brands and things with attributes and relationships. If you're not a recognised entity, the engines are guessing who you are. We make you unambiguous.

Why entities matter

Search stopped being a keyword-matching game years ago. Google and the AI answer engines build a Knowledge Graph — a map of entities (people, brands, products, organisations) and the relationships between them. When you're a resolved entity in that graph, the engine knows what you are, what you do, and how you connect to everything else.

That resolution is what unlocks the visible wins: it's why Google can show a knowledge panel for some brands and not others, and it's why an AI engine will confidently name one company while it hedges or stays vague about another. Being a known thing is the difference between "cited by name" and "not mentioned".

Without it, every mention of your brand is just an ambiguous string. The engine has to guess which thing you are — and it can guess wrong, attaching your reputation, reviews or facts to a different company that shares your name. Establishing your entity removes the guesswork.

How we establish your entity

Four concrete, machine-readable moves that make you one consistent, resolvable identity across the web.

A straight note on Wikipedia: we target Wikidata and sameAs schema — we do not promise a Wikipedia article. Wikipedia has strict notability rules and is not something to game; trying to force a page usually backfires. Wikidata and structured markup are the legitimate, effective levers, and they're the ones we pull.

Fully automated

The Wikidata entry and the sameAs schema are structured and rule-based — things our agents can prepare and apply end-to-end. This is one of the cleanly automatable services: fast to produce, low-friction to deliver, and easy to keep consistent as your profiles change.

How it's delivered

Three delivery modes — pick the one that fits how much you want us touching your accounts.

① DIY no access cheapest

We prepare the Wikidata entry and the sameAs schema for you. You submit the entry and paste the schema onto your site (or hand it to your own AI to install). Nothing to grant, nothing to revoke — the lowest-friction, lowest-cost way in.

② Done-for-you scoped access most value

You grant scoped, revocable access — a scoped OAuth grant, a WordPress application password, or a temporary invite — and our agents handle it end-to-end: create the entry, wire the sameAs links, publish the schema. When it's done, you revoke. Priced on the value of the done-for-you work, not on token counts.

③ MCP no access credits per call

Your AI agent calls entity setup as a tool over the Model Context Protocol and gets the structured Wikidata entry and sameAs schema back inside its own workflow. Billed as credits per call.

ModeHow it's deliveredAccess neededWho executesPriced on
① DIYwe prepare the entry & schema → you submit/pastenoneyou (or your AI)cheapest
② Done-for-youyou grant scoped access → our agents handle it end-to-end → you revokeOAuth / app-password / temp inviteus (agents)value, not tokens
③ MCPyour AI calls entity setup as a toolnoneyour AI, via our toolcredits per call

How it's billed

Entity work is billed as usage-based credits — you burn credits for the setup, and there's no standing subscription for a job that's essentially one-and-done. Pricing is enquiry-based: we scope your situation and quote it. No fixed package prices, no fake tiers, no invented numbers.

The audit that checks your entity presence is free. This service sits in the same action layer as our other AEO work — see the AEO action layer for how entity, schema and answer-shaped content fit together.

Questions, answered

What is an entity in SEO and AEO?

An entity is a distinct, known thing — a person, brand, product or organisation — that engines track with attributes and relationships in a Knowledge Graph. Modern search and AI engines reason about entities rather than raw keywords, so being a recognised entity is what lets them name you confidently instead of guessing.

How do you establish my entity?

We create or clean up a structured Wikidata entry, add sameAs links that tie your official profiles together into one consistent identity, and mirror that with Organization or Person schema on your own site. The result is that engines resolve every mention of you to the same known thing.

Will you get me a Wikipedia page?

No, and we won't pretend to. Wikipedia has strict notability rules and is not something to game — trying to force a page usually backfires. We target Wikidata and sameAs schema, which are structured, legitimate and feed the Knowledge Graph directly, without misrepresenting your notability.

Is this something AI agents can fully automate?

Largely, yes. The Wikidata entry and the sameAs schema are structured and rule-based, so our agents can prepare and apply them end-to-end. It's one of the cleanest services to automate, which is why it's fast and low-friction to deliver.

How is it delivered and priced?

DIY, where we prepare the entry and schema for you to submit; done-for-you, where our agents handle it end-to-end; or MCP, where your AI calls entity setup as a tool. It's billed as usage-based credits, quoted enquiry-based — there are no fixed package prices.

See if the engines know who you are

The free audit checks your entity and Knowledge-Graph presence — whether engines can resolve you to a known thing.

Run my free audit →