🎉 Introducing AIQ — the new platform from Five Blocks that shows you exactly what AI says about your brand. Discover AIQ →

I have a common name and someone else’s scandal is hurting my search results. What can be done?

Quick answer

This is a solvable technical problem called entity disambiguation: you give each same-named person distinct Person schema with unique identifiers and sameAs links to their own reference set (LinkedIn, professional bios, Wikidata, and Wikipedia where notable), so search and AI engines learn to treat them as two separate identities and stop attaching the other person's scandal to your name.

Common-name confusion is a recognizable category of problem, and the fix is technical. The work is called entity disambiguation: making it unambiguous to search and AI engines that two distinct individuals exist and that they are not the same person. Google and AI engines do not automatically assume that a website, a LinkedIn page, a Wikidata entry, and a press profile all describe one person, they resolve scattered references to a single identity only when the signals explicitly say so. The goal is to supply those signals for each person separately.

Entity-disambiguation diagram showing two people who share the name 'Alex Carter.' Each Person entity is anchored by its own distinct.
Two same-named people, each anchored by its own Person schema and sameAs links to its proper LinkedIn, bio, Wikidata, and Wikipedia references, so engines separate the two identities and the unrelated scandal detaches from your name.

How the fix works, step by step

  1. Add distinct Person schema on each person’s owned properties. Person schema markup with unique identifiers can distinguish two distinct individuals to search engines, anchoring each identity to its own bio site and profiles.
  2. Establish the differences with structured data. Schema markup and structured data help search and AI engines understand what a page asserts and attach it to the correct entity, using contextual signals such as industry, location, role, and associated topics to tell the two people apart.
  3. Add sameAs links pointing each entity to its proper reference set. The sameAs property in Person schema links each person to their own authoritative profiles: LinkedIn, professional bios, Wikidata, and Wikipedia where notable, explicitly telling engines that those profiles are one identity and not the other.
  4. Update Wikidata so the distinction flows into the Knowledge Graph. AI engines use Wikidata for entity disambiguation via unique identifiers and sameAs links, and Knowledge Panel signals can be influenced through Wikidata properties, so a clean, distinct Wikidata item for each person carries the disambiguation into Google’s entity layer.
  5. Where Wikipedia is involved, clarify the distinction on the affected articles. Google and AI engines disambiguate same-named entities using Wikipedia disambiguation pages and distinct articles; where Wikipedia applies, edit requests on the relevant articles help separate the two identities. (Any Wikipedia work is done as disclosed conflict-of-interest editing.)

Why this works

AI model outputs cannot be edited directly; influence comes from shaping the sources, entity signals, authoritative content, and structured data, that the models draw on. Because sameAs links and Person schema establish disambiguation that engines learn over time, the engines gradually separate the two identities, and the unrelated person’s scandal stops attaching to your name.

Last reviewed: 19/05/2026

Sources (4)
Work with Five Blocks

Five Blocks helps companies manage exactly this.

If this is a live issue for you, our team can help. Let's talk about your situation.

Error: Contact form not found.

Skip to content