Where does knowledge panel information come from?
Google describes knowledge panels as generated automatically from its Knowledge Graph, a database of entities and the facts that connect them. The information is compiled from many sources across the web, including licensed data. A panel for a company might show its logo, a short description, its founding date, headquarters and official social profiles; a panel for a film might show its cast, release date and reviews.
Because it is automated, the content can be wrong or out of date. Google lets people and organizations that are the subject of a panel verify themselves and suggest changes, and anyone can send feedback through the link shown on the panel. Google decides whether to apply the changes.
How is a knowledge panel different from a business profile?
The two are easy to confuse. The panel shown for a local business, such as a restaurant or a dentist, is usually driven by its Google Business Profile, which the owner manages: address, hours, phone number, reviews and photos. Knowledge panels for broader entities such as people, brands or works come from the Knowledge Graph and are not edited directly by their subject. For local businesses, the data a developer usually needs is the business listing itself, not the panel layout around it.
Can you get knowledge panel data from an API?
BestSERP does not return the knowledge panel today. Its web search response contains organic results, plus videos and Top stories when Google shows them, but the panel is not parsed into a field.
For businesses there is a practical alternative. The /places and /maps endpoints return local listings with title, address, category, rating, ratingCount, hours, latitude, longitude, placeId and cid, which covers much of what a local business panel shows. For entities such as people or brands, you can monitor the organic results for the name instead: which official sites, profiles and news pages rank, and how their titles and snippets describe the entity. Tracking that over time shows how the entity is presented to searchers, even without the panel itself.
Example
For a business, /places returns listing data similar to what its panel shows (one result, shortened).
POST /places
{"q": "example bakery portland", "gl": "us", "hl": "en"}
{
"places": [
{
"title": "Example Bakery",
"address": "123 Example St, Portland, OR",
"category": "Bakery",
"rating": 4.6,
"ratingCount": 312,
"hours": "Open · Closes 6 PM",
"latitude": 45.5231,
"longitude": -122.6765,
"placeId": "ChIJexampleBakery01",
"cid": "1234567890123456789"
}
]
}