Google's 2026 structured data updates shift markup from decoration to identity. A new Product category property, expanded ProductGroup variants, and an active crackdown on misleading markup — on top of an entity graph that decides whether AI Overviews can cite you at all. Here's the model, and how we implement it.
Schema markup used to be a rich-result tactic. In 2026 it is the layer where search engines and language models decide what your business actually is. Instead of treating keywords as plain text, modern markup connects entities — people, places, organizations, products — into a logical graph that machines can traverse.
The practical consequence: standalone schema blocks per page are obsolete. What wins is entity stacking — one sitewide graph, stable identifiers, and every page declaring which known entities it is about. That graph is what feeds the Knowledge Graph, and the Knowledge Graph is what AI Overviews reach for when they choose a source to cite.
category property on Product.ProductGroup support lets merchants group size, material, and colour variations into one cohesive multi-variant entity via variesBy and hasVariant. Stores still shipping one flat Product per variant fragment their own review, price, and availability signals.A unique, machine-readable URL for each entity. Declare the entity once, then reference it by @id everywhere else. This is what stops Google seeing forty separate 'Example Corp' organizations across forty templates and instead merges them into one authoritative node.
Link your entity to Wikidata, Wikipedia, official company registers, and verified social profiles. sameAs is how a retrieval model confirms that the brand in your markup is the same brand it already knows about — and it is the cheapest trust signal available to a new domain.
Nested inside Person or Organization, knowsAbout states the exact fields you have expertise in. It converts 'we write a lot about X' into a machine-readable claim, and it is the single most under-used property for building conceptual topical authority.
about names the primary entity a page covers; mentions lists the secondary entities. Together they tell a retrieval system exactly which concepts a page is authoritative on, instead of leaving it to embedding similarity.
Google's new explicit category field on Product maps your listing to its internal merchant product taxonomy. Getting it right places your products in the correct comparison set inside Shopping surfaces and AI-assembled product answers. Getting it wrong buries them among the wrong competitors.
Expanded ProductGroup support lets you group size, colour, and material variations under one parent entity with variesBy and hasVariant. Done right, it kills variant-level duplication and consolidates review and price signals onto a single product entity.
Google prefers JSON-LD embedded in your HTML head. This example connects a company entity to its founder, declares that founder's expertise, and maps a page to the entities it covers — all through a single @graph.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Corp",
"url": "https://example.com",
"sameAs": [
"https://www.wikidata.org/wiki/Q000000",
"https://www.linkedin.com/company/example-corp"
],
"founder": { "@id": "https://example.com/#founder" }
},
{
"@type": "Person",
"@id": "https://example.com/#founder",
"name": "Jane Doe",
"knowsAbout": [
"Artificial Intelligence",
"Search Engine Optimization"
],
"sameAs": ["https://www.linkedin.com/in/janedoe"]
},
{
"@type": "WebPage",
"@id": "https://example.com/guide#webpage",
"about": { "@id": "https://example.com/#organization" },
"mentions": [
{ "@type": "Thing", "name": "Knowledge Graph" },
{ "@type": "Thing", "name": "Generative Engine Optimization" }
],
"publisher": { "@id": "https://example.com/#organization" }
}
]
}Paste your own markup into our free schema markup checker to see what's missing, or read the GEO guide for how this feeds citation share.
We can promise this because our methodology already works. Hundreds of pages now sit in position #1 across our clients' catalogs. The risk shouldn't be on you — it's on us.
Three things matter. Google added an explicit category property to Product structured data that maps your listings to Google's internal merchant product taxonomy. ProductGroup support expanded so multi-variant products (size, color, material) can be grouped as one cohesive entity. And Google formally began penalizing misleading markup — content-schema mismatches, such as Product markup on a page with nothing purchasable, are now treated as a violation rather than ignored.
Entity-based SEO means declaring machine-readable identities instead of hoping a crawler infers them from your text. Every organization, person, product, place, and concept on your site gets a stable @id, is disambiguated with sameAs links to authoritative databases, and is connected into a single @graph. Search engines and LLMs then read your site as a knowledge graph rather than a bag of keywords.
@id is the anchor. It gives an entity one canonical, machine-readable URL identifier that you can reference from every other page without duplicating the entity. Without @id, each page creates a fresh, unlinked copy of your organization or author — and Google has to guess whether they are the same thing. With @id, your entities merge into one strong node in the Knowledge Graph.
Yes, indirectly but strongly. Retrieval systems favour content whose claims are unambiguous and attributable. Structured data supplies clean, quotable facts (price, availability, author, expertise, publish date) with no parsing ambiguity, and sameAs links let a model verify the entity against Wikidata or an official register. Pages with a coherent entity graph get cited more often than pages with equivalent prose and no markup.
It can trigger a structured data manual action, which removes your rich results — and in aggressive cases suppresses the page. The common triggers are Product markup on non-commerce pages, Review markup for reviews not visible on the page, FAQPage markup where the Q&As are not user-visible, and aggregate ratings that do not exist. Every audit we run starts by removing markup you should not be shipping.
For a typical ecommerce or SaaS site, we deliver the full entity map and JSON-LD templates in 2–3 weeks. Implementation is usually a single template-level change per page type. Knowledge Graph consolidation and citation lift typically show up 30–90 days after deployment, once Google recrawls and merges the entities.
We'll map your current markup, flag every misleading tag, and show the graph you should be shipping.