You have a launch date in the calendar and a CEO who wants the Wikipedia page live before it. Every vendor you ask gives some version of "it depends — anywhere from days to months." That answer is useless for planning a launch. Here is the honest one: a professionally managed Wikipedia page project takes 6 to 16 weeks from first briefing to a stable published article, and the spread is not random. It splits cleanly into the weeks you control and the weeks nobody does. This article walks the timeline week by week, so you can put real dates in front of your CEO — and know which of those dates you can actually commit to.
Key takeaways
- Realistic end-to-end: 6–16 weeks. The 6-week end assumes strong existing sources, same-week sign-offs, and a fast review. The 16-week end assumes a source gap, a slow internal review, or one decline-and-resubmit cycle.
- Two clocks run in every project. Your Clock (briefing, sources, draft sign-off) — every day of delay adds a day, 1:1. Wikipedia's Clock (volunteer review) — nobody can buy it down, and anyone who claims otherwise is describing a scam.
- The Articles for Creation queue holds roughly 4,300–4,500 pending drafts at any time, reviewed in no fixed order. Plan 3–12 weeks for review alone, and treat the first 90 days after publication as part of the timeline.
The one-sentence answer, unpacked
Six to sixteen weeks. What separates the two ends is worth spelling out, because each end makes assumptions someone has to own.
The 6-week end assumes: the independent press coverage already exists, your team returns the draft with sign-off inside a week, the conflict-of-interest disclosure is clean, and the draft happens to be picked up early from a queue that is reviewed in no particular order. Every one of those is plausible. Stacking all four is luck, not planning.
The 16-week end assumes: the source audit finds gaps that take time to think through, the draft sits in your legal review for three weeks, or the first submission is declined and you go around the resubmission loop once. None of those is a disaster. All of them are common.
Most projects we run land between weeks 8 and 12. If a vendor quotes you a single fixed date — "live by March 15" — they are quoting certainty on a process they do not control. That is the first credibility test in this market, and most pitches fail it.
The Two-Clock Model
The reason "it depends" survives as an answer is that two fundamentally different clocks run inside one project, and most vendors blur them. Separating them is the whole trick to setting expectations.
Your Clock covers everything inside your and your agency's control: the briefing, collecting and auditing sources, drafting, your internal review, the paid-editing disclosure, the submission itself. This clock is deterministic. Every day your team sits on the draft adds exactly one day to the launch date, 1:1. If the draft spends nineteen days in legal, the timeline grows nineteen days. No mystery.
Wikipedia's Clock covers volunteer review — the Articles for Creation queue and, after publication, New Page Patrol. This clock is probabilistic. Reviewers are unpaid volunteers working through a backlog in whatever order they choose. You cannot pay to move up. You cannot call anyone. There is no expedited lane, no priority fee, no contact who "pushes it through." A draft can clear in four days or sit for three months, and both outcomes are normal.
The planning rule that follows: commit to dates on Your Clock; give a range with a confidence level on Wikipedia's Clock. Tell your CEO "draft signed off by April 4" as a commitment, and "published between late April and mid-June, most likely mid-May" as a forecast. A vendor who refuses to split the timeline this way either has not run many projects or intends to compress Wikipedia's Clock by methods that get pages deleted and accounts blocked. More on those below.
Weeks 0–2: briefing, source audit, and the go/no-go decision
The first two weeks run entirely on Your Clock, and they decide more than any other phase.
Week 0–1: briefing and source audit. A structured intake — who the subject is, what the article should cover, what coverage exists — followed by the audit that matters: every independent, reliable source listed, scored for depth, and mapped against Wikipedia's notability standard. Not your press releases. Not interviews where your CEO supplies the quotes. Independent journalism and analysis about you.
Week 1–2: go/no-go. This is the gate. In our intake experience, roughly three in ten projects should end here, because the independent coverage is not yet strong enough to survive review. That is not a polite rejection — it is the cheapest possible outcome. Finding out for the cost of a notability audit in week 1 beats finding out in week 14 with a declined draft, a burned submission history, and a CEO asking what happened. The audit gives you a documented verdict either way: proceed now, or here is the specific coverage gap to close first.
This gate is also why honest success rates exist at all. A 93% approval rate is not a property of clever writing — it is a property of declining the 30% that would have failed.
What "stuck" looks like in this phase: sources trickling in from your side over three weeks. The audit cannot finish without the material, and every day of trickle adds a day, 1:1.
Weeks 2–5: drafting, your review, and Wikidata in parallel
Weeks 2–4: drafting. Industry guides put professional drafting at 2–4 weeks, and that matches our experience. The time goes into citation mapping — every sentence traceable to an independent source — not into prose. A Wikipedia article is short by marketing standards; what takes time is making it bulletproof.
Weeks 4–5: your review. One discipline keeps this phase on schedule: correct facts, do not add adjectives. Every "leading," "innovative," and "award-winning" your team pushes into the draft converts directly into decline risk on Wikipedia's Clock. The longest Your-Clock delay we see in practice is not drafting — it is the draft sitting in internal legal or comms review for three weeks. Book the reviewers' time in week 0, not week 4.
In parallel: Wikidata. A Wikidata item carries no review queue and goes live in days. Building it alongside the draft means your structured data — the layer that feeds Google's Knowledge Graph and AI assistants — exists regardless of how the article review goes.
Weeks 5–14: the review queue nobody can skip
The draft is submitted, and the project moves onto Wikipedia's Clock. Two routes exist. Experienced autoconfirmed editors can publish directly to mainspace, where the article still faces New Page Patrol review after the fact. But for disclosed paid editing — which is what a legitimate agency engagement is — Wikipedia's paid-contribution policy expects new articles to go through Articles for Creation, where a volunteer reviews the draft before it goes live.
The AfC queue typically holds around 4,300–4,500 pending drafts, and drafts are reviewed in no specific order — newer submissions are sometimes reviewed before older ones. Independent guides to the process put typical waits at 3–12 weeks, which matches what the backlog math implies.
Here is the full timeline in one table:
| Milestone | Who owns the clock | Typical duration | What "stuck" looks like |
|---|---|---|---|
| Briefing + source audit | You + agency (Your Clock) | Week 0–1 | Sources arrive in pieces over weeks |
| Go/no-go decision | Agency (Your Clock) | Week 1–2 | Vendor skips the gate and starts billing for drafting |
| Drafting | Agency (Your Clock) | Weeks 2–4 | Endless rewrite cycles chasing promotional wording |
| Client review + sign-off | You (Your Clock) | Weeks 4–5 | Draft parked in legal for three weeks |
| Wikidata item | Agency (parallel track) | Weeks 3–4 | Skipped entirely; structured data never built |
| AfC submission + review | Wikipedia volunteers (Wikipedia's Clock) | Weeks 5–14 | Silence — which is normal; 12+ weeks without review happens |
| Decline + resubmission (if needed) | Shared | +4 to 14 weeks per cycle | Resubmitting unchanged text and burning reviewer goodwill |
| New Page Patrol + search indexing | Wikipedia volunteers | Up to 90 days post-publication | Maintenance tags appear; nobody is watching to respond |
What legitimately shortens the wait — and what gets you banned
Three things genuinely compress the timeline. None of them touches the queue itself; all of them reduce review friction and decline risk.
- Source quality. A reviewer who can verify three strong, independent sources in five minutes approves faster and declines less. Source strength is the single biggest lever on total elapsed time, because it prevents the resubmission loop entirely.
- Clean COI disclosure. Undisclosed conflict of interest is exactly what reviewers dig for. A correct, visible disclosure removes the investigation from the review and signals a draft that plays by the rules.
- Tight scope. Six hundred neutral, well-cited words clear review faster than two thousand words carrying promotional gloss. Every unsourced claim is a reason to decline.
Against those, four "acceleration" offers you will hear in sales calls — each one a scam, a policy violation, or both:
- "We know reviewers who will approve it." No editor can sell queue position. Offering insider approval is the signature move of the extortion schemes covered below.
- "We publish straight to mainspace and skip the queue." Done with undisclosed accounts, this is sockpuppetry plus undisclosed paid editing — the combination behind Wikipedia's largest enforcement actions. The page faces New Page Patrol anyway, now with a deletion-magnet edit history attached.
- "Guaranteed live in 7 days." A guarantee on a volunteer review process is the tell. The only way to hit a 7-day promise reliably is to break the rules and hope nobody checks.
- "Expedited review fee." There is no paid lane at AfC. The fee buys nothing except evidence that the vendor invents process.
A decline is not death — but it costs weeks
A decline at AfC is feedback, not a verdict. The reviewer states a reason — usually notability or sourcing — and the draft remains editable, ready to fix and resubmit. The honest accounting: one resubmission cycle costs 1–2 weeks of revision plus a fresh 3–12 week queue wait. That is the main reason the realistic range ends at 16 weeks rather than 10, and a serious proposal budgets for one cycle even when it expects none.
Two cautions. First, resubmitting without substantive change burns reviewer goodwill and converts a soft decline into a hard rejection. Most declines are diagnosable before submission — the patterns are catalogued in why Wikipedia drafts get rejected. Second, an abandoned draft is not stable: drafts untouched for six months are deleted under criterion G13. A declined draft you park in January can simply be gone by August.
After publication: the first 90 days are still the timeline
"Approved" is not the finish line, and a timeline that ends at publication is incomplete. A new article enters the New Page Patrol queue, and until a patroller reviews it — or 90 days pass — it stays unindexed by external search engines. Practical translation: the page can be live on Wikipedia and still invisible in Google for weeks.
The same window is when maintenance tags appear, when other editors trim or challenge content, and when an unwatched article quietly accumulates problems. This is why the first 90 days belong inside the project, not after it — and why our engagements include 90-day monitoring as standard, with annual support for the years after. What that watching actually involves is covered in our guide to Wikipedia page maintenance and monitoring.
Download: PDFthe first-90-days checklist (PDF) — what to watch, week by week, from approval to the 90-day mark.
The post-rejection danger window
One more timeline fact your CEO should know, because it arrives by email. The weeks immediately after an AfC decline are a known hunting window: scammers monitor declined drafts and cold-contact the subjects, posing as editors or administrators who can get the article approved — for a fee.
This is not hypothetical. In Operation Orangemoody, Wikipedia's largest sockpuppet investigation, 381 accounts were blocked after a coordinated ring targeted exactly this population — businesses with declined or deleted drafts — charging them for publication and then demanding ongoing monthly payments to "protect" the pages from deletion they themselves controlled. Extortion built on a rejection letter.
The defense is simple: legitimate providers do not cold-email you off a declined draft, and nobody on Wikipedia sells protection. If the approach arrives uninvited and references your rejection, you are the target of the oldest scheme in this market.
Five timeline questions to ask any vendor
Put these in your RFP. The answers separate operators from salesmen in one pass.
- Which weeks in your timeline run on your process, and which on Wikipedia's volunteer review? The two-clock split is the competence test. "It's all handled" is a fail.
- What happens at go/no-go — will you tell me to stop, and what does stopping cost? A vendor with no kill gate sells drafting to everyone, including the 30% who should not buy it.
- What is the current AfC wait, and what is that estimate based on? The answer should reference the live backlog, not a brochure.
- If the draft is declined, what does one resubmission cycle cost in weeks and in fees? The honest answer has numbers: 1–2 weeks of revision, 3–12 weeks of queue, and a clear fee policy.
- What exactly do you monitor in the first 90 days after publication? "Nothing, the project ends at approval" means the riskiest window is unstaffed.
If you want those answers about your own project — contact us and you will get a dated, milestone-based timeline in the proposal, with Your-Clock commitments and Wikipedia's-Clock ranges marked as exactly that. Not "it depends."