Ayush Goyal

Wikipedia Notability: The Data Report on What It Is, Why Pages Fail It, and What Your Subject Needs to Qualify

Wikipedia Notability: The Data Report on What It Is, Why Pages Fail It, and What Your Subject Needs to Qualify

68% of Wikipedia submissions are rejected. 57% of those fail because of one thing: notability.

68% of Wikipedia submissions are rejected. 57% of those fail because of one thing: notability.

68% of Wikipedia submissions are rejected. 57% of those fail because of one thing: notability. This blog is entirely about notability — what it means, how it is measured, which subjects qualify and which do not, and what the numbers say about your chances.

Table 1: Wikipedia Notability Rejection Data (2025–2026)

These figures come from the Lumino Digital study (2026), the first large-scale empirical audit of Wikipedia's Articles for Creation (AfC) process, covering 1,009 submissions from September and October 2025.

Notability Metric

Figure

Source

Total AfC submissions studied

1,009

Lumino Digital AfC Report, 2025–26

Overall AfC rejection rate

68%

Lumino Digital AfC Report, 2025–26

Share of rejections caused specifically by notability failure

57%

Lumino Digital AfC Report, 2025–26

Second most common rejection reason (after notability)

Promotional tone / NPOV failure

Lumino Digital AfC Report, 2025–26

Notability failure rate for startups and tech companies

94% rejected (only 6% approved)

Lumino Digital AfC Report, 2025–26

Notability failure rate for business executives

88% rejected (only 12% approved)

Lumino Digital AfC Report, 2025–26

Notability failure rate for general business articles

84% rejected (only 16% approved)

Lumino Digital AfC Report, 2025–26

AfC drafts currently pending review (July 16, 2026)

5,179 drafts

Wikipedia:AfC Help Desk, July 16, 2026

Typical wait time for AfC notability review

Up to 3 months or more

Wikipedia:AfC Help Desk, 2026

Source: Lumino Digital Wikipedia AfC Approval Rates Report (2025–26) | Wikipedia:AfC Help Desk (July 16, 2026)

Notability is the single largest cause of Wikipedia rejection. It accounts for more than half of all declined submissions. A well-written draft with strong formatting does not overcome a notability problem. The subject either has sufficient independent press coverage or it does not.

Table 2: Notability-Based Approval Rates by Article Category

Approval rates differ sharply by subject type. The difference is not writing quality. It is whether the category of subject typically generates the kind of independent press coverage that meets the notability standard.

Article Category

Approval Rate

Rejection Rate

Why Notability Succeeds or Fails in This Category

Arts and Culture

48%

52%

Cultural subjects attract organic independent journalism without PR involvement

General Business

16%

84%

Most business submissions cite press releases and company-arranged coverage rather than earned journalism

Business Executives and CEOs

12%

88%

WP:BIO requires coverage of the individual specifically; company coverage does not substitute

Startups and Tech Companies

6%

94%

Submitted before earned media establishes notability; lowest approval of all categories

Source: Lumino Digital Wikipedia AfC Approval Rates Report (2025–26) | Based on 1,009 AfC submissions

Primary cause of the 6% startup approval rate: companies submit Wikipedia pages before they have generated enough earned, independent media coverage to meet WP:N. Writing a better article does not solve a coverage gap.

Table 3: The Three Tests Inside Wikipedia's General Notability Guideline (WP:N)

Wikipedia's General Notability Guideline (WP:GNG) requires that a subject passes three distinct tests simultaneously. Passing two and failing one is not sufficient.

Notability Test

What It Requires

What Passes

What Fails

Test 1 — Significant coverage

The source devotes meaningful space to the subject itself, not a passing mention

A full profile, a detailed news report, an investigative piece about the subject specifically

One-line mention in a funding roundup; the subject listed alongside 10 other companies

Test 2 — Reliable sources

Sources must have editorial oversight, fact-checking, and accountability for what they publish

National newspapers, established business magazines, peer-reviewed journals, books by credible publishers

Press releases, company blogs, social media posts, content farm websites

Test 3 — Independent of the subject

The journalist covered the subject without direction, briefing, or involvement from the subject

A journalist who found the story independently and wrote without being approached by the company

An interview the company arranged; a profile the CEO was paid to appear in; a guest column the subject wrote

Source: Wikipedia:Notability (WP:N) | Wikipedia:General Notability Guideline (WP:GNG)

Table 4: All Wikipedia Notability Guidelines by Subject Type

Wikipedia applies different notability thresholds depending on the subject's category. These are the specific policy codes and what each one requires.

Subject Type

Policy Code

Notability Requirement

Most Commonly Failed Element

All subjects (baseline)

WP:N / WP:GNG

Significant coverage in reliable, independent sources

Independence of coverage

Companies and organisations

WP:CORP

Coverage beyond routine announcements, directory listings, or product reviews

Depth of coverage — mentions alongside competitors do not qualify

Startups and tech businesses

WP:CORP

Same as WP:CORP; no reduced standard for early-stage companies

Earned media does not yet exist at submission time

Individual biographies

WP:BIO

Recognised beyond a narrow professional circle; independent coverage of the person, not just their company

Person-level press coverage that exists separately from the organisation they lead

Academic and scientific figures

WP:PROF

Published in peer-reviewed journals; widely cited within the academic field

Citation count and recognition beyond a single institution

Books and authors

WP:AUTHOR

Published by a credible mainstream publisher with independent critical coverage of the work

Independent reviews in mainstream press, not just publisher promotional material

Websites and online platforms

WP:WEB

Significant coverage in reliable sources — offline press is weighted most heavily

Digital-only subjects struggle because offline mainstream coverage is rare

Non-profit organisations

WP:ORG

Wide mainstream press coverage beyond local community or sector-specific publications

National coverage rather than local-only press

Biographies of living persons

WP:BLP

All WP:BIO requirements plus strict sourcing for any negative claims about the person

Unsourced negative content triggers BLPPROD deletion independent of notability

Source: Wikipedia:Notability (WP:N) | WP:CORP | WP:BIO | WP:PROF | WP:AUTHOR | WP:WEB | WP:ORG | WP:BLP | Lumino Digital AfC Report (2025–26)

Table 5: Specific Reasons Notability Fails — With Frequency Data

Within the 57% of AfC rejections caused by notability failure, the failure traces to specific patterns. These are the most common causes and how frequently each appears.

Notability Failure Reason

How Frequently Seen

Why This Fails WP:N

What Would Change the Outcome

Subject submitted before sufficient earned media exists

Most common for startups — primary cause of 6% approval rate

No independent coverage exists yet to establish significance under WP:N

Wait until 3 to 5 substantial independent articles are published before submitting

Only press release pickups counted as notability evidence

Most common error in all business submissions

40 sites reprinting one announcement equals one source; independence test fails

Original independent journalism where a journalist wrote about the subject without being approached

Coverage exists but is not significant enough in depth

Common

Single-sentence mentions do not pass the significant coverage test

Profile-level or depth journalism about the subject in at least one credible publication

Sources pass reliability but fail independence

Common for PR-driven companies

An interview the company arranged still lacks full editorial independence under WP:N

Coverage where the journalist initiated contact, not the company's PR team

Coverage only in trade or niche publications

Common for B2B businesses

WP:CORP expects mainstream press; trade-only coverage is insufficient alone

At least one national business newspaper alongside trade coverage

Executive has no coverage separate from their company

Near-universal for exec and founder bios

WP:BIO requires the person to be covered as an individual, not just as part of company news

Profile of the person specifically in mainstream press, not just company PR coverage

Social media following or subscriber count cited as significance

Growing problem

Wikipedia does not recognise social metrics as evidence of notability under any guideline

Press coverage of the subject in editorially independent publications

Award from a non-notable or self-selected organisation

Occasional

Award must come from a notable, independently recognised body to contribute to notability

Awards from organisations that themselves have Wikipedia articles and mainstream press coverage

Source: Wikipedia:Notability (WP:N) | WP:CORP | WP:BIO | Lumino Digital AfC Report (2025–26)

Table 6: Notability Benchmarks — What Wikipedia Reviewers Practically Expect

Wikipedia's policy does not state a minimum source count. But based on WP:N guidelines and documented AfC reviewer practice, these are the practical benchmarks that determine whether a submission is likely to pass.

Notability Benchmark

Minimum to Pass

Strong Notability

Note

Number of independent articles about the subject

3 substantial independent articles

5 or more across different credible publications

Each must independently cover the subject in depth, not just mention it

Type of publication required

At least one national or mainstream business publication

Multiple national publications plus credible regional or trade press

Trade press alone does not meet WP:CORP; mainstream press required

Depth of each article about the subject

Substantial coverage — more than a sentence or list entry

Full profile, interview, or investigative piece

Roundup articles that mention the subject alongside 10 competitors carry little weight

Independence of each article

No company arrangement or direction in the coverage

All coverage journalist-initiated without PR involvement

Even accurate coverage the company arranged is treated as weaker

For individual biographies — person-level coverage

At least 2 articles about the person specifically, not their company

Multiple person-level profiles in mainstream press

Company founding and funding news does not substitute for individual press coverage

Currency of coverage

No strict rule but recent coverage is weighted more heavily

Mix of historical context and recent independent journalism

Very old sources for current claims may be questioned by reviewers

Source: Wikipedia:Notability (WP:GNG) | Wikipedia:CORP | Wikipedia:BIO | Documented AfC reviewer practice

Table 7: Wikipedia Deletion Routes Triggered by Notability Failure

When a subject fails notability, the page can be removed through three different processes depending on how obviously it fails and whether any editor contests the deletion.

Deletion Route

Code

Notability Trigger

Timeline

Can Be Recovered?

AfC Decline — pre-publication

AfC review

Reviewer finds the subject's coverage does not meet WP:N; draft never goes live

During review (up to 3 months wait)

Yes — improve notability evidence and resubmit

Speedy Deletion — No importance claim

CSD A7

Published article makes no claim that the subject is notable; no credible indication of significance

Within hours of publication

Yes — add notability claim; appeal via WP:REFUND

Proposed Deletion

PROD

Page is non-notable but not obviously so; no editor objects within 7 days

7-day window

Yes — any editor can remove the PROD tag

Articles for Deletion

AfD

Notability is disputed; community debates and votes on outcome over 7 days

7-day community discussion

Partially — Deletion Review (DRV) available but rarely overturns community consensus

G13 — Stale draft deletion

CSD G13

Draft with notability problems not improved or resubmitted within 6 months

After 6 months of inactivity

Yes — WP:REFUND/G13 request available

Source: Wikipedia:CSD A7 | Wikipedia:PROD | Wikipedia:AfD | Wikipedia:G13 | Wikipedia:Deletion policy

A page that goes through AfD and is deleted creates a permanent public record. Future submissions on the same subject face a higher bar because reviewers can see the prior deletion discussion. Premature submission is more damaging than waiting.

Summary: What the Notability Data Tells You

57% of Wikipedia rejections are caused by notability failure. Startups face a 94% rejection rate. Business executives face 88%. The cause is consistent: pages are submitted before the subject has generated enough independent earned media coverage to satisfy WP:N.

Notability cannot be fixed in the draft. The coverage must exist in the real world before a Wikipedia submission is made.

The practical notability rule: 3 or more substantial, independent articles in credible mainstream publications where the journalist wrote about the subject on their own initiative — before any draft is started.

 ExpertRight starts every Wikipedia project with a notability eligibility assessment using the same framework Wikipedia reviewers apply. Free check before any project begins. www.expertright.com/wikipedia-page-creation



Ayush Goyal

CEO

ExpertRight pioneers streamlined outsourcing solutions, connecting businesses with top freelance talent while managing all aspects of project execution.

Contact

info@expertright.com

+91 9460068385

39, Pankaj Singhvi Marg, Everest Colony, Vidhayak Nagar, Lalkothi, Jaipur, Rajasthan 302015

Legal

Term & Condition

Privacy Policy

Cookies Policy

Join Our Mailing List

Email

 Expert Right, All Rights are Reserved 2025.

ExpertRight pioneers streamlined outsourcing solutions, connecting businesses with top freelance talent while managing all aspects of project execution.

Contact

info@expertright.com

+91 9460068385

39, Pankaj Singhvi Marg, Everest Colony, Vidhayak Nagar, Lalkothi, Jaipur, Rajasthan 302015

Legal

Term & Condition

Privacy Policy

Cookies Policy

Join Our Mailing List

Email

Expert Right, All Rights are Reserved 2025.

ExpertRight pioneers streamlined outsourcing solutions, connecting businesses with top freelance talent while managing all aspects of project execution.

Contact

info@expertright.com

+91 9460068385

39, Pankaj Singhvi Marg, Everest Colony, Vidhayak Nagar, Lalkothi, Jaipur, Rajasthan 302015

Legal

Term & Condition

Privacy Policy

Cookies Policy

Join Our Mailing List

Email

 Expert Right, All Rights are Reserved 2025.