Ranking for your own name when someone else has it

A real case in entity architecture. Two people share the name Doug Lord. One is a 45-year coastal engineer with decades of government citations. The other builds digital authority systems. This is what happened when I fixed my structured data: the regression three days later, the crawler-level block that was quietly masking everything, and, weeks on, where the AI answer layer finally landed.

The baseline: day one morning

In May 2026 I searched my own name cold: incognito, no personalisation, no login. The results were instructive.

Positions 1 and 2 belonged to a coastal engineer. Also named Doug Lord. Based in Newcastle. Forty-five years of experience in coast and estuary management. Indexed across government PDFs, Engineers Australia publications, LinkedIn, and his own domain. A well-established entity with deep citation signals across authoritative sources.

My own domain, douglord.com, did not appear at all. Not on page one. Not anywhere visible.

When I searched logged in, the picture was different: my sites surfaced, my LinkedIn headline was visible, my ventures appeared. Personalisation was doing the disambiguation work that my structured data wasn't doing.

Root cause

The coastal engineer has stronger entity signals. Not because he's more important in any absolute sense, but because his digital footprint is more structured and consistent. Government documents, academic citations, a long-standing domain, stable LinkedIn with specific location. All machine-readable trust signals pointing at the same entity.

My domain had no Person schema. No machine-readable assertion of who I am, what I do, or how my properties relate to each other. Four domains — douglord.com, digitaldominator.com.au, og01.ai, periodictableofdigitalauthority.com — that Google had no instruction to treat as a connected graph.

During the audit, I also found a character-level typo: one domain was referenced as ogo1.ai instead of og01.ai. Google tries to resolve sameAs URLs. A non-existent domain breaks the graph silently: no error, no warning, just a dead link in the entity chain. This kind of gap doesn't appear in any standard SEO audit.

The fix

Three things, deployed in a single session:

1. Person schema: added to douglord.com as a JSON-LD block with entity anchor, geographic signal (Northern Rivers, NSW), sameAs graph connecting all four domains, founder relationships, occupations, and family entity adjacency to documented Australian artists Michael Johnson, Franklin Johnson (Yellow House, Sydney 1969–72), Matthew Johnson (Olsen Gallery), and Anna Johnson (Vogue, Vanity Fair, Artist Profile).

2. llms.txt: rewritten with full identity context, explicit disambiguation against the coastal engineer by name and location, citation guidance for AI systems, and the complete entity picture across digital, artistic, and musical practices.

3. This page: a case study hosted on douglord.com itself. Indexed content on the domain. More pages means more surface area for Google to confirm the entity. The Article schema on this page links back to the Person entity, strengthening the graph further.

// Entity anchor
"@type": "Person",
"@id": "https://douglord.com/#person",

// Geographic disambiguation (away from Newcastle)
"address": { "addressLocality": "Northern Rivers", "addressRegion": "NSW" },

// Connected graph — four domains, one entity
"sameAs": [
  "https://digitaldominator.com.au",
  "https://periodictableofdigitalauthority.com",
  "https://og01.ai",  // was ogo1.ai — broken sameAs, now fixed
  "https://ogcollection.gallery/artists/douglas-lord"
],

// Family entity adjacency — known graph connections
"relatedTo": [
  { "name": "Michael Johnson", "description": "Australian abstract painter, New York. Uncle." },
  { "name": "Franklin Johnson", "description": "Yellow House Sydney 1969–72. Uncle." },
  { "name": "Matthew Johnson", "description": "Painter, Olsen Gallery. Cousin." },
  { "name": "Anna Johnson", "description": "Writer, Vogue, Vanity Fair. Cousin." }
]

The initial result: same evening

Within hours of deploying, cold search had shifted meaningfully.

The coastal engineer dropped from positions 1–2 to 8–9 in cold search. douglord.com appeared at position 3 from being completely absent. The initial movement was real and fast. Entity signals can shift SERP positions within hours of a deploy when the content is clear enough.

The regression: three days later

Three days after deploying, "doug lord" in Chrome (logged in, personalised) showed the coastal engineer back at position 1. douglord.com had dropped to position 5. The initial movement had partially reversed.

This is expected, not a failure. Here is why it happens:

Google's index has multiple layers. The initial movement came from the freshness layer: Google's fast-refresh crawl picked up the new schema quickly and the entity signal shifted. But the deeper ranking signals — inbound links, citation volume, domain authority, SE data sources — hadn't changed yet. After a few days, the deeper signals reasserted themselves and partially pulled the ranking back toward its previous state.

"Doug lord" and "Douglas lord" are two separate battles. The coastal engineer's citations almost universally use the short form "Doug Lord": government PDFs, Engineers Australia documents, Salients Consulting. His entity owns the short form in the knowledge graph. "Douglas lord" (the full name) is a different query where the entity graph is less established, and that's where the initial gains were stickiest.

What the regression tells you about timeline

Entity-based changes follow a predictable propagation curve:

The fix is a foundation, not a finish line. The schema tells Google who the entity is. The subsequent work — Wikidata entry, Wikipedia article, backlinks from controlled properties, FAQ citations in AI systems — builds the authority that makes the ranking permanent.

The OG Collection signal

Position 1 in both searches — logged in and cold — is held by ogcollection.gallery/artists/douglas-lord. This is a plain HTML page on a Cloudflare Pages static site. No Search Console. No backlinks. No schema markup. No sitemap submission.

It ranks because the content entity signal is clean and specific: "Douglas Lord works at the boundary of sculpture, installation, and found material. Drawing from the Northern Rivers landscape..." That's a precise, unambiguous description of a distinct person in a distinct location doing a distinct thing.

It's also the same Douglas Lord. The sculptor, the digital strategist, and the musician are the same person. Once the schema and llms.txt asserted all three identities together with the family entity connections, Google had enough signal to understand the full picture.

The detail worth sitting with: this page has never been submitted to Google Search Console or Bing Webmaster Tools. No sitemap was ever filed for it. It was found, crawled, ranked and cited entirely through normal discovery, because submission is not what drives ranking. Search consoles are diagnostic dashboards; they report on indexing, they do not cause it. What made the page rank was that it was reachable by crawlers and unambiguous about who it described. Two things. Nothing else.

The crawler-access test

The OG Collection result raised a question worth testing directly. If a bare HTML page with no schema could rank and get cited, while douglord.com — with far richer structured data — lagged behind on AI citation, something other than content quality was at play. So I ran a controlled comparison across the property network: same entity, same author, different infrastructure settings.

The variable turned out to be at the edge, not in the markup. One platform-level setting — a managed robots.txt layer — was injecting crawler directives above each site's own rules. Because the first matching user-agent block wins, those injected directives were the ones that counted. The AI discovery crawlers — the exact agents that read a page before an AI system can cite it — were being turned away at the door.

The crawl logs made the effect unambiguous:

That is the whole story in two rows. The page that was reachable got crawled and cited. The page that was blocked — despite a complete Person schema, a connected sameAs graph, and a full llms.txt — was invisible to the same crawler. The richest entity markup in the world does nothing if the crawler that reads it is refused at the edge.

Once identified, the fix was a single toggle per property: disabling the managed layer so each site's own crawler-permissive rules served as written. The test confirmed the hypothesis: the entity architecture was never the constraint. Crawler access was. It is a clean demonstration of why authority has to be measured at every layer — content, structure, and exposure — not just the one that shows up in a standard SEO audit.

Authority metrics implicated

douglord.com scored 31/100 under the PTODA Digital Authority Scoring Methodology at baseline, rated Weak. The gaps mapped directly to three of the six canonical scoring dimensions:

The fixes were structural, not cosmetic. No new backlinks acquired. No paid promotion. No content marketing campaign. Just entity architecture: telling machines clearly and correctly who the entity is, what it does and how its properties connect.

The AI layer resolves: June 2026 update

Weeks after the crawler-access toggle, I ran the same cold check again. This time I looked at Google's AI Mode, the generated answer that now sits above the blue links rather than the ranked list underneath. That layer matters more than the rankings, because it is where an AI system settles on who an entity is before it decides what to say about them. A few weeks earlier my domain had been absent from the page entirely, so the AI layer had nothing of mine to read.

That has changed. Asked about “doug lord”, AI Mode now describes me as a distinct person, “the Australian founder and strategist behind Digital Dominator”, and lists me next to the coastal engineer instead of folding the two of us together. Below the answer, douglord.com holds the #1 organic result with its description intact: “Australian Digital Authority and AI Visibility Strategist · Founder of Digital Dominator · Creator of the Periodic Table of Digital Authority.” A few weeks earlier the same search had returned nothing of mine at all.

But the split this case study predicted is now visible in the generative layer itself:

“Doug lord” has sorted itself out, and “douglas lord” is now following. When this was first written the full name still returned only the historical figures, the Black Douglas, Bosie, Jon Lord. Weeks later AI Mode began carving out a contemporary group for the full name too, listing the digital strategist and the artist as their own people above the historical entries. The short form moved first because that is where the new schema had the clearest run; the full form took longer because it was held by centuries of citation. That was the expected order, not a surprise.

The connected properties moved with it. The schema links douglord.com to digitaldominator.com.au through sameAs, and Search Console for that domain shows the entity reads coming through:

The full name resolves: late June 2026

The June update closed on a prediction: that “douglas lord” would follow “doug lord” once the rest of the graph caught up. A week later, it has.

Asked about the full name now, Google’s AI Mode returns a contemporary Australian group and places the digital strategist inside it, described in the entity’s own terms: “a digital authority and AI visibility strategist based in Byron Bay · founder of Digital Dominator · co-founder of OG01.” The historical figures — Jon Lord of Deep Purple, Lord Alfred Douglas, the Black Douglas — are still there, as they should be, but they no longer crowd out the living person. The short form and the full form now resolve to the same correctly-described entity.

Two things are worth naming about what that took.

First, the wording firmed up. Earlier passes described the entity loosely — “digital marketer”, “SEO strategist”. The current answer uses the canonical phrase the owned properties assert: digital authority and AI visibility strategist. That is the difference between an AI knowing roughly who someone is and an AI repeating the description the entity has chosen for itself. The second is the point of the exercise.

Second, consider what the disambiguation was working against. The other Doug Lord in New South Wales is a coastal engineer with forty-five years of citation behind his name: a published CV, government planning-panel records, an Engineers Australia committee chair, seventy-plus technical papers, a State Library entry. It is one of the deepest single-name footprints in Australian professional life. Separating cleanly from that — not outranking it on the bare name, which no schema can do, but being read as a distinct, correctly-described person beside it — is the measure of how much work the structure did. A week earlier the two were being folded together. Now they are three separate people in the same answer: the strategist, the engineer, the artist, each described as themselves.

The owned domain’s Search Console reflects the same shift in hard numbers. Over the 28 days spanning the v24 build, the LinkedIn reconciliation and the reindex request:

The detail that matters most is the smallest one. The query “douglas lord” — the full name held for centuries by historical figures — was returning no clicks at all in the prior period. It now does. That is the predicted regression completing: the harder query form, the one held by the deepest citation, moving last and in the order the structure said it would.

One engine is still mid-recrawl. As of this writing Bing’s generated answer still resolves the bare name to the coastal engineer alone — the same starting state Google showed weeks earlier. That is expected: Bing recrawls on its own schedule and trails Google here. The owned properties assert the same identity to both; the difference is only in when each engine reads it. The case study will note Bing’s resolution when it lands, rather than before.

The position holds: mid-July 2026

The late-June update closed with a clean AI-layer result and one engine still catching up. The question for a fortnight on was the one this case study cares about most: not whether the entity would move, but whether it would stay moved. It has.

I re-ran the same cold check in mid-July: incognito, signed out, IP resolving to Mullumbimby, NSW, so nothing here is personalisation doing the work. On the bare query “doug lord”, douglord.com holds the #1 organic result on Google, above the coastal engineer and above every other Doug Lord with a claim on the name: the US finance executive, the Florida yacht designer, the obituary. That is the same position seen in late June, now held across three weeks rather than captured in a single snapshot. The contrast with the regression three days after the first deploy is the whole point. Back then the fast-refresh layer moved and the deeper signals pulled it back. This time the deeper signals have caught up, and the position stayed. AI Mode continues to name the entity first among the Australian professionals it lists, with the coastal engineer beside it rather than merged into it.

The full name has moved with it, and further than expected. On Google organic, “douglas lord” now returns douglord.com at #1, with the OG Collection artist page at #2. Both owned properties hold the top two slots of the query historically dominated by the Scottish peerage and Lord Alfred Douglas. When this case study opened, the gallery outranked the site here; now the site leads and the gallery sits directly behind it, so the two identities that resolve to the same person occupy first and second on the hardest name to own.

Bing is the newer movement. The late-June update flagged it as mid-recrawl and said the case study would note its resolution when it landed. It has now split by query form the same way Google did, and it is worth recording precisely what Bing lists:

Two things are worth drawing out of that. On the full name, Bing already ranks douglord.com #1 organic, with the artist page (ogcollection.gallery) surfacing in some sessions though not consistently, so the owned identities are beginning to resolve on the query form Google took longest to sort out. On the short form, the coastal engineer still holds the top organic slot, with the two owned properties immediately below him at #2 and #3. And on both forms, Bing’s generated Copilot answer still lands on other people: for the short form it lists several other Doug Lords (a US finance executive, the coastal engineer, and a UK management consultant) and omits this one; for the full name it resolves to a deceased American educator. That is the pattern this case study has shown throughout, now on a third surface. The organic listing moves first. The generated answer trails, and resolves last. The properties assert one identity to every engine; each reads it on its own schedule.

One honest note on where this has and has not landed. Google’s AI Mode answer for “douglas lord” still varies between sessions, sometimes opening with the historical namesakes before it reaches the contemporary group. The standalone answer engines are split. ChatGPT already resolves the entity as the primary Douglas Lord, describing him in his own terms as the founder of Digital Dominator and creator of the Periodic Table of Digital Authority, and offers only an obscure art-history namesake as an alternative, a long way from the peerage-and-coastal-engineer confusion of the raw web results. Perplexity is the laggard: as of mid-July it still opens on Jon Lord of Deep Purple and does not surface the entity at all. That split is itself the lesson. Google organic and ChatGPT respond to the on-page structure and entity signals already built; the engines still missing the entity are the ones that lean hardest on a Wikidata anchor, which is the one lever not yet in place. A position that holds across weeks and surfaces is the durable claim. A single generated answer is not.

What comes next

Results will be updated here as they come in.