There is a question I get asked more than almost any other by ambitious business owners, and it always arrives with a particular gleam of hope in their eyes. "How do we get a Wikipedia page?" They have noticed that the companies Google seems to truly understand — the ones with the elegant panel of information on the right side of the search results, the ones AI assistants describe confidently and correctly — tend to have Wikipedia articles. And so they reason, sensibly enough, that a Wikipedia page is the key that unlocks all of it.
I have to gently disappoint them, and then immediately re-encourage them, because the reality is both worse and far better than they imagine.
The worse part: you probably cannot get a Wikipedia article. Not because you do not deserve one, but because Wikipedia's bar for inclusion is genuinely, deliberately high, and most businesses — even successful, legitimate ones — do not clear it. Chasing a Wikipedia page you cannot earn is one of the most common wastes of energy I see.
The better part: Wikipedia is not actually the thing doing the heavy lifting. Underneath it sits a less famous but more important structure — Wikidata — and Wikidata is far more reachable. Let me explain how this whole machinery works, because once you see it, the path becomes clear.
The layer almost no one talks about
When Google constructs its understanding of who you are — the entity, in the proper jargon — it is not really reading your Wikipedia article as prose. It is drawing on Wikidata, the structured data layer that quietly powers entity recognition across Google, across large language models, across most of the modern web. Wikidata is where the world's facts live in a machine-readable form: this entity is a company, founded in this year, headquartered in this city, in this industry, with these official links.
This is the foundation of the Knowledge Graph, and it is the foundation of how AI systems decide they know who you are. And here is the crucial thing that hope-filled business owners almost never realize: Wikidata has a much lower barrier to entry than Wikipedia. The two are often spoken of in the same breath, as if they were one entity with one impossible standard. They are not. They are different projects with different rules, and the gap between their standards is where your opportunity lives.
What notability actually requires
Let us be precise about the two bars, because the difference is everything.
Wikipedia demands what it calls significant coverage in reliable, independent sources. That means multiple substantial articles about you, written by people with no connection to you, in publications with genuine editorial standards. Press releases do not count. Your own blog does not count. Paid placements do not count. You need the world to have written about you, at length, repeatedly, on its own initiative. Most businesses simply have not crossed that threshold, and no amount of wishing changes it.
Wikidata is a different animal. Its notability guidelines still require external verification — you cannot simply invent an entity from nothing — but the bar is considerably lower. An item is generally acceptable if it can be described using serious, publicly available references, or if it carries a valid link to a page on Wikipedia or a sister project. In practice this means that a real business with a verifiable existence — official registration filings, genuine press coverage however modest, documented public presence — can often have a legitimate Wikidata entry created, where a Wikipedia article would be rejected outright.
So the strategic move is not to batter your head against Wikipedia's wall. It is to establish yourself properly in Wikidata, the layer that actually feeds the Knowledge Graph and the AI systems, and to do it with scrupulous honesty so the entry survives.
A word of caution before you touch anything
I want to say this clearly, because the Wikimedia community is vigilant and unforgiving of self-promotion, and getting this wrong can do lasting damage to your reputation in exactly the places you most want to be trusted.
Wikidata is not a place to advertise. It is a place to state verifiable facts. Every statement you add should carry a proper reference — the platform uses a reference-URL property precisely so that each fact points back to an authoritative source like an official filing, a piece of genuine press coverage, or a formal company announcement. An entry full of unsourced puffery will be noticed, flagged, and likely removed, and the act of having tried will not endear you to anyone. Approach it the way you would approach giving testimony: state only what is true, cite where each fact comes from, and resist every temptation to editorialize. The discipline is the point. Wikidata's value to Google flows precisely from the fact that it is not a self-promotional space, and the moment you treat it as one, you forfeit the benefit.
Closing the loop with sameAs
Establishing the Wikidata entry is half the work. The other half is connecting it back to your own site so that Google can confidently stitch all the references together into a single, coherent entity — you.
This is where structured data earns its keep. On your website, in your Organization schema markup, you use the sameAs property to point at your various authoritative presences: your Wikidata entry, your verified social profiles, your professional listings. What this does, in effect, is hand Google a signed statement that all of these scattered references across the web — the Wikidata item, the LinkedIn page, the official site, the press mentions — are the same entity. You are removing Google's doubt. You are saying, explicitly and in machine-readable form, "these are all me," and backing it with structured data the crawler trusts.
When Google sees your entity linked through sameAs to Wikidata and other trusted sources, its confidence in your authenticity rises, and with that confidence comes a greater likelihood of Knowledge Graph inclusion — and, increasingly, of being recognized and described accurately by the AI assistants that now mediate so much discovery. You are not tricking the system. You are doing the genuine work of making yourself legible to it, connecting the dots that were always there but scattered.
And what about Wikipedia, eventually?
Here is a nuance worth holding onto, because it reframes the whole pursuit. The relationship between the two projects runs in one direction. When a Wikipedia article is published, a Wikidata entry is generated from it more or less automatically. But it does not run the other way — creating a Wikidata entry by hand will not summon a Wikipedia article into being. The two are separate goals, and you should treat them as such.
What this means practically is that Wikidata is not a back door into Wikipedia. It is its own destination, valuable in its own right, and you should pursue it for what it directly gives you: entity legibility in the Knowledge Graph and in AI systems. If, over years, your business earns enough genuine independent coverage that a Wikipedia article becomes defensible, wonderful — pursue it then, ideally with help from someone who understands the community's norms, and let the automatic Wikidata generation follow. But do not hold the more reachable prize hostage to the less reachable one. Build the entity foundation you can build today.
The shift this represents
Step back and notice what has happened to SEO here. For most of its history, the discipline was about ranking pages — getting a particular URL to a particular position for a particular query. Entity optimization is something else. It is about making your organization itself a known, trusted, well-defined thing in the structured understanding of the web. Less "rank this page" and more "be recognized as who you are."
This matters more every month, because AI systems do not retrieve and rank ten blue links the way classic search did. They reason over entities. They want to know what something is, how confident they can be about it, and which facts about it are reliable. A business that exists clearly in Wikidata, that is connected through sameAs to a coherent web of trusted references, is a business the machines can describe with confidence. A business that exists only as an unconnected scatter of pages is one they hesitate over — and hesitation, in AI search, means you do not get mentioned.
The truth, in the end, is almost reassuring in its fairness. You cannot buy your way into the Knowledge Graph, and you cannot fake your way into Wikidata for long. But you can earn your place in both, through verifiable facts honestly stated and properly connected. It is patient work. It is exactly the kind of work that compounds.
If you would like to understand how clearly the machines currently recognize your business as an entity — and where the connections that would strengthen that recognition are missing — that is precisely the analysis Licheo provides. Contact us, and we will map your entity footprint and show you where the gaps are.