For most brands, the answer is no, not yet. A Wikipedia page is not a listing you buy, a profile you claim, or a form you submit. It is an article that volunteer editors decide your brand has earned, by the test of significant coverage in reliable, independent, secondary sources. Most brands fail that test, and a page created for a brand that fails it gets deleted, often with a public deletion discussion that an AI system can then quote. The question to ask first is not whether a page would help AI search. It is whether your brand has the independent coverage to survive the community's decision. If it does not, the work is building the coverage, not writing the page.
A page also does not promise what brands assume it promises. Nothing in Wikipedia's own pages promises a knowledge panel, a citation in AI answers, or a boost in any ranking. A page gives AI systems a stable, sourced summary to read, and that summary is only as good as the sources behind it. It is a long, slow, public asset, and it is one you will not control. The rest of this guide is how to tell whether your brand is the exception, and what to do if it is not.
Where it goes wrong
Brands get Wikipedia wrong in a few specific ways, and the mistakes are public, which makes them worse than a quiet failure.
- The brand writes its own page. Wikipedia's conflict of interest guideline tells anyone with a financial connection to a subject to disclose it, to avoid editing the subject's article directly, and to send new articles through Articles for Creation, where volunteer editors review the draft. Employees, founders, agencies, and contractors hired to edit all fall inside that rule. Paid editors must also disclose their employer, their client, and their affiliation, as the Wikimedia Foundation's Terms of Use require. An undisclosed paid edit is a violation, and the community is experienced at spotting it.
- The brand treats press releases and funding news as notability. Wikipedia's notability guideline for organizations and companies requires significant coverage in multiple reliable secondary sources that are independent of the subject. A press release is not independent. Routine announcements, including funding rounds, product launches, hiring news, and expansions, do not count toward notability, however many of them exist. A source must pass the test on its own.
- The brand hires someone who promises a page. No editor can promise a page, because no editor decides alone. A draft goes to a review queue, volunteer editors decide, and a page that survives can still be nominated for deletion later. Anyone selling a guaranteed Wikipedia page is selling something they do not control, and the attempt itself can end with the brand flagged in a public noticeboard discussion.
- The brand expects to control the article. Once an article exists, the brand has no right to control its content or to delete it outside the normal channels, and anyone can add anything the public record supports, including criticism, as long as it is sourced and neutral. A brand that wants a page it can edit is looking for its own website, not Wikipedia.
- The brand counts its own coverage as independent. Your website, your blog, your social posts, and interviews where a founder tells the brand's own story do not count as independent coverage. Independence means the publisher had editorial control and the piece was not generated from your materials. Most of a young brand's press file fails this test, and the test is applied source by source, not to the pile as a whole.
- The brand builds the page before the coverage exists. A page written from thin sources gets deleted, and the deletion discussion becomes an indexed page that AI systems can retrieve and summarize. The brand ends up worse off than before: no article, and a public record that the community found it not notable. The coverage comes first.
- The brand mistakes a page for an AI strategy. A Wikipedia page is one source among many that an AI system may read. It does not replace readable product pages, structured data, reviews, or guides. A brand with a Wikipedia page and an unreadable store will still be unreadable where it matters most: on the pages where shoppers buy.
The steps
Step 1. Score your coverage against the notability test. The marketer gathers every piece of press about the brand and scores each one alone against four tests from Wikipedia's notability guideline for organizations and companies: significant coverage that addresses the brand directly and in depth, completely independent of the brand, reliable, and secondary. A source must pass all four on its own. Strike every press release, every paid placement, every routine announcement, and every piece based on your own materials. If fewer than two sources survive, stop here. The work is earning coverage, not a page.
Step 2. Check that at least one surviving source reaches past your own city. The marketer confirms that at least one qualifying source is regional, national, or international in scope, as the guideline requires. A brand covered only by its local press, however warmly, does not clear the bar. If all your surviving sources are local, the coverage work continues.
Step 3. Decide whether to proceed, and disclose everything. If the coverage clears the test, the marketer decides whether the brand wants a public article it cannot control, with sourced criticism included. If the answer is yes, anyone paid to work on the draft discloses their employer, their client, and their affiliation on their user page and on the draft's talk page, as the Terms of Use require. The account is registered in a person's name, not the company's, and the disclosure comes before any edit, not after.
Step 4. Draft in the review queue, not on the live site. The marketer or the disclosed editor writes a neutral draft, built only from the qualifying sources, and submits it through Articles for Creation. The draft states facts, cites each one, and carries no promotional language, no superlatives, and no claims the sources do not support. Volunteer editors review it, and they may accept it, decline it, or ask for stronger sources. A decline is a decision about the sources, not a negotiation. Strengthen the sources or wait.
Step 5. If a page already exists, request edits, do not make them. The marketer posts edit requests on the article's talk page, states the affiliation plainly, describes the specific change, and cites independent published sources that support it. An uninvolved volunteer editor then evaluates the request and implements it, modifies it, or declines it. Straightforward factual corrections, such as a wrong founding year or a stale address supported by a reliable source, are usually welcomed. Anything touching tone, prominence, or competitive framing must go through the request process without exception.
Step 6. Keep the brand's own house in order. Whether or not a page exists, the marketer keeps the brand's own pages readable: clear product pages, structured data with price and availability, an llms.txt file, and guides that answer buyer questions. These are the sources an AI system reads first, because they are the sources the brand controls and keeps current. A Wikipedia page is a complement to them, never a substitute.
Step 7. If the coverage is not there, build it the slow way. The marketer plans a long stretch of earning independent coverage: real product news that journalists choose to cover, expert commentary that outlets seek out, and work worth writing about. There is no shortcut that survives the notability test, and every shortcut that has been tried, paid placement, press release syndication, and undisclosed editing, is named in the guidelines as a reason to decline or delete.
The machine-readable piece
A Wikipedia page has no file to publish and no markup to add. The machine-readable piece that supports this work lives on your own site: the Organization structured data that ties your brand to its public profiles, including the Wikipedia article if one exists. The sameAs property states that the brand and the article are about the same subject, in a form machines can read. Only add the Wikipedia link when the article exists and is live. Do not add it for a draft, a deleted page, or a page you hope to have. Replace the placeholders with your own brand details, replacing yourdomain.com with your actual domain.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Lantern Board Games",
"url": "https://[yourdomain.com]/",
"description": "Lantern Board Games publishes cooperative board games for families, designed in-house and printed in small runs.",
"sameAs": [
"https://en.wikipedia.org/wiki/[your-brand]",
"https://www.instagram.com/[your-brand]",
"https://www.youtube.com/@[your-brand]"
]
}
</script>
Check the block with the rich results test Google documents, and confirm the page shows the same facts a reader sees: the same name, the same description, the same links. Do not add a Wikipedia link that does not resolve, and do not add a field, a profile, or a value you cannot verify against the live site. A sameAs link to a page that does not exist is a false claim about who you are.
What it looks like when it works
When it works, the shape is quiet. A brand with years of independent coverage has a short, neutral article, written by volunteers, citing the coverage that earned it. The article states what the brand is, when it started, and what it is known for, with each fact sourced. An AI system answering a question about the brand can read the article alongside the brand's own pages, and the two agree. The article is not doing the selling. The store is. The article is doing the confirming.
Say you run a board game publisher with a decade of releases, reviewed by independent games press, covered by national outlets for a game that won a major award, and written about in trade press for a cooperative design the brand pioneered. The marketer scores the coverage: three sources pass all four tests, and one is national. The brand decides it wants the article, knowing it cannot control it. A disclosed editor drafts it from the qualifying sources only, submits it through Articles for Creation, and the volunteers accept it after asking for one stronger source on the award. The article goes live, short and neutral, with a section on the award and a sourced note about a delayed release the brand would rather forget. The brand does not edit it. It posts a factual correction on the talk page when a release count goes stale, with a source, and a volunteer updates it. An assistant asked about the brand quotes the article for the history and the brand's own pages for the current games and prices.
The fundamentals
These mechanics are shared across every engine and covered in full in their own guides:
- •The llms.txt format and a complete sample, see our guide to writing a good llms.txt file
- •The markup AI systems read to verify facts, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
What this guide does not cover
This guide covers whether your brand should have a Wikipedia page and how the community decides. It does not cover Wikidata, which keeps its own notability rules and its own editing process, and it does not cover the full technical audit, or the transaction layer that lets an agent complete a purchase. It is not legal advice, and Wikipedia's own pages are the authority on its rules, so read them in Sources before acting on anything here.
Check your own store now
Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan
Run the free scanSources
- Wikipedia, Notability for organizations and companies (specific): https://en.wikipedia.org/wiki/Wikipedia:Notability_(organizations_and_companies)
- Wikipedia, Conflict of interest (specific): https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest
- Wikipedia, Articles for creation (general docs): https://en.wikipedia.org/wiki/Wikipedia:Articles_for_creation
- Google Search Central, Organization structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/organization
- Schema.org, Organization type (specific): https://schema.org/Organization
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
