Wikidata vs Wikipedia for Entity Building: What Qualifies

By Cory Maki · Aug 20, 2026

Most SaaS founders confuse Wikidata and Wikipedia, and the confusion costs them. They assume the two run on the same rulebook, so they either overreach — drafting a Wikipedia article they will never qualify for — or they underreach, ignoring the one platform that would actually accept them. These are two different systems with two different bars. Wikipedia is an encyclopedia that admits a small fraction of the organizations that apply. Wikidata is a structured database that admits most legitimately-documented entities. If you want your brand recognized as an entity in the Knowledge Graph, you need to know which door you are actually eligible to walk through.

This post answers the two questions founders keep getting wrong: Do I actually qualify for Wikipedia? and What will get my Wikidata entry removed? I will not re-explain the broader entity strategy — the schema, the sameAs links, the Knowledge Graph plumbing — because I have covered that in Building Your Entity: Schema and the Knowledge Graph for SaaS and in How to Connect Entities with Schema Markup. This is about qualification thresholds only: the exact lines that decide whether an entry survives editorial review or gets deleted.

Wikipedia's bar is significant coverage in independent sources — and most companies fail it

Wikipedia notability is not a popularity measure. It is a sourcing test. The barometer of notability is whether people independent of the topic have actually considered it worth writing and publishing non-trivial works of their own that focus upon it — without incentive, promotion, or other influence by people connected to the topic. For companies specifically, an organization is presumed notable if it has been the subject of significant coverage in multiple reliable secondary sources that are independent of the subject.

Start with the uncomfortable baseline. Only a small percentage of the world's organizations meet the requirements for a Wikipedia article. And no company or organization is considered inherently notable. Not because you are big, not because you raised money, not because your founder is well-known.

What "significant coverage" actually means

The phrase does a lot of work. Significant coverage addresses the topic directly and in detail, so that no original research is needed to extract the content. It is more than a trivial mention, but it does not need to be the main topic of the source material. The organizations guideline (WP:CORPDEPTH) is stricter than the general one: deep or significant coverage provides an overview, description, commentary, survey, study, discussion, analysis, or evaluation of the company, and provides a level of attention that extends well beyond brief mentions and routine announcements.

And volume does not save a weak case. Quantity does not determine significance. It is the quality of the content that governs. A collection of multiple trivial sources does not become significant. Editors are explicit that vanity metrics are irrelevant: views, hits, likes, and shares have no bearing on establishing whether coverage is significant. Similarly, arbitrary statistics — number of employees, amount of revenue or raised capital, age of the company — do not make the coverage significant.

What does not count toward notability

This is where founders' evidence collapses. Press releases and marketing materials are not valid sources for establishing notability, and paid media placements such as sponsored content are not reliable for building a case. Independence is defined broadly: "independent of the subject" excludes works produced by those linked with the subject, including self-publicity, advertising, self-published material, autobiographies, and press releases. Even a product manual does not help — non-promotional self-published sources like technical manuals are still not evidence of notability, because they are not a measure of the attention a subject has received.

Two more traps. First, your founder's fame is not your company's fame. Some organizations try to establish notability through their founders or executives, assuming notable individuals automatically confer notability. Wikipedia treats individuals and organizations as separate subjects, each requiring independent notability justification. Second, routine business news rarely qualifies. Funding announcements, acquisitions, and IPO filings are contested case-by-case — if they are covered superficially or via PR they are trivial; only when analyzed deeply by outlets with editorial integrity do they contribute to CORPDEPTH.

The practical test: can you point to roughly a dozen substantial, independent, secondary articles that are about your company, not passing mentions? Wikipedia requires a substantial number of sources — think 10 or even 20 — with significant coverage; mere mentions or directory listings won't meet the standard. Look for whole paragraphs or entire articles just about your company. If you cannot, you do not qualify yet, and no writer or agency can change that.

Wikidata's bar is verifiable existence — which most documented SaaS brands can meet

Here is the door most founders can actually use. Because a linked data entry has many elements that are entries in their own right, Wikidata's notability requirements are more flexible. An item qualifies if it meets any one of three criteria. An item is acceptable if it contains at least one valid sitelink to a page on Wikipedia, Wikivoyage, Wikisource, Wikiquote, Wikinews, Wikibooks, Wikidata, Wikispecies, Wikiversity, or Wikimedia Commons. Failing that, it refers to an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references, or it fulfills a structural need — for example, it is needed to make statements in other items more useful.

For a SaaS brand with no Wikipedia article, criterion two is your path. Wikidata's criteria are different from Wikipedia's. Wikipedia requires significant coverage in independent secondary sources — a higher bar that excludes most small and mid-size brands. Wikidata accepts an entity that refers to an external structural source: a database, an authority record, or a registry. In practice that means a presence in Crunchbase, an industry database, a government business registry, an authoritative directory, or any similar structured source can be enough to justify a Wikidata entry. The framing that matters: the bar is "verifiable existence" rather than "fame." A small business that appears in legitimate external sources can qualify; a larger brand whose only presence is its own website may struggle.

The single-website problem

That last clause is the disqualifier. If the only source describing your company is your own domain, you fail criterion two — self-published material is not a "serious and publicly available reference" any more than it is on Wikipedia. The fix is not writing more copy on your own site; it is earning at least one external structural reference (a registry, a reputable database, an authority identifier) before you create the item. On whether one source is enough: experienced editors generally consider one good reference sufficient to pass the source criterion, though best practice is to have multiple independent references.

What gets a Wikidata entry deleted — and how to avoid it

The lower bar to create an item is not a lower bar to keep it. Entries get removed for predictable reasons. Common causes are unreferenced statements, promotional language, undisclosed paid editing, or notability challenges. Handle a challenge the way the community expects: open the talk page for your item, explain the source you relied on, and engage the reverting editor. Do not re-add the same content without discussion — the three-revert rule will get you blocked. If a notability challenge is filed, respond at Wikidata for deletions with your best references.

The disclosure rules are where founders create their own worst problems. Across the entire Wikimedia ecosystem, the Wikimedia Foundation requires that all paid editing be disclosed. On Wikipedia the mechanics are strict: if you make a contribution for which you receive or expect to receive compensation, you must disclose your employer, client, and affiliation — via a statement on your user page, in your edit summary, or on the talk page. Skipping this is not a gray area. Editors who fail to disclose paid contributions are prohibited from editing. And having a financial connection means you should not be editing the article directly at all: those with a conflict of interest, including paid editors, are strongly discouraged from directly editing affected articles, but may post content proposals on talk pages and should put new articles through the Articles for Creation process.

The reputational stakes are real, not theoretical. If a brand is caught engaging in undisclosed paid editing or violating COI guidelines, it can lead to public scrutiny, negative press, and content being flagged or removed. This is the same discipline I preach for Reddit-based GEO: earn your place inside the rules, or watch the platform erase your work — and sometimes your reputation with it.

The realistic sequence for founders

Start honest. Run the Wikipedia test first: do you have roughly a dozen substantial, independent articles about your company? If yes, pursue Wikipedia through Articles for Creation with full disclosure. If no — which is most SaaS brands — do not force it. Build your Wikidata entry on criterion two instead, anchored to a real external identifier, then let that structured record feed your Knowledge Graph presence and the AI systems that read it. Both projects reward patience and punish volume.

Qualification is step one, not the whole strategy. Once your entity exists and its facts are consistent across every source, the work shifts to earning citations. If you want to see where your brand stands today across ChatGPT, Perplexity, Gemini, and Google AI Overviews, that is exactly what a proper AI visibility audit measures — and where the ARC Method begins.