Legitimate Wikipedia agencies work inside three interlocking rules: disclose paid status under WP:PAID (a mandatory Wikimedia Terms of Use requirement since June 2014), request edits on an article's Talk page rather than editing mainspace directly when a conflict of interest exists (WP:COI), and route new company pages through Articles for Creation (AfC) for independent review before publication. Any agency that skips these steps — or promises a guaranteed outcome no volunteer-run process can promise — is operating outside compliance, regardless of how polished its sales page looks.
TL;DR
- WP:PAID disclosure has been a binding Terms of Use requirement since June 16, 2014 — not optional best practice.
- Compliant agencies use Talk-page "edit request" templates on existing articles instead of editing directly with a conflict of interest.
- New company pages should go through AfC (Articles for Creation), where an independent reviewer approves or declines before the article goes live.
- "100% approval," "guaranteed publication," or "guaranteed AI answers" language is a reliable red flag — no agency controls volunteer consensus.
- As of July 2026, WhiteHatWiki, Wikiconsult, Reputation X, and Five Blocks state disclosed-editing practices explicitly on their sites; Reputn, NetReputation, and Lumino Digital do not; Elite Wiki Publishers is the subject of a documented Wikipedia Signpost fraud investigation.
Disclosure: WikiBusines (our company) appears in this comparison. Competitor assessments are based on public information as of July 2026 — pricing pages, service descriptions, and public reviews. We link to every provider so you can verify.
What does WP:PAID actually require?
WP:PAID is the Wikimedia Foundation's paid-contribution disclosure policy, and since a June 2014 amendment to Wikipedia's Terms of Use, it's mandatory, not optional. Anyone editing Wikipedia for compensation — an employee editing their own company's page, a freelancer, or an agency — must disclose that relationship on their user page, the article's Talk page, or in edit summaries. WP:COI (conflict of interest) treats paid advocacy as inherently biased even when the writing itself is neutral; disclosure doesn't waive the conflict, it makes it visible so volunteer editors can weigh contributions accordingly. Background: wikipedia-coi-policy-explained and wikipedia-paid-editing-coi-disclosure.
How does the Talk-page request process actually work?
For an existing article, a disclosed paid editor should not edit the article directly. The compliant path is:
Step 1 — Disclose on the article's Talk page. State the paid relationship and the specific change proposed, with sources.
Step 2 — Use the {{edit request}} template. This flags the request for an independent volunteer editor to review.
Step 3 — Wait for review. A volunteer evaluates the sourcing and neutrality of the proposed text — this can take days to weeks depending on how active the article's watchers are.
Step 4 — Implementation by an independent editor. If accepted, a volunteer (not the paid editor) makes the edit, preserving the separation between advocacy and mainspace content.
Agencies that skip straight to editing a client's article directly are not following this process, regardless of what their marketing copy claims about "compliance."
What is AfC and why does it matter for new pages?
Articles for Creation (AfC) is the review queue new articles pass through before going live in mainspace, particularly when there's a known COI. A reviewer checks the draft against WP:NCORP (the notability standard for companies and organizations — independent, in-depth, reliable secondary coverage) and WP:GNG (Wikipedia's General Notability Guideline). AfC doesn't guarantee acceptance; a weak source base gets declined, and a page built without this review is more exposed to CSD (speedy deletion) or AfD (Articles for Deletion) later. This is why a credible agency runs a notability audit before writing anything — if sources can't clear WP:NCORP, no prose fixes that. See history-of-paid-editing-wikipedia for how this review layer developed in response to earlier abuse.
Why is "guaranteed publication" always a red flag?
Wikipedia articles are approved or declined by unpaid volunteers with no contractual relationship to any agency and no obligation to accept anything. No vendor can guarantee that outcome. "100% approval rate" or "guaranteed Wikipedia page" claims either overstate a historical average as a promise, or signal the agency isn't actually following the disclosed, reviewed process (which has real rejection points built in). The honest framing is a measured probability based on source quality, plus a defended process if the article is later challenged — not an outcome guarantee. This is a legal question too, covered in is-paying-for-a-wikipedia-page-legal: paying for edits is legal; paying for undisclosed edits or a guaranteed outcome runs into policy violations and, in documented cases, outright fraud.
The 7-point compliance checklist
Before hiring any Wikipedia agency, check for these seven items — most take under ten minutes to verify:
- Public disclosure statement. Does the agency state, on its own site, that it discloses paid status per WP:PAID and the Terms of Use — not just "we follow guidelines" in the abstract?
- Talk-page process. Does it describe edit requests rather than direct mainspace edits when a COI exists?
- Disclosed editor accounts. Are the Wikipedia usernames doing the work identifiable as paid/COI-disclosed on-wiki, not anonymous?
- No outcome guarantees. Absence of "100% approval," "guaranteed publication," or similar language.
- Notability audit before commitment. Does it assess sourcing against WP:NCORP/WP:GNG first, and will it say no if sources are thin?
- Refund terms tied to process, not promises. A defensible policy describes what happens if a page is deleted after publication — vague "money-back guarantee" with no documented terms is a warning sign.
- Verifiable company identity. A real registered business, named founders, a physical address — not a cluster of interchangeable domains with no attributable owner.
Who in the market actually discloses paid editing?
Not every agency states its compliance model in writing, and the gap between marketing language and documented practice is where most of the risk lives. As of July 2026, based on public site content:
| Provider | Discloses paid editing explicitly? | Talk-page/edit-request process stated? | Guarantee language |
|---|---|---|---|
| WhiteHatWiki | Yes — explicit "full disclosure that we are paid consultants," Talk-page disclosure, staff barred from parallel volunteer editing | Yes | None published |
| Wikiconsult | Yes — cites WMF paid-contributions framework directly | Implied via audit-first process | Explicitly states no 100% guarantee is possible |
| Reputation X | Yes — "full compliance with Wikipedia's terms of use, including proper disclosure of paid editing relationships" | Not detailed on-site | No outcome guarantee; guarantees resources invested |
| Five Blocks | Yes — talk-page edit requests described on company blog | Yes | Not published |
| Beutler Ink | General "careful adherence to guidelines" language; no explicit Talk-page disclosure statement located | Not detailed on-site | Not published |
| WikiBusines | Explicit: published Editorial & Disclosure Policy — WP:PAID disclosure, Talk-page COI workflow — plus a full compliance guide | Documented in the published compliance guide | 80% refund if a deleted page can't be restored after 3 attempts in a 90-day window |
| Reputn | Not found; markets "100% approval rate" for Wikipedia creation, which conflicts with the volunteer-review model | Not found | Lifetime guarantee + 90-day refund claimed |
| NetReputation | Not found on-site | Not found | "100% money-back guarantee" claimed; BBB shows 10+ unresolved complaints |
| Lumino Digital | Not found — only general "carefully following guidelines" phrasing | Not found | Money-back guarantee cited only by third-party aggregator, not the company's own site |
| Elite Wiki Publishers | No — documented in a Wikipedia Signpost investigation (2024-01-31 "Disinformation report") as part of a network operating without disclosure | No | "100% money-back guarantee" claimed; independent complaints (Trustpilot, BBB) document refusals |
The Elite Wiki Publishers case is worth naming directly because it shows what non-compliance looks like in practice, not theory. Wikipedia's own Signpost investigation documented a network of related "wiki" brands — including Elite Wiki Writers, Wiki Moderator, and a typosquat domain imitating the Wikimedia Foundation — with a chat log in which a representative told a client: "There won't be any mention that it is a paid article. It will be independent." That's a direct instruction to violate WP:PAID, and Signpost tied the network to a sub-5% successful-publication rate across roughly 100 documented clients. That's the practical cost of choosing "guaranteed" over "disclosed."
How does a compliance-first project actually run?
Step 1 — Notability and source audit. Before any drafting, sources are checked against WP:NCORP/WP:GNG. If the base is thin, the honest answer is to build media coverage first, not to write anyway.
Step 2 — Disclosed drafting. For new articles, work proceeds as an AfC submission written to Wikipedia's neutral-tone standards, with every claim backed by an independent secondary source.
Step 3 — Independent review. The AfC reviewer approves, declines, or requests revisions — outside the agency's control by design.
Step 4 — Post-publication monitoring. A defensible process includes a monitoring window (WikiBusines runs 90 days) during which the agency defends the article if it's nominated at AfD, rather than disappearing after the invoice clears.
FAQ
Is it legal to pay someone to edit Wikipedia?
Yes. Paying for disclosed, policy-compliant edits is explicitly permitted under Wikipedia's Terms of Use, provided the paid relationship is disclosed as WP:PAID requires. Paying for undisclosed edits violates the Terms of Use and, per cases like Elite Wiki Publishers, can shade into outright fraud.
Can an agency guarantee my Wikipedia page gets approved?
No, because approval depends on independent volunteer reviewers applying WP:NCORP and WP:GNG, not the agency. A vendor claiming "100% approval" or "guaranteed publication" is either exaggerating a historical average or not following the disclosed review process.
What happens if my published Wikipedia page gets deleted later?
It depends on the vendor's process and refund terms. WikiBusines includes a 90-day post-publication monitoring window with up to 3 restoration attempts, and an 80% refund if the page can't be restored after that. Ask any agency for its written refund terms before starting — vague "money-back guarantee" claims with no documented process are the pattern behind the NetReputation and Elite Wiki Publishers complaints above.
How much does a compliant Wikipedia page creation service cost in 2026?
2026 public pricing varies widely: Wikiconsult starts around €1,700, WikiBusines starts at €1,930 for an English company page (from €600 for lower-tier languages), and enterprise firms like Reputation X or Beutler Ink either quote custom fees or don't publish pricing at all. Price alone doesn't indicate compliance — check the seven-point list above regardless of budget.
What's the difference between AfC and AfD?
AfC (Articles for Creation) is the pre-publication review queue for new drafts. AfD (Articles for Deletion) is the post-publication process where an existing article's notability is challenged and debated by the community. A compliance-first agency should be prepared to participate in both — building the source base for AfC and defending it at AfD if challenged later.
If you want a compliance-first assessment before you spend anything on a Wikipedia project, WikiBusines reviews source lists free as part of a €490 AI-visibility audit credit-able against any package, and full guarantee terms are published on the guarantees page.