AI Search & LLMs: Entity SEO and Knowledge Graph Strategies for Brands
- Knowledge Graph Fundamentans
- Live Entity Audit: Diagnosing Gaps and Opportunities
- Entity Relationship Mapping
Search & SEO Concepts
In shortSearch results with extras beyond a plain link, such as review stars, prices, carousels and event dates, usually generated from structured data on the page.
Rich results are search results with extra visual or interactive features beyond the standard title, link and description. Product prices and availability, review stars, event dates, recipe cards, breadcrumbs and carousels are all rich results. Google uses the term for all of these enhancements, including what used to be called rich snippets.
Most rich results depend on structured data. A page describes its main entity, for example a product, event or article, with schema.org markup (Google recommends JSON-LD). Google checks that markup against the requirements for each rich result type listed in its search gallery. Pages that meet the requirements become eligible, but Google still decides whether to show the feature for a given search.
The markup must describe content that is visible on the page and follow Google’s structured data policies; misleading markup can lead to a manual action. Google’s Rich Results Test and the enhancement reports in Search Console show which types a page qualifies for and which errors block them.
A course provider adds Course and Organization markup to every course page. The Rich Results Test confirms the markup is valid, and the Search Console enhancement report flags two pages missing a required property. Because Google retired the Course info rich result, the team keeps the markup for entity clarity and stops expecting it to change how the listing looks.
Structured Data Automation with Python: Detect, Generate and Validate JSON-LD at Scale
Image SEO in 2026: The Complete Guide to Image Optimisation, Advanced Tactics and Multimodal Search
How Structured Data Reinforces Entity Understanding in AI Search
Consistency beats completeness: schema for machines, not results