When ChatGPT doesn't know your name yet.

You typed your own name into ChatGPT. Or your brand name. The model either returned nothing, returned someone else with a similar name, or described you in language that belongs to a previous version of yourself, a version you left behind three years ago. That moment, quiet and slightly unsettling, is now a common experience for Indian founders, professionals and brand builders. It is not a glitch. It is the predictable output of a system that has read the open web and found your identity either absent, contradictory, or unresolvable. This guide explains the mechanics, and the remedies, for both individuals and brands operating in India.

Why ChatGPT does not know your name yet

A generative model does not retrieve records the way a database does. It does not look up your name and return a file. Instead, it generates a response by drawing on patterns encoded during training across billions of text passages from the open web. If those passages described you clearly, consistently, and in corroborated form, the model will generate accurate text about you. If those passages described three different versions of you, or none, the model will either hallucinate, defer, or name someone else.

The technical term for this is entity resolution: the model's process of deciding whether a string of words refers to a single, stable, real-world thing. Your name, in the model's training corpus, may be a string that resolves confidently (one person, one role, one context) or ambiguously (multiple people, multiple roles, contradictory descriptions). The model will always favour the confident resolution. If that confident resolution belongs to a namesake in another country, the model will return that person.

This is not malice. It is arithmetic. The model cannot guess your canonical identity from noise. It needs to read it, repeatedly, from sources it trusts, in language that does not contradict itself.

The difference between a brand and an individual in AI memory

The model resolves brands and individuals through different entity types, and the signals it trusts for each differ in important ways.

How a brand is resolved

A brand resolves through the Organisation entity type (or its specialisations: LocalBusiness, ProfessionalService, Corporation). The model looks for a canonical name, a founding date, a headquarters, a category, a set of named products or services, and at least one authoritative corroboration: a company registry entry, a Wikipedia article, a Crunchbase profile, or a tier-one trade press mention. When all of those align, the model has a stable referent. The brand exists as a thing the model can name.

The most common failure for Indian brands is category confusion. A firm describes itself as "a digital agency" on its homepage, "a technology company" on LinkedIn, and "an AI-first solutions provider" on Crunchbase. The model cannot determine which category is canonical, and so it either omits the firm or assigns it to a vague catch-all that no buyer is asking about.

How an individual is resolved

An individual resolves through the Person entity type. The model looks for a full name in a consistent form, a professional role, an institutional affiliation, a body of named work, and a set of sameAs references: links or mentions that confirm this person is the same entity across multiple sources. The sameAs relationship is borrowed from the Wikidata and Schema.org vocabulary, but its practical meaning is simple: the model needs to see that the "Priya Venkataraman" on LinkedIn, the "Dr. P. Venkataraman" on a university faculty page, and the "Priya V." in a press article are the same person.

For individuals, the personal domain is a particularly powerful anchor. A domain like dravinaash.com (the founder of this firm uses exactly this pattern) functions as a canonical hub: one URL that resolves one name and points outward to all the corroborating surfaces. A model reading that domain reads a clear signal: this is the primary home of this person's professional identity.

The India-specific gap

Indian founders, professionals and brands face a set of structural disadvantages that are particular to the Indian context. Understanding them is not cause for despair; it is the reason an entity-first strategy pays better returns in India than almost anywhere else.

Transliteration and name form variation

Indian names transliterate from scripts with no single standard. Krishnaswamy becomes Krishnaswami, Krishnaswamy, or K. Swamy depending on the document. Thiruvalluvar becomes Thiruvalluvar, Tiruvalluvar, or Thiruvalluvar across different corpora. Each variant is a different string. The model's entity resolution system has to bridge those variants through corroboration. Without deliberate cross-linking, a person's identity splinters across the web into fragments that never fully resolve.

Weak Wikipedia coverage of Indian figures and mid-market brands

Wikipedia's coverage of Indian professionals, founders, and mid-market brands is structurally thin relative to comparable figures in the United States or the United Kingdom. This is not a permanent condition. Wikipedia is an editable, growing corpus, and the Wikidata layer beneath it is even more amenable to structured additions. But the gap exists today, and it means that a model trained on the current web has fewer high-trust anchor points for Indian entities than for Western ones.

This is also an opportunity. An Indian professional who has a well-maintained Wikidata entry and a Wikipedia stub today is operating in a low-competition space. The threshold for being the best-documented instance of a given Indian entity type is lower than it will be in three years. Personal branding in the AI era has a narrower window now than it will later.

Namesakes and common-name collision

Indian names have a statistical structure different from Western naming conventions. The combination of a common given name and a common family name or single-name usage produces collision rates that are high by global standards. If a buyer asks ChatGPT about "Rajesh Kumar, the supply-chain consultant," there are, statistically, hundreds of Rajesh Kumars in supply chain across India. The model will return the one whose entity is best resolved, which may not be the one the buyer meant.

The remedy is specificity in entity construction. A person who is known as "Rajesh Kumar, founder of Procure21, Chennai, specialising in automotive supply-chain digitalisation" is a much more resolvable string than "Rajesh Kumar, consultant." The specificity is not padding. It is the resolution signal.

Step 1 · Build a resolvable entity

Entity construction is the foundation on which everything else depends. Without it, evidence and corroboration are wasted: the model cannot attach them to a single stable referent.

For individuals

Choose one canonical name form and use it everywhere. If you are Dr. Avinaash Subramaniam, that is the string that should appear on your homepage, your LinkedIn, your Wikidata entry, your bylines, your speaker bios, and your press mentions. Variations are acceptable as redirects and aliases, but they must all point back to the canonical form.

Register a personal domain using the canonical form (the pattern dravinaash.com illustrates this). Place on it: a brief structured bio using Schema.org Person markup, a sameAs array pointing to your LinkedIn, Wikidata entry, Crunchbase if applicable, and institutional affiliations. This domain becomes the anchor that the model can use to triangulate all the other mentions of your name.

Create or claim a Wikidata item if your public profile warrants it. The threshold for a Wikidata entry is lower than for a Wikipedia article, and Wikidata is read directly by multiple AI systems as a trusted structured knowledge source. A Wikidata item with correct P31 (instance of: human), P21 (sex or gender), P27 (country of citizenship), P106 (occupation), P108 (employer or affiliation), P856 (official website), and P2002 or P4016 (social profiles) is a powerful entity anchor even in the absence of a Wikipedia article.

For brands

Pick a canonical brand name and reconcile it across every registry. If you are registered as "Ascent Analytics Pvt Ltd" at the Registrar of Companies but operate as "Ascent Analytics" everywhere else, make that explicit in your structured data and your company description. The model should never be surprised by a legal name variant that does not appear in the primary web presence.

The canonical description should be a single sentence that names the category precisely. Not "a leading provider of innovative solutions" but "an analytics consultancy that builds demand-forecasting systems for Indian FMCG brands." That sentence, reproduced consistently across LinkedIn, Crunchbase, the Google Business Profile, and the website's Organization schema, gives the model a clean category placement it can use when composing answers.

Step 2 · Publish liftable evidence

Once the entity is resolvable, the model needs something to say about it. Not marketing prose. Liftable evidence: named work, dated artefacts, specific claims the model can reproduce in an answer without fabricating.

What makes evidence liftable

Three properties distinguish liftable evidence from unliftable prose. First, it is named. A method called "The Chennai Demand Model" is liftable. "Our proprietary methodology" is not. Second, it is dated and bounded. "In our 2025 analysis of forty Indian FMCG manufacturers, we found that…" is liftable. "We have extensive experience in FMCG" is not. Third, it is structurally exposed: placed in the visible reading window of a page, ideally marked up with Article or HowTo schema, so the model's retrieval pass can find it without excavating beneath carousels and hero sections.

For individuals

The highest-value liftable evidence for an individual is a named framework, a published article with a byline, or a recorded talk with a transcript. The framework does not need to be complex. It needs a name, a brief description, and a home on a page the model can retrieve. Authored articles in Indian trade press (The Hindu BusinessLine, Economic Times, Mint, YourStory, Inc42) carry corroborative weight because the model's training corpus includes those publications. A bylined article in one of them is both evidence and corroboration in one artefact.

For brands

The highest-value liftable evidence for a brand is a named case study: one client problem, one named approach, one bounded outcome. The client need not be named if confidentiality applies, but the sector, the scale, and the method should be named. A brand with five such case notes, each with Article schema and a direct-answer paragraph near the top, has a fundamentally different AI visibility profile than a brand with a portfolio page full of unnamed logos.

The model is not going to name you because you worked hard. It will name you because it can read, clearly and without contradiction, what you did, when, and for whom.· Observation from the firm's 247-brand audit (2024-2026)

Step 3 · Earn corroboration where the model looks

Evidence on your own site is necessary but insufficient. The model needs to see corroboration from sources it has been trained to treat as authoritative. For Indian entities, that means a specific set of surfaces.

Wikipedia and Wikidata

Wikipedia is the single highest-trust source in most generative models' training corpora. A Wikipedia article about you or your brand is not merely a vanity marker. It is a structured corroboration that the model can cross-reference against every other mention it has seen. Where a full Wikipedia article is not warranted, a Wikidata item serves as the structured backbone. The two work together: Wikidata for machine-readable facts, Wikipedia for prose context.

Reddit (higher weight than most assume)

Reddit carries a disproportionate weight in the training corpora of several leading models, including in the retrieval layers of Perplexity. In the firm's 247-brand audit (2024-2026), Reddit emerged as one of the surfaces where a positive, substantive mention correlated most strongly with a brand appearing in AI-generated answers. The implication is counter-intuitive: a genuine, detailed discussion of your brand or your work on a relevant Indian subreddit (r/india, r/indianstartups, r/IndiaInvestments, category-specific subreddits) has measurable corroborative value. This is not a recommendation to seed fake threads. It is an observation that authentic community presence matters.

Indian trade press

The Hindu BusinessLine, Economic Times, Mint, The Ken, YourStory, Inc42, and sector-specific publications carry strong corroborative weight for Indian entities. A single well-placed, substantive mention in one of these outlets is worth more than fifty mentions in syndicated PR wire services. The model recognises the publication hierarchy and weights accordingly.

LinkedIn density and the Edelman effect

LinkedIn functions as a high-trust professional registry. The volume and quality of LinkedIn content associated with a person or brand, across their own profile and in the profiles of colleagues, clients and partners who mention them, contributes to corroborative density. The LinkedIn-Edelman B2B Thought Leadership Institute has documented, across successive annual studies, that decision-makers actively consult thought-leadership content when evaluating providers. The model's training corpus includes a substantial slice of LinkedIn's public content, and the pattern of who mentions whom in professional context carries weight.

Quora and structured Q&A

Quora's Indian presence is significant, and answers to genuine questions in your domain, written under your canonical name, contribute a searchable, indexable artefact that the model can retrieve. A thoughtful Quora answer that names your framework and links to your primary domain is a low-cost corroboration point that many Indian professionals overlook.

Brand vs individual in AI · a comparison

The 90-day plan

What an individual or a brand operating in India can do, in sequence, without a large budget.

For an individual (days 1 to 90)

Days 1 to 14 · Entity anchor. Choose one canonical name form. Register the matching personal domain if you have not already done so. Publish a structured personal bio on that domain, marked up with Schema.org Person, including a sameAs array pointing to your LinkedIn profile URL, your Wikidata item (create one if it does not exist), and any institutional or publication pages where your name appears. Reconcile your LinkedIn headline to match the canonical category description precisely.

Days 15 to 30 · Liftable evidence. Name at least one framework, method, or practice area. Write a single 600-word article for your own site or a trade publication that explains that framework, opens with a direct-answer paragraph, and uses Article schema. Ensure the byline uses the canonical name form. Add the article URL to your sameAs array.

Days 31 to 60 · Corroboration. Pitch one substantive piece to an Indian trade publication (YourStory, Inc42, The Ken, or a sector-specific outlet). Write two or three substantive answers on Quora in your domain, using the canonical name. Engage authentically in one or two relevant Indian subreddits where your expertise is genuinely applicable. If the Wikidata item is not yet created, create it in this window and submit it for community review.

Days 61 to 90 · Measurement and iteration. Run your name across ChatGPT, Perplexity, Gemini and Claude with five queries that your target audience would ask. Log the output: are you named, at what position, and with what accuracy? Identify the weakest surface and direct the next month's effort there.

For a brand (days 1 to 90)

Days 1 to 14 · Entity consolidation. Pull every public reference to the brand. Audit for name-form consistency, category-label consistency, and founding-information accuracy. Reconcile across LinkedIn, Crunchbase, Google Business Profile, and the company registrar entry. Add Organization and ProfessionalService schema to the homepage with a canonical description, founded date, founder names, headquarters, and a sameAs array pointing to LinkedIn and Crunchbase.

Days 15 to 30 · Evidence construction. Publish one named case study on the brand's site, using Article schema, with a direct-answer paragraph near the top. Give the methodology used in the case a name. Ensure the founder's name appears in the byline and that the byline links to the founder's personal entity page.

Days 31 to 60 · Corroboration. Secure one substantive mention in an Indian trade publication. Ensure the brand's LinkedIn page is fully completed, with a consistent category label and a description that matches the homepage. Where applicable, initiate a Wikipedia article for the brand or a Wikidata item for the Organisation. Audit and remove or update any press-wire syndications that describe the brand in contradictory terms.

Days 61 to 90 · Geometry and measurement. Build three canonical answer pages on the brand's site, each addressing one buyer question with a direct-answer paragraph and named evidence beneath. Run the ten queries that matter most for the brand's category across four AI engines. Log citation share and position quality. Identify the gap and plan the next quarter accordingly. The related guide, how to get recommended by ChatGPT for B2B services, covers the answer-geometry layer in greater depth for brand operators.

How to measure it

Measuring AI visibility for a personal or brand entity does not require expensive tooling at the start. It requires a consistent discipline.

The four-engine monthly probe

Each month, run your name or brand name through ChatGPT, Gemini, Perplexity and Claude using five to ten queries that a genuine enquirer would use. For an individual: "who is [canonical name]," "who are the leading [your discipline] professionals in [your city or sector]," "recommend an expert in [your specific practice area] in India." For a brand: "who are the leading [category] firms in India," "recommend a [your service] provider for [your target client type]."

Log four data points for each query on each engine: (1) whether you or your brand is named at all; (2) the position in the answer (first, second, listed, absent); (3) the accuracy of the description (does it match your current canonical description?); (4) whether the answer cites a specific artefact from your own site or from a corroborating source.

What movement looks like

Healthy movement across a 90-day period looks like this: citation share rises (more queries return your name), position improves (you move from listed to first or second), accuracy improves (the description matches the current canonical form), and cited artefacts begin to include your own pages rather than only third-party mentions. A programme that produces all four improvements simultaneously is working. A programme that improves citation share without improving accuracy has a naming problem but an entity-description problem, which usually means the canonical description is not yet consistent across corroborating surfaces.

The full methodology for tracking AI citation share across multiple engines is described in the firm's guide to multi-LLM brand visibility evaluation. For an overview of what the firm's broader research found when applying this framework across 247 Indian brands, see the 247-brand audit report. For those who want to understand the AI visibility landscape for public figures specifically, the firm's page on AI visibility for public figures covers the additional considerations that apply when the entity is a person with a significant public profile.

The model will not learn your name by accident. It will learn your name because you gave it a clean entity to resolve, evidence worth lifting, and corroboration from sources it trusts. In India, in 2026, the baseline is low enough that doing these three things well, for an individual or a mid-market brand, is still a genuine competitive advantage. That window will close. The cost of building your entity now is low. The cost of rebuilding it in three years, against a field that has already acted, will be considerably higher.