Structured data that earns rich results, and what does not
Only some schema types produce a visible search feature. The rest still matter, but for a different reason: they tell machines what your entities are.
Key takeaways
- Product, Article, LocalBusiness and a few others can produce visible rich results; most types cannot.
- Organization, WebSite, BreadcrumbList and sameAs do the invisible work of entity resolution, which matters for AI answers.
- Define each entity once with a stable identifier and reference it; conflicting definitions are worse than none.
- Markup must describe content visible on the page, or it is misrepresentation and subject to manual action.
Structured data does two separate jobs. A small set of types are eligible for rich results in Google, which changes how your listing looks. A much larger set does nothing visible but tells search engines and language models what your entities are and how they relate. Both matter in 2026, and confusing them leads teams to implement the wrong markup and conclude that schema does not work.
The types that produce a visible feature
- Product with Offer. Price, currency and availability in the result. The highest commercial return of any markup for retailers.
- FAQPage and HowTo. Eligibility varies by query and has been narrowed over time, but the markup remains useful for machine comprehension even when the visual feature does not appear.
- Article and NewsArticle. Feeds publication date, author and headline into news and discovery surfaces.
- LocalBusiness, Event, Recipe, JobPosting, Course, VideoObject. Each has its own eligibility rules and its own required fields; read the specific documentation rather than assuming.
The types that do the invisible work
Organization, Person, WebSite, BreadcrumbList and the sameAs property produce little or nothing visible, and they are the ones that matter most for being understood. They let a machine resolve who you are, connect your site to your profiles elsewhere, and distinguish your company from another with a similar name. When a language model has to decide whether a claim belongs to your brand, this is the material it uses.
Consistency across the site matters more than completeness on any single page. Define your organisation once with a stable identifier and reference it from every page rather than restating it with small variations. Conflicting definitions of the same entity are actively harmful, because they force a resolver to guess.
Rules that prevent penalties
Markup must describe content that is actually visible on the page. Review markup for reviews that do not appear, FAQ markup for questions nobody asked, and price markup that disagrees with the checkout are all misrepresentation, and manual actions for structured data spam are issued. The test is simple: could a person reading the page verify every claim in the JSON-LD.
How to implement without breaking it later
Generate structured data from the same source that renders the page, so the two cannot drift. Hand-written JSON-LD pasted into a template is correct on the day it ships and wrong within a quarter. Validate with the Rich Results Test before deployment and monitor the enhancement reports in Search Console afterwards, since eligibility changes without notice and a type that produced a feature last year may not this year.
A minimum set worth shipping on every site
If you implement nothing else, implement four things. An Organization entity with a stable identifier, your legal name, logo and sameAs links to the profiles you actually control. A WebSite entity so your site is recognised as a publication rather than a collection of documents. BreadcrumbList on every page below the top level, which both produces a visible breadcrumb in results and tells a machine where the page sits in your hierarchy. And Article markup on editorial content with an accurate publication date, a named author and a headline that matches the visible one.
That set takes an afternoon on a well-built site, produces one visible feature, and does most of the entity work. Everything beyond it should be justified by a specific eligibility requirement rather than added because the vocabulary exists.
Why authors matter more than they did
Naming a real author, with a Person entity linked to a genuine profile and a page describing their experience, is one of the few remaining ways to signal that content came from someone accountable. Anonymous or house-byline content is not penalised, but it forfeits a signal that costs nothing to provide. Where the author has verifiable expertise in the subject, say so in the markup and on the page, and link to somewhere that corroborates it.
Rich results are the visible half. Entity clarity is the half that decides whether a machine can say who you are.
Sources