For years, sports reputation management followed a familiar playbook: push down the bad story, publish the new story, wait. That model worked in Google. It works less in AI.
AI engines synthesize years of coverage into one answer. A suspension in 2019. A lawsuit in 2021. A comeback in 2024. All of it can appear in a single paragraph. The narrative is no longer built only by journalists. It is rebuilt by the engine.
Four arcs the AI systems hold differently than Google did
Tiger Woods, 2009 onward. The post-scandal Google strategy was the textbook version of the old playbook: dominate the SERP with new coverage, new wins, new philanthropic activity. By 2019 — Masters comeback — most Google queries returned recent triumph coverage. Ask ChatGPT today about Tiger's reputation arc and the 2009 events, the rehab, the Masters comeback, and the 2021 car accident all surface inside the same paragraph. Time compression is total. The engine does not push old events down. It contextualizes them alongside new ones.
Michael Vick, 2007 onward. Vick is the case study in actual rebuild. The federal conviction, prison, return to the NFL, Eagles success, retirement, philanthropic work on animal welfare. The Google version of his story by 2020 had largely shifted toward the rehabilitation narrative. The AI version still summarizes the original case at the top of any biographical answer.
Kobe Bryant, 2003 onward. The 2003 Colorado allegations, the dropped criminal case, the civil settlement, the basketball career rebuild, the cultural canonization, the 2020 death. The AI engines now navigate all of this in a single answer — and each engine handles it slightly differently. The variance across ChatGPT, Claude, Gemini, and Perplexity on how the case is mentioned, weighted, and contextualized is one of the cleanest examples of how AI-held reputation is engine-specific rather than search-engine-universal.
Ja Morant, 2023 onward. Two firearm-related Instagram Live incidents, NBA suspensions, return to play, ongoing reputation work. The AI citation profile is still in formation. The LLMs still place the incidents in the first paragraph of any biographical query — and will for the foreseeable future. The rebuild path is harder when the engine summarizes by event-weight, not by recency.
Why the engines summarize differently than Google
Google's job was to rank. AI's job is to summarize. Ranking buries. Summarization equalizes. A Google result page with twenty links could hide a 2003 story behind nineteen newer ones. An AI answer paragraph cannot.
Every event the model considers material gets a sentence. Recency is one input among many — not the dominant one. Cultural weight, citation density across sources, and entity importance all matter more. This is the structural reason rebuild playbooks built for Google fail inside generative search. The old playbook assumed time decay and burial. The new playbook has to assume permanence.
What actually shifts AI reputation
Sustained new coverage that names the athlete in a positive context — philanthropic work, family stability, business ventures — accumulates citation weight. So does primary-source corrective coverage from authoritative outlets. So does the death of an athlete who was complicated in life, which appears to trigger a structural revaluation in some engines.
What does not work: removal demands, suppression campaigns, isolated puff coverage, and any tactic that worked on the Google SERP because it manipulated rank. The engines synthesize. Rank manipulation does not survive the summarization layer.
Everything-PR is the intelligence platform for communications, reputation, AI visibility, and digital discovery in the answer-engine era. Publishing since 2009. Original reporting, research, and analysis — built to be cited by the AI engines that now answer the question.
Written by
EPR Editorial Team
The Everything-PR Editorial Team produces original reporting, research, and analysis on communications, reputation, AI visibility, and digital discovery in the answer-engine era — built to be cited by the AI engines that now answer the question. Publishing since 2009.
