How a Financial Brand Gets a Google Knowledge Panel (and Why AI Reads It)

By Yamm Labs · Updated October 2026 · 13 min read

The marketing head types the company’s name into Google before a board meeting. On the right sits a box with a retired logo, the parent group’s founding year and a description lifted from an old press note. She asks an AI assistant who the company is and gets the same wrong year back. Nobody on her team wrote either answer, and nobody knows who may change them. That box is a Google knowledge panel, and fixing it is a project with owners, approvals and a paper trail.

What you need before you start on a Google knowledge panel

You need a named owner, a compliance reviewer and a short list of facts that legal has confirmed. Without those three, every later step stalls on one question: who said this is true?

A knowledge panel is the information box Google shows for a person, place, organisation or thing held in its Knowledge Graph, which is Google’s database of entities and the facts that connect them. Google’s help pages say panels are automatically generated and update as information on the web changes. An entity, in this sense, is anything Google can tell apart from everything else that shares its name.

• An entity owner. One person in marketing or digital who answers for the brand’s record across Google, Wikidata and every official profile.
• A reviewer. Someone in compliance or the company secretary’s office, with a turnaround written into the plan.
• The registered name. Exactly as it appears on the Ministry of Corporate Affairs record and on your regulator’s register, plus the trade name you use in advertising.
• The core facts. Founding date, registered office, headquarters city, corporate identity number, and any regulator registration you are content to state in public.
• The group structure. The parent or holding company, with the relationship worded the way your annual report words it.
• A logo file. Square, and at least 112 by 112 pixels, which is the minimum Google’s Organization markup guidance gives.
• A profile list. Website, YouTube, LinkedIn, X, Facebook, Instagram and app store listings, each with the login holder named.
• Search Console access. Owner access for your main domain, since Search Console is one of the accounts Google accepts when you claim a panel.

Put all of this on one page and have the marketing head and the compliance head sign it. We call it the entity fact sheet. Every later step copies from it, and nobody gets to improvise a founding year in a press release again.

Google decides whether you get a panel. You decide whether the facts it finds agree.

Phase 1: your facts have to agree everywhere before Google trusts them

The Knowledge Graph needs to see the same facts about you from more than one source. If your website says 2009, your LinkedIn page says 2011 and a news story says 2007, you have described three companies, or none. Phase one removes the disagreement at the source, before any markup is written.

1. Pick one canonical name for the entity and record the registered name as a separate field. Most Indian financial brands trade under a shorter name than the one on their certificate of incorporation.
2. Write a one-line description of what the company is, who licenses it and where it is based. Keep products, rates, returns and rankings out of it, because compliance will read it as an advertisement.
3. Fix the founding date. For a company that changed form, decide whether the date means incorporation, licence or launch, and write down which in the fact sheet.
4. Correct the same facts on every profile you control, in the same words, within the same fortnight.
5. List the third-party pages that carry wrong facts, such as old directory entries and stale partner pages, and request corrections in writing.

The naming decision is where regulation shows up first. IRDAI’s 2024 policyholder-protection regulations require an insurer’s advertisements to show its registered name with its trade name or logo displayed prominently. An insurer’s ads already pair the two names, so mirror that pairing in the entity record. The trade name becomes the name Google displays, the registered name goes into the legalName field of your markup, and the about page states both in one sentence. An engine then meets the same pairing on your ads, your site and the regulator’s list of insurers.

The description decision matters even more for lenders and fund houses. RBI’s rules on the Key Facts Statement require lenders to give a borrower the statement, including the annual percentage rate, before the loan contract is executed. A rate in a panel description would go stale the week you reprice and would sit far from its disclosures. Keep regulated numbers on the product page, with an “as of” date and the disclosure beside them. The same logic keeps a fund house’s returns out of the description, since SEBI’s mutual fund advertisement rules attach the standard risk warning to promotional material.

SIGNALNewsletter by Yamm Labs

The next piece, straight to your inbox.

New writing on BFSI brands, B2B and influencer marketing, and AI search.

Email *

Subscribe

Subscription form is not available at the moment

One click to unsubscribe. Privacy policy

Phase 2: one about page with Organization structured data becomes the anchor

Your website is the one source you fully control, so it has to state the entity facts most plainly. Google’s guidance on Organization structured data says to put the markup on your home page or on a single page that describes the organisation, and that it does not need to be on every page.

1. Choose the about page as the entity home. Make sure the visible text states every fact in the fact sheet in plain sentences a reader can check.
2. Add Organization markup with name, alternateName, legalName, url, logo, description, foundingDate and address, all copied from the fact sheet.
3. Add sameAs links to the official profiles on your list and, once it exists, to the Wikidata item.
4. Add identifiers that Google’s documentation supports where you hold them, such as an LEI code or a tax ID, if compliance is content to publish them.
5. Run the page through Google’s Rich Results Test or the Schema Markup Validator and clear every error before release.
6. Link the about page from the footer of every page so crawlers reach it often.

One decision we make on every BFSI entity home: the regulator’s register is cited in the visible text, with a link, and kept out of sameAs. A sameAs link says “this other page is also us”. A register entry is a third party vouching for you, which is a different statement. Treating it as a citation keeps the markup’s meaning clean and gives a reader, or an engine, the evidence in one click.

Expect no instant result. Google’s documentation says it does not guarantee that features using structured data will appear in search results. The markup tells Google how to read your page. It does not oblige Google to believe it.

Phase 3: Wikidata and independent sources do the corroborating

In our experience, a panel follows corroboration: independent sources repeating the facts your own site states. Wikidata, the free structured database hosted by the Wikimedia Foundation, is the most direct way to give your entity a public record that other systems can reuse.

1. Check whether a Wikidata item already exists for the company, including under an old name or folded into the parent group’s item.
2. If none exists, confirm the company meets Wikidata’s notability policy. One route it allows is a clearly identifiable entity that can be described using serious and publicly available references.
3. Create or correct the item with instance of, official name, inception, headquarters location, official website, parent organisation and logo. Give each statement a reference to a public source.
4. Use regulator registers, stock exchange filings and national business press as references. An item referenced only to the company’s own site is easy for other editors to challenge.
5. Leave Wikipedia to independent editors. Its conflict-of-interest guideline requires paid editors to disclose who pays them and strongly discourages them from editing affected articles directly, so propose any correction on the article’s talk page.
6. Build independent coverage over the same quarter: industry body member lists, conference speaker pages, and interviews in trade and business press that use the same name and founding year.

A Wikipedia article is not a requirement. Many companies hold panels without one, and plenty of Indian financial firms will not clear Wikipedia’s notability bar for years. A well-referenced Wikidata item, a clear about page and consistent coverage are the more dependable route for most of them.

Disclose the relationship when an agency edits Wikidata for you, because the edit history is public. We set up entity records this way in our AI visibility work for BFSI brands, with the client’s own team holding the account.

Phase 4: claiming the panel gives you a voice, not control

Once a panel appears, the subject or an official representative can claim it. Google’s verification page sets out the process.

1. Sign in to a Google account that the company owns, never a personal one.
2. Search Google for the company and find its panel.
3. Select “Claim this knowledge panel”, which usually sits at the bottom of the panel.
4. Review the information Google shows.
5. Sign in to one of the official sites or profiles Google lists, such as YouTube, Search Console, X or Facebook. Google’s page still calls X by its old name, Twitter.
6. If Google cannot find an associated site, give the extra identity details it asks for.

After verification you suggest changes by selecting Feedback below the panel, flagging the fact and adding links that verify the correction. Attach the sources from the fact sheet: the regulator register, the annual report, the about page. Google reviews suggestions and does not apply them on request. Its Knowledge Graph policies say it may decline to act on facts that are reasonably disputed.

Google lets you add people as owners, managers or contributors. Add at least two company staff, and never leave the agency as the only manager. If a former employee or agency holds the panel, Google’s recovery process gives the current manager three business days to respond before the panel becomes claimable again.

Not every panel shows the claim option. Google says some panels cannot be claimed and suggests checking back. Branches are a separate matter: a bank branch or an insurer’s city office belongs in a Google Business Profile, which Google runs as a different product with its own verification.

Phase 5: a Google knowledge panel needs an owner long after it appears

Panels update as the web changes, and that cuts both ways. A merger, a rename, a new chief executive or a logo refresh reaches the panel only when the sources agree again, and until then the old facts win.

1. Recheck the panel, the Wikidata item and the about page markup every quarter and after any corporate event.
2. Update the fact sheet first and get it signed, then roll the change out to the site, profiles and Wikidata in the same week.
3. Keep a log of every suggestion sent to Google, with the date, the fact and the evidence link.
4. Ask the main AI assistants who the company is, and record whether their answers match the fact sheet.
5. When compliance changes a registered name, licence or group structure, treat it as an entity change and run the whole checklist again.

Skipping the quarterly check is how a panel ends up showing a chief executive who left two annual reports ago.

How long it takes and who signs off

Most of the time goes on approvals. The markup takes a day; agreeing which founding year is correct can take a month. The timings below are planning estimates, not published figures, and Google publishes no timeline of its own.

Two people sign off. The marketing head owns the description, the logo and the profile list. Compliance or the company secretary owns the legal name, dates, registration details and group structure. This split stops legal rewriting the description and marketing rewriting the legal name.

Budget is mostly staff time. Google’s help pages describe no way to apply or pay for a Google knowledge panel. The paid parts, if any, are PR effort and agency time for markup and Wikidata.

How to tell your Google knowledge panel work has worked

The work has worked when Google shows one panel for your brand name alone, built from the facts on your signed sheet. Each of the checks below can be done in a browser in a few minutes.

• Brand query. A panel appears for the plain brand name, without a qualifier such as “insurance” or “bank”.
• Registered name. The same panel appears when you search the registered name, which shows Google has joined the two names into one entity.
• Facts. The logo, founding date, headquarters and description match the fact sheet.
• Ownership. The panel is claimed, and at least two company staff hold access.
• Wikidata. The item has stayed stable for a quarter with no deletion request on its talk page.
• AI answers. The assistants you test describe the company with the same name, year and licence.

For the AI check, pick four engines your customers use, such as ChatGPT, Gemini, Perplexity and Copilot. Ask the same three questions each quarter: who is the company, when was it founded, and who regulates it. Score each answer against the fact sheet and keep the log. None of these engines publishes how it resolves entities, so treat a match as a good sign, not proof. Our GEO and AEO FAQ for financial brands covers how we run these checks.

What to do when a step fails

Most failures trace back to too little corroboration or a name that collides with something else. Diagnose before you resubmit anything to Google.

1. No panel after six months: count the independent sources that state your name and founding year. If there are fewer than a handful, the fix is coverage, not more markup.
2. Panel shows the wrong company: your name collides with another firm or a common word. Add disambiguating facts everywhere (city, regulator, parent group), use alternateName for old names, and add a “different from” statement in Wikidata.
3. Wrong logo: check that the logo in your markup is square, crawlable and at least 112 pixels on each side, then claim the panel and suggest the change with a link to the about page.
4. Wikidata item proposed for deletion: add references from regulator registers and national press, and answer on the discussion page with sources.
5. No claim option: check whether someone else already manages the panel, and use Google’s recovery process if they have left the company.
6. Suggestion rejected: send it again only with stronger evidence, ideally a primary source such as the regulator’s register or an exchange filing.

Change one source at a time and wait for Google to pick it up, so you can tell which change mattered.

Why AI answers depend on the same entity facts

An AI assistant answering a question about your company first has to work out which company you mean. Google’s own AI features sit on top of Google Search, where a Knowledge Graph entry either exists for you or does not. Other assistants retrieve web pages at answer time, and none of them publishes the exact steps.

Our working view: the sources that feed a panel are the ones an engine finds when it searches your name, from the about page and Wikidata item to the regulator’s register and press coverage. When they agree, engines repeat them. When they disagree, an engine picks one, blends them or drops the fact.

That is why entity work comes first in a GEO (generative engine optimisation) plan: an engine has to identify the company before it can describe it. A Google knowledge panel is the visible readout of that identification, and the cheapest early test that your facts have landed. Our AI search and GEO service starts with this record for that reason.

A panel will not make an engine recommend you in answers to category questions such as “best term plan for a first-time buyer”. Those answers draw on product pages, comparisons and reviews. A correct entity record makes sure that, when you are named, the facts beside your name are the ones your compliance team signed.

People also ask

Can a company pay Google for a knowledge panel?

No such route exists in Google’s documentation. Google’s help pages say panels are automatically generated and describe no way to apply or pay for one. A vendor promising a guaranteed panel is promising something Google does not offer.

Does a financial brand need a Wikipedia page to get a knowledge panel?

No. Wikipedia helps when independent editors judge a company notable, but many panels exist without an article. A well-referenced Wikidata item, a clear about page and consistent independent coverage are the more dependable route for most Indian banks, insurers and fintechs.

Should a knowledge panel show our interest rates or fund returns?

Keep them out. Rates and returns change, and Indian regulators attach disclosures to them, such as RBI’s Key Facts Statement for loans and SEBI’s risk warning for mutual fund promotion. State them on dated product pages with the disclosure beside them, and keep the entity description to what the company is.

How long does a Google knowledge panel take to appear?

Google publishes no timeline and guarantees no panel. A brand with steady press coverage usually gets there sooner than a young company with little independent coverage, so measure progress by how many sources agree with your fact sheet.