When your company is in the news for the wrong reasons, your Wikipedia article changes within hours, the new material comes from the most negative coverage, and more people read the article than at any other time. This page covers the first forty-eight hours, the months that follow, and which problems can be fixed while the story is still developing versus which ones only time will fix.
Start with one fact that changes how teams think about this. During a crisis, readership of your article can rise many times over, because looking a company up on Wikipedia is what people do when it's in the news. Those readers arrive when the article is at its worst. It isn't only people, either: AI tools like ChatGPT summarizing the situation draw on the article too. Whatever the article says that week is what most people will take away. That is why the routine upkeep this library recommends matters: the state of your article the day before a crisis affects how the crisis plays out.
What happens, and how fast
Volunteer editors add the story as news coverage appears, usually within hours of the first major report. The first version reflects the earliest and often most alarming framing, because those are the only stories available to cite. From there, the article changes as fast as the news does. During a heavy week it can be edited dozens of times a day.
Two other things often happen. If editing becomes heavy, Wikipedia's administrators (experienced volunteers with extra permissions) may lock the article so only established editors can change it. The lock applies to everyone: it slows down vandals and well-meaning company employees alike. And the article's talk page, the public discussion page attached to every article, gets busy. That matters to you because the talk page is where your team's requests will go, in public and with timestamps, where journalists covering the story can read them. Write every request as if it could be quoted in a news story about the crisis, because it could be.
The first forty-eight hours
First, read before doing anything. Read the article, its recent changes (every article has a public "history" tab showing every edit ever made), and the talk page. Know what the article actually says, not what someone summarized in an urgent email.
Second, set internal rules. Tell everyone that no employee, contractor, or agency is to edit any related article directly, and make sure the message reaches everyone, including the newest hires. This matters because edits can be traced, either through the account that made them or through the company's internet address, and both reporters and editors know how to check. "Company caught editing its own Wikipedia page mid-scandal" is a common follow-up headline, and it is entirely avoidable.
Third, correct clear factual errors through the proper channel. The proper channel is called an edit request: your team posts a suggested correction on the talk page, states openly who you work for, and includes a news source that supports the correction. Volunteers review it and make the change if it holds up. For now, limit requests to clear factual errors: wrong names, wrong numbers, the wrong company blamed, a rumor stated as fact, or a headline's exaggeration presented as a finding. These requests are legitimate, usually granted, and often handled quickly even during a crisis, because volunteers want the article to be accurate too.
Fourth, start a log. Everything that is wrong but not urgent, including every unfair emphasis and every overblown detail, goes on a dated list for later. The list keeps the team from arguing about fairness during the worst possible week.
Fifth, monitor everything until the news slows down. That means the article, the talk page, the Wikipedia biographies of any executives involved, and Wikidata, the database of facts that feeds Google's Knowledge Panels, where vandalism can go unnoticed while everyone is focused on the main article.
What can be fixed now, later, and never
Now: factual errors, as described above. Material that breaks Wikipedia's own rules can also be removed quickly, and one rule matters most here. Wikipedia's policy on biographies of living people requires damaging claims about a named person to be backed by strong sources, and claims that fall short are removed quickly, sometimes within hours, even in the middle of a crisis. If coverage is attacking your CEO personally with weak sourcing, that policy is the strongest tool available that week.
Later, usually months from now: proportion. While news is breaking, editors add detail as it comes in, and the section about the crisis grows longer than it will seem to deserve in hindsight. Wikipedia's editors recognize this pattern and call it recentism, and their own guidelines say such sections should eventually be trimmed. Once coverage has died down, your team can file a request proposing a shorter, accurate summary, and it will often succeed, because you are asking editors to follow their own guidelines. The same request filed during the crisis looks like damage control and fails.
Never: removing the event. A crisis that received real news coverage becomes a permanent part of the article in some form. Companies that accept this early put their effort into accuracy and fair proportion, where it pays off. Companies that try to remove it make things worse.
Executives and their biographies
Crises involve people, and articles about people follow different rules. Because of the biographies policy described above, a claim about your CEO can sometimes be removed from the CEO's article the same day, while the same claim remains in the company's article and has to go through slower processes. Work on both, but know which one moves faster.
The reverse also happens: a crisis can make a previously low-profile executive well known enough that volunteers create a Wikipedia article about them during the crisis, built entirely from crisis coverage. Once that coverage exists, the article can't be prevented. What you can do is make sure the new article is factually accurate from its first week, using the same edit requests, filed quickly.
The months after
Six months later, very few companies do the follow-up work, even though that is where the long-term outcome is decided. The follow-up looks like this: file the request to shorten the crisis section once coverage has died down. Bring the rest of the article up to date, because a fuller, current article makes the crisis one part of the company's history rather than the most recent thing it says. Fix Wikidata. Carry the corrections into the most important other-language versions of the article, which added the crisis as it happened but won't be cleaned up unless someone asks. And keep monitoring, because anniversary stories and follow-up coverage will bring the section back into focus at predictable times.
An article left as it was during the worst week stays that way for years, and AI answers about the company keep leading with the crisis. The companies that end up with a fair record are the ones that did the follow-up work.
The mistakes that make news
Someone at headquarters edits the article directly, is identified through the edit history, and becomes the next day's story.
Someone deletes the entire crisis section. It is restored within minutes, and the deletion is later cited as evidence of bad faith.
New accounts appear defending the company in suspiciously similar language. Editors recognize this pattern quickly and have formal tools for investigating it, and once it is discovered, it undermines every legitimate request that follows.
A lawyer posts a threatening letter on the talk page. Wikipedia has an explicit rule against legal threats; the accounts involved are blocked, and the threat draws more attention, not less.
The team argues about fairness and emphasis while coverage is still coming in, losing credibility in a dispute that can't be won at that stage.
And the most common and most costly: the team, worn out, never returns for the cleanup six months later, and the company's worst week becomes the permanent version of its Wikipedia article.
What a good outcome looks like
If the goal is for the story to disappear, Wikipedia will disappoint you: the event will be documented, and it will stay documented. If the goal is to protect the company, a good outcome is achievable: an article that is factually accurate every day of the news cycle, executives protected by the rules designed to protect them, no self-inflicted follow-up story, and a record that reads fairly a year later. All of that is possible if the work is done in the right order.
If this page applies to you today, start with the first forty-eight hours above, and talk to us. Experience with these processes matters most during a crisis week.
