I sold a company that had a scandal before I joined. My name is now tied to it. What are my options?

Old-company-by-association cases are a recognizable pattern, and the fix is structured. When an executive’s name became tied to a company they sold, particularly one that carried a scandal predating their tenure, the engines have consolidated a conflated narrative from whatever sources were available at the time. Correcting it means intervening at the source layer, not at the visible symptom.

Step 1, Establish the individual as a distinct entity

The first task is entity disambiguation: making clear to the engines that this person is a distinct entity with their own defined timeline, not a permanent association with the former company. The technical levers are:

• Person schema with sameAs links on owned properties, connecting the individual’s bio site to their LinkedIn profile, Wikipedia article (where applicable), and Wikidata Q-ID. These links give engines an unambiguous identity anchor and provide biographical disambiguation signals that separate the individual from the company they once led.
• Wikidata entry or update with accurate employment dates, clear demarcation of the former-owner relationship with a departure date, and a correctly stated current role, so that AI engines drawing on Wikidata for entity resolution have the right timeline.
• Wikipedia article or Talk-page edit request to ensure the article accurately reflects the sequence: the scandal predated this person’s tenure, and the individual exited via sale. Wikipedia is among the strongest disambiguation signals search engines use and one of the heaviest-weighted sources in AI engine responses.

Step 2, Refresh and expand the individual’s own content footprint

Once the entity infrastructure establishes a clean identity, the content layer gives engines material to weight on the right side of the timeline:

• LinkedIn profile updated with a complete, current role description, accurate employment history with dates, and a summary that reflects the individual’s record, not the former company’s. LinkedIn feeds the entity layer and creates a sameAs path that engines follow.
• Bio site or employer bio page with Person schema markup and authoritative content on current work, professional accomplishments, and public commentary. A bio site with clean schema is a direct entity signal the engines extract.
• Authoritative third-party content covering the individual’s actual record in their current role: thought leadership placements, trade press features, podcast appearances with accurate transcripts, and conference profiles. These give the engines evidence to weight against the legacy association. Engines prefer to cite this kind of fact-dense, named-author third-party material.
• Professional directory and association profiles (relevant board memberships, bar listings, industry registries) that corroborate the individual’s standing and current identity in a way self-published content cannot.

Step 3, Monitor and correct AI narratives across leading engines

Entity infrastructure and content alone are not enough if the engines have already consolidated an inaccurate narrative. AIQ monitoring runs the relevant queries across the eight AI engines it currently tracks daily and flags when any engine is still conflating the individual with the former company’s history rather than accurately representing the timeline. When conflation persists, which is common because inaccurate information can embed in AI training data and remain even after live coverage is corrected, source-level work addresses the specific inputs each engine is weighting wrongly.

The engines that weight Wikipedia and Wikidata most heavily (Gemini, Google AI Overviews, AI Mode, Perplexity) typically update fastest once those sources are corrected. Engines drawing more heavily on crawled web content may require sustained third-party coverage before the narrative shifts. AIQ makes that engine-by-engine trajectory visible so the work is targeted rather than diffuse.

What the trajectory looks like

The combination of clean entity infrastructure, refreshed owned properties, authoritative third-party content, and AI narrative monitoring typically produces meaningful movement over six to twelve months. Movement is not linear: the Google entity panel and Wikipedia-weighted engines often respond within weeks of entity-layer corrections; the broader AI narrative and SERP picture takes longer as new content accumulates authority. Cases with strong third-party coverage of the individual’s current work compress the timeline; cases where the former company’s scandal generated durable, heavily-cited long-form coverage require the full horizon and sometimes longer for the legacy content to be displaced in the engines’ weighting.