A knowledge graph is a database of entities and the facts that connect them: a brand, its founders, its products, its locations, and the relationships between them. Google's Knowledge Graph powers the knowledge panel, the information box that appears in search results when Google is confident enough in an entity's identity to show structured facts about it. Getting your brand into a knowledge graph is not a submission. There is no form that guarantees inclusion, no fee that buys a place, and no single edit that creates an entity. It is the result of giving the web enough consistent, corroborated facts about your brand that systems can resolve them to one entity and trust them enough to show.
That distinction matters, because it decides where your effort goes. You do not apply to a knowledge graph. You build the evidence that lets one recognize you, and you keep that evidence consistent across the sources the graph reads.
What a knowledge graph reads
A knowledge graph does not read your site in isolation. It reads the web and looks for agreement. The sources it weighs most heavily are the ones that are independent of you, structured, and hard to fake:
- Your own site, with clear identity markup and consistent facts.
- Wikidata, the open structured knowledge base that stores facts about entities in machine-readable form.
- Wikipedia, where a brand qualifies only under its own notability rules, which are stricter than Wikidata's.
- Independent coverage: press, trade publications, and review sites that write about your brand without being paid to.
- Your verified profiles: social accounts, review profiles, and business listings that you control and keep current.
No one of these creates an entity on its own. Together they form a pattern: the same name, the same web address, the same founders, the same location, appearing in independent places. That pattern is what a knowledge graph recognizes.
Start with the identity on your own site
The cheapest evidence is the evidence you control. Before you touch Wikidata or anything else, make your own site unambiguous:
- Pick one canonical name and one canonical web address, and use them the same way everywhere on your site, including in your markup.
- Add Organization markup to your homepage or About page. Google's Organization structured data docs say adding this markup to your home page can help Google better understand your organization's administrative details and disambiguate your organization in search results. Include the name, web address, logo, and the profiles you control, and keep every value true and current.
- Add your Wikidata item to the sameAs list in that markup once you have one, so the graph can connect your site to the structured record. Do not add a Wikidata link for a different brand, or a profile you do not control. A wrong sameAs link attaches someone else's identity to yours.
- Write an About page that states the facts a graph needs: what the brand is, when it started, where it is based, who runs it, and what it sells. Write it in plain sentences a person can read, not in a list of keywords. The About page is the human-readable version of the same facts your markup states.
If your site contradicts itself, no outside source can fix it. A graph that reads two different names on your own pages will not trust either one.
Wikidata: the structured record you can help build
Wikidata is the most practical structured source for most brands, because its bar is lower than Wikipedia's and its records are built for machines. But it is not a free-for-all. Wikidata's notability policy says an item is acceptable only if it meets at least one of three criteria: it contains at least one valid sitelink to a page on a Wikimedia project, 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 by making statements in other items more useful.
For a brand, the second criterion is the one that usually applies: a real, identifiable business that can be described using serious and publicly available references. That phrase does the work. Your own website alone is not enough. A directory listing alone is not enough. What counts is references that are serious and public: independent coverage, a business registry record, or a profile in a source that checks its facts before publishing.
Before you create an item, gather the references:
- Two or more independent sources that name your brand and state at least one fact about it, such as what it sells, where it is based, or who founded it. A press article, a trade publication piece, or a registry record all count. A press release you wrote, republished word for word, does not count as independent.
- Your official website address, for the official website property.
- The basic facts you can support with a reference: the type of entity, the industry, the location, and the founding date, if a source states it. Do not add a fact you cannot support. An unreferenced claim on Wikidata is a claim another editor can challenge or remove.
When you create the item, add references to the statements you add. A thin item with no references is a thin item, and it will not convince a graph of anything. A well-referenced item with a handful of solid statements is a record a graph can use.
Do not create a duplicate item if one already exists for your brand. Search Wikidata first. If an item exists, improve it with referenced statements instead of starting a second one. Two items for one brand split the evidence, and a split entity is a weak entity.
And do not confuse Wikidata with Wikipedia. A Wikidata item does not guarantee a Wikipedia article, and a Wikipedia article is governed by much stricter notability rules. If your brand does not meet Wikipedia's rules, do not try to force an article. The attempt itself can damage the record, because a deleted article leaves a trace.
Earn the independent coverage
Wikidata references and knowledge panels both depend on sources you do not control. That is the hard part, and it cannot be shortcut. Independent coverage comes from the same work that builds authority everywhere else: original work that is worth writing about.
- Publish the test, the measurement, or the guide that no one else has. A journalist needs a fact. Give them one.
- Answer press and creators with specifics, not with a pitch deck. A founder who can explain why a material failed and what replaced it is quotable. A founder who repeats a tagline is not.
- Keep your facts easy to check. A press page with the founding story, the location, and the leadership, all in one place, makes it easy for a writer to get the facts right, and easy for a graph to confirm them later.
Do not pay for coverage and present it as independent. A paid placement is not a serious public reference, and a graph that reads enough of them will discount the pattern. Do not hire a service that promises to create your knowledge panel. Google's help pages say panels are generated automatically, and no one can create or delete a panel manually. A service that promises to create one is selling something Google does not offer.
Claim the panel if one appears
A knowledge panel appears when Google's systems decide to show one, not when you ask for one. Once it exists, you can claim it and suggest corrections. Google's verification help page lays out the process: create a Google account if you do not have one, search for yourself or the entity you represent and find your knowledge panel, click Claim this knowledge panel at the bottom, review the information, and sign in to one of the official sites or profiles listed, such as YouTube, Search Console, or Facebook. Not all knowledge panels are claimable, and Google advises checking back to see if the claim option appears.
Claiming does not give you an editor. It gives you a channel to suggest changes, and Google reviews those suggestions. The way to change what a panel says is to fix the underlying source: update the Wikidata item with a referenced fact, correct your own site, or earn coverage that states the right fact. Suggesting an edit with a link to a source that proves it is far more effective than suggesting an edit with no source at all.
A local business panel is a different thing from a brand knowledge panel. Google's verification page says that though both look similar, Business Profiles are specific to businesses that serve customers at a particular location or within a designated service area. If you run a local store, claim or create the Business Profile. That is the listing that feeds the local panel.
What not to expect
- No guaranteed inclusion. A Wikidata item, a Wikipedia article, and perfect markup together do not guarantee a knowledge panel. Google's systems decide whether to show one based on relevance to the query, and they do not publish a threshold.
- No timeline. A panel can appear quickly for a well-covered brand, or not at all for a brand with thin independent coverage. Anyone who quotes you a number of weeks is guessing.
- No control over the description. The panel description often comes from Wikidata or Wikipedia, not from your site. If you want it to change, change the source it comes from, with a reference.
- No shortcut through a form. There is no submission form for the Knowledge Graph. The work is the evidence, not the application.
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 this engine reads, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
Say you run a furniture brand
Say you make solid wood tables, and you want your brand to be recognized as an entity, not just a website. You start on your own site: one name, one web address, Organization markup on the homepage with your logo, your profiles, and an About page that states where you are based and who founded the company. Then you check Wikidata and find no item for your brand, so you gather your references: a trade publication article about your workshop, a local business registry record, and a review site profile. You create the item with those references, add the official website property, and add the Wikidata link to your markup. A few months pass, and a knowledge panel appears when someone searches your brand name. You claim it through Google's verification flow and suggest one correction, with a link to your About page as the source. The panel was not bought, and it was not submitted for. It appeared because the same facts, from independent sources, agreed with each other.
What this guide does not cover
This guide covers how a brand becomes an entity a knowledge graph can recognize. It does not cover the Organization markup in full detail, which is our Organization schema guide, or the review markup that carries customer ratings, which is our review schema guide, or the transaction layer that turns a recommendation into a sale. An entity gets you recognized. The rest of the system has to be ready when the shopper arrives.
Check your own brand now
Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your pages today: aizii.ai/aeo-scan
Run the free scanSources
- Google Support, Get verified on Google (specific): https://support.google.com/knowledgepanel/answer/7534902
- Wikidata, Notability policy (specific): https://www.wikidata.org/wiki/Wikidata:Notability
- Google Search Central, Organization structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/organization
- Schema.org, Organization type (general standard): 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.
