Entity SEO: Distinguish the People and Organisations Behind a Site

Start with the ambiguity you need to resolve

An entity is a particular identifiable thing, not simply a phrase repeated across pages. A person, company, product or concept can have several names, while the same name can describe several different things. Entity SEO begins by finding where that ambiguity could mislead a reader. A consultant and an unrelated software company might share a short trading name. Repeating that name more often does little to explain which one operates your website or authored an article.

Write a plain identification statement that includes the relevant distinction. An illustrative business called Northbridge might describe itself as a training company based in Leeds, while its product has a separate name and function. Those details are useful because they separate it from other Northbridge organisations. Avoid stuffing every service phrase into the name field. A factual identity statement should remain recognisable on a profile, a contact page and a cited article even when the surrounding description changes.

Name collisions also affect people. If two contributors share a name, a profile should provide enough relevant context to distinguish them without collecting unnecessary private details. Their work, organisation or professional profile may supply the distinction. Keep those identifying facts consistent with the bylines that reference them, and do not merge the contributors because a search result happens to combine their names.

Separate the person, publisher and website

A founder is a person, a company is an organisation and a website is a publication surface. Their relationships may be close, but they are not interchangeable. If a founder writes an article published by their company, make both roles visible. If an independent contributor writes for the same site, do not automatically assign the founder as author. Readers should be able to tell who made a claim and which organisation takes responsibility for publishing it.

Use an about page for ownership and purpose, and an author biography for an individual's relevant contribution. This division prevents one promotional paragraph from carrying every identity role. In an illustrative small business, the founder may also edit and publish the material. It is acceptable to state that honestly. Inventing a separate editorial board to make the arrangement appear larger adds ambiguity instead of credibility, and it creates claims the site cannot support.

Build a small factual identity record

Collect the name, preferred public URL, meaningful alternate names and verified relationships that you need to publish consistently. A short internal record can serve as the source for visible descriptions and structured data. Record where each factual field came from and who can approve a change. Do not collect personal details simply because a vocabulary allows them. Relevance matters: a professional identity usually needs a public profile and applicable role, not an unrelated private address.

Google's Organization documentation explains that organisation markup can communicate administrative details and help disambiguation. That is a useful technical expression of a factual record, not a substitute for one. Organisation schema covers the implementation details. Begin with information a reader can inspect on the site, then represent it accurately. A machine readable claim that contradicts the visible business name or relationship gives the site two competing versions of its identity.

Use identity links with a strict meaning

An external profile is useful when it clearly refers to the same person or organisation. A directory search result containing several similar names is weaker than a specific maintained profile. A news article mentioning a company may support a particular event without functioning as its identity page. Distinguish those purposes. Link a source near the claim it supports, and use identity references only when the destination unambiguously identifies the entity you mean.

The Schema.org sameAs definition makes that identity requirement explicit. Do not use sameAs to connect a company to a famous customer, an industry topic or a publication that merely mentioned it. Those are different relationships. An illustrative agency that works with a retailer remains a different organisation from that retailer. Their association needs an appropriate factual description and evidence. Treating association as identity can turn an otherwise valid structured record into a misleading explanation of the business.

Understand what corroboration can and cannot establish

Your own site is the natural source for your stated services and editorial ownership. It is not independent confirmation that those services are best in their category. Several owned microsites repeating the same claim do not solve that limitation. Ask what each external source actually knows and how it obtained the information. A company registry may establish a legal identity, while a published project may demonstrate work on a specific subject. Neither automatically proves every promotional claim on a homepage.

Use source corroboration to distinguish genuinely separate support from copied announcements. For example, a conference programme can support that someone was scheduled to speak on a topic; it does not necessarily support a broader assertion that they lead the industry. Write the narrower supported statement. This discipline helps people understand the record and avoids creating a web of confident assertions that all trace back to one unsupported sentence in a founder's original biography.

Keep structured relationships modest and accurate

A simple entity model often needs only a person, a publisher, a website and the articles connecting them. Stable identifiers let you refer to those entities consistently. You do not need to declare hundreds of speculative relationships to keywords. If the article explains a concept, describe that subject accurately. Do not turn every term appearing in a paragraph into an assertion of expertise or ownership. The model should clarify the content's real relationships rather than add a second layer of marketing.

Knowledge graphs explains how entities and relationships can be represented. Publishing such a model on your site does not mean a search platform imports it wholesale into its own knowledge graph. Platforms maintain their own systems and may use other information. Avoid measuring entity work solely by whether a knowledge panel appears. A corrected publisher identity, a resolved name collision or a consistent author record is a concrete improvement even when the search presentation remains unchanged.

Maintain identity through changes in the business

Rebrands, acquisitions and role changes require careful distinctions between history and current facts. If a person leaves a company, historical articles can retain the accurate author identity while the profile explains their former role. If a product is renamed, preserve meaningful old names where they help users recognise it. If ownership changes, update the visible explanation and relevant records together. Do not silently rewrite past relationships as though the current structure always existed.

Prioritise inconsistencies that affect a reader's decision: who provides a service, which business receives an enquiry and whether a credential is current. Brand consistency covers the correction work across public surfaces. Use content governance to assign an owner for each identity record, then review the resulting pages as a new visitor with no background knowledge. If that visitor can identify the people, organisation and relevant evidence without deciphering slogans, the foundation is doing its job. Clear identity supports interpretation; earned evidence supports the claims attached to it.

Sources and further reading

• Google Organization structured dataOrganisation markup can communicate administrative details and support disambiguation.
• Schema.org sameAssameAs identifies an unambiguous reference to the same entity.