How to Get a Google Knowledge Panel for Your Company

You search for your company name in Google. Ten blue links come up. Maybe your website is #1. Maybe your LinkedIn page shows up too. But on the right side of the screen? Nothing. No panel. No structured data. No logo, no description, no "People also search for." Just empty space.

That empty space is where a Knowledge Panel would go. And for most companies, it stays empty for years. Not because Google is ignoring them. But because Google genuinely does not know who they are as an entity.

This essay explains how to change that. Not through Wikipedia (most companies do not qualify). Not through paid services that promise panels in 30 days (those are scams). Through the systematic process of building entity corroboration until Google has no choice but to recognize you.

What a Knowledge Panel actually is

A Knowledge Panel is Google's way of saying: "We have confirmed that this entity exists and we are confident enough in our data to display it publicly." It is not a search result. It is not an ad. It is a factual statement from Google's Knowledge Graph about a verified entity.

The Knowledge Graph is Google's database of entities and their relationships. It contains information about people, companies, places, events, and concepts. When Google has enough data about an entity from enough independent sources, it generates a Knowledge Panel to display that information alongside search results.

For companies, a Knowledge Panel typically shows: company name, logo, description, founding date, headquarters location, key people, website, social profiles, and related entities. Each of these data points comes from Google's entity model, not from your website.

That last part is important. Your website can claim anything. A Knowledge Panel represents what Google has independently verified about you. That is why it matters for trust, for enterprise procurement, and for AI search citations.

Why most companies do not have one

The short answer: Google cannot verify them.

The longer answer involves understanding what "verification" means in this context. Google does not manually review companies. It uses automated systems to build entity models from data it finds across the web. For Google to create a Knowledge Panel for your company, its systems need to find consistent, corroborating information about you from multiple independent authoritative sources.

Jason Barnard, who has done more empirical research on Knowledge Panels than anyone I know of, established a benchmark: roughly 30 corroborating mentions across authoritative sources before Google generates a panel. Not 30 backlinks. Not 30 blog posts mentioning you. 30 independently authoritative sources that agree on who you are, what you do, and where you are located.

Most companies have their own website and maybe a Google Business Profile. That is two sources. They need 28 more.

The Wikipedia trap

The most common advice for getting a Knowledge Panel is "get a Wikipedia page." This advice is technically correct and practically useless for most companies.

Wikipedia has notability requirements. For a company to have a Wikipedia article, it needs significant coverage in reliable, independent sources. Not press releases. Not paid advertorials. Genuine editorial coverage from established publications. Most mid-market B2B companies, even ones doing $50M in revenue, do not meet this threshold.

As I explored in Wikipedia Is Not the Only Path to Entity Verification, there are multiple routes to entity corroboration that do not require Wikipedia. Wikidata, structured data, industry databases, government registries, and institutional references all contribute to the entity model that eventually triggers a Knowledge Panel.

Do not wait for Wikipedia. Build your entity corroboration through every other available channel first. If you eventually qualify for Wikipedia, that accelerates the process. But it is not a prerequisite.

The Knowledge Panel qualification pipeline

Based on Barnard's research and my own observations working on entity infrastructure projects, the process follows a predictable pipeline:

Each phase builds on the previous one. You cannot skip phases. A company that goes straight to press outreach without having proper structured data and a Wikidata entry is wasting effort. The signals need to be machine-readable before they can be machine-verified.

Phase 1: Foundation (Week 1-2)

The foundation is the minimum set of signals your company controls directly. Every subsequent phase depends on getting these right first.

Organization schema on your website. This is the machine-readable declaration of who you are. It should include your legal name, description, founding date, location, logo, and sameAs links to all your verified profiles. Without this, Google has to guess what your website represents. With it, you are giving Google a structured starting point.

Google Business Profile (GBP). If you have a physical location, a verified GBP is one of the strongest signals available to you. Google trusts its own data. Verify it with a real address, add photos, get the category right, and keep it updated. If you are a service-area business without a storefront, you can still create a GBP with your service area.

Consistent naming. Decide on your canonical company name and use it everywhere. Not "PT Arsindo" on one platform and "Arsindo Integrasi Pompa" on another and "AIP Group" on a third. Google's entity reconciliation system works by matching names across sources. If your names do not match, Google treats them as different entities.

Phase 2: Primary corroboration (Week 2-6)

This is where most companies stall. They have the foundation but never build beyond it. Primary corroboration means getting your entity data into sources that Google trusts more than your website.

Wikidata. Creating a Wikidata item for your company is free and does not require Wikipedia notability. Wikidata is a structured data repository used by Google, Bing, and AI systems. A well-constructed Wikidata entry with properties like "instance of: business," "country: Indonesia," "official website," and "industry" gives Google a machine-readable entity record from a source it considers highly authoritative. See the Wikidata visibility guide for the technical details.

Industry directories. Not random web directories. Industry-specific databases that Google recognizes as authoritative for your sector. For manufacturing: Kompass, ThomasNet, GlobalSpec. For professional services: industry association member directories. For Indonesian companies: the KADIN member directory, relevant ministry registries.

Government registries. Your company registration data with the Ministry of Law and Human Rights (AHU Online), NIB from OSS, any sector-specific licenses. These are among the highest-trust sources for Google because they are government-operated.

Social profiles. LinkedIn company page, Crunchbase, Facebook business page, official social media accounts. Each one that uses your canonical name and links back to your website becomes a corroborating node. The key is consistency: same name, same logo, same description across all platforms.

Phase 3: Extended corroboration (Month 2-6)

Extended corroboration involves sources you do not directly control. This is harder and slower but carries more weight because Google views independent mentions as stronger signals than self-published data.

Press coverage. Genuine editorial mentions in industry publications or news outlets. Not paid advertorials or press releases on wire services. One real article in a recognized publication is worth more than twenty press releases. Aim for coverage that mentions your company name, describes what you do, and links to your website.

Academic and institutional mentions. If your company has worked with universities, government agencies, or research institutions, those relationships are gold for entity corroboration. An acknowledgment in a research paper, a mention in a government report, a listing as a project partner on an institutional website. These carry enormous weight.

Awards and certifications. ISO certifications listed on the certification body's website. Industry awards where your company appears on the award organization's page. These are third-party confirmations that Google's systems can verify.

Product/service reviews. Independent reviews on platforms like Google Reviews, Trustpilot, or industry-specific review sites. Not testimonials on your own website. Third-party reviews on established platforms.

Phase 4: Cross-referencing (Ongoing)

This phase is often overlooked and it is critical. Having 30 sources that mention your company is not enough if those sources do not connect to each other. Google needs to reconcile all these mentions into a single entity model.

sameAs links. Your Organization schema should include sameAs links to every verified profile. Your Wikidata entry should include "official website" and external identifiers. Your LinkedIn page should link to your website. Each connection helps Google's entity reconciliation engine understand that all these mentions refer to the same entity.

Consistent NAP data. Name, Address, Phone. These three data points must be identical across every source. Not "almost the same." Identical. Different formatting of the same address can prevent Google from reconciling mentions.

Reciprocal linking. Where possible, make the connections bidirectional. Your website links to your GBP which links to your website. Your Wikidata entry references your website which includes schema that references Wikidata. These closed loops accelerate entity reconciliation.

Phase 5: Claim and optimize

Once a Knowledge Panel appears, you can claim it through Google's Knowledge Panel verification process. This gives you the ability to suggest changes to the information displayed, though Google ultimately decides what to show.

Claiming is done through Google Search. When you search for your entity and see a Knowledge Panel, there is a "Claim this knowledge panel" link at the bottom. You verify your identity through one of Google's approved methods (typically through an official social profile or website associated with the entity).

After claiming, you can suggest edits to the featured image, description, social profiles, and other attributes. Google reviews each suggestion and applies it if it aligns with their entity data. This is not a guarantee that your suggestions will be accepted. It is an opportunity to correct inaccuracies.

The 30-source benchmark in practice

Thirty sources sounds like a lot. In practice, for a company that has been operating for several years, the sources are often already there. They just are not connected properly.

A company with a solid operational history can often identify 20+ existing sources within a week. The work is not creating them from scratch. It is making them consistent, machine-readable, and cross-referenced.

How long does it take?

Based on Barnard's data and case studies from Kalicube, the typical timeline is 3 to 18 months from initial entity infrastructure work to Knowledge Panel appearance. The variation depends on several factors:

Faster (3-6 months): Companies with existing press coverage, industry awards, government registrations, and active social profiles. The infrastructure exists but is not connected. The work is primarily schema implementation, Wikidata creation, and cross-referencing.

Medium (6-12 months): Companies with basic online presence but limited independent corroboration. Need to build additional verification nodes through directory listings, press outreach, and institutional partnerships.

Slower (12-18 months): Newer companies or companies with very limited digital footprint. Need to build both the verification nodes and the underlying credibility that makes those nodes meaningful.

The Entity Infrastructure course covers each phase with specific checklists and timelines adapted for companies at different stages.

Common mistakes that delay the process

Inconsistent naming. This is the most common killer. Using different versions of your company name across platforms makes entity reconciliation impossible. Pick one canonical name and standardize everything.

Ignoring structured data. Many companies have good online presence but zero structured data. Without Organization schema, Google's automated systems have to extract and guess entity attributes from unstructured text. That is slow and unreliable.

Focusing on quantity over authority. Getting listed in 50 low-quality web directories does not help. Getting listed in 5 authoritative industry databases does. Google weighs sources by their authority. A mention in Kompass is worth more than mentions in twenty generic business directories.

No cross-referencing. Building verification nodes without connecting them. Each source that mentions you should ideally link to your website, and your website should link back via sameAs. Without these connections, Google struggles to reconcile the mentions into a single entity.

Expecting instant results. Entity reconciliation is a slow process. Google recrawls sources on its own schedule. New data takes time to be incorporated into the Knowledge Graph. The timeline is months, not days. Patience is not optional.

What about your competitors?

If your competitor has a Knowledge Panel and you do not, that is a signal worth investigating. Look at what they have that you do not. Do they have a Wikidata entry? Press coverage? Industry directory listings? Awards? Use their panel as a checklist for what Google considers sufficient corroboration in your industry.

Do not copy their strategy blindly. But do use it as a diagnostic tool. If every company in your industry that has a Knowledge Panel also has a Kompass listing and a Crunchbase profile, those are probably important signals for your sector.

Knowledge Panels and AI search

This matters beyond Google Search. Knowledge Panel data feeds into Google's AI Overviews. Companies with Knowledge Panels are more likely to be cited in AI-generated answers because they are already verified entities in Google's Knowledge Graph.

The same entity signals that trigger a Knowledge Panel also influence how ChatGPT, Perplexity, and other AI systems evaluate your company. These systems all rely on entity corroboration from similar source types. Building toward a Knowledge Panel is simultaneously building toward AI visibility.

In that sense, a Knowledge Panel is not just a display feature in Google Search. It is evidence that your entity infrastructure is working. It is a visible indicator that the machines can verify who you are.