Paid Editing, COI, and Disclosure: A Practical Compliance Guide for Brands and PR Teams

Answer box: is paid Wikipedia editing allowed?

Yes. Paid Wikipedia editing is allowed, on one condition: you must disclose it. The Wikimedia Foundation's Terms of Use require anyone paid to contribute to disclose "each and any employer, client, intended beneficiary and affiliation," and the English-Wikipedia policy WP:PAID implements that rule on-wiki. What is not allowed is hiding it. There is no rule against hiring help, and no rule against having a financial interest in an article; the only hard line is concealment. Equally, conflict-of-interest (COI) editors — including paid ones — are "strongly discouraged from editing affected articles directly" and are expected to propose changes on the talk page instead. So the compliant path for a brand is not "edit quietly," it is "declare openly, then request through the front door." This guide shows exactly where your company sits on the disclosure spectrum, what you must declare, and the talk-page workflow that protects both the article and your reputation.

TL;DR

• Paid editing is legal on Wikipedia if disclosed. The Terms of Use and WP:PAID require you to declare employer, client, and affiliation. Undisclosed paid editing is the only version that gets you banned.
• COI ≠ paid editing. Paid editing is a subset of conflict of interest. You can have a COI (you are the subject, an employee, a friend) without being paid, and both require honesty.
• Don't edit your own article directly. COI editors should propose changes on the talk page or via Articles for Creation (AfC), not edit the live page themselves.
• The Disclosure Ladder (below) maps six positions from "no conflict" to "undisclosed paid editor (high risk)" so you can locate your situation and act correctly.
• Hiding COI damages the page and the brand — it triggers deletion reviews, sock-puppet investigations, and press coverage. Transparency is cheaper than the cleanup.

The Disclosure Ladder: a framework for knowing where you stand

Most compliance failures on Wikipedia are not malice. They are people who genuinely did not know which rung of the ladder they were standing on. A marketing manager "just fixing a typo" on her own company's article does not feel like a paid editor — but under policy, she is a COI editor, and if Wikipedia work is part of her job, she is a paid editor too. The Disclosure Ladder is a simple instrument we use with every client to remove that ambiguity before a single edit is made.

The Ladder has six rungs. Rungs 1 to 5 are all legitimate; the only forbidden state is rung 6. Your obligations increase as you climb, but climbing is fine — what matters is that your declared rung matches your real rung. The danger is never being on rung 4 or 5; the danger is being on rung 4 while presenting as rung 1.

Read the Ladder as a diagnostic, not a hierarchy of virtue. A disclosed paid editor on rung 5 is in good standing; an undisclosed employee on rung 6 is not. The single decision that moves you from compliant to non-compliant is whether you disclose — not whether money changed hands. We will return to each rung's mechanics below, but if you remember one thing, remember this: find your rung, then disclose to match it.

A note on terminology. "Paid editing" on Wikipedia does not only mean a freelancer paid per article. Per WP:PAID, it covers anyone who "received or expected to receive payment" for the contribution — including in-house staff whose job includes Wikipedia work, and agencies retained by a client. If Wikipedia is in your job description or your statement of work, you are a paid editor, and the disclosure rule applies to you.

Is paid editing allowed? Yes — and here is the exact rule

The confusion is understandable because two things are simultaneously true: Wikipedia discourages conflicted editing, and Wikipedia permits paid editing. Both can hold because they answer different questions. "Discouraged" governs how you edit (don't touch the live article yourself). "Permitted-if-disclosed" governs whether you may participate at all (yes, with declaration).

The binding obligation lives in the Wikimedia Foundation's Terms of Use, which every editor accepts by editing. Section 4 states that you must disclose "each and any employer, client, intended beneficiary and affiliation with respect to any contribution for which you receive, or expect to receive, compensation." That is the legal contract, not merely a community custom. The English-Wikipedia policy that operationalises it, WP:PAID, is blunter still: "If you were paid or expected to be paid in any way for contributing to Wikipedia, you must disclose it," and "Editors who fail to disclose paid contributions are prohibited from editing."

So the answer to "can I pay for a Wikipedia page?" is genuinely yes — provided whoever does the work discloses correctly and edits through the right channel. The answer to "can I pay for one secretly?" is no, and the people who try it are exactly the ones whose pages get deleted and whose brands end up in a press story about Wikipedia manipulation.

This is also where most vendors quietly mislead clients. A provider that promises a page with "no community risk," "guaranteed approval," or "confidential editing" is either misunderstanding the rules or planning to break them. We say plainly what the rules say: outcomes on Wikipedia are decided by an independent community and cannot be guaranteed by anyone. What a serious provider controls is risk — through notability assessment, source research, neutral drafting, transparent disclosure, and post-publication monitoring — not the verdict.

If you are still at the "do we even qualify" stage, that risk question comes before the disclosure question. Notability is decided by independent reliable-source coverage, not by willingness to pay; our companion guide Can My Company Get a Wikipedia Page? walks the notability decision tree, and the Notability Audit gives you a documented yes/no before any drafting spend.

What must be disclosed: employer, client, affiliation

WP:PAID is specific about the three things a paid editor must name. The policy states that "editors who received or expected to receive payment must disclose their employer, client, and affiliation, on their user page, talk page, or in edit summaries." The live Terms of Use widen "client" to "client, intended beneficiary" — so if you are an agency retained by a PR firm that is in turn retained by the brand, each link in that chain is disclosable.

Here is what each term means in practice for a brand or PR team:

That last row catches agencies off guard. The Terms of Use add a rule aimed squarely at vendors: "if you make a public posting off the Projects advertising editing services on Wikipedia in exchange for compensation of any kind, you must disclose all Wikipedia accounts you have used or will use for this service in the public posting." In other words, an agency that markets Wikipedia work must publicly tie its marketing to its editing accounts. A vendor that sells Wikipedia pages but refuses to name its accounts is, by definition, out of step with the Terms it operates under.

Disclosure is not a one-time checkbox. It must accompany the work — on the user page, on the talk page where the contribution happens, or in edit summaries — so that any reader or reviewer can trace who did what and for whom. The point is auditability: the community should never have to guess whether an edit is paid.

What we will NOT promise, and why

We will not promise approval, a deletion-proof page, or "no risk." We cannot, and neither can anyone else — Wikipedia's community decides independently, and WP:GNG says coverage "creates an assumption, not a guarantee." We will not edit your live article while pretending to be a neutral volunteer, we will not hide that you are a paid client, and we will not "manage" admins. Anyone offering those things is selling you the exact behaviour that gets pages deleted and brands named in the press. What we do promise is honest risk reduction before money is spent, full WP:PAID disclosure, and a transparent talk-page process you can inspect at every step.

What brands should avoid

The fastest way to turn a Wikipedia project into a reputational liability is to do any of the following. None of these are grey areas; each one violates policy and most are actively hunted by the community.

• Editing your own live article while posing as neutral. WP:COI says COI editors "are strongly discouraged from editing affected articles directly." Doing it anyway, undisclosed, is the classic trigger for a sock-puppet investigation.
• Hiring a "confidential" editor. Confidentiality and the disclosure requirement are mutually exclusive. A vendor selling secrecy is selling a Terms-of-Use violation.
• Buying "100% approval" or "no-deletion" guarantees. These are impossible and they signal an operator who relies on undisclosed editing or sock-puppets. Our scorecard guide, How to Choose a Wikipedia Page Creation Service, scores vendors on exactly this red flag.
• Creating sock-puppet or meatpuppet accounts to manufacture consensus or evade scrutiny. This is among the most severely sanctioned behaviours on the platform.
• Paying journalists, planting fake sources, or buying aged accounts. Beyond Wikipedia sanctions, this is straightforward fraud and a media story waiting to break.
• Trying to "suppress" negative but reliably-sourced content. Wikipedia represents what reliable sources say; attempting to scrub sourced criticism violates neutrality and usually backfires publicly.
• Treating the article as a brochure. WP:NPOV is "non-negotiable"; promotional tone gets flagged, then deleted.

Notice the common thread: every avoidable failure is a form of concealment or coercion. The legitimate path — disclose, request, let the community decide — is slower and less flattering to the ego, but it is the only one that produces a page that survives.

Direct editing vs talk-page requests vs AfC vs consultant-guided: which channel, when

"Paid editing is allowed with disclosure" raises an immediate practical question: allowed to do what, exactly? There are four channels, and choosing the right one is most of compliance. They differ by who clicks "publish" and how much community review sits between you and the live article.

Two of these channels deserve emphasis because brands most often get them wrong.

Talk-page edit requests are the workhorse of compliant maintenance. If your company already has an article and a fact is wrong — a stale revenue figure, a former CEO still listed as current — you do not edit it yourself. You open the talk page, post a neutral, specifically-worded request ("Please change X to Y, per [reliable source]"), tag it for review, and wait for an uninvolved editor. WP:COI is explicit that COI editors "can propose changes on article talk pages instead" of editing directly. This is slower, but it is bulletproof, and it is the exact mechanism our free lead magnet formats for you.

Articles for Creation is the required route for new pages when you have a COI. WP:AFC states the process "must also be used by editors with a conflict of interest." A reviewer then checks the draft against notability and sourcing before it ever reaches the public encyclopedia. One warning the same policy gives, increasingly relevant in 2026: "Articles that are generated entirely by LLMs will be rejected." A draft that is obviously machine-written without human sourcing judgement is a fast decline — see our companion piece on why Wikipedia pages get rejected or deleted for the full failure-pattern list.

The consultant-guided channel is not a fifth loophole; it is simply rungs 4–5 of the Ladder executed properly. A disclosed specialist writes a neutral, well-sourced draft, declares the paid relationship, and then submits it through the same AfC or talk-page channels above. The value is in the drafting quality and the disclosure discipline, not in any special access — because there is none to be had.

Why hiding COI damages the page and the brand

Brands sometimes reason that disclosure invites scrutiny, so secrecy is safer. The opposite is true, and it is worth understanding the mechanism rather than taking it on faith.

For the page: Undisclosed COI editing is detectable, and the community is good at detecting it. Editing patterns, IP ranges, and tone give it away. Once an article is suspected of undisclosed paid editing, it attracts maintenance tags ("This article may have been created or edited in return for undisclosed payments"), a possible deletion discussion, and a sock-puppet investigation. The article you paid for can be deleted faster than a neutral one, because the suspicion itself becomes grounds for review. WP:DEL notes that deletion "removes the current version and all previous versions from public view" — your investment vanishes, including the history. Worse, a deletion for promotional/COI reasons makes a future legitimate attempt harder.

For the brand: This is the part the page-level analysis misses. Wikipedia's paid-editing scandals do not stay on Wikipedia. Undisclosed campaigns are routinely written up by technology and business press, and the resulting story — "Brand X caught secretly editing its own Wikipedia page" — is exactly the reputational damage the brand was trying to avoid by getting a page in the first place. The asymmetry is brutal: disclosure costs you a few sentences on a user page; concealment, if discovered, costs you a news cycle. For a company whose Wikipedia presence increasingly feeds AI assistants and knowledge panels (we cover that in Wikipedia, Wikidata, and AI Search), a manipulation story is the worst possible signal to send into the AI training pipeline.

There is also a trust dimension that compounds. WP:COI explains why the community cares: undisclosed COI "undermines public confidence and risks causing public embarrassment to the individuals and companies being promoted." The rule is not bureaucratic box-ticking; it exists because Wikipedia's value to everyone, including your brand, depends on readers trusting that articles are not covert advertising. Disclosure protects that trust, and your brand is a beneficiary of it.

A decision tool you can use right now: the COI Self-Assessment

You do not need to hire anyone to find your rung. Run this five-question check before touching any article. It mirrors how we open every engagement.

1. Am I, or my organisation, the subject of the article — or closely tied to it (employer, client, family, financial interest)? → If no to all: you are rung 1–2. You may edit directly, but stay neutral. → If yes to any: continue.

2. Is any payment, salary, retainer, or in-kind benefit involved in my doing this Wikipedia work? → If yes: you are a paid editor (rung 4–5). Full WP:PAID disclosure is mandatory. → If no: you are a COI editor (rung 3). COI disclosure is still expected.

3. Does the page already exist? → Exists → use a talk-page edit request (do not edit the live page). → Does not exist → use Articles for Creation (submit a draft for review).

4. Have I disclosed — employer, client, affiliation — on my user page and the relevant talk page? → If no: stop. Disclose first. Editing before disclosing is the violation. → If yes: proceed to the request.

5. Is my proposed text neutral, specific, and backed by a reliable independent source? → If no: revise. Promotional or unsourced requests get declined and flag your account. → If yes: post the request and let an uninvolved editor decide.

If you answered "paid editor," "page exists," and reached step 5 cleanly, you are on rung 5 doing it correctly — which is precisely the position a compliant consultant occupies. If any step tripped you, that is the step to fix before spending money. For the deeper "should this article exist at all" question, pair this with the Notability Audit; for what a good source looks like in step 5, WP:RS requires sources "with a reputation for fact-checking and accuracy."

Pricing and operational specifics

Compliance is not a line item you can skip to save money — it is built into how the work is scoped. Disclosure and talk-page process do not cost extra; doing the work without them is what eventually costs you a deletion and a re-do. Here is how WikiBusines prices the underlying work, all in EUR with approximate USD for orientation. Final pricing depends on source strength, language edition, complexity, COI sensitivity, and maintenance scope.

A word on our published refund clause: if a published page cannot be defended after three attempts within the 90-day monitoring window, we refund 80%. Read what that is and is not. It is not a guarantee of approval — nothing can be. It is an honest allocation of risk: we put our own fee on the line for defensibility after publication, which is the part a disciplined process can actually influence. A vendor that guarantees the outcome is bluffing; a vendor that stands behind the defensibility of its work is doing the only thing integrity allows.

For full price logic across editions and the five-year total cost of ownership, see How Much Does a Wikipedia Page Cost in 2026? and the pricing guide.

FAQ

Is paid editing allowed on Wikipedia? Yes, if it is disclosed. The Terms of Use and WP:PAID permit paid contributions provided you declare your employer, client, and affiliation; undisclosed paid editing is prohibited and "editors who fail to disclose paid contributions are prohibited from editing." The only forbidden version is the secret one.

Do you have to disclose paid editing on Wikipedia? Yes — it is a Terms of Use requirement, not optional etiquette. You must disclose on your user page, the relevant talk page, or in edit summaries, and disclosure must accompany the paid work so it is auditable. Skipping it is the single most common reason paid-editing accounts get banned.

What must a paid editor disclose? Three things at minimum: employer, client, and affiliation, per WP:PAID. The live Terms of Use extend "client" to "client, intended beneficiary," so every party who benefits in the chain should be named. Agencies that advertise Wikipedia services must additionally disclose their editing accounts in that public marketing.

Can I edit my own company's Wikipedia page? You can, but you should not edit the live page directly. WP:COI strongly discourages COI editors from editing affected articles directly and says they "can propose changes on article talk pages instead." Use a talk-page edit request and let an uninvolved editor apply it.

What is the difference between COI editing and paid editing? Paid editing is a subset of conflict of interest. A COI exists whenever you edit about yourself, family, friends, clients, or employers; paid editing is the case where money or compensation is involved. Both require honesty, but paid editing carries the stricter, legally-binding disclosure obligation under the Terms of Use.

What happens if you don't disclose paid editing? You face account blocks or permanent bans, and the article you worked on can be tagged, sent to deletion, and removed — including its full history. Beyond Wikipedia, undisclosed campaigns are frequently exposed in the press, turning a reputation project into a reputation crisis. The downside is wildly disproportionate to the few sentences disclosure would have cost.

How should a Wikipedia agency disclose on behalf of a client? A compliant agency creates named accounts, states on each editor's user page that the work is paid and identifies the client and affiliation, repeats the client disclosure on the article's talk page, and submits new pages through Articles for Creation rather than publishing directly. It also discloses its editing accounts in its public marketing. You can read more in Who Edits My Wikipedia Page? and our COI policy explainer.

Since when has Wikipedia required paid-editing disclosure? The Wikimedia Foundation amended its Terms of Use to require paid-contribution disclosure in 2014, and the English-Wikipedia WP:PAID policy implements it. The obligation has only been reinforced since, and detection has become more sophisticated. Treat it as a settled, enforced rule, not an emerging one.

Lead magnet: COI-Safe Edit Request Template

If your company's article contains an error and you have a conflict of interest, the correct move is a neutral, properly-formatted talk-page edit request — never a direct edit. We have packaged the exact format we use, so you can do it yourself, for free, without contacting us.

Get the COI-Safe Edit Request Template — a copy-paste talk-page request that includes the disclosure line, the {{request edit}} structure, the change-X-to-Y format reviewers expect, and a worked example with a reliable-source citation. Built directly from WP:COI and WP:PAID requirements.

Form fields:

• Name (text, required)
• Work email (email, required)
• Company / brand (text, required)
• Your role (dropdown: In-house / PR agency / Legal / Founder / Other)
• Wikipedia article URL (text, optional)
• Consent (checkbox, required): "I agree to receive the template and occasional WikiBusines compliance updates. Unsubscribe anytime."
• Button: Send me the COI-Safe Template

The complete 2026 Wikipedia playbook

This guide is one part of a ten-part series — an honest, end-to-end walkthrough of getting and keeping a Wikipedia page in 2026. Each part stands alone; together they cover the whole journey.

Before you start — Can my company get a page? · Company vs founder vs public figure Budget & vendor — What it costs — 5-year TCO · The honest vendor scorecard Compliance & risk — Paid editing, COI & disclosure (you are here) · Why pages get deleted — 12 patterns Strategy & growth — Wikipedia, Wikidata & AI search · Multilingual strategy After publication — Monitoring & the lifecycle risk curve The data — Wikipedia Risk Report 2026

Not sure where your case stands? A fixed-scope Notability Audit reads your real sources against policy — or just talk to the team.