If your Wikipedia draft was declined at Articles for Creation (AfC), it isn’t the end — a decline is reviewer feedback, not a permanent verdict. AfC is a volunteer-run process where experienced editors check a draft against Wikipedia’s core policies before it goes live, and drafts are usually declined for notability, sourcing, or tone. Read the reviewer’s reason, fix that specific problem, and resubmit. This guide explains how the process actually works and how to respond well.
What Articles for Creation Is
Articles for Creation is the recommended path for anyone who doesn’t have an established editing history or who has a connection to the subject. Instead of publishing a page directly, you build it in the Draft namespace and submit it for review. A volunteer reviewer then decides whether it’s ready to become a live article.
The point of AfC is protective, for both Wikipedia and you. It catches problems — weak sourcing, promotional language, undisclosed conflicts — before a page is public and exposed to speedy deletion. Going through AfC is also the responsible move when you have a conflict of interest, because it puts an independent editor between you and publication.
How the AfC Review Works
The mechanics are straightforward, even if the wait can be long.
- You submit the draft. A template is added marking it as pending review.
- It enters a queue. Reviews are done by volunteers, so waiting times vary widely — from days to many weeks depending on the backlog.
- A reviewer assesses it against core standards: is the subject notable, is every significant claim backed by a reliable independent source, and is the tone neutral?
- The draft is accepted or declined. If accepted, it’s moved to the main encyclopedia. If declined, the reviewer leaves a reason and the draft stays in place for you to improve and resubmit.
A crucial point: reviewers evaluate the draft as submitted. They aren’t obligated to fix it for you, and a “decline” simply means “not yet ready,” not “never.”
Why Drafts Get Declined
Most declines trace to a short list of recurring issues. Recognizing which one applies to you is the whole game.
- Notability not demonstrated. The most common reason. The draft doesn’t show significant coverage in multiple independent, reliable sources.
- Sources aren’t good enough. References lean on press releases, the subject’s own site, interviews, sponsored posts, or passing mentions rather than substantial independent reporting.
- Promotional tone. The writing reads like marketing, with superlatives and unsourced praise.
- Reads like it already exists, or is a copyright issue. Text copied from elsewhere, or content that duplicates an existing article.
- Formatting and verifiability. Missing inline citations, no clear lead paragraph, or claims that don’t match their sources.
These overlap with the broader patterns we cover in why Wikipedia pages get rejected. The single biggest lever, by far, is your sourcing — which is why it pays to understand what counts as reliable sources for Wikipedia before you write.
How to Respond to a Decline
The worst response is to resubmit an unchanged draft — that just earns another decline and can frustrate reviewers. Instead, work the problem methodically.
Read the decline reason carefully. The reviewer’s note points to a specific policy. That’s your instruction list, not a rejection.
Diagnose the real issue. If the reason is notability or sourcing, adding more of the same weak references won’t help. You need genuinely independent, substantial coverage — and if it doesn’t exist yet, no amount of editing will fix that.
Fix that specific problem. Strengthen citations, rewrite promotional passages into neutral prose, add inline references after every meaningful claim, and tighten the structure.
Disclose any conflict of interest. If you’re connected to the subject or being paid, state it plainly on your user page and in edit summaries. Transparency is treated as good faith.
Then resubmit. Once you’ve genuinely addressed the feedback, put it back in the queue. A draft that clearly responds to the reviewer’s concern stands a far better chance. This patient, feedback-driven approach is exactly how Arnab Piush Biswas and the WikiSEO team turn declines into accepted articles.
When the Problem Is Notability
It’s worth being blunt here: if a draft is declined because the subject isn’t notable, that’s not a writing problem you can edit your way around. Notability depends on what independent sources have already published — not on how the article is worded. The honest path is to wait until real, in-depth coverage exists, and then build the draft around it. This applies just as much to organizations; our guide to creating a Wikipedia page for a business walks through how to assess eligibility before you invest time in a draft.
Frequently Asked Questions
How long does an AfC review take?
It varies a lot. Reviews are handled by volunteers, so depending on the backlog a draft may wait anywhere from a few days to several weeks or more. There’s no way to pay for or guarantee a faster review.
Can I resubmit a declined draft?
Yes. Declined drafts stay in the Draft namespace so you can improve and resubmit them. The key is to actually address the reviewer’s reason first — resubmitting an unchanged draft will simply be declined again.
Does going through AfC guarantee my page will be accepted?
No. AfC is a review process run by independent volunteers, and no one can guarantee acceptance. What improves your odds is genuine notability, strong independent sourcing, neutral tone, and full disclosure of any conflict of interest.
Is a decline the same as deletion?
No. A decline happens in review, before the page is public, and is fixable feedback. Deletion removes a page that was already live. Using AfC properly is one of the best ways to avoid ending up in deletion in the first place.
Turn a Decline Into an Approval
A declined draft is a solvable problem when you address the exact issue the reviewer raised and build on genuinely reliable sources. If you’d like an experienced review of your draft and a policy-compliant path to resubmission, contact us and message the WikiSEO team on WhatsApp or Telegram.
