How to get a Google Knowledge Panel as a journalist

How Knowledge Panels work for journalists

Google describes a Knowledge Panel as an automatically generated summary of an entity—such as a person or organisation—based on its understanding of content available across the web. For journalists, the entity can be harder to resolve when names, roles, profiles, works, or organisations overlap.

No website, database, schema field, press placement, or agency controls Google’s final decision. Accurate evidence helps systems interpret the subject; it does not buy or unlock a search feature. If a panel appears, the subject or an authorised representative may be able to claim it and suggest evidence-backed corrections through Google’s official workflow.

The practical process

Seven steps to strengthen a journalist entity

1. Create a canonical fact register

Begin with a source-backed record of preferred byline, full name, current newsroom, past appointments, reporting beat, location, awards, and public professional identifiers. For every fact, record the preferred wording, a reliable source URL, who owns the correction, and the last review date. This prevents a website update from creating new conflicts elsewhere.

Search the public name with role, location, organisation, and important-work qualifiers. Note same-name entities, outdated biographies, duplicate profiles, incorrect images, and mismatched dates. Resolve ambiguity with evidence rather than keyword repetition.

2. Build the official identity hub

The strongest owned foundation is a stable newsroom biography or personal site that links a complete byline archive, current role, verified profiles, contact route, and corrections. The page should identify the subject immediately, use a stable canonical URL, and link only to profiles and organisations that genuinely belong to the entity.

• Put essential facts in crawlable HTML.
• Use descriptive page titles, headings, links, and image alternatives.
• Maintain a visible updated date for facts that change.
• Redirect retired canonical pages rather than abandoning their authority.
• Keep biography and contact information accessible on mobile.

3. Align the records specific to journalists

Generic social profiles are only one layer. Review consistent publisher author URLs, Article or NewsArticle author markup, author sitemaps, Muck Rack or equivalent profiles where appropriate, and accurate archive attribution. Correct duplicate, merged, or misattributed records through each platform’s supported process.

Do not create accounts or database entries merely to fill a checklist. A record is useful when it is legitimate, maintained, relevant to the profession, and capable of supporting a fact without contradicting stronger sources.

4. Add structured data that matches visible content

Use the most accurate Schema.org type for the page and subject. For this guide, Person is the usual starting point, but more specific types and relationships may apply. Google recommends using accurate author or organisation types and valid URLs that uniquely identify the entity.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Preferred public name",
  "url": "https://official.example/",
  "description": "Accurate visible description",
  "sameAs": ["https://relevant-platform.example/profile"]
}

Only include facts and links that visitors can verify. Validate the rendered page and remember that valid markup does not guarantee a Knowledge Panel or rich result.

5. Build independent corroboration

Owned pages describe the subject’s position. Independent sources test whether other credible organisations recognise it. Relevant evidence for this niche includes industry awards, conference biographies, media interviews, professional registers, citations, and reporting about the journalist’s work.

Evaluate every source for editorial independence, specificity, factual depth, permanence, and relevance. Ten copied announcements do not provide the same corroboration as one detailed, independently reported profile.

6. Connect relationships without merging entities

Map the subject to works, employers, companies, publications, collaborators, events, and official profiles. Each connected object may be its own entity. Describe the relationship explicitly and use stable URLs so machines do not have to infer whether two names refer to the same thing.

Review the journalist service page for the signal categories used in our public-source assessment.

7. Monitor, claim, and correct

Keep a dated snapshot of relevant searches and the sources supporting important facts. Recheck after substantive website, profile, publication, or role changes—not simply every day. When an eligible panel can be claimed, use Google’s verification process. Submit corrections with a concise explanation and reliable evidence URLs.

KnowledgePanel.io planning framework

The four-layer evidence stack

This framework organises work; it is not a Google score, eligibility test, or forecast.

A 20-point evidence inventory

Score each category from 0 to 4 using evidence available today. The total is an internal completeness measure, not Google’s score.

A practical 30/60/90-day plan

This is an operational sequence, not a promise that Google will create or update a panel within 90 days.

Common mistakes to avoid

• Using an organisation as the named individual author.
• Splitting one byline across duplicate newsroom profiles.
• Deleting author pages after a journalist leaves.
• Combining journalists with the same name.
• Using outdated job titles without dates.
• Adding Article markup that disagrees with the visible byline.

Frequently asked questions