Attribution and Entity

An engine can retrieve your page, find a clean passage, and still leave your name out of the answer, because being quotable and being known are different problems. This chapter is about the second one: making sure the engines can resolve your business into a distinct, confident entity, so that when your evidence gets used, you get named.

What an entity is, in practice

To an engine, your business is a bundle of facts it has pieced together from across the web: a name, a location, an offering, people, a history, and the connections between all of it. When the bundle is consistent everywhere it appears, the engine holds it with confidence and uses it freely in answers. When the bundle is contradictory, thin, or entangled with a similarly named business somewhere else, the engine hedges, and hedging engines leave names out. Attribution work is the unglamorous job of making the bundle coherent.

Your site is the entity's home

Start where you have full control. Your About page should state the facts a machine needs, plainly, in prose: legal and trading name, what the business does, where it operates, when it started, who founded and runs it. Most About pages are inspirational copy with no facts in them, which is exactly backwards for this job; the inspiration can stay, but the facts have to be there in extractable sentences. Put your name, location and contact details in the site footer so they appear on every page. Keep the description of what you do identical, word for word where possible, across your homepage, About page, Google Business Profile, LinkedIn, and every directory that lists you. You are writing the canonical version of yourself and repeating it until the web agrees.

Put names on the words

Engines weigh who wrote a thing, especially for advice on money, health, law, and anything where being wrong costs the reader. Anonymous content from an unnamed "team" carries the least weight it ever has. Every substantial page on your site should have a named author, and every named author should have a bio that establishes why they're qualified to say it: role, credentials, years in the field, linked to a real profile that exists off your site too. Founder-authored content is the strongest version of this. If you own the business and know the subject, the words should be yours and say so. The opinion here is blunt: publishing anonymous expertise in this era is spending money on content while withholding the one signal that makes engines trust it.

Say it in the machines' format too

Everything above should also exist as structured data: Organization markup carrying your name, logo, address and profiles, with sameAs links pointing at your LinkedIn, Google Business Profile and other verified presences, so the engines can connect the dots you've drawn instead of guessing at them. Person markup does the same for your authors. A plain-text llms.txt file at your site's root, describing who you are and what you do in a few clear sentences, is a small, cheap addition aimed squarely at AI crawlers. Chapter ten covers the broader structured data toolkit and chapter eleven the technical layer; the point for now is that entity facts should exist twice, once for humans in prose and once for machines in markup, and they must never disagree.

Attribution work is finite, which makes it satisfying. A focused effort can take an entity from muddled to coherent in a month or two, and it compounds with everything else: liftable content gets attributed, corroboration attaches to the right name, and the engines stop hedging. Corroboration is next, because a coherent entity that only your own website vouches for is still just one voice.