Somebody changed your company's Wikipedia article, and the change is bad. A section disappeared, or a sentence now reads like an accusation. The instinct is to find whoever did it and file a complaint. Here is the uncomfortable truth we share with every client at this point: on Wikipedia, "vandalism" is a narrow technical term, most complaints filed under that word are misfiled, and a misfiled complaint costs the one resource that moves things on Wikipedia — credibility.
This guide is the escalation ladder we use in practice: how to diagnose what happened, which venue handles which problem, what response times to expect, and the three mistakes that turn a fixable situation into a permanent one. Disclosure up front: we operate Wikimonitoring, a paid change-alert subscription, and a disclosed-compliance Wikipedia editing service. The ladder below works whether you hire anyone or not.
Step zero: diagnose before you complain
Three very different situations look identical in the moment of discovery.
True vandalism. Wikipedia's definition requires deliberate intent to damage: blanked sections, profanity, gibberish, deliberately falsified facts, offensive images. Real, but rare on corporate pages, because Wikipedia's own defenses catch most of it — the counter-vandalism bot ClueBot NG reverts obvious cases within seconds, and volunteer patrols catch much of the rest within minutes.
A good-faith edit that happens to be wrong. An editor misread a source, pulled an outdated revenue figure, or confused two similarly named companies. Not vandalism — the easiest problem on this list to fix, and the easiest relationship to destroy by opening with an accusation. Our breakdown of who actually edits corporate articles covers why this group, well-intentioned community editors, is an asset rather than a threat.
Sourced negative content you dislike. A lawsuit with a real citation. A critical paragraph from a trade publication. The honest framing: the majority of "vandalism" complaints we see on intake calls are this third category, and under Wikipedia policy it is not vandalism at all. Filing it as vandalism gets the report declined in minutes and tags you as a partisan in the page's history. The correct levers are content arguments — undue weight (WP:UNDUE) and balance (WP:BALANCE) — made on the article's talk page.
Everything below assumes an honest diagnosis. The ladder only works when you stand on the right rung.
The escalation ladder
Start at the lowest rung that fits. Every rung above it costs more time, invites more scrutiny, and burns more goodwill if misused.
Rung 1 — revert obvious vandalism yourself. Anyone may revert obvious vandalism, including the article's subject; conflict-of-interest rules do not require you to leave profanity in place. Open "View history", find the bad revision, click undo. The operative word is obvious. If you would need a paragraph to explain why the edit is vandalism, it is not obvious — stop and use rung 2.
Rung 2 — the article talk page, with sources. The workhorse venue for everything else: factual errors, outdated figures, undue-weight arguments. Declare your connection to the company, propose a specific change, attach the source. Short, specific, neutral requests get answered. Long emotional essays get archived unanswered.
Rung 3 — the editor's user talk page. When one account or IP address keeps making harmful edits, warn them with the standard escalating templates — {{subst:uw-vandalism1|PageName}} through level 4. This step is not optional: administrators at the next rung act on vandals who continued after warnings; reports about unwarned editors get deferred back here.
Rung 4 — WP:AIV, the fast lane. Administrator Intervention against Vandalism handles active, unambiguous, repeat vandalism that continued past warnings. Clear-cut reports are typically actioned within minutes to a few hours, usually with a block. AIV is fast because its scope is narrow; content disputes filed there are declined on sight.
Rung 5 — WP:ANI, the conduct board. The Administrators' Noticeboard for Incidents covers what AIV will not: edit warring, harassment, long-term agenda accounts, undisclosed paid editing by others. It is slower — days, not hours — fully public, and it examines everyone involved, including you (regulars call this the boomerang). Bring diffs, not adjectives.
Rung 6 — WP:BLPN, for content about people. If the material concerns a living person — your founder, CEO, a board member — the Biographies of Living Persons noticeboard is stronger and faster than ANI. BLP is among Wikipedia's strictest policies: contentious claims about living people that lack reliable sources may be removed immediately, and BLPN brings experienced editors who enforce that standard.
Rung 7 — WP:RFPP, page protection. For sustained waves of vandalism from changing IP addresses, request semi-protection, which blocks edits from anonymous and brand-new accounts for a set period. Requests are usually processed within a day. Protection stops an ongoing wave; it is not granted preventively because you fear one.
Where to go, at a glance
| Situation | Right venue | Typical response time |
|---|---|---|
| Blanked section, profanity, gibberish | Revert it yourself (rung 1) | Seconds to minutes; bots often get there first |
| Same vandal returns after warnings | WP:AIV | Minutes to a few hours |
| False or unsourced claim about a living person | WP:BLPN, plus immediate removal | Hours to a day |
| Sourced negative content, arguably excessive | Article talk page, citing WP:UNDUE / WP:BALANCE | Days; depends on who watches the page |
| Edit warring, harassment, agenda campaign | WP:ANI | Days; expect scrutiny in both directions |
| Ongoing wave of IP vandalism | WP:RFPP (semi-protection) | Usually within a day |
| Good-faith factual error | Article talk page, with the correct source | Days |
Three things that make everything worse
Revert wars. The three-revert rule: more than three reverts on one page within 24 hours earns a block, even if you are right. Obvious vandalism is exempt, but administrators define "obvious", not you. The practical failure mode is worse — pages caught in revert wars get protected in whatever version they happen to be in, frequently the wrong one.
Legal threats. Posting anything that reads like "our lawyers will be in touch" — on a talk page, in an edit summary, anywhere on the platform — triggers WP:NLT, and the account is blocked until the threat is withdrawn. The old playbook of escalating to lawyers when administrators "fail to help" is backwards. Genuine legal remedies exist off-wiki and occasionally matter against coordinated defamation, but they are slow, expensive, and must never be announced on Wikipedia.
Sock accounts. Creating a second account, or recruiting employees, to pose as independent voices supporting your position. Sockpuppet investigations have technical means to connect accounts, the resulting blocks are logged publicly and permanently, and the investigation archive ties the whole episode to your company's name. We have seen the sockpuppetry record do more lasting damage than the vandalism it was meant to fight.
Evidence hygiene: the part everyone skips
Wikipedia's saving grace in conduct disputes is that every edit ever made is permanently recorded and attributable. Use that.
- Collect diffs first. Every revision comparison has a permanent URL ("View history", then compare revisions). A diff link is proof; a description of what you remember is not.
- Note timestamps. Wikipedia logs run on UTC, and patterns matter: ten edits in eight minutes reads differently from ten edits across three months.
- Pull the editor's contribution history. An account whose entire history is your article tells its own story to any administrator.
- Keep the report short. Three to five strongest diffs, one neutral sentence each. Reports that read like logs get acted on; reports that read like grievance letters get skimmed.
When to stop self-handling
The ladder works for discrete incidents. It strains against persistent campaigns — the vandal who returns under a new IP address each week, the agenda account that relitigates the same paragraph monthly, protection that expires on schedule while the attacker's patience does not. It also strains in sensitive conflict-of-interest situations where every word the company posts gets parsed for spin. Those are the cases where policy-fluent professional help earns its fee: WikiBusines handles talk-page representation under disclosed paid-editing accounts through the editing service, and annual support covers long-term maintenance and defense when campaigns recur.
One structural fact makes every rung work better: speed. Wikipedia does not notify subjects when an article changes, and in our internal monitoring records the median gap between a problematic edit and the subject discovering it unaided is about seven days — after the change has propagated into search snippets and AI answers. The ladder is most effective in the first hours, not the second week. That is the case for Wikimonitoring: near-real-time alerts with the full diff and the editor's history, so you start climbing the day the edit happens, not the week a journalist mentions it.
Something already happened to your article — or you want to be sure nothing has? Wikimonitoring watches your page and related articles around the clock, delivering every change with the diff, the editor's profile, and the context to know which rung applies.