Google's Knowledge Panel — that information box on the right side of search results — is not something you can apply for. There is no form to fill out, no fee to pay, and no Google employee to email. The Knowledge Panel appears when Google's Knowledge Graph has enough entity data from enough trusted sources to be confident that you are a notable entity worth displaying.
The two most accessible sources that feed the Knowledge Graph directly are Crunchbase and Wikidata. Both are free. Both are open to self-service profile creation. And both carry disproportionate weight in Google's entity recognition system.
I created profiles on both platforms for the entities in our 52-site network. Within six weeks, two of those entities triggered Knowledge Panels.
How the Knowledge Graph Works
Google's Knowledge Graph is a database of entities — people, organizations, places, products, concepts — and the relationships between them. It was launched in 2012 and now contains billions of entities sourced from structured data across the web.
When you search for a well-known entity, the Knowledge Panel draws from this graph. It pulls the entity's description, key facts, images, social profiles, and related entities. The data comes from sources Google considers authoritative: Wikipedia, Wikidata, Crunchbase, LinkedIn, official websites with schema markup, and government databases.
The key insight is that the Knowledge Graph is built from convergent signals. Google does not rely on a single source. It looks for the same entity information appearing consistently across multiple trusted platforms. When your name, organization, website, and description match across Crunchbase, Wikidata, your LinkedIn profile, and your website's schema markup, Google gains confidence that you are a real, notable entity.
This convergence is what triggers the Knowledge Panel.
Crunchbase: The Business Entity Signal
Crunchbase is primarily known as a startup and venture capital database, but it accepts profiles for any legitimate business entity. Google has a documented data partnership with Crunchbase — it is one of the explicit sources that feeds the Knowledge Graph.
Creating a Crunchbase profile is free. The basic profile includes:
- Organization name — your company or brand name
- Description — a factual summary of what the entity does
- Website URL — your primary domain
- Founded date — when the entity was established
- Headquarters location — city and state/country
- Categories — industry and sector tags
- Social profiles — links to official social media accounts
- Key people — founders, executives, and team members
The profile does not need to represent a venture-backed startup. It needs to represent a legitimate entity with a verifiable web presence. I created Crunchbase profiles for publishing entities and content brands in our network, not just for incorporated businesses.
Crunchbase Optimization Tips
Use your exact entity name consistently. The name on Crunchbase must match the name on your website, your schema markup, your Wikidata entry, and your social profiles. Inconsistency is the number one reason entities fail to trigger Knowledge Panels.
Write a factual, third-person description. Crunchbase descriptions should read like an encyclopedia entry, not marketing copy. "J.A. Watte is an author and publisher of personal finance and real estate analysis books" works. "The world's most innovative publishing platform" does not.
Add key people with LinkedIn profiles. Google cross-references people entities across Crunchbase and LinkedIn. When the same person appears on both platforms with consistent information, it strengthens both the person entity and the organization entity.
Include your founding date. This seems minor, but it is a structured data point that Google uses for entity disambiguation. If multiple entities share a name, founding date helps Google distinguish between them.
Wikidata: The Open Knowledge Base
Wikidata is the structured data companion to Wikipedia. It is maintained by the Wikimedia Foundation, and unlike Wikipedia, it does not require notability standards for basic entries. Anyone can create a Wikidata item for an entity, provided the entity has at least one verifiable external reference.
This is a critical distinction. Getting a Wikipedia article requires meeting notability guidelines, which most small publishers and authors cannot achieve. Getting a Wikidata entry requires a verifiable external source — a published book on Amazon, a Crunchbase profile, a news mention, or an official website.
Google explicitly uses Wikidata as a Knowledge Graph source. When an entity exists in Wikidata with structured properties and external identifiers, Google can pull that data directly into its graph.
Creating a Wikidata Entry
A Wikidata entry for an author or publisher should include:
- Label — the entity name in English (and other languages if applicable)
- Description — a brief, factual one-line description
- Instance of — the entity type (e.g., "human" for a person, "business enterprise" for a company)
- Occupation — for person entities (e.g., "writer," "publisher")
- Official website — your primary URL
- Country of citizenship or country — geographic identifier
- Notable works — books, publications, or products (each linked to their own Wikidata items if possible)
- Identifiers — ISBN numbers, ORCID, ISNI, Crunchbase ID, Amazon author ID
The identifiers section is where Wikidata becomes powerful. Each external identifier creates a cross-reference that strengthens the entity in Google's graph. An author entity that has a Wikidata entry linked to their Amazon author page, their Crunchbase profile, their ORCID ID, and their official website creates a web of convergent signals that Google can verify.
Wikidata Best Practices
Add references for every statement. Every claim in your Wikidata entry should have a reference — a URL pointing to a source that verifies the claim. "Occupation: writer" should reference your Amazon author page or your publisher's website.
Create entries for your works. Each book should have its own Wikidata item with an ISBN identifier and an "author" property linking back to your person entry. This creates bidirectional entity relationships that strengthen both entries.
Use existing properties. Wikidata has thousands of predefined properties. Use them instead of creating free-text descriptions. "Employer: [Wikidata item]" is more useful to the Knowledge Graph than a description that mentions your employer by name.
The Convergence Strategy
Creating profiles on Crunchbase and Wikidata individually helps. Creating them together with consistent information and linking them to each other creates convergent signals that are significantly more powerful.
Here is the implementation sequence I used:
-
Standardize your entity name. Decide on the exact name format you will use everywhere. "J.A. Watte" is different from "Joshua Watte" to an entity recognition system. Pick one and use it consistently.
-
Create the Crunchbase profile first. It requires less effort and gives you a live URL you can use as a reference in Wikidata.
-
Create the Wikidata entry. Add the Crunchbase ID as an identifier. Add your official website. Add references to published works with ISBNs.
-
Update your website's schema markup. Add
sameAsproperties pointing to your Crunchbase profile, Wikidata entry, LinkedIn, and any other authoritative profiles. This tells Google: all of these profiles represent the same entity.
{
"@context": "https://schema.org",
"@type": "Person",
"name": "J.A. Watte",
"url": "https://jwatte.com",
"sameAs": [
"https://www.crunchbase.com/person/ja-watte",
"https://www.wikidata.org/wiki/Q-XXXXXXX",
"https://www.linkedin.com/in/jawatte",
"https://www.amazon.com/author/jawatte"
]
}
- Wait 4-8 weeks. Knowledge Panel generation is not instant. Google needs to crawl and process all sources, verify convergence, and build confidence in the entity. In our experience, panels appeared 4-6 weeks after all sources were in place.
What Happened With Our Network
Of the entities I created profiles for across Crunchbase and Wikidata, two triggered Knowledge Panels within six weeks. The panels displayed the entity name, description, official website, and social profiles — all pulled from the structured data we had placed across these platforms.
The entities that did not trigger panels were missing one or more convergent signals. In most cases, they lacked published works with ISBNs or had inconsistent name formatting across platforms. After correcting these issues, one additional entity triggered a panel in the following month.
The Knowledge Panel is not the only benefit. Even without a panel, having Crunchbase and Wikidata entries strengthens your entity signals for AI citations. Both ChatGPT and Perplexity reference Crunchbase data when answering questions about companies. Wikidata entries influence how AI models categorize and describe entities.
Time and Cost
Creating a Crunchbase profile: 20 minutes per entity. Free.
Creating a Wikidata entry with proper references and identifiers: 30-45 minutes per entity. Free.
Updating website schema markup with sameAs properties: 15 minutes per site. Free.
Total cost to implement across the entire network: $0 and approximately 6 hours of time.
For the complete entity amplification strategy and 49 other novel marketing tactics, see The $100 Dollar Network.