On this page
- The advice you found was written for companies, which is why it does not work
- Two different pipelines decide whether your name appears
- Three keys, and most consultants hold one
- What names a company versus what names a person
- You are competing to be an item in a list, not to have the best page
- The namesake problem, which companies never have
- The answer you already get tells you which key is missing
- Run the check monthly, and record it properly
- What will not move it, said plainly
Company advice fails here because a company is resolved by its domain and a person is not. A model names an individual only when three conditions hold at once: your name resolves to one person, that name sits next to a category phrase in consistent wording, and at least one source you do not own repeats both. Most consultants have the first, half of the second and none of the third.
The advice you found was written for companies, which is why it does not work
Almost every guide to being mentioned by AI assumes the thing being mentioned is a company, and a company has a property that you do not have. It owns a domain that functions as its identity. Structured data on that domain, a crawlable site architecture, a file at the root describing the business, review-site profiles and vendor directories all point at one address, and that address is the entity.
A person has no equivalent anchor. Your website is a site about you, which is not the same thing as being you in the way a company domain is the company. You could delete it tomorrow and the model's picture of you would barely shift, because that picture was assembled from bylines, interview transcripts, speaker rosters, directory entries and other people's mentions, most of which sit on servers you have never had access to.
So the company playbook produces a specific, frustrating result for individuals. You do everything on the list, your own pages become immaculate, and the answer to who is the best consultant in your field still contains four other names and not yours. Nothing on that list addressed the actual constraint.
A company can publish its way into being described. A person can only publish their way into being findable, and has to be repeated by others to be recommended. Those are different jobs with different source lists and different timelines.
Two different pipelines decide whether your name appears
There are two mechanisms and they have almost nothing in common. The first is trained memory, which is what the model absorbed from text before its training cut-off. The second is retrieval, where the product runs a search at the moment of the question and writes its answer from the pages it fetches. Advice that does not say which one it is addressing cannot be acted on, because the two respond to opposite inputs.
| Question | Trained memory | Retrieval at answer time |
|---|---|---|
| What it draws on | Text that existed before the training cut-off, weighted toward material repeated and mirrored across many independent sites | Whatever the search layer fetches for this specific query, at this moment |
| Lead time on new work | Long and outside your control, measured in model releases rather than in weeks | Days to weeks, once the page is indexed and can win the query |
| What moves it | Volume, age and mirroring of text that carries your name next to your category | Winning the query the product actually issues, which is usually a list-shaped search rather than a search for your name |
| What barely moves it | Anything published this month | Anything gated behind a login, unindexed, or ranked below the fetched set |
| How to test it | Ask with web access switched off and no links pasted into the chat | Ask the identical question with search or browsing enabled |
| Realistic goal | Being one of the names the model already holds for your category | Being inside the pages returned for the query sitting behind the question |
The two pipelines, and why the same tactic can be useless for one and decisive for the other.
Run both tests before you spend a rupee or an hour. If the offline answer omits you and the online answer names you, your problem is historical text volume and the fix is slow. If both omit you but the online answer names people whose visible credentials are no better than yours, your problem is retrieval and the fix is measured in weeks.
Three keys, and most consultants hold one
A model produces a person's name when three conditions are true at the same time. Each one has a distinct failure mode, and the failures look different enough that you can identify which key is missing from a single answer.
The order matters and it is not negotiable. Corroboration for an unresolved name simply strengthens somebody else's entity, which is the quiet reason a scattergun publicity push can produce genuine coverage and zero change in what a model says about you.
What names a company versus what names a person
The two source lists overlap far less than the shared vocabulary suggests. Below, the same sources are scored for a company and for an individual, with the key each one supplies and whether you can publish it yourself.
| Source | For a company | For a person | Key it supplies | Yours to publish |
|---|---|---|---|---|
| Your own site with Person markup and links to your other profiles | Strong | Useful, weak on its own | Resolution | Yours |
| A file at your domain root describing you to model crawlers | Sometimes | Rarely | None on its own | Yours |
| LinkedIn profile | Weak | Strong for resolution | Resolution and category | Yours |
| Vendor and software review directories | Strong | Does not apply | Corroboration | Not yours |
| Bylined articles on established publications | Weak | The strongest single source | All three | Not yours |
| Podcast interviews with published show notes and transcripts | Weak | Strong | Category and corroboration | Partly |
| Conference speaker pages and panel line-ups | Weak | Strong | Category and corroboration | Not yours |
| Awards shortlists, and seats on judging panels | Moderate | Strong | Corroboration | Not yours |
| A structured reference record such as a Wikidata item | Strong | Strong for resolution | Resolution | Not yours |
| Association, faculty or professional body member pages | Weak | Moderate | Resolution and corroboration | Partly |
| A book with an ISBN, and the library records that follow it | Weak | Strong | Resolution and category | Partly |
| Being quoted by a journalist in ordinary news coverage | Moderate | Strong | Category and corroboration | Not yours |
A source map for a named individual. Read the last two columns together: the strongest person sources are mostly the ones you cannot publish.
Count the strong rows in the person column. Seven of them are sources you cannot publish, which is the entire reason the company playbook misfires. For a business, visibility work is largely a publishing problem. For an individual it is largely an access problem, and the two require different budgets, different skills and different patience.
Your profile still matters, but not for the reason most people assume. It is the resolution anchor that the other sources point back at, which is a specific job with specific requirements, examined in what AI reads on your profile.
- A company is anchored to a domain it controls, while a person is assembled from sources scattered across the web, which is why advice about site structure and files on your own server misfires for an individual.
- Two separate pipelines can produce your name, trained memory and live retrieval, and they respond to completely different inputs, so any advice that does not say which one it addresses cannot be acted on.
- The strongest person-level sources are the ones you cannot publish yourself: bylines on established publications, interview transcripts, speaker rosters, awards shortlists and independent reference records.
- A question asking for the best in a field is list-shaped, so the model draws on list-shaped sources, and a name that has never appeared inside somebody else's list of names is not a candidate.
- The shape of the answer you already get tells you which of the three keys is missing, which means the diagnosis costs one prompt rather than an audit.
You are competing to be an item in a list, not to have the best page
Look closely at the question you are worried about. Who is the best consultant for X is list-shaped. It asks for names in a set, not for a description of one person. A model answering a list-shaped question draws on list-shaped sources, and if your name has never appeared inside somebody else's list of names, you are not in the candidate pool at all.
This is the distinction that explains most of the confusion. A page about you is evidence that you exist. A list that contains you is evidence of standing. Only the second can answer a superlative, because a superlative is a comparison and a page about one person contains no comparison.
- Roundup articles where a writer names several practitioners, which is why being useful to journalists outperforms pitching yourself to them.
- Awards shortlists, including the ones you do not win, because the shortlist page carries every name on it.
- Conference speaker rosters and panel line-ups, which are permanent, indexed pages listing people beside a topic.
- Professional association and accreditation directories, where the category is in the page title and your name is in the body.
- Contributor and expert panels attached to publications, where a masthead page lists people with their specialisms.
- Podcast guest indexes, where a show archive becomes a list of names attached to a subject.
- Book contributor and anthology pages, where several named people sit under a single category heading.
Paid inclusion lists exist, they are indexed, and a model cannot reliably tell a paid placement from an editorial one. A human buyer often can, and a journalist checking you certainly can. Buying your way into a list may move a model answer while damaging the thing the model answer was supposed to produce. Decide that deliberately rather than discovering the trade-off later.
The namesake problem, which companies never have
A company can register a trademark, buy the exact-match domain and own its name in a way you cannot. You share your name with strangers, and if one of them is more prominent, the model's entity for that string belongs to them. Everything you publish then reinforces a record filed under somebody else's identity.
members on LinkedIn. At that scale name collision is the ordinary case rather than bad luck, and a model resolving a bare first name plus surname is making a guess whether or not it sounds confident.
LinkedIn, 2026The repair is unglamorous and it works. Choose one canonical form of your name and never publish under another. Include the middle initial if you need it, keep or drop the accent consistently, and stop alternating between the short form your friends use and the long form on your passport. Then place a disambiguator immediately adjacent to it everywhere: the city, the category, or the firm.
Test it in one prompt. Ask a model to tell you about your full name plus your category. If it returns the other person, or blends both of you into one biography, resolution is your problem and no amount of publishing will fix it until the name itself is disambiguated. The same failure shows up in ordinary search, which is why when nothing comes up for your name and this problem are usually the same problem wearing two coats.
The answer you already get tells you which key is missing
You do not need an audit to diagnose this. Ask one question, read the shape of the reply, and the missing key is named for you. The shapes are surprisingly consistent across products.
| What the model returns | What it means | Missing key | First move |
|---|---|---|---|
| It says it has no information about that person | Your name string carries no entity at all | Resolution | Establish one canonical name form, then get it onto two indexed pages you do not own |
| It describes a different person with your name | The string resolves, to somebody else | Resolution | Add a permanent disambiguator beside your name everywhere, and stop publishing under variants |
| It gets your role and employer right and says nothing else | You exist as a record with no claim attached | Category attachment | Fix the wording of your category so it matches a phrase people type, then repeat it identically across every bio |
| It states confident details that are wrong | The name resolves but the surrounding text is thin, so it fills the gap | Corroboration | Publish a small number of high-quality third-party pages that state the correct facts plainly |
| It names four peers in your field and not you | You are absent from list-shaped sources | Corroboration | Target one roundup, one speaker roster and one shortlist this quarter rather than more of your own content |
| It names you with a specific claim and cites a source | All three keys are working | None | Read the cited source. That page is now doing your positioning, so make sure it says what you want said |
Six answer shapes and the diagnosis each one carries.
The final row is the one people skip. Once a model does name you, it names you using somebody else's sentence, and that sentence becomes your public description whether or not you would have written it that way.
Run the check monthly, and record it properly
This has to be a repeatable measurement rather than an anxious spot check, because a single answer from a single session tells you almost nothing. Models sample from a distribution, so the same question asked twice can produce different names. What you are tracking is a rate, not an event.
One list-shaped prompt asking for the best practitioners in your exact category and geography. One name-shaped prompt asking who you are. One comparison prompt asking how you differ from a named peer. One verification prompt asking what you are known for. Changing the wording later destroys your ability to compare months.
Personalisation and chat memory will show you a flattering answer that no prospect will ever see. Use a private window and an account that has never discussed you. If the product has a memory feature, confirm it is off before you start.
Once with web access disabled, which tests trained memory, and once with search or browsing enabled, which tests retrieval. Record which mode produced which answer, because the two results point at different work with different timelines.
Different assistants use different search layers and different training data, so being absent from one is a data point and being absent from all three is a diagnosis. Note which ones cite sources, because those tell you exactly which pages are speaking for you.
Paste the full reply into a dated sheet along with any cited URLs. Summaries hide the exact wording, and the wording is the evidence. Three runs per prompt gives you a crude rate rather than a single sample.
Score it with the diagnosis table above and write down the single move it implies. Re-run the identical prompts a month later. Movement between shapes is the only progress signal that means anything here, and it is slower than any other channel you work on.
One practical note. Keep the sheet even when the answers are bleak, because the value arrives in month four when a shape changes and you can point to exactly which piece of work landed between the two dates.
What will not move it, said plainly
Several popular tactics have no mechanism behind them for an individual, and knowing which ones are inert saves the budget for the ones that are not.
- Posting more on LinkedIn, on its own. Posts are excellent for the humans who see them and they are a poor entity source, because they are not indexed the way an article on a publication is and they do not corroborate anything.
- A file on your own domain that describes you to model crawlers. Even where it is read, it sits on a server you control, which means it can describe an entity and can never corroborate one.
- Keyword stuffing your bio with your category ten times. Repetition on one page you own is not the same signal as repetition across pages you do not own.
- Telling the model about yourself inside a chat. That context lasts for the conversation and changes nothing for the next person who asks.
- A single press release on a distribution wire. It creates many near-identical copies of one source, and near-identical copies are closer to one source than to many.
- Buying followers or engagement. Neither is visible to the mechanisms described here at all.
Meanwhile the work does have a real timeline, and it is honest to say that the timeline is long. Resolution can be fixed in a week. Category wording can be fixed in an afternoon. Corroboration is the slow one, because it depends on other people publishing, and other people publish on their own schedule.
That is an argument for doing the fast keys immediately and treating corroboration as a standing quarterly commitment rather than a campaign. It is also an argument for not letting this work displace the things that produce enquiries this month, which is why your profile as a conversion step stays the higher priority while the entity work compounds quietly underneath it.
Questions people ask next
How long before an AI assistant starts naming me?
Does adding Person structured data to my website actually help?
Do I need a Wikipedia page to be mentioned by AI?
Should I pay to be included in a best-of list?
Why does the answer change every time I ask the same question?
Is this the same work as ranking on Google?
Send your profile, keep the aha.
One email with your LinkedIn URL. One specific, actionable insight back, free. If it is obvious, we did not look hard enough.
Email your profile →