How to Get a Wikipedia Page: A Complete, Honest Guide
If you have searched for this guide, you are probably one of three people. Someone who believes their organization or work merits a Wikipedia article and wants to know how to create one. Someone who tried, watched it get rejected or deleted, and wants to understand why. Or someone whose job is to manage a public profile, wondering whether Wikipedia should be part of the strategy.
This guide is written for all three. It is longer and more careful than most of what is online, because the honest answer to “how do I get a Wikipedia page” is rarely a five-step checklist. The honest answer is that Wikipedia has spent two decades developing standards that exist precisely to keep most people from getting articles, and the path to one is built on understanding those standards rather than working around them.
The good news: the standards are knowable, the path is repeatable, and organizations that meet the bar can get articles that hold up over time. The bad news: organizations that do not meet the bar will not get an article that lasts, no matter how skilled their consultant, how persistent their submissions, or how clever their strategy. The wall is real, and it is built into the system on purpose.
What follows is the actual process, organized into the eight gates a successful article has to pass through. Each section explains why the gate exists, what policy governs it, what you actually do, and what condition you have to meet before moving on.
Gate 1: Confirm notability before anything else
The reason this gate exists. Wikipedia is an encyclopedia, not a directory. Its model rests on the idea that articles should exist for subjects the world has already taken notice of, not for subjects that hope to use the article to attract notice. The notability gate is what keeps the encyclopedia from becoming a phone book. It is also the gate that filters out roughly 90 percent of submissions made by hopeful subjects.
The guiding policy. Wikipedia’s General Notability Guideline (GNG) says a subject is presumed notable if it has received “significant coverage in reliable sources that are independent of the subject.” Each phrase is doing precise work. Significant means substantial discussion, not a passing mention. Coverage means written treatment of the subject as the focus of the source. Reliable means published by an outlet with editorial oversight and a reputation for accuracy. Independent means produced by people without a financial or organizational tie to the subject. All four conditions have to be met simultaneously, in multiple sources.
What you actually do. Set aside an afternoon and audit the coverage that exists. Open a spreadsheet. List every article, profile, study, book chapter, or major feature where the subject is the primary focus. For each entry, note the publication, date, whether the publication has independent editorial control, and whether the article is genuinely about the subject or merely mentions it in passing. Then count the entries that pass all four GNG tests. Three is a floor. Five to ten is a comfortable case. Ten or more, especially across years and outlets, is a strong case.
The most common mistake is counting sources that feel like they should qualify but do not. Press releases never count, even when republished by news outlets. Sponsored content does not count. Profiles in publications the subject paid to be in do not count. Interviews are mixed: an interview where the journalist did real reporting and contributed independent context can sometimes count; a pure Q&A with softball questions does not. Trade publications that exist to cover an industry positively rarely count. Local news is uneven, depending on whether the outlet has genuine editorial standards or functions mostly as a community bulletin board.
Caution. If you find yourself reaching, you do not have notability. The instinct to count borderline sources is the single biggest predictor of an article that will be deleted. Wikipedia editors are professionally skeptical and have seen every variant of this audit done dishonestly. The bar is either met or it is not.
Closing condition. Before moving on, you should be able to point to at least three to five sources that any neutral reader would agree are independent, substantial, and from outlets with real editorial standards. If you cannot, the answer is not to proceed anyway. The answer is to build the underlying coverage first, which is Gate 1B.
Gate 1B: When you do not yet meet notability
The reason this gate exists. Most subjects who want a Wikipedia article do not yet qualify, and the most useful thing this guide can do is name that honestly. Pursuing an article you do not qualify for is not a difficulty problem. It is an impossibility problem. The right move is to build the foundation that will eventually justify an article, then return to Gate 1 in a year or two.
The guiding principle. Notability is earned, not granted. It accumulates as a byproduct of doing work that journalists, scholars, and researchers want to write about on their own initiative.
What you actually do. Stop thinking about Wikipedia and start thinking about your public record. Build relationships with journalists who cover your industry. Be genuinely useful to them as a source on stories that are not about you. Speak at conferences with editorial selection processes. Publish in venues that have editorial review. If you are a company, do things that are newsworthy beyond your own announcements. If you are a person, do work that other writers find worth analyzing.
Caution. Hiring a PR firm to chase coverage that will satisfy Wikipedia editors is a common move, and it sometimes works, but it carries a real risk. Wikipedia editors can often tell when coverage was generated through a coordinated PR push rather than organic editorial interest. Coverage that reads as PR-generated has been increasingly discounted at notability discussions over the past few years.
Closing condition. Return to Gate 1 only when you can name three to five new pieces of substantial, independent coverage that you did not pay for and did not write.
Gate 2: Confirm an article does not already exist
The reason this gate exists. Wikipedia editors are protective of their work, and recreating an article on a subject that has previously been deleted, merged, or redirected is one of the fastest ways to get a submission rejected without serious review.
The guiding policy. Wikipedia maintains deletion logs and a notability-based deletion review process. Articles deleted as non-notable are flagged in the system, and any new submission on that title gets extra scrutiny.
What you actually do. Search Wikipedia directly for the subject’s exact name and any common variants. Then search the deletion log at Special:Log/delete for the same terms. If a prior article existed and was deleted, read the deletion discussion (usually linked from the log). Understand why it was deleted. If the reason was lack of notability and your situation has not materially changed, you are facing a much higher bar.
Caution. Some article titles are “salted,” meaning Wikipedia administrators have prevented their recreation entirely after repeated low-quality submissions. Salted titles can only be unblocked by an administrator and require a strong showing that circumstances have changed.
Closing condition. You have either confirmed no prior article exists, or you have read the prior deletion discussion and understand specifically what failed. If a previous version was deleted for non-notability and your case has not strengthened substantially, do not proceed without expert guidance.
Gate 3: Disclose any conflict of interest before you write a word
The reason this gate exists. Wikipedia operates on a model of volunteer editing by people without financial stakes in the subjects they write about. When someone with a conflict of interest edits without disclosing it, they are violating Wikipedia’s terms of service. When they get caught, which they almost always do, the consequences extend beyond the single article: the user account gets flagged, the subject’s public record on Wikipedia gets a permanent talk-page discussion of the violation, and the article itself becomes harder to maintain.
The guiding policy. Wikipedia has two relevant rules. The Conflict of Interest guideline (WP:COI) covers anyone with a personal, professional, or financial relationship to the subject. The Paid Editing policy (WP:PAID) covers anyone receiving compensation, directly or indirectly, for editing about the subject. WP:PAID is part of Wikipedia’s Terms of Use, so violating it breaks the legal agreement every editor accepts when creating an account. Both policies require explicit disclosure on the user’s account page and on the talk page of any article they affect.
What you actually do. Before creating a Wikipedia account, decide who will do the editing. If you are the subject, an employee, a contractor, a board member, a publicist, or anyone receiving compensation in connection with the editing, you have a conflict and must disclose it. Create your account using a real name or one that clearly identifies your affiliation. Add a disclosure to your user page using the {{paid}} or {{connected contributor}} templates. State the relationship in plain English. If you are paid, name who is paying you. If you are the subject, say so.
The disclosure cannot be vague. “Has an interest in this topic” is not disclosure. “Is employed by X organization and is editing about X organization” is disclosure.
Caution. Do not create a second, undisclosed account to do the editing while keeping your disclosed account clean. This is called sockpuppetry, and Wikipedia’s Sockpuppet Investigations process catches it routinely through technical and behavioral analysis. The consequences include indefinite blocks of all related accounts and, for paid editors, public naming on Wikipedia’s noticeboards.
Closing condition. You have a Wikipedia account with explicit, unambiguous disclosure of any conflict of interest, posted on your user page before you make any edits to articles related to your subject.
Gate 4: Build the source list before drafting prose
The reason this gate exists. Wikipedia articles are built from sources outward, not from prose inward. Most failed submissions are written first and then padded with whatever citations the writer can find. Successful submissions start with a strong source list and write only what those sources support. Wikipedia’s verifiability standard requires every substantive claim to be traceable to a reliable source. If your prose contains claims your sources do not support, those claims will be deleted.
The guiding policy. Wikipedia’s Verifiability policy (WP:V) and No Original Research policy (WP:NOR) together require that everything in an article must be traceable to a published reliable source, and that the article cannot synthesize or interpret sources to draw conclusions the sources themselves did not draw.
What you actually do. Take the source list from Gate 1 and expand it. Find every substantial, independent piece of writing about your subject. Read all of them carefully. Take detailed notes on what each one says and does not say. Group facts that appear in multiple sources. Note discrepancies. Identify the major themes that emerge organically from the body of coverage.
The goal is a document that lists every important fact about your subject, with a citation to which source supports it. Facts that no independent source mentions cannot go in the article. Facts that only appear in your own materials cannot go in the article.
Caution. Be especially careful about facts you know to be true but that no reliable source has reported. The temptation to include them is strong because you know they are accurate. Wikipedia’s policy is unambiguous: if no independent source has published the fact, it does not belong in the article, regardless of whether you can confirm it is true.
Closing condition. You have a source-by-source notes document covering your subject’s history, work, significance, and any well-documented controversies. The document is long enough to support an article and disciplined enough that every fact is traceable to a specific source.
Gate 5: Draft in encyclopedic prose, not marketing prose
The reason this gate exists. Wikipedia has a specific tone, and learning to write in it is harder than it looks for anyone who has spent professional time writing for any other purpose. Marketing copy tries to make readers feel something. Encyclopedic prose tries to inform readers without making them feel anything in particular. Articles that fail this test get tagged for promotional tone and become harder to defend at every later stage.
The guiding policy. Wikipedia’s Neutral Point of View policy (WP:NPOV) is the most foundational of all its content rules. It requires articles to represent fairly, proportionately, and without bias all the significant viewpoints published in reliable sources on a topic. The Manual of Style (WP:MOS) provides specific guidance on tone, formatting, and structure.
What you actually do. Write in third person, past tense for events, present tense for ongoing facts. Use the subject’s full name in the opening sentence and a shortened form thereafter. Avoid every word that connotes evaluation: leading, innovative, premier, world-class, renowned, acclaimed, pioneering, cutting-edge, passionate, committed. Avoid every phrase that reads as advocacy: “is dedicated to,” “strives to,” “is committed to.” If your draft contains a sentence that could appear unchanged on the subject’s About page, rewrite it.
Include the harder material when independent sources have covered it. Controversies, criticism, regulatory actions, lawsuits, leadership turnover, layoffs. An article that omits significant negative coverage from reliable sources fails NPOV and will be flagged.
Caution. A well-written promotional article reads to its author as fair and accurate. The author has spent months internalizing the subject’s perspective and cannot easily see what an outside reader would notice. Read the draft aloud. Better, have someone with no connection to the subject read it aloud. Watch their face for the moments when the prose tips toward advocacy. Those are the sentences to rewrite.
Closing condition. A draft that an experienced Wikipedia editor would describe as flat and informative rather than glossy or persuasive. If your draft is exciting to read, it is probably wrong.
Gate 6: Submit through Articles for Creation
The reason this gate exists. Articles created directly in Wikipedia’s main space by new editors, especially editors with conflicts of interest, get higher scrutiny and faster deletion than articles submitted through proper channels. The Articles for Creation (AfC) process exists to give new submissions a structured review by experienced editors before they appear in the encyclopedia. Going through AfC signals respect for the process and substantially improves outcomes for COI submissions.
The guiding policy. Wikipedia’s COI guidelines specifically request that editors with conflicts use AfC rather than creating articles directly. AfC reviewers apply notability and sourcing standards before approving the article for main space.
What you actually do. Navigate to Wikipedia’s Article Wizard, which walks new editors through the AfC submission process step by step. Paste in your draft. Confirm your COI disclosure is visible. Submit for review. Then wait. AfC review queues typically run from a few weeks to several months, depending on backlog.
If the submission is declined, read the reviewer’s feedback carefully. Most declines are for one of three reasons: insufficient notability, promotional tone, or insufficient independent sourcing. Each is addressable, but only by going back to the relevant earlier gate and doing the work properly. Resubmitting without addressing the substantive feedback typically results in a faster second decline.
Caution. Do not respond defensively to AfC reviewers. Do not argue about whether the sources are sufficient. The reviewer is applying standards that were settled long before your submission, and arguing tends to harden their position rather than soften it. The productive response to a decline is to fix what the reviewer flagged.
Closing condition. An AfC submission with explicit COI disclosure, a strong source list, and encyclopedic prose. If declined, you have responded by addressing the substantive feedback rather than arguing.
Gate 7: Engage the community after acceptance
The reason this gate exists. Once an article is accepted, the work shifts from creation to maintenance. Articles do not stay good on their own, and articles about organizations are particularly prone to drift, vandalism, and unilateral edits by people who may not understand the subject as well as you do. Engaging the Wikipedia community properly from day one establishes you as a responsible contributor and makes future maintenance easier.
The guiding policy. Wikipedia’s editing model rests on talk pages and edit requests. For COI editors, direct edits should be limited to uncontroversial corrections (factual errors, broken links, clear vandalism reversals). Substantive changes should be proposed on the talk page using the {{request edit}} template and reviewed by uninvolved editors.
What you actually do. Add the article to your watchlist so you see every change. When you spot a factual error, post on the talk page using the request edit template, explain the error, cite the source that supports the correction, and wait for a reviewing editor. When the article needs a substantive update, go through the same process. Be patient. Be specific. Cite sources for every requested change.
Caution. The temptation to edit directly grows over time, especially for small changes that feel obviously correct. Resist this. A pattern of direct COI editing, even of small changes, accumulates into a record that can be used to question your good faith on more important edits later.
Closing condition. An established pattern of using talk pages and edit requests for substantive changes, with a track record of cited proposals that uninvolved editors have implemented.
Gate 8: Maintain the article over time
The reason this gate exists. Wikipedia articles age. Information goes stale. New events happen. Independent coverage continues to accumulate, and a healthy article reflects all of it. Articles that are created and then ignored degrade over time. AI systems drawing from outdated articles produce outdated descriptions. Search results based on a stale article describe an organization that may no longer exist in the form the article describes.
The guiding principle. A good Wikipedia article is a living document. Its quality reflects ongoing attention from people who care about the subject and ongoing oversight from the broader community.
What you actually do. Schedule a quarterly review. Read the article. Note what has changed in the world that the article does not yet reflect. Identify any new independent coverage that has appeared. File request-edit proposals for the updates the article needs. Watch for new tags or flags. Engage promptly when issues are raised on the talk page.
Caution. A Wikipedia article you are not maintaining is a Wikipedia article that is gradually becoming inaccurate. The downstream effect on AI summaries, knowledge panels, and search results is real and measurable. The article you stopped paying attention to two years ago is the version of you that AI systems are still describing today.
Closing condition. A pattern of regular, light-touch engagement that keeps the article current, neutral, and well-sourced over years.
What this looks like done right
An organization that works through these eight gates carefully ends up with something genuinely valuable: a Wikipedia article that is accurate, defensible, durable, and free of the cleanup tags that erode trust across every system that touches Wikipedia. That article does the work of representing the organization across search results, AI summaries, knowledge panels, and the dozens of other surfaces that draw from Wikipedia. It does that work for years, with relatively little maintenance, because it was built correctly the first time.
An organization that skips gates ends up with something quite different: a draft rejected at AfC, an article tagged or deleted shortly after creation, a public record on Wikipedia talk pages of attempted shortcuts, and a downstream reputation problem in AI-mediated search that is harder to fix than it would have been to do correctly the first time.
The wall between the two outcomes is not luck or persuasiveness. It is whether the work was done in the right order, with the right disclosures, on a real foundation of independent sourcing.
Where help helps
The eight gates are knowable, and reading this guide gets you most of the way to understanding them. The harder part is execution, particularly for first-time editors with conflicts of interest who are also under pressure to get the article live quickly.
This is where WikiBlueprint comes in. Our work is the eight-gate process described above, applied with the experience of having walked dozens of organizations through it. We do the notability audit honestly, including telling clients when they do not yet qualify and what they would need to do first. We show you how to handle COI disclosure correctly. We help you build the source foundation, draft the encyclopedic prose, manage the AfC submission, engage the community, and maintain the article on an ongoing basis. We do this within Wikipedia’s rules, with full transparency, because doing it any other way produces articles that do not last.
If your organization meets the notability bar and you want to do this right, we can help. If your organization does not yet meet the bar, we can tell you that honestly and outline what would need to happen first. Either way, the path is clearer than it looks once you know what you are walking toward.
A Wikipedia article is not a marketing asset. It is a public record of who you are, written by people who do not work for you, and increasingly, it is the foundation under nearly every AI system’s account of your organization. Building one well is worth doing carefully.
WikiBlueprint is an ethical Wikipedia consulting firm working with cultural institutions, nonprofits, and companies that take their public record seriously. Schedule a conversation at WikiBlueprint.com.
