Owning "Atur Mehta": knowledge panel, name disambiguation, and AI visibility

The confusion is documented, not hypothetical

• In Oct 2020 you publicly corrected BookMyShow for calling you Harshad Mehta's son, and your clarification tweet ("I am not related to Harshad Mehta in any way…") is now the most-quoted disambiguation text about you. Useful, but it also got scraped by the same content mills, which keeps the two names lexically glued together.
• gmda.in is the single worst offender: it merges both identities into one profile ("Son of the stockbroker Harshad Mehta… co-founder of Square Off… $10 million net worth"). That is a full entity merge in the wild.
• Google's AI overview already flip-flops: one phrasing correctly says you are unrelated to Harshad Mehta; a differently worded query asserts you are "the only son" of him. The conflation is live at the AI layer today.
• Spelling fragmentation makes it worse: Crunchbase and chess.com file you under "Aatur", while the namesake also appears as both "Atur" and "Aatur". Machines cannot cleanly split the two on the name string alone.
• Your "pilot" credential has zero third-party corroboration anywhere. It exists only in your own bios, which is the weakest possible signal for search engines and LLMs. This is a gap, and also your biggest opportunity (Section 5).

You cannot buy or apply for a panel. Google generates one automatically when it is confident a real entity exists and knows what to say about it. The whole industry, Lindy Panels included, sells the same underlying loop:

1. Entity Home. One canonical page on a domain you control (usually your About page) that states exactly who you are. Google's systems treat it as the "source of truth" to reconcile everything else against.
2. Machine-readable identity. Google's documented ProfilePage structured data with a nested Person: name, jobTitle, image, and a sameAs array linking every real profile. One property exists for your exact situation: disambiguatingDescription (schema.org's own example is separating the two George Bushes).
3. Corroboration. Independent sites repeating the same facts about you, worded consistently. Practitioner rule of thumb: roughly 30 trusted sources for people without Wikipedia. Your own site, LinkedIn, and Crunchbase alone do not count; that is "corroborating your own information".
4. Structured-data seed. A Wikidata item (not Wikipedia; the bar is far lower) feeds Google's Knowledge Graph directly. In the best-documented DIY case (Ben Sigman, benobi.one/panel), a panel appeared 73 days after this stack went live, with his Wikipedia draft rejected. Adding a Wikimedia Commons headshot linked via Wikidata's image property (P18) was "the unlock"; the panel appeared about 5 weeks later.
5. Claim and correct. Once any panel appears, claim it via Google's official flow (verified via YouTube / Search Console / X / Facebook). Verified owners get corrections processed in days-to-weeks; anonymous feedback takes 4-16 weeks.

You can watch progress objectively: Google's free Knowledge Graph Search API (kgsearch.googleapis.com/v1/entities:search?query=Atur+Mehta) returns a machine ID (kgmid) and confidence score once you exist as an entity. Empty response = still a string, not a thing.

Wikipedia is not required. Verified examples of panels without Wikipedia: Rand Fishkin; SEO practitioner John McAlpin (~1 year, via Crunchbase + bylines + consistent schema); Ben Sigman (73 days, via Wikidata + Commons + schema). Timelines for a contested name like yours: expect 3-6 months to a stable panel after the foundation is live, and treat it as an ongoing program; panels can appear, change, and disappear.

What they sell: Knowledge Panel creation ("KGMIDs for founders, executives, investors") plus ongoing management. The "Lindy Method" is Assess → Shape → Trigger → Maintain, powered by a "proprietary Knowledge Graph Signal Stack". Their own technical blog post gives the proprietary bit away: entity home + Person JSON-LD + 20-30 authoritative profiles + "7 or more significant news articles on high-authority, Google News-approved sites" + monitoring via the same free Google API described above. It is the standard playbook, packaged.

Their numbers: Stage 1 "mini-panel" in 15-20 days; full panel in 2-2.5 months; contested/common names (you) 3-4 months. Payment 50% upfront, 50% only after the full panel; full refund if no panel or KGMID is delivered. Pricing is quote-only (their /pricing page currently 404s). They do handle same-name cases via a "name-variant and disambiguation strategy", i.e. the middle-name play you can run yourself.

Due-diligence picture: one named principal (founder Abhay Aditya Jain), one testimonial, inconsistent claims on their own homepage ("350+" vs "500+" panels), no Crunchbase presence verified, and, notably, zero independent reviews anywhere (Reddit, X, Trustpilot) for a firm claiming hundreds of delivered panels. Not proof of a problem, but you would be buying on faith. If you engage them, demand 2-3 verifiable, currently-live client panels first.

Four principles govern everything in the roadmap:

1. Disambiguate, don't fight. The target is Google and LLMs holding two clean, separate entities. You win "atur mehta entrepreneur", "atur mehta pilot", "atur mehta square off", and your own panel; he keeps "harshad mehta son". On the bare name query, your owned assets (site, LinkedIn, Instagram, press) crowd page one alongside his tabloids.
2. One name string, everywhere. Standardize on "Atur Mehta" for display (it is what Forbes and LinkedIn already use) with "Atur Mayur Mehta" as the formal/legal form on structured data, Wikidata, and new press. Fix Crunchbase's "Aatur" spelling. His convention ("Atur Harshad Mehta") does the other half of the split for you.
3. One entity at a time. Build "Atur Mehta the person" first; do not simultaneously push a new company entity. Practitioners warn that split signals get locked into a wrong panel permanently once it forms.
4. Starve the co-occurrence. Never publish "I am not related to Harshad Mehta" content again on social platforms. Your 2020 tweet was correct but got scraped into the tabloid corpus, strengthening the very association it denied. The disambiguation line belongs in exactly one place: your entity home (and later Wikidata's "different from" property, P1889), where structured context tells machines the relationship is a negation.

There is no submission channel to any AI assistant. They read the same web you are about to fix, so Phases 1-3 are the GEO program. The per-engine mechanics tell you where each fix lands:

• What measurably lifts AI visibility (Princeton GEO study, KDD 2024): citing authoritative sources (+25-40%), statistics (+25-41%), and quotations (+28%) in your content. Keyword stuffing reduces visibility. Write the About page like a well-sourced mini-profile, not an SEO page.
• Recency beats prestige: over half of AI citations reference material under 11 months old; earned media drives ~84% of citations, press releases under 2%. Hence Phase 3.
• Skip llms.txt: not adopted by any consumer AI engine (Google is on record against it; server logs show crawlers do not fetch it). Vendor claims otherwise are marketing.
• Monitoring: manual monthly scorecard is fine and free; if you want tooling, Otterly.AI (~$29/mo) or Rankscale (~$20/mo) track "Who is Atur Mehta" prompts across engines.
• Feedback loops: when an assistant outputs the false "son of" claim, report it in-product and fix the cited source; the documented correction cases all resolved via the underlying web record, not the feedback button alone.

The evidence pack (already assembled by the research): your railing photo appears on dreshare.com (2019 template, filename literally "Atur-Mehta-CTO-and-founder-of-Square-Off.jpg"), autobuysellsignal.in (2021 Wayback capture, "Harshad Mehta Son" baked into the image), gmda.in (live, updated Jul 2026, merged-identity profile), qnaclub.com (filename hedges "Atur-Mehta-OR-Aatur-Harshad-Mehta"), plus a SlideShare PDF. Two variants overlay "SON OF HARSHAD MEHTA" text directly on your face; those are the most damaging single assets in your search results.

Execution order

1. Correction emails to each site (template: quote the exact caption, state "this photo depicts Atur Mayur Mehta, co-founder of Square Off, not Aatur Harshad Mehta", attach dated proof, request replacement or removal, follow up at day 10-14, then escalate to the editor). Priority order: gmda.in (identity merge), autobuysellsignal.in and the doctored-overlay images, qnaclub, dreshare, slideshare, dailycelebmagazine, punwish, zestdaze, thesportstribune, wikimag, bizadda360, theopinionatedindian, livethecharmedlife.
2. Allies, not targets: thecinemaholic.com and tfiglobalnews.com already disambiguate you correctly; ask them to link your new entity home. DNA India is real journalism repeating the "son Atur Mehta" line innocently; send a gentle clarification, not a takedown.
3. Google-side removals in parallel: image "Remove result" flow on each misattributed image; "Refresh outdated content" after a site corrects; DMCA form only if you own copyright in the photo (check who shot it; a wrongful DMCA filing creates its own liability, worth one hour with an IP attorney).
4. Legal escalation lever for refusers: a media attorney demand letter citing false light invasion of privacy (your photo + false "son of" claim is the textbook fact pattern) moves indifferent small publishers. Budget $500-1,500 if needed.
5. Ongoing detection: monthly reverse-image sweep (Google Lens + TinEye + Yandex) on your canonical headshots, plus Google Alerts on "Atur Mehta" + "Aatur Mehta" + each name with "Harshad".