Schema Markup Is a Claim — Here's How Google Verifies It Through Knowledge Graph Entities and sameAs

Google's Knowledge Graph represents the world as entities — people, organisations, places, products, concepts — and the relationship between structured data markup and Knowledge Graph inclusion is more nuanced than "add schema, get a knowledge panel," because schema markup communicates what you claim while Knowledge Graph inclusion depends on what Google can verify through multiple corroborating signals

When organisations obsess over getting a Knowledge Panel or rich results for specific schema types, they're often treating structured data as a magic trigger rather than as one part of a broader entity establishment process. Understanding how Google's entity-based understanding works shifts the strategy from "which schema type should I add?" to "how do I make this entity clearly recognisable and verifiable to Google?"

What an entity is in Google's model

An entity in Google's Knowledge Graph is a distinct, identifiable thing — one that has attributes (name, description, location, founding date), relationships with other entities (an organisation has founders who are persons, a product is made by an organisation, an article is authored by a person), and ideally a canonical identifier that distinguishes it from similar entities.

The Wikidata connection: Wikidata (the machine-readable sibling of Wikipedia) is one of the primary sources Google uses to establish entity identity. An organisation with a Wikidata item (Q number), a Wikipedia article, and consistent schema markup on its own website that references these external identifiers is strongly established as a known entity. An organisation with schema markup but no external corroboration is making an uncorroborated claim.

The @id property in JSON-LD: schema markup allows specifying a canonical URL as the identifier for an entity:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Ltd",
  "url": "https://example.com",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q12345",
    "https://www.linkedin.com/company/example-ltd"
  ]
}

The @id creates a persistent identifier for the entity. The sameAs array tells Google that this entity is the same as the specified external identifiers — connecting your schema markup to corroborating external sources.

The sameAs property: connecting your entity to the knowledge graph

sameAs is one of the highest-value properties in Organization and Person schema precisely because it establishes connections between your entity declaration and already-verified external knowledge:

High-value sameAs targets for organizations:

• Wikidata item URL (https://www.wikidata.org/wiki/QXXXXXXX)
• Wikipedia article URL (if one exists)
• LinkedIn company page
• Crunchbase profile
• Companies House or equivalent national business registry
• Industry-specific directories with structured data of their own

For Person schema:

• Wikidata item (if one exists)
• Wikipedia article
• LinkedIn profile
• Official institutional profile (university faculty page, author page at a publisher)

Why this matters for Knowledge Panel eligibility: Google's confidence that an entity is real, notable, and correctly described increases with the number of corroborating sources that independently describe it similarly. Schema markup that only exists on the entity's own site is the entity describing itself — useful but lower confidence than the same information confirmed by multiple independent third-party sources.

Product schema and merchant trust signals for shopping results

Product schema is one of the schema types with clear, direct rich result eligibility — but the requirements go beyond syntactically valid markup:

Required properties for basic Product eligibility:

• name
• At least one of: image, description
• Pricing information via offers (with price, priceCurrency, availability)

Additional properties that significantly improve Shopping rich result eligibility:

• aggregateRating with ratingValue and reviewCount (drives star rating display)
• brand with @type: Brand and name
• gtin, mpn, or sku for product identification (crucial for price comparison features)

The merchant trust layer: Google increasingly evaluates the seller's overall merchant quality signals alongside schema validity — return policy pages, shipping information, clear contact details, and positive reviews on Google's own platform influence whether a merchant's Product schema generates rich results. Technically valid schema from a low-trust merchant site may generate fewer rich results than schema from an established, trusted merchant.

HowTo and Recipe schema: when structured content meets schema

HowTo and Recipe schema are content-type schemas where the markup should reflect the actual page structure — not add information that doesn't exist in the user-visible content:

Google's core structured data policy: the schema should describe what's actually on the page. Adding HowTo schema to a page that lists steps briefly without sufficient instructional detail violates Google's quality guidelines, even if the markup is technically valid.

The over-marking trap: pages that use step elements in HowTo schema for what are really bullet point tips, or that add Recipe schema to a page discussing cooking techniques generally rather than giving a specific recipe, may be technically valid but misleading — and Google's manual review process specifically looks for this mismatch.

What genuinely helps: HowTo schema with detailed step objects (each containing name and text, optionally with image) that mirror substantive, numbered steps visible in the content. Recipe schema with complete data (prep time, cook time, nutrition, ingredients, specific step-by-step instructions) adds more value than minimal Recipe markup.

VideoObject schema: the underused rich result opportunity

VideoObject schema is consistently underutilised by sites hosting original video content, despite providing clear rich result opportunities:

Rich result types for video:

• Video rich results in standard search (thumbnail, duration, publication date)
• Video carousel appearances
• Inclusion in the Videos tab
• Key moment annotations (chapters that appear as segments within the result)

The Key Moments opportunity: by adding hasPart with Clip objects to VideoObject schema, each clip can specify a start time, end time, name, and URL — Google uses this to display chapter markers in video search results, significantly improving click-through rate for longer videos.

Host platform considerations: YouTube automatically generates VideoObject-equivalent structured data for YouTube-hosted videos — this gives YouTube-hosted videos schema benefits automatically. Self-hosted videos on your own domain require explicit VideoObject schema to receive the same treatment.

How to use the Schema Generator on sadiqbd.com

1. Start with Organization and WebSite schema: before any content-specific schema, establish the site's entity identity with a sitewide Organization (or LocalBusiness) and WebSite block in the <head>, including @id, sameAs, and url properties — this entity foundation supports all subsequent schema
2. Match schema to page content type: generate schema that matches what's actually on the page — Article for editorial content, Product for e-commerce product pages, HowTo for step-by-step guides, Recipe for specific recipes — avoid applying schema types to content that doesn't genuinely match
3. Validate and test for rich results separately: use the generated schema in Google's Rich Results Test (search.google.com/test/rich-results) after implementing — validation confirms correct syntax, but the Rich Results Test additionally shows whether the page is eligible for the specific enhanced presentation

Frequently Asked Questions

Does adding schema markup directly improve search rankings, or does it only affect rich result appearance? Schema markup's primary direct effect is on rich result eligibility, not rankings — Google has consistently stated that structured data is not a direct ranking signal. The indirect effects are real but less predictable: rich results (star ratings, recipe cards, FAQ dropdowns) typically improve click-through rate for the pages that earn them, and higher CTR can be a positive quality signal. Additionally, entity establishment through Organization and Person schema with strong sameAs references may improve how Google understands and relates pages to known entities — contributing to topical authority signals that do influence rankings. The clearest ROI from schema is the direct, visible rich result improvement for eligible content types like Product, Recipe, and VideoObject; the ranking effect is real but more diffuse and harder to attribute cleanly.

Is the Schema Generator free? Yes — completely free, no sign-up required.

Try the Schema Generator free at sadiqbd.com — generate valid JSON-LD schema markup for any page type instantly.