Earning a Google Knowledge Panel for a SaaS Brand, Step by Step

A Knowledge Panel is the box Google shows beside or above the results when it is confident a search refers to one specific thing: your company, your founder or your product. It pulls a name, a logo, a short description, a founding date, social profiles and related entities into one card. You cannot buy one, and you cannot submit a form that creates one. Google generates it when its Knowledge Graph holds an entity for you with enough consistent, corroborated facts to display.

By the end of this guide you will have a SaaS brand that Google can identify as a single entity, a structured data layer that tells it which facts are true, a set of outside sources that agree with those facts, and a path to verify and claim the panel once it appears. The same work changes how AI assistants describe you. ChatGPT, Claude, Gemini and Perplexity lean on many of the same reference sources Google uses, so a brand with a clean entity record gets named and described more accurately in AI answers too.

I have run this process on early-stage SaaS brands with almost no press and on growth-stage companies whose entity data was a mess of old names and dead profiles. The steps are the same. The difference is how long each one takes. Plan for weeks to months, depending on how much independent coverage your brand already has, because the slowest part is outside proof that you do not fully control.

What you need:

• Admin access to your website's CMS, so you can edit the About page and add JSON-LD structured data to the site template
• A verified Google Search Console property for your domain
• Control of your official social and directory profiles: LinkedIn company page, X, YouTube, GitHub, Crunchbase and the review sites your buyers use
• A personal Google account you will use to verify and claim the panel, ideally one tied to a company role that will not leave
• A free Wikidata account, created in your own name and not as a brand account
• A Google Cloud project with an API key, if you want to query the Knowledge Graph Search API yourself
• An agreed canonical fact sheet: legal name, brand name, founding date, founders, headquarters city, one-sentence description, logo file and official URL

Step 1: Decide Which Entity Deserves the Panel First

Pick one entity to work on: the company, the founder or the flagship product. Each is a separate node in the Knowledge Graph, and each needs its own sources. Trying to push all three at once spreads thin evidence across three records, and none of them crosses the threshold.

For most B2B SaaS startups, the company is the right first target. Buyers search the brand name during evaluation, procurement teams search it before signing, and AI assistants are asked to compare it against named alternatives. A company panel also gives the founder and product entities something to connect to later through properties such as founder and owns.

There are two cases where the founder comes first. The first is a solo operator or bootstrapped builder whose name is the brand: people search the person, follow the person and quote the person. The second is a founder who already has press coverage, conference talks and a body of published writing, while the company is weeks old. In both cases the person has more independent evidence than the business, and evidence is what the Knowledge Graph runs on.

• Search your brand name in a private window and note whether Google shows any panel, a panel for a different entity with the same name, or nothing
• Search your founder's full name the same way
• List which of the three entities already has independent articles, interviews or listings that name it
• Choose the entity with the most outside evidence, unless the company is the only one buyers search

Check for name collisions before you invest. If your brand shares a name with a better-known company, a town or a common word, Google will resolve the ambiguous query to the stronger entity. You will need a disambiguating description (for example, the brand name plus your category) used consistently everywhere, and you should expect your panel to trigger on that longer query first.

Step 2: Write a Canonical Fact Sheet and Retire Old Variants

Google's systems build an entity by reconciling facts from many sources. When those sources disagree, confidence drops, and a panel either never appears or shows the wrong value. The fix is to decide on one version of every fact before you touch a single profile.

The scale of the reconciliation problem explains why this matters. By May 2020, Google's Knowledge Graph had grown to 500 billion facts on 5 billion entities). That figure is historical context, and the graph has only grown by 2026. A system resolving facts at that volume does not stop to work out that "Acmeflow Inc.", "AcmeFlow" and "Acme Flow Labs" are the same company. It treats disagreement as uncertainty.

• Legal name, exactly as registered, and the brand name you want displayed
• One-sentence description of 20 to 30 words that names your category and your buyer
• Founding year, and the founding date if you can document it
• Founders' full names, as they appear on their own LinkedIn profiles
• Headquarters city and country
• Official URL, including the exact protocol and whether you use www
• Logo file at a square aspect ratio on a plain background
• Former names, with the year each was retired

The former names line is the one teams skip. SaaS companies rebrand often, and the old name still lives on in launch posts, directory listings, investor announcements and podcast show notes. You cannot delete all of it, but you can record the old name as an alternate name in your structured data so Google connects the two instead of treating them as rival entities.

Store the fact sheet somewhere your whole team can see, and make it the source for every bio, boilerplate, press kit and directory listing from now on. In practice, most entity problems I find in audits trace back to a sales deck or a partner page that someone wrote from memory.

Step 3: Turn Your About Page Into the Entity Home

The entity home is the single page on your own site that describes the entity and links out to every other profile about it. For a company, that is the About page. It gives Google a reference point it can trust because you control it, and it gives AI assistants a clean, quotable description to lift.

Most SaaS About pages are written as culture pages: team photos, values and a mission statement. That content can stay, but it should sit below a factual block that reads like a reference entry. Write the first paragraph so it can be quoted on its own, with the brand name as the subject and the category stated plainly.

• Open with the canonical one-sentence description from your fact sheet, word for word
• Add a short facts block: founded, founders, headquarters, category, product names
• Name the founders with links to their own bio pages on your site, which become their entity homes later
• Link to every official profile: LinkedIn, X, YouTube, GitHub, Crunchbase, review site listings and your Wikidata item once it exists
• Show the logo file you chose in Step 2 as an image with descriptive alt text
• Keep the page at a stable URL that you will not move during a redesign

Link to the About page from your site footer and from the logo in your header, and use the same anchor text each time. Internal links tell Google which page your site treats as authoritative about itself. If you are still working out how to get website pages ranking and crawled reliably in the first place, fix that first: a Knowledge Panel cannot form around an entity home Google does not index.

Step 4: Add Organization Schema With sameAs Links

Structured data is the most direct way to state your facts in a format the Knowledge Graph can read. Add an Organization block in JSON-LD to the About page, or to the home page with a matching block on About. The sample below is for a fictional company called Acmeflow and shows the properties that do the work for entity recognition.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.acmeflow.com/#organization",
  "name": "Acmeflow",
  "legalName": "Acmeflow Inc.",
  "alternateName": "Acme Flow Labs",
  "url": "https://www.acmeflow.com/",
  "logo": "https://www.acmeflow.com/assets/acmeflow-logo-square.png",
  "description": "Acmeflow is a workflow automation platform for B2B finance teams that syncs approvals between ERP and banking systems.",
  "foundingDate": "2021",
  "founder": [
    {"@type": "Person", "name": "Dana Reyes", "url": "https://www.acmeflow.com/team/dana-reyes"},
    {"@type": "Person", "name": "Sam Okafor", "url": "https://www.acmeflow.com/team/sam-okafor"}
  ],
  "address": {"@type": "PostalAddress", "addressLocality": "Austin", "addressCountry": "US"},
  "sameAs": [
    "https://www.linkedin.com/company/acmeflow",
    "https://x.com/acmeflow",
    "https://www.youtube.com/@acmeflow",
    "https://github.com/acmeflow",
    "https://www.crunchbase.com/organization/acmeflow",
    "https://www.wikidata.org/wiki/Q000000000"
  ]
}
</script>

What each property in the sample does

The @id line gives the organization a stable identifier on your own domain. Any other schema block on your site (an Article author's employer, a SoftwareApplication's publisher) can point to that same @id, so Google reads one company instead of many unconnected mentions.

The name, legalName and alternateName lines settle the naming question from Step 2. Name is the display name you want on the panel. LegalName is the registered entity. AlternateName holds the retired brand so old coverage still resolves to you.

The description line repeats the canonical sentence exactly. Do not write a different, punchier version for schema. A description that matches your About page, your LinkedIn tagline and your Crunchbase summary is a description Google and language models can treat as settled.

The founder array creates Person entities with URLs to their bio pages. That is the hook a founder panel will later hang from. The address block gives a headquarters location without exposing a street address, which most remote-first SaaS companies prefer.

The sameAs array is the most important part of the block. Each URL says, in effect, that the profile at this address is the same entity as this organization. Only list profiles you control and that describe the company with the fact sheet's details. A sameAs link to a stale Crunchbase page with the old name works against you.

Validate the block with the Rich Results Test and the Schema Markup Validator before you publish, and check the rendered HTML in Search Console's URL Inspection tool. JavaScript-injected schema that Google fails to render is the same as no schema at all.

Step 5: Align Every Profile to the Same Facts

Each profile in your sameAs list is a separate source Google can cross-check. Alignment means every one of them carries the same name, description, logo, founding year, location and website link. This step is tedious and it has no shortcuts. It is also the step that most often separates brands with a panel from brands without one.

The sources do not carry equal weight. Profiles you edit yourself confirm what you claim. Profiles that a third party maintains, or that require verification, carry more weight because you cannot write anything you like. The table below sets out the profiles I prioritize for a B2B SaaS company and why: the editor-controlled sources at the bottom are the ones that move the needle most.

• Open every profile in a spreadsheet, one row per source, one column per fact
• Mark each cell that differs from the fact sheet
• Fix the profiles you control first, starting with LinkedIn and Crunchbase
• Request corrections on directories you do not control, using their claim or update forms
• Ask partners, investors and accelerators to update their portfolio and partner pages
• Remove or redirect any duplicate pages, such as an old LinkedIn page for the pre-rebrand name

Founder profiles need the same treatment. The founder's LinkedIn headline, X bio and conference speaker bios should name the company exactly as the fact sheet does. When a person entity and an organization entity point at each other consistently, each one makes the other easier for Google to resolve.

Step 6: Create a Wikidata Item That Meets Its Rules

Wikidata is the open, structured knowledge base behind Wikipedia, and its facts are reused widely by search engines and by the datasets language models learn from. A Wikidata item gives your entity a public identifier (a Q-number) with machine-readable properties for name, website, founding date, founders and industry.

Wikidata has a notability policy. An item is kept when it fulfils a structural need or when it can be described using serious, publicly available references. A new startup with no outside coverage often fails that test, and an item that gets deleted leaves a history that does you no good. Create the item only after you have at least some independent references to cite.

• Search Wikidata for your brand name first, in case an item already exists and only needs correcting
• Create the item from a personal account and disclose your affiliation on your user page
• Add the label, a short description that matches your category, and aliases for former names
• Add the statements: instance of (business or software company), official website, inception, founded by, headquarters location, industry
• Attach a reference to every statement, using independent sources where possible and your own site only for basic facts
• Add the identifiers for your other profiles, such as the Crunchbase organization ID and the LinkedIn company ID
• Add the Wikidata URL to your sameAs array once the item is stable

Keep the edits factual. Wikidata editors remove promotional language, and an item stuffed with marketing claims draws scrutiny. A short, well-referenced item is worth more than a long one built on your own press releases.

Do not pay anyone who promises a guaranteed Wikidata or Wikipedia entry. Paid editing without disclosure breaks both projects' rules, and entries created that way are often deleted, sometimes with your brand's pages flagged for review afterwards.

Step 7: Earn Independent Coverage That Names You

Independent coverage is the evidence that turns a self-described company into an entity Google trusts. Everything you have done so far is a claim. Articles, interviews, analyst mentions and directory listings written by other people are corroboration. Google needs both, and the second is where most SaaS brands are thin.

Coverage only helps if it names you in a way that maps to your entity. A trade publication that writes "a finance automation startup" without your name gives the Knowledge Graph nothing to attach. A piece that names the company, the founder and the category, and links to your site, gives it three facts and a connection.

• Pitch data your product generates, such as anonymized benchmarks from customer usage, to trade publications in your category
• Put founders forward for podcasts and conference talks where the show notes and agenda pages name the company
• Publish original research on your own site that other writers will cite and link
• Get listed in category directories, partner marketplaces and integration pages for the platforms you connect to
• Contribute bylined pieces to industry outlets, with an author bio that uses the fact sheet description
• Answer journalist requests in your niche where your founder has real expertise

Links matter here, but for a slightly different reason than in a classic link building campaign. Each linked mention is both an authority signal and an entity signal. When you audit what you already have, it helps to find backlinks that mention the brand by name, because those pages are the ones to ask for small corrections (current name, current description) before you chase new coverage.

Where Wikipedia fits

A Wikipedia article is the strongest single input to a Knowledge Panel, but you should treat it as a result of coverage and never as a task to do in this step. According to InstantPress, a Wikipedia page about the entity "is the single highest-leverage signal," and most Knowledge Panels for people, companies and creative works are anchored by a Wikipedia page that Google treats as the canonical source of basic facts.

Wikipedia requires significant coverage in reliable, independent sources, and it discourages people with a conflict of interest from writing about their own company. Most seed and Series A SaaS companies do not meet that bar yet, and that is fine. Panels for smaller brands do form from Wikidata, structured data and consistent profiles alone. When your independent coverage grows to the point where an uninvolved editor could write a neutral article from it, that article tends to follow.

Step 8: Build Branded Demand and Topical Association

Google shows a Knowledge Panel when a query is about an entity. That means people need to search for your brand name, and Google needs to see that the brand is connected to a topic. Both grow from the same source: a body of useful content that people find, remember and come back to by name.

Topical association is the part teams underrate. If your site publishes in depth about finance approval workflows, and outside writers cite those pages when they discuss the subject, Google learns that your entity relates to that topic. AI assistants learn the same thing. When a buyer asks ChatGPT or Claude which tools handle ERP approval syncing, the brands that come up are the ones whose names appear alongside that topic across many independent pages.

• Publish a steady run of articles on the specific problems your product solves, each written so a passage can be quoted on its own
• Mention your brand name in context, not in every sentence, so the association reads naturally
• Link every article's author to a bio page that carries Person schema and points to the organization
• Track branded queries in Search Console and watch impressions for the brand name rise over time
• Watch whether AI assistants describe your company correctly when asked about it directly

Branded queries are easy to overlook inside overall organic traffic reports, so split them out. A rising count of impressions for the brand name, and for the brand name plus your category, is one of the clearest signs that the entity is gaining weight.

This is the slowest step to run manually, because it needs output every week for months. A small team can usually produce the profile work in Steps 2 to 6 in a sprint. Producing enough on-topic content to build association is a different kind of job: research, drafting, internal linking, schema and publishing, repeated for every article. Autonomous content systems change the mechanism. Gofylo's Content Engine researches, writes and publishes up to 30 articles a month to your CMS, each in a few minutes, with schema markup, internal links and FAQ blocks included, in 18+ languages. Every published article adds another page where your brand name sits next to your topic, without someone prompting each draft.

Step 9: Check Whether Google Already Holds an Entity for You

Google can hold an entity for your brand before it shows a panel. Checking tells you whether you are building a record from nothing or strengthening one that exists but lacks confidence. The Knowledge Graph Search API returns entities that match a name, with a machine ID (often called a kgmid), the types Google assigns and a result score.

Here is a request for the fictional Acmeflow brand. Replace the query and add your own API key from your Google Cloud project.

GET https://kgsearch.googleapis.com/v1/entities:search?query=Acmeflow&types=Organization&limit=5&indent=True&key=YOUR_API_KEY

The query parameter is the name you are testing. The types parameter limits results to organizations, which filters out people and places with the same name. The limit parameter caps the number of matches returned. The response lists each match with its @id (a value beginning with kg:/), its name, its types, a description and a resultScore.

• If your company appears with the right name and description, Google holds an entity for you and the remaining work is confidence
• If your company appears with the old name or wrong description, fix the sources from Step 5 that carry that wrong value
• If a different entity with your name appears and you do not, you have a collision and need the disambiguating description from Step 1
• If nothing appears, Google has not reconciled an entity yet, and Steps 5 to 8 are where to spend your time

Note the kgmid if you find one. You can search Google with the parameter kgmid followed by that ID to see how Google renders the entity, which sometimes shows a panel that does not yet appear for the plain brand query. That is a useful sign that you are close.

Step 10: Verify and Claim the Panel

Claiming is only possible once a panel exists. When Google shows a panel for your entity, a link to claim it appears at the bottom of the card for signed-in users. Claiming verifies that you represent the entity and gives you the ability to suggest changes that Google reviews with more weight than anonymous feedback.

• Search for the entity while signed in to the Google account you chose for verification
• Find the claim link at the bottom of the panel and select it
• Review the verification options Google offers, which are tied to official profiles it already associates with the entity, such as your Search Console property or an official social or YouTube account
• Sign in to that official profile through the flow Google shows, or follow its instructions to confirm ownership
• Wait for Google's review, which can take some days, and watch for a confirmation email
• After approval, use the suggest an edit option on the panel to correct facts, citing a public URL that supports each change

Search Console is the verification route most SaaS teams already have ready. If you have not set it up for your domain, Connect Google Search Console before you start the claim, because a verified property for the entity's official website is one of the routes Google can recognise as proof of ownership.

Claim with an account that will survive staff changes. If the marketing manager who claimed the panel leaves and the account is deleted, you lose the verified role and have to claim again. Use a role-based Google account that the company owns, with two-step verification and a documented owner.

Edits are suggestions, not commands. Google checks them against the sources it already trusts. If you ask it to change the founding year on the panel while Crunchbase and Wikidata still show the old year, the suggestion is unlikely to stick. Fix the sources first, then suggest the edit, and cite the corrected sources in the request.

Step 11: Monitor the Panel and the AI Answers

A panel is not permanent. It can lose its image, switch to an older description, merge with a similarly named entity or disappear when confidence drops. Monitoring catches those changes early, and it shows whether the same facts are reaching AI assistants.

• Search the brand name and the brand name plus category every month from a private window, and save a screenshot for your records
• Re-run the Knowledge Graph Search API query and compare the description and score against the last result
• Check the Wikidata item's history for edits you did not make
• Ask ChatGPT, Claude, Gemini and Perplexity to describe your company, and note any wrong founding year, wrong category or competitor confused with you
• Ask each assistant for the leading tools in your category, and record whether your brand is named
• Update the fact sheet and every profile within days whenever a fact changes, such as a new headquarters or a funding round

The AI check matters as much as the panel check. A buyer researching your category in an assistant never sees your Knowledge Panel. The assistant's description of you comes from the same pool of reference pages, profiles and articles, so a wrong fact in that pool shows up in both places. A panel that is correct while ChatGPT describes you as a different product is a sign that some of your coverage carries an outdated description.

Doing this by hand works for a single brand query. It stops working when you want to know whether assistants name you for the dozens of buyer questions in your category. Gofylo's AI Visibility tracking records how assistants including ChatGPT and Claude answer those searches, which businesses they name in place of yours, and which sites they cite. Those cited sites are often the exact pages to approach for coverage in Step 7.

Troubleshooting

Most Knowledge Panel problems come from conflicting sources or thin evidence, and the fix is almost always upstream of the panel itself. These are the problems I see most often on SaaS brands, with the fix for each.

No panel appears after months of work. Re-run the Knowledge Graph Search API check. If no entity exists, your independent coverage is too thin, so shift effort to Step 7 and to branded content from Step 8. If an entity exists but no panel shows, test the brand name plus category as a query. A panel that appears only for the longer query means Google has the entity but cannot yet tie the bare brand name to it with confidence.

The panel shows a different company with the same name. This is a collision, and the stronger entity wins the bare query. Use your disambiguating description everywhere, add your category to the Wikidata description, and make sure your schema description names the category in its first words. Do not try to claim the other entity's panel. Over time your own panel can appear for the qualified query and, with enough branded demand, for more variations.

The panel shows an old name, logo or description. Find the source that still carries the old value. It is usually Crunchbase, an old LinkedIn page, a directory listing or a Wikidata label. Correct it, add the old name to alternateName in your schema, and then suggest an edit on the panel citing the corrected sources. Expect the change to take some weeks, because Google re-reads sources on its own schedule.

The claim link does not appear on the panel. Make sure you are signed in and viewing the panel on a standard Google search. If the link still does not appear, Google may not have connected the entity to an official profile it can use for verification. Check that your website, Search Console property and official social profiles all appear in your sameAs list and point back to the same About page.

Google rejected the verification request. Rejections usually mean the profile you verified with is not one Google associates with the entity. Verify with a different official profile from the options offered, and confirm that the website listed on the panel matches the Search Console property exactly, including the www and protocol.

The Wikidata item was nominated for deletion. Respond on the deletion discussion with independent references: trade articles, published interviews, directory entries that are not self-submitted. If the brand does not yet have those, let the item go and recreate it later with stronger references. Arguing for an item without sources tends to make the next attempt harder.

The panel is right but AI assistants describe the company wrongly. Ask each assistant where its description comes from, or use one that shows citations. The wrong fact usually traces to one or two widely copied pages, such as an early launch article or an outdated comparison listicle. Request corrections on those pages, publish an up-to-date description on your own site in a quotable first paragraph, and keep publishing on-topic content so the newer description outweighs the old one.

The panel disappeared after it was live. Check for a recent change: a domain migration, a rebrand, a moved About page, a broken schema block, or a Wikidata edit. Any of these can drop Google's confidence. Restore the stable URL or redirect it, fix the schema, revert unwanted edits, and keep the profiles aligned. Panels often return once the conflicting signal is gone.

Related: Entity SEO: How Google's Knowledge Graph Drives Rankings

Frequently Asked Questions

How to be known on Google?

Being known on Google means Google recognises your brand as a distinct entity and ties it to a topic. Get there by describing the company the same way everywhere, adding Organization schema with sameAs links to your official profiles, creating a referenced Wikidata item, earning independent coverage that names you, and publishing steady content on the problems you solve so people search for your brand by name.

How do I join the knowledge panel?

You cannot add yourself to a Knowledge Panel through a form. Google creates the panel when its Knowledge Graph holds an entity for you with enough consistent, corroborated facts. Once a panel appears, you can claim it through the link at the bottom of the card, verify with an official profile such as your Search Console property, and then suggest edits backed by public sources.

The entity work above only compounds if your brand keeps showing up next to its topic in Google and in AI answers. Start with Gofylo's free AI Visibility report to see which businesses AI assistants name for your buyers' searches and which pages to write. Then run a 7-day free trial of Gofylo to have those articles researched, written and published to your CMS, with schema and internal links included.

Sources

• Google Knowledge Panel 5-Step Verification Guide for 2026 - instantpress.co