How we build your Wikipedia presence
A structured, compliance-aware workflow from eligibility assessment to post-publication monitoring. Eight discrete stages, each with its own deliverable and decision point.
From inquiry to monitoring
Each step is a discrete deliverable with its own scope and decision gate. We never start drafting before source review is closed; we never submit before risk assessment is signed off.
-
01
Initial inquiry
You submit an audit request
We review your brand, markets, current public knowledge footprint and target language editions. We confirm whether the project is worth a full audit or if a Source Readiness review is the better next step.
-
02
Eligibility & source audit
We assess Wikipedia notability
Independent assessment of whether your company or brand meets Wikipedia's notability requirements: significant coverage in independent, reliable, substantial sources. Press releases, paid placements and self-published content do not count.
-
03
Source strategy
We build a structured source pack
Mapping existing coverage, identifying gaps and scoring source quality across each target language edition. Some editions need more local-language sources; some need more substantial English coverage; the strategy is per-edition, not global.
-
04
Risk assessment
We evaluate moderation and discussion risk
Per-edition assessment of editorial sensitivity, deletion-nomination likelihood and active discussion patterns. Risk profile drives which editions go first and which need source readiness work before submission.
-
05
Neutral encyclopedic drafting
English flagship draft, neutral tone
A neutral, verifiable, encyclopedic draft in English following Wikipedia's Manual of Style and Neutral Point of View policy. This is not promotional copy. Every claim is sourced; promotional language is removed; structure follows existing community conventions for the article type.
-
06
Localization
Edition-specific adaptation, not literal translation
For multilingual packages, we adapt the article for each target language edition. Each Wikipedia community has its own editorial norms, source preferences and depth conventions. Localization integrates local-language sources where they exist and adjusts emphasis to what the local edition expects.
-
07
Submission support & community interaction
We support submission and discussion
We support the submission process and respond to community questions, source clarifications and feedback during review. Wikipedia editors review all submissions independently — we do not influence editorial outcomes, but we do represent the article on its merits with disclosed paid-contribution status.
-
08
Post-publication monitoring
Vandalism alerts, deletion-nomination response, expansion
After publication we monitor the article for edits, vandalism, deletion nominations and community discussions. Duration depends on your package and any maintenance plan. Annual maintenance plans extend this into structured ongoing coverage.
How long does the workflow take?
Timelines depend on source readiness, number of editions and editorial complexity. The ranges below are internal workflow timelines — they do not include Wikipedia community review timelines, which are independent and can vary widely.
| Package | Internal workflow | Drives the range |
|---|---|---|
| Core English | 4–8 weeks | Source readiness, single edition |
| Essential 3 | 6–12 weeks | English first, then UK + ES localization |
| Global 7 | 8–16 weeks | Per-edition source strategy across 7 communities |
| Global 10+ | 12–24 weeks | Cross-region rollout, batch preparation, AR/JA/ZH editorial complexity |
Compliance is built into every step
Paid contribution disclosure follows Wikimedia Terms of Use — employer, client and intended beneficiary disclosed before any drafting begins.
Neutral point of view and verifiable sources only. We refuse projects where the available source base cannot support a neutral encyclopedic article.
No promises of publication, retention or specific community outcomes. We deliver review, drafting, support and monitoring — not a guaranteed page.
Ready to start step 01?
An eligibility audit is the first concrete deliverable. We'll review your source base and recommend the safest rollout — or, if you're not ready, the Source Readiness Program.