The Wikipedia page exists, but it is outdated, incomplete or simply wrong. A former job title, an old revenue figure, a merger that is missing, a claim that no source supports. The obvious response — clicking "edit" and fixing it yourself — is usually the wrong move when the page is about you, your company or your client. This article explains the route that does work.
Why you should not simply edit the page yourself
Wikipedia's conflict-of-interest guideline strongly discourages editing articles about yourself or organizations you are connected to. The reason is structural: someone with a stake in the subject is poorly placed to judge neutrality, even with good intentions. Direct edits from involved parties are routinely reverted, and they have a second-order effect that many people underestimate — they draw attention. An article that sat quietly for years suddenly gets reviewed line by line, and content you never touched may be challenged or removed in the process. The background is covered in our article on conflict of interest on Wikipedia.
Editing without logging in does not avoid the problem. IP addresses are visible, patterns are recognizable, and edits from a company network to the company's own article are among the most commonly detected forms of conflicted editing.
Prepare before you request anything
Effective updating starts with reading, not writing. Open the article's history tab and see who has edited it, how recently, and whether changes similar to yours have been attempted and reverted before — that history tells you how your request will land. Read the talk page for earlier discussions; a request that ignores a settled discussion restarts an argument you will lose. And inventory your evidence: for every change you want, identify the independent published source that supports it. A request without a source is an opinion, and opinions do not change articles.
This preparation also produces a sharper request list. Distinguish between errors (wrong facts, fixable with a source), omissions (developments the article missed), and grievances (accurate content you dislike). The first two are legitimate requests. The third is not a request at all, and mixing it in undermines the other two.
The correct route: an edit request on the talk page
Every Wikipedia article has a talk page, and Wikipedia provides a formal mechanism for involved parties: the edit request. You state your connection to the subject, describe the specific change you propose, and support it with a reliable source. An uninvolved editor then reviews the request and implements it, adjusts it, or declines it with a reason.
This route is slower than editing directly, but it produces changes that stick. A correction implemented by an independent editor after review has standing; the same correction made by the subject invites reversal.
What a good edit request looks like
Reviewers process requests faster when they can verify them in minutes. That means: quote the exact sentence as it currently stands, give the exact replacement text you propose, cite an independent, reliable source that supports the change, and disclose your relationship to the subject in one sentence. Requests phrased as "please update our page, a lot has changed" tend to sit unanswered, because they transfer all the work to a volunteer.
Want to know if your case qualifies?
Independent editors assess within 24 hours whether your subject meets Wikipedia criteria. Free, confidential, no obligations.
Request a confidential assessmentWhich updates are realistic
Wikipedia responds well to verifiable facts. Changes with a high success rate include correcting factual errors — dates, names, titles, figures — supported by a source; replacing outdated information after leadership changes, relocations or rebrandings; and adding significant developments that received independent press coverage, such as acquisitions or major publications. What counts as an acceptable source is a subject of its own; our article on which sources Wikipedia accepts covers it in detail.
Note the pattern: every realistic update rests on a published, independent source. An update that only the subject can confirm — internal milestones, planned launches, self-reported numbers — has no place in the article, however accurate it may be.
What you cannot expect
Some requests fail regardless of how well they are formulated. Well-sourced critical content will not be removed because the subject dislikes it; neutrality on Wikipedia means reflecting what independent sources say, including the unflattering parts. Promotional rewrites — replacing sober description with marketing language — are declined and damage the credibility of future requests. And unsourced additions are declined even when true, because verifiability, not truth, is the operating standard.
If your concern is not an update but the existence of the page itself, that is a different procedure with different rules; see our article on how to remove a Wikipedia page.
If your request is declined
A declined request comes with a reason, and the reason determines the next step. If the source was judged too weak, a stronger source reopens the discussion — the decline was about evidence, not about you. If the change was judged promotional, rephrase it in plainer terms and try once more. If the disagreement is substantive, the correct escalation is further discussion on the talk page, where other editors can weigh in; for biographies of living persons, the dedicated noticeboard for BLP issues exists precisely for sourcing disputes about people.
What never helps is making the declined change yourself out of frustration. That converts a declined request into a conflict-of-interest incident, and it is remembered the next time you ask for anything.
When the page has larger problems
Sometimes the issue is not one sentence but the article as a whole: written promotionally years ago, tagged for problems, or based largely on primary sources. In those cases, piecemeal edit requests treat symptoms. A structured approach — reassessing the source base, proposing a rewritten draft on the talk page, and working through review with disclosure — is more work but addresses the cause. This is also the scenario in which involving a specialist adds the most value; our articles on what a Wikipedia consultant does and hiring a Wikipedia editor describe what to look for.
Language editions and timing
The talk-page mechanism exists on every major language edition, though templates and conventions differ; on Dutch Wikipedia the request culture is less formalized than on English Wikipedia, and a clearly written, sourced message on the talk page serves the same function. If your subject has articles in several languages, treat each edition separately — each has its own editors, its own state of the article, and its own review of your request. Expect simple corrections to be handled within days on active editions and allow weeks on smaller ones; patience is part of the method, because chasing a request with repeated messages slows it down rather than speeding it up.
Maintenance is part of the work
A Wikipedia article is not a document you correct once. Facts age, sources accumulate, and other editors make changes. Organizations that treat their article seriously check it periodically, keep a record of independent coverage as it appears, and use the talk-page route consistently when something needs to change. The alternative — ignoring the article until something goes wrong — is how most escalations start.