Free entity SEO learning
Distinguish entities that share similar names
Identity and disambiguation
Use names, aliases, identifiers and contextual evidence to decide which entity a page describes. A shared name is a reason to investigate identity, not a reason to merge a town, business and person.
State the intended referent and the ambiguous name
Ask which observed thing the statement concerns. Record its type, relevant location, official website and other supported identifying details. A short name may be enough within one paragraph, but an isolated search result, table row or exported record can lose that context.
Retain the original name as it appears in the source. Record the candidate things it might describe, then look for context that separates them. The question is which thing is intended, not which spelling is most frequent.
Separate aliases, word meanings and related organizations
An alias is another name for the same entity. Similar wording is not automatically an alias. A renamed organization, a separate subsidiary and an unrelated business with a similar trading name require different treatment. Keep uncertainty explicit until the relationship is supported.
The word “bank” can describe a river edge or a financial institution. Choosing that meaning is different from identifying which organization is intended. In a fictional example, Alder Bank and Brookhaven Bank may both be organizations while remaining separate entities. A shared type does not identify one as the other.
Keep this distinction at the level of the page task. It is not an account of an NLP system or a method for predicting a search provider’s identity decision. Start with the entity definition if the distinction between a thing and its label is unclear.
Read the Brookhaven example without transferring facts
Imagine Brookhaven as the name of a town, Brookhaven Studio as a business and Alex Brookhaven as a person. These are fictional records for this lesson. The word Brookhaven occurs in all three names, but the records describe different things.
A page about the town needs place context. A business page needs the organization’s own identifying evidence. A biography needs evidence about the person. A statement about the town’s location should not become a statement about the business’s registered address or the person’s residence.
Brookhaven
- Distinguishing context
- Place; location and administrative context
- Do not infer
- That every named business operates there
Brookhaven Studio
- Distinguishing context
- Organization; official site and confirmed business details
- Do not infer
- That a matching surname identifies its founder
Alex Brookhaven
- Distinguishing context
- Person; confirmed role and biography
- Do not infer
- That the person owns the town or the business
Compare independent identifying details
Look for identifiers appropriate to the entity and claim. An official organization identifier can help distinguish legal entities. A product model or edition can separate similar items. A stable profile URL may support a person’s identity, but a URL alone can be stale, redirected or controlled by someone else.
Check the surrounding evidence: type, location, role, dates and relationships. A matching name plus a matching profession may still be inconclusive. Conflicting dates or locations are a signal to investigate, not an invitation to discard inconvenient facts.
Three directories that copied the same description supply one repeated observation, not three independent confirmations. Check where the information began and what each source can establish. No fixed number of matching details proves a match; the details must address the intended identity.
Use identifiers with their namespace and limits
Keep the identifier together with its issuer and scope. A registration number belongs to the authority that issued it. A product model belongs to a manufacturer and often a version or market. A profile URL can change or redirect. A familiar code without that context can identify the wrong record.
Review the date and the surrounding description before treating an identifier as current. An expired role does not automatically invalidate a person’s identity, but it can invalidate the statement that the person currently holds that role. See stable entity IDs and page nodes.
Compare conflicting observations openly
These two Studio observations are invented. Their dates and references are part of the teaching exercise, not claims about a real business.
Observation ST01
- Name
- Brookhaven Studio.
- Place
- Northfield, as written in example source A.
- Date and source
- Example source A, version 1, dated 1 October 2026.
- Open question
- Does this describe the same studio as ST02, a move, or another business?
Observation ST02
- Name
- Brookhaven Studio.
- Place
- Eastmere, as written in example source B.
- Date and source
- Example source B, version 1, dated 20 October 2026.
- Open question
- The matching name does not explain the conflicting location. Both records remain separate pending confirmation.
Keep both observations while checking the source, date, role and possible rename or move. Use the evidence conflict method to record why the proposed match remains unresolved.
Record a merge decision so it can be reversed
Keep identifiers stable and preserve separate records until a merge is justified. Record why two records were combined and which evidence supported that decision. A later editor should be able to reverse a mistaken merge without losing the source history.
A useful decision record states what was compared, what supports the match, what opposes it and what happened next. The following records are fictional examples of three different outcomes.
Same entity confirmed within the exercise
- Candidate IDs
- AW01 and AW02.
- Evidence for
- The invented owner record expressly states that AW02 is the renamed AW01.
- Evidence against
- Earlier names differ; no contrary identity evidence supplied.
- Decision and reason
- Keep AW01 as the continuing record; attach AW02 as a retained alias reference because the example source establishes the rename.
- Reviewer and date
- Example editor, 24 October 2026.
- Retained history
- Keep both source versions and the original names. Reverse the merge if later evidence contradicts the claim of shared identity.
Distinct entities
- Candidate IDs
- PL01 Brookhaven town and ORG01 Brookhaven Studio.
- Evidence for a match
- The names share a word.
- Evidence against
- One record describes a place; the other describes an organization.
- Decision and reason
- Keep distinct records. A shared word does not establish shared identity.
- Reviewer and date
- Example editor, 24 October 2026.
- Retained history
- Keep both records and their separate descriptions.
Unresolved identity
- Candidate IDs
- ST01 and ST02 from the observations above.
- Evidence for a match
- Matching studio names.
- Evidence against
- Conflicting location descriptions with no confirmed explanation.
- Decision and reason
- Keep separate candidate records marked unresolved; do not transfer claims.
- Reviewer and date
- Example editor, 24 October 2026.
- Retained history
- Keep both sources, their dates and the request for confirmation.
Avoid false equivalence in links and markup
Link to a page that describes the intended entity. Do not treat a directory entry, a related organization or an article mentioning a person as automatically equivalent to that person’s identity. A relationship such as member, employer or parent organization is different from being the same thing.
A property asserting shared identity such as sameAs needs a page that identifies the same thing. A page mentioning a person or describing an employer is a different relationship. Check the identity record across pages before propagating a correction.
Carry clear identity into titles and openings
Use an informative opening sentence and title that identify the intended subject. Add a location, role, edition or organization name when it genuinely resolves ambiguity. Do not stuff every alias into headings or invent associations to make a page appear more connected.
Use main and supporting entities to keep the page’s subject clear. A helpful qualifier resolves an ambiguity; an unrelated location or role creates a new claim.
Review after a rename or correction
Google describes systems that use context to interpret words and concepts, but that does not reveal the identity decision made for a particular page. Clear descriptions and verified relationships help readers interpret the subject; they do not guarantee a knowledge panel, ranking or a specific internal search representation.
Keep a changed label separate from a changed thing. When a rename is confirmed, review titles, visible references and identity links that use the old label. The names and aliases method explains the continuing record.
Sources and next steps
Read the semantic SEO learning hub and the entity SEO overview for the surrounding topics.
Official references: Schema.org data model, RDF concepts, Google Search guidance. Examples on this page are illustrative, not measured customer results.
