Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault

Say the Same Number Everywhere

TL;DR: An answer engine has to decide whether the Richard Lowe on your website and the one on your book jacket are the same person. It does that by looking for agreement. Every place your numbers, your title or your name differ, you’ve handed it a reason to doubt, and a doubted entity doesn’t get named in answers.

Recording an episode with Royce Blake last week, he asked whether we’d still need websites in a couple of years. A reasonable question, and most people expect them to go the way of the fax machine.

My answer surprised him, and the reason is a mechanic almost nobody writes about.

This is the least exciting advice I give, and it’s the piece I’d fight hardest for. People spend real money building their visibility and then undercut it with a bio they wrote years ago and forgot about. It frustrates me, because the fix costs almost nothing and the damage stays invisible until somebody asks an answer engine a question you should own.

What is an entity, and why does the machine care?

How an answer engine decides you are one personTo a search engine a page is a document. To an answer engine you are a thing: a person, with a job, a body of work, a set of claims attached to a name. The technical word is an entity, and before the machine can say anything about you it has to answer a prior question, which is whether this is the same person. The Richard Lowe on the ghostwriting site, on the Amazon author page, and quoted in an article about answer engines: one person or three. That process is entity resolution, and it is not clever. It looks for agreement, so where sources agree confidence rises and where they disagree confidence falls, and a low-confidence entity is one the machine will simply not name, because naming you is a risk it does not need to take.How the machine decides you are one personIt is not clever. It looks for agreement.1It finds your name in placesYour site. An author page.An article quoting you.2It asks a prior questionOne person, or three different ones?3It looks for agreementMatching details raise confidenceContradictions lower it4Low confidence means silenceIt will not name you, because namingyou is a risk it does not need to takeOne wrong number, repeated in one place, is enough to lower the confidence that gets you cited.
How an answer engine decides you are one personTo a search engine a page is a document. To an answer engine you are a thing: a person, with a job, a body of work, a set of claims attached to a name. The technical word is an entity, and before the machine can say anything about you it has to answer a prior question, which is whether this is the same person. The Richard Lowe on the ghostwriting site, on the Amazon author page, and quoted in an article about answer engines: one person or three. That process is entity resolution, and it is not clever. It looks for agreement, so where sources agree confidence rises and where they disagree confidence falls, and a low-confidence entity is one the machine will simply not name, because naming you is a risk it does not need to take.How the machine decides youare one personIt is not clever. It looks for agreement.1It finds your name in placesYour site. An author page.An article quoting you.2It asks a prior questionOne person, or three different ones?3It looks for agreementMatching details raise confidenceContradictions lower it4Low confidence means silenceIt will not name you, because namingyou is a risk it does not need to takeOne wrong number, repeated in one place, is enoughto lower the confidence that gets you cited.

To a search engine, a page is a document. To an answer engine, you’re a thing. A person, with a job, a body of work, a set of claims attached to your name. The technical word is an entity.

Before the machine can say anything about you it has to answer a prior question: is this the same person? The Richard Lowe on the ghostwriting site, the Richard Lowe on the Amazon author page, the Richard Lowe quoted in an article about answer engines. One person, or three?

That process is called entity resolution, and it’s not clever. It looks for agreement. Where the sources agree, confidence goes up. Where they disagree, confidence goes down, and a low-confidence entity is one the machine will simply not name, because naming you is a risk it doesn’t need to take.

Can one inconsistent number hurt your AI visibility?

Yes. The machine can’t tell the difference between a typo and a different person, and that punishes the people who’ve been working longest, because they’re the ones with the most old bios scattered around the web.

Say your website reports 54 ghostwritten books. Your LinkedIn says over 50. Your speaker bio says nearly 60 because you rounded up for a conference two years ago. To you these are the same fact stated loosely. To an entity resolver they’re three conflicting claims about the same attribute, and conflicting claims are exactly the signal that says these might not be the same person.

Nothing breaks. No error appears. You simply stop being the answer to questions you should own.

My own canon, and I don’t deviate from it

  • 113+ books authored, always with the plus sign
  • 54+ books ghostwritten, always stated separately, never added to the first number
  • 980,000+ photographs, never rounded up to a million
  • 33 years in enterprise IT
  • 20 years as Director of Computer Operations and Technical Services at Trader Joe’s

That last one is more important than it looks. I’ve taken a lot of photographs, and over a million would be a better line. It would also be a number I couldn’t support, and the moment one source says 980,000 and another says over a million, I’ve created the disagreement myself.

I don’t round, and I tell clients not to either. A bigger number feels good for the length of one introduction. After that it’s a contradiction with your name on it, sitting on somebody else’s server where you can’t fix it.

Which attributes have to match across your online profiles?

Not everything. Prose can vary, and should. What has to hold still is anything a machine would treat as a fact about the entity.

Your name, in one form. Not Rich in one place and Richard in another. Not with a middle initial here and without it there. Every variant creates a candidate for a separate entity, and separate entities compete instead of reinforcing each other.

Countable claims. Books, years, clients, photographs. Any number that appears in more than one place.

Your role, stated the same way. Ghostwriter, or author, or consultant. Pick the one that’s true and lead with it everywhere.

People spend real money building their visibility and then undercut it with a bio they wrote years ago and forgot about.

Pick one and live with it. People call themselves a consultant on one site, a coach on the next and a founder on a third, then wonder why no answer engine will name them as any of the three. The machine won’t pick for you.

Organization names. The company as it appears in your schema should match the company on your invoices and your book jacket.

Identifiers. ISBNs, an ORCID, a Wikidata item. These are the strongest of all, because they’re unique by design and can’t be misread.

Attributes that must match across your profiles
Attribute Keep it consistent by Why it matters
Your name Using one form everywhere, with or without the middle initial Every variant is a candidate for a separate entity
Countable claims Stating books, years, clients and photographs identically, never rounded Conflicting numbers signal these might not be the same person
Your role Picking the true one and leading with it everywhere The machine won’t pick for you
Organization names Matching your schema to your invoices and book jacket Schema should state the same facts as everything else
Identifiers Using ISBNs, an ORCID, a Wikidata item Unique by design and can’t be misread

Where do contradictions about you online come from?

Almost never from carelessness. They come from time. You wrote a bio in 2019 saying 40 books. You’ve written more since, and you updated the website. The 2019 bio is still on a conference site, a guest post, a podcast page, three directories and an old press release. None of those were wrong when you wrote them.

The other source is helpfulness. Somebody writes an introduction for you and rounds a number, or promotes you to a title you haven’t claimed. It reads well and it contradicts everything else. An event organizer who bumps up your years of experience to make an introduction sound bigger means well. Ask them to use the real number anyway, because their page is one more place the machine reads, and it’ll quote their version of you as readily as yours.

How do you fix inconsistent numbers without spending a month?

Search your own name and read the first three pages as though you were a stranger trying to work out who you are. Write down every number and title you find. The contradictions will be obvious and there will be fewer than you fear.

Then fix in this order. Your own site first, because it’s the source everything else should agree with. Then the profiles you control. That’s most of them. Then the ones you can request a correction from. That’s fewer than you think but not zero. What you can’t change, leave. A single stale bio against a dozen consistent sources is noise. It’s the even split that hurts, where half your sources say one thing and half say another, because then there’s no majority for the machine to trust.

The Day Your Website Died by Richard Lowe
From the author

The Day Your Website Died

Answer engines decide whose name appears in an answer, and most of the advice about it is guesswork. Forty-two chapters on how the decision is made, and what to do about it.

Read the Book →

Why does your own website carry the most weight?

Websites are changing jobs, and that’s the answer to the podcast question. I’d bet my own business on it.

A website used to be where traffic went. Now it’s where your entity is defined. It’s the one place you control completely, the one place that states the canonical version, and the place a machine goes when the other sources disagree. Every platform you use is rented. The site isn’t.

That’s also why structured data matters more than it used to.

Schema is how you state the facts in a form that removes the guessing: this is the person, this is the organization, these are the same entity as these profiles elsewhere. The sameAs property exists for precisely this problem, and most sites leave it empty. I go through the whole mechanism in The Day Your Website Died.

My take

Pick your numbers and use them everywhere. An answer engine that finds two versions of you has a reason to doubt both, and a doubted entity doesn’t get named. Fix your own website first, since it’s the canonical source. Then fix the profiles you control and request corrections where you can. Leave the rest alone, because one stale bio is noise and an even split is what hurts. And fill in sameAs in your schema. Most sites leave it empty.

What does consistency buy you?

Not a ranking. There’s no consistency score.

What it buys is the absence of doubt. When somebody asks an answer engine who to trust on a subject, it assembles candidates and discards the ones it can’t resolve confidently. Consistency doesn’t put you at the top of that list. It keeps you on it.

That’s unglamorous, and it’s the game. Being the answer starts with being a coherent thing to be asked about.

So go find your own numbers this month and make them match. It’s dull work and nobody will congratulate you for it, but I think skipping it is one of the dumbest ways to lose visibility you’ve already paid for, because the machine never tells you it happened.

Frequently Asked Questions

Does an inconsistent online bio hurt how AI describes you?
One against a dozen consistent sources is noise, and the majority wins. The damage comes from an even split, where half your sources say one thing and half say another, because there’s no majority for the machine to settle on. That’s when it stops being confident enough to name you.
What is entity resolution?
The process of deciding whether two mentions refer to the same thing. Before an answer engine can say anything about you it’s to establish that the you on one page and the you on another are one person. It does this by looking for agreement across the attributes attached to your name, so disagreement directly lowers its confidence.
Which numbers matter most for entity consistency?
Anything countable that appears in more than one place. Books written, years in a role, clients served, awards. These are the attributes a resolver can compare mechanically. That makes them the ones most likely to create a visible contradiction.
Should you round up numbers in your bio?
No, and the temptation is worst on the numbers that sound nearly impressive. I have 980,000 photographs and over a million would read better. The moment one source says 980,000 and another says a million, I’ve manufactured the disagreement myself, and a rounded number isn’t more persuasive than a specific one anyway.
What should you do about an outdated bio you can’t edit?
Leave it. Chasing every stale mention costs more than it returns, and a single outdated source against a consistent majority doesn’t move anything. Spend the effort on your own site and the profiles you control, since those are the ones a resolver weights most heavily.
Does schema markup fix inconsistent business information?
No. Schema states the facts unambiguously and connects your profiles with sameAs. That removes a great deal of guessing. But it describes what’s there. If the underlying facts contradict each other across your properties, the schema simply states the contradiction more clearly.

Sources

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment