How long does it take to create a Wikipedia page?
The work we control takes 4–5 weeks; the review that follows depends on Wikipedia's volunteers. Planning around one total number hides that split, and the split is what lets you plan honestly.
What fits inside 4–5 weeks: a structured briefing, an audit of independent sources against Wikipedia's notability standard, a go/no-go decision, the draft with every sentence tied to a citation, your review and sign-off, and submission. What does not: the volunteer review that starts after submission, and anything that happens after publication.
If a vendor quotes you one fixed go-live date, they are quoting certainty on a process they do not control. That is the first credibility test in this market.
What are the two clocks in every Wikipedia project?
Every project runs on two clocks: yours, which is deterministic, and Wikipedia's, which is probabilistic.
Your clock covers everything you and your agency control: the briefing, collecting and auditing sources, drafting, internal review, the paid-editing disclosure and the submission. Every day your team sits on the draft adds exactly one day to the launch date. A draft that spends three weeks in legal review makes the project three weeks longer.
Wikipedia's clock covers volunteer review in the Articles for Creation queue (AfC) and, after publication, New Page Patrol. Reviewers are unpaid and work through a backlog in whatever order they choose. There is no priority lane and nobody to call.
The planning rule that follows: commit to dates on your clock, give a range on Wikipedia's. "Draft signed off by April 4" is a commitment. "Reviewed some weeks later, with the outcome not guaranteed" is a forecast.
What happens in weeks 0–5, before Wikipedia sees anything?
Weeks 0–5 run entirely on your clock, and they decide how smoothly the review goes.
Week 0–1: briefing and source audit.
We list every independent, reliable source about the subject and judge it for depth and independence. Press releases and interviews where your CEO supplies the quotes do not count; independent journalism and analysis do.
Week 1–2: go/no-go.
If the independent coverage is too thin to survive review, the honest advice is to stop and build coverage first. A notability audit (from €490, credited toward the page if you proceed within one month) puts that verdict in writing in week 1, which costs far less than finding out from a declined draft months later.
Weeks 2–4: drafting.
Most of the time goes into citation mapping, not prose. A Wikipedia article is short by marketing standards; making every claim verifiable is what takes time.
Weeks 4–5: your review.
Correct facts, do not add adjectives. Every "leading", "innovative" or "award-winning" that creeps into the draft raises decline risk. The longest delay we see is not drafting but a draft parked in internal legal or PR review: book those reviewers in week 0.
In parallel: Wikidata.
A Wikidata item (Wikipedia's open structured-data database) has no review queue, so the structured data layer that feeds knowledge graphs and AI assistants can exist whatever happens to the article.
How long does Wikipedia's review take?
There is no published service level: the AfC queue has held thousands of pending drafts, they are reviewed in no fixed order, and waits range from days to months. The live backlog count is on the AfC WikiProject page; third-party guides to the process commonly describe waits of several weeks to a few months. We treat that as a range, not a promise.
Why a draft goes through AfC at all: experienced editors can publish directly to mainspace, but for disclosed paid editing, Wikipedia's paid-contribution policy and the Wikimedia Foundation Terms of Use require disclosure, and new articles from a paid editor are expected to be reviewed before they go live. We always disclose paid editing on Wikipedia in WikiBusines' name, and we never guarantee that an article will be published.
Timeline at a glance
| Step | Who owns the clock | Typical duration | What "stuck" looks like |
|---|---|---|---|
| Briefing + source audit | You + agency | Week 0–1 | Sources arrive in pieces over weeks |
| Go/no-go decision | Agency | Week 1–2 | Vendor skips the gate and bills for drafting |
| Drafting | Agency | Weeks 2–4 | Rewrite loops chasing promotional wording |
| Client review + sign-off | You | Weeks 4–5 | Draft parked in legal for weeks |
| Wikidata item | Agency (parallel) | Weeks 3–4 | Skipped; structured data never built |
| AfC submission + review | Wikipedia volunteers | A range, outside our control | Silence, which is normal |
| Decline + resubmission (if needed) | Shared | Revision time + a new queue wait | Resubmitting unchanged text |
| New Page Patrol + search indexing | Wikipedia volunteers | Up to 90 days after publication | Maintenance tags and nobody watching |
What shortens the wait, and what only looks like it does?
Three things reduce review friction; none touches the queue itself.
- Source quality. A reviewer who can verify three strong independent sources in minutes approves faster and declines less. It is the biggest lever because it prevents the resubmission loop.
- Clean COI disclosure. A conflict of interest (COI) is a connection between the editor and the subject. Undisclosed, it is exactly what reviewers look for; disclosed correctly, it removes the question.
- Tight scope. Six hundred neutral, well-cited words clear review more easily than two thousand with promotional gloss.
Four "acceleration" offers you may hear are signs of a fake agency:
- "We know reviewers who will approve it." Nobody can sell queue position.
- "We publish straight to mainspace." Done from undisclosed accounts, this is sockpuppetry plus undisclosed paid editing, and the page still faces patrol.
- "Guaranteed live in 7 days." A guarantee on a volunteer process means rules are being broken.
- "Expedited review fee." AfC has no paid lane.
What happens if the draft is declined?
A decline is feedback: the reviewer states a reason, usually notability or sourcing, and the draft stays editable. One resubmission cycle costs revision time plus a fresh wait in the queue, which is why a serious plan allows for one cycle even when it does not expect it.
Two cautions. Resubmitting without substantive change burns reviewer goodwill; most declines are diagnosable beforehand, and the patterns are in why Wikipedia drafts get rejected. And an abandoned draft is not stable: drafts untouched for six months can be deleted under criterion G13.
When does a published page show up in Google?
Not necessarily at once: a new article enters the New Page Patrol queue and stays hidden from external search engines until a patroller reviews it or 90 days pass. The page can be live on Wikipedia and still invisible in Google for weeks.
That window is also when maintenance tags appear and other editors trim or challenge content. This is why our engagements include 90 days of monitoring and a guarantee after publication, and annual support afterwards; continuous monitoring after the first 90 days comes with Managed Protection (€1,500 per year). What monitoring involves is in Wikipedia page maintenance and monitoring.
Download: the first-90-days checklist (PDF).
Which scams target declined drafts?
Cold emails offering to "get your declined page approved" for a fee are a known pattern. In Operation Orangemoody, Wikipedia's large sockpuppet investigation, 381 accounts were blocked after a ring targeted businesses with declined or deleted drafts, charging for publication and then demanding monthly payments to "protect" pages.
Legitimate providers do not cold-email you off a rejection, and nobody on Wikipedia sells protection: only Wikipedia administrators set page protection, and they do not do it for a fee.
What should you ask a vendor about the timeline?
Put these five questions into any agency selection:
- Which weeks run on your process and which on Wikipedia's volunteer review?
- What happens at go/no-go, and will you tell me to stop?
- What is the current AfC wait and what is the estimate based on?
- If the draft is declined, what does a resubmission cost in time and fees?
- What do you monitor in the first 90 days after publication?
How WikiBusines helps
We run your clock and are open about Wikipedia's. For this exact problem:
- Wikipedia page creation from €2,400 for English, 4–5 weeks, with 90 days of monitoring and guarantee after publication and an 80% refund if a published page cannot be defended after 3 attempts within that window.
- Notability audit from €490, credited toward the page if ordered within one month: the week-1 verdict on whether to proceed.
- Annual support, from €720 per year, with a 12-month guarantee. Near real-time monitoring and alerts come with Managed Protection at €1,500 per year.
Before you talk to anyone, the free tools are the media list, the notability index and the DR checker. Start with the free 10-minute assessment: contact us. If the case is unclear, we offer the paid notability audit from €490, credited toward the page if you order it within one month. See also how it works and our guarantees.
Frequently asked questions
Our part (brief, source audit, draft, your sign-off, submission) takes 4–5 weeks. Wikipedia's volunteer review then follows and varies from weeks to months; nobody can fix its date.
No. Articles for Creation is a volunteer queue with no paid or priority lane. What helps is strong independent sources, a clean disclosure and a neutral, tightly scoped draft.
Reviewers are unpaid volunteers working through a backlog of thousands of drafts in no fixed order. See the AfC WikiProject page for the live backlog.
The reviewer gives a reason, usually notability or sourcing, and the draft stays editable. You fix the cause and resubmit; each cycle adds revision time and another queue wait. See why drafts get rejected.
Technically some accounts can, but a conflict of interest and paid editing must be disclosed, and a self-published page is still patrolled and carries a higher risk of challenge. Disclosed drafts go through AfC.
A new article can stay hidden from search engines until it is patrolled or 90 days pass. Indexing can therefore lag publication by weeks.
No. Wikidata has no review queue; our Wikidata setup (from €680) takes 1–2 weeks and runs in parallel with the draft. See Wikidata and the knowledge graph.
No. Publication depends on independent reviewers and the sources that exist. We never guarantee publication or a review date, and an offer that does is a red flag.
Authors and editorial policy
Bohdan DubylovskyiCo-founder and CBO, WikiBusines→
Roman MelnykCo-founder & Chief Editor, WikiBusines→The article was prepared by the WikiBusines co-founders. We sell paid Wikipedia services, so we disclose this interest: paid editing is always declared on Wikipedia in WikiBusines' name, and claims about the rules are backed by links to primary sources.
Editorial policy: payment disclosure, conflicts of interest, sources