PILLAR 02 · TRUST & AUTHORITY
Part of the Business Growth Architecture framework. Machine trust and human trust as a precondition for conversion: entity, reputation, Knowledge Graph.
View pillar →
Entity SEO · Knowledge Graph service · Last reviewed: September 23, 2026

Knowledge Panel groundwork, done properly.

As an SEO & GEO expert with 20+ years of practice, I offer a complete Knowledge Panel service. I build the foundation Google draws on: entity home, Wikidata, Schema graph, media corroboration. Three levels: audit, full-service setup, or claim and upkeep. Timeline: 3-12 months, no panel guarantee.

Framework
8 steps 6 trust layers Schema · Wikidata · GEO
Murat Ulusoy · Knowledge Panel service
Entity engineering
“Optimize the panel and you optimize the output. Optimize the entity and you fix the cause.”
Murat Ulusoy
CEO · Head of SEO · SUMAX
Panels live12+
3-12
months timeline
6
trust layers
8
framework steps
0 %
panel hacks
01 - The misconception

“Panel hacks” work briefly. Then Google deletes.

Plenty of vendors promise “a Knowledge Panel in 30 days” through fake press, bought Wikipedia edits or aggressive entity injection. In our experience, such panels often disappear within 6 to 18 months, and the entity is burnt afterwards. Rebuilding it takes far longer than the clean route would have.

◎ The six trust layers

Six layers. All of them have to hold.

(1) Entity identity and disambiguation, (2) an authoritative entity home, (3) independent corroboration, (4) referenced Wikidata statements, (5) a coherent Schema.org graph, (6) consistency over time. Skip one and the entity stays below Google's confidence threshold.

The audit shows which layer is the bottleneck, and that is where the work goes, not into generic checklists.

◆ 8-step framework
  1. 01Online presence audit & name-collision check
  2. 02Build the entity home (own domain, @id)
  3. 03Consistent data across 7–10 curated profiles
  4. 04Wikidata & Wikipedia (if notable)
  5. 05Press & authoritative corroboration
  6. 06Schema.org JSON-LD with @id graph
  7. 07Monitoring & entity drift control
  8. 08Verification & claiming
02 - Service levels

Three models, matched to maturity.

Not everyone starts from zero. Different starting points call for different engagements.

A

Panel audit (standalone)

Four-week diagnosis of maturity, name collisions, Wikidata, Schema and corroboration gaps. Outcome: a 90-day roadmap for your team, or the scope for full service.

StandaloneDiagnosisRoadmap
B

Panel setup (full service)

6-12 months: entity home, Wikidata item (after an eligibility check), Schema graph, trade media corroboration, monitoring. No guarantee that Google shows a panel; the audit tells you honestly whether your notability base holds.

End-to-end6-12 monthsRetainer optional
C

Panel claim & upkeep

For entities that already have a panel: verification through Google's identity process, fact corrections, photo updates, drift monitoring. Ongoing retainer, typically 6-12 hours a month.

VerificationCorrectionRetainer
● Entity maturity check · free

Where does
your entity stand?

A 30-minute live check of Wikidata, sameAs, Schema and name collisions. You then know whether A, B or C fits.

Wikidata presenceItem + properties
Sample
Schema graphPerson/Organization + @id
Sample
sameAs coherence5-15 profiles consistent
Sample
03 - Deliverables

What you get.

Every artefact is verifiable, machine-readable and handed over to you.

01 / Artefact

Entity home

A structured person or organization page with @id anchor and provenance chain.

02 / Artefact

Wikidata item

Where eligible: a QID with maintained properties, external IDs and referenced statements.

03 / Artefact

Schema graph

Production-ready JSON-LD: Person, Organization, Article linked via @id, plus sameAs, knowsAbout, parentOrganization, ImageObject.

04 / Artefact

Profile set

Consistent data across 15-25 profiles (LinkedIn, Crunchbase, Xing, speaker platforms, directories); the 7–10 strongest go into sameAs.

05 / Artefact

Corroboration plan

A briefing for 3 to 7 authoritative trade media, with consistent fact fingerprints and author Schema.

06 / Artefact

Monitoring dashboard

Knowledge Graph API tracking, Bing entity checks, Wikidata drift watch, panel emergence indicators.

04 - Definition

What is a Google Knowledge Panel, and why does it matter in 2026?

A Google Knowledge Panel is the entity box in Google's search results that bundles structured facts about a person, organization, product or place: image, short description, key attributes and links. Behind it sits a node in Google's Knowledge Graph, connected to the entity's wider online presence through entity IDs, Wikidata properties and a sameAs cluster. The panel itself is not something you can optimize directly. It is the visible by-product of a stable Knowledge Graph entry, and Google alone decides whether to show it. A panel tends to appear once five conditions hold: enough independent, authoritative sources (notability), clean disambiguation from namesakes, consistent mentions across the sameAs cluster, an entity home with Schema.org markup, and a Wikidata item with referenced statements. Ignore one of them and the entity stays below Google's confidence threshold, however much classic SEO or PR goes into it.

In 2026 the panel matters twice: as a trust signal in classic results, where Google's confirmation reads like a seal of approval, and as input for AI search. ChatGPT, Perplexity and Claude rely on many of the same structured sources, such as Wikidata. Entities missing there are cited less often.

KNOWLEDGE GRAPH

The graph link

The panel visualizes a Knowledge Graph node. What you optimize is the node: entity home, Wikidata item, Schema.org properties and referenced secondary sources.

TRUST LAYERS

Six layers

Identity, entity home, corroboration, Wikidata, Schema graph, consistency over time. Each must hold measurably, or confidence stays below Google's threshold.

DATA SOURCES

Wikidata & sameAs

Wikidata with referenced statements is the main structured source, backed by consistent profiles, press coverage and industry directories.

CORRECTIONS

Source over request

Fix wrong facts at the source (Wikidata edit, Schema update, authoritative secondary source) rather than only through Google's feedback form. The source fix lasts.

05 - 8-step framework

Eight steps towards a verified panel.

Each layer rests on the one before. Start with Wikidata before the entity home and you build on sand.

01

Presence audit & name collision

Inventory of profiles, Wikidata and Schema, disambiguation against namesakes. Output: maturity score and bottleneck.

AuditDisambiguation
02

Build the entity home

A structured page on the primary domain with @id anchor and full Schema.org profile: Google's primary reference.

Entity home@id
03

Profile consistency

Identical spelling, image and references across 15-25 platforms such as LinkedIn, Crunchbase, speaker platforms and industry directories.

sameAsConsistency
04

Wikidata item & properties

After an eligibility check, create or maintain the QID with referenced properties (P31, P106, P108, P856, P1416). Wikipedia only with sufficient notability.

WikidataQID
05

Corroboration via trade media

Briefing for 3-7 authoritative trade media with consistent fact fingerprints, author Schema and clean references back to the entity home.

PRCorroboration
06

Schema.org JSON-LD graph

Person, Organization and Article linked via @id, validated in the Schema Markup Validator.

JSON-LD@id graph
07

Monitoring & entity drift

API tracking, Bing entity checks and a Wikidata watch catch drift before it destabilizes a panel.

MonitoringDrift
08

Verification & claiming

Once a panel appears: claim it via Google's identity process, control the photo, link profiles, then move to upkeep.

ClaimVerification
06 - Differentiation

How does a Knowledge Panel service differ from PR, Wikipedia and SEO?

Panel work is often confused with PR, writing a Wikipedia article or generic SEO. All three contribute building blocks, but none replaces structural entity engineering.

CriterionKnowledge Panel servicePR & communicationsWikipedia articleClassic SEO
What gets optimizedEntity in the Knowledge GraphReach & sentimentEncyclopedia articleURLs & keywords
Data structureSchema.org + Wikidata + sameAsUnstructured textWikitext, possibly WikidataHTML, meta, partial Schema
Target outcomePanel-ready, verifiable entityMentions, coverage, imageWikipedia entryRankings & traffic
Effect on AI searchDirect citation sourceIndirect via mentionsHigh (LLM training source)Medium (URL crawling)
Timeline3-12 monthsOngoing3-9 months (notability)6-18 months
ComplementsPR + Wikipedia + SEOKnowledge Panel serviceKnowledge Panel serviceKnowledge Panel service
07 - Use cases

Six use cases with the highest leverage.

A panel is not worth pursuing for every entity. In these situations the trust leverage is unusually high.

PERSON

CEO, founder, author

A personal panel with photo, job title, publications, links to LinkedIn, YouTube or the publisher. Supports thought leadership, recruiting and speaking.

BRAND

Organization & brand

Logo, founding year, headquarters, subsidiaries, ticker symbol. A trust anchor for B2B sales, investor relations and recruiting.

LOCAL

Local branches

Multi-location brands with a panel per location, tied to Google Business Profile, reviews and LocalBusiness markup. Drives footfall.

PRODUCT

Product & software

SaaS, hardware and consumer goods with manufacturer, price range and comparison set. Feeds “best of” AI answers and comparison results.

CREATOR

Artists & creators

Musicians, speakers and authors with works and tour dates. A shop window for bookings and licensing.

YMYL

Medical institutions

Clinics, practices and research institutes with accreditations, specialties and author profiles. A YMYL trust factor that directly affects patient decisions.

08 - Investment

What does the Knowledge Panel service cost?

It depends on entity maturity, name-collision complexity and market scope. Every model includes senior consulting, a documented hand-over and transparent source evidence. Exact terms are set in the first call, based on an audit snapshot.

AUDIT

Panel audit

Four weeks of diagnosis. Outcome: a 90-day roadmap to implement yourself.

  • Entity maturity score
  • Name-collision check
  • Wikidata & Schema audit
  • 90-day roadmap (PDF)
PROJECT

Build project

6-12 months of full service. No guarantee that a panel will be shown, because no one can honestly give one. Instead: documented prerequisites and an honest pre-check.

  • End-to-end 8-step framework
  • Wikidata + Schema + sameAs
  • Corroboration with 3-7 media
  • Monitoring dashboard
RETAINER

Upkeep retainer

Ongoing care for existing panels: verification, corrections, drift monitoring, updates after role or market changes. Typically 6-12 hours a month.

  • Entity drift monitoring
  • Correction workflows
  • Schema & Wikidata upkeep
  • Quarterly review
09 - Related

Go deeper.

10 - FAQ

Frequently asked questions.

Answers on the service, how panels come about and how they connect to AI search. Anything else we cover in the first call.

What exactly is a Knowledge Panel, and why does it matter in 2026?

The entity box in Google's results, the visible projection of a Knowledge Graph node. It is a trust signal in classic search and structured input for AI search, where missing entities are cited less often.

Can I apply to Google for a Knowledge Panel?

No. A panel is the by-product of an entity Google considers unambiguous, not an order. Only claiming an existing panel runs through Google, via identity verification.

How long does it take?

Typically 3 to 12 months with clean execution, depending on name collisions, notability and market. Shortcuts such as fake press or bought wiki edits can produce short-lived panels, which in our experience Google often removes within 6-18 months.

What does the service cost?

Three models: audit (four weeks), build project (6-12 months) and upkeep retainer for existing panels. Price drivers: entity maturity, name collisions, market and corroboration effort. Exact terms follow an audit snapshot in the first call.

Do you guarantee a panel?

No, deliberately. Google's confidence threshold decides, not the provider, so no one can honestly guarantee a panel. We build the verifiable prerequisites, document progress over an 18-month observation window and tell you upfront whether your notability base holds.

For a person or a company?

Both, often combined. Founder and organization entities strengthen each other when cross-references are consistent (worksFor and founder in Schema, P108 and P112 in Wikidata). Two linked panels beat a single one carrying double notability.

How does a Knowledge Panel differ from the Knowledge Graph?

The Knowledge Graph is Google's internal store of entities, attributes and relationships. The panel is the visible projection of a node with enough confidence. You optimize the node; the panel follows.

What if facts in my panel are wrong?

Use Google's feedback form (slow, in our experience 4-12 weeks) and correct the source: a referenced Wikidata edit, a Schema update, a correction in an authoritative source. The source fix lasts.

Does this work for local businesses?

Yes, with different mechanics. Local panels draw more on Google Business Profile, reviews and LocalBusiness markup. Knowledge Graph trust complements the local component but does not replace it.

Which use cases benefit most?

CEOs, authors and founders; brands and organizations; local branches of large groups; products and SaaS; artists, speakers and creators; and medical institutions with YMYL trust needs.

How is the service different from PR or writing a Wikipedia article?

PR creates reach and mentions, a Wikipedia article covers notability, classic SEO optimizes URLs for keywords. The panel service combines all three in an entity-centred framework, but only structural entity engineering builds the conditions for a panel.

Let's talk

Shall we build your entity properly?

A 30-minute first call: a live check of your online presence, an honest view of how likely a panel is, and a scope proposal. No contract talk.