Schema markup: which types actually earn rich results
By AI Digital Marketings · Published · Updated
Which schema markup types produce rich results?
The schema types most likely to produce visible rich results for Australian businesses are Product, Review, Event, Recipe and BreadcrumbList. FAQPage no longer earns one — Google restricted it to government and health sites in 2023 and removed the feature entirely in May 2026 — though the markup is still worth keeping because AI answer engines extract from it. Organization and LocalBusiness markup rarely produce a visible result directly but help Google identify your business entity, which affects knowledge panels and local visibility.
Rich results are not guaranteed
Valid markup makes a page eligible for a rich result. It does not entitle it to one. Google decides per query whether to display it.
This is worth understanding before implementation, because agencies occasionally sell schema as though it guarantees enhanced listings.
The types worth implementing first
BreadcrumbList is the one every site should have — it improves how your URL displays in results and is one of the few types a service business can reliably earn something from. Product and Offer markup are essential for ecommerce. LocalBusiness matters for entity recognition even without a visible result.
FAQPage is the cautionary tale. It was the highest-value option for service businesses until Google narrowed it to government and health sites in 2023, then withdrew the feature altogether in May 2026. Keep the markup if you already have it, because AI answer engines and AI Overviews extract from its question/answer structure, but do not let anyone sell it to you as a search appearance win.
Place Organization and LocalBusiness on your homepage or a single page that describes the business — Google's own guidance says you do not need it on every page, and repeating a full business description sitewide adds weight without adding meaning.
Where businesses get it wrong
The most common failure is marking up content that is not visible on the page. Google requires structured data to reflect what users actually see, and marking up hidden content is a policy violation.
The second is fabricated review markup — inventing ratings for testimonials that were never real reviews. It is a reliable route to a manual action, and it misleads customers.
Use one graph per page
Rather than scattering separate script tags across a page, combine entities into a single @graph and reference them by @id.
This lets Google resolve relationships — that this WebPage belongs to this WebSite, published by this Organization — and makes validation far simpler.
Validate, then re-validate
Google's Rich Results Test shows eligibility; the Schema Markup Validator checks syntax. Both are worth running, since they catch different problems.
Re-check after template changes. Schema silently breaking during a redesign is extremely common and nobody notices for months.
Frequently asked questions
01Does schema markup improve rankings?
Not directly. Structured data is not a ranking factor. It affects how your result is displayed, which can substantially improve click-through rate — and higher click-through on the same position means more traffic without ranking movement.
02Was HowTo schema removed?
Google significantly reduced HowTo rich results, retaining limited mobile display. It is still worth implementing for clarity and AI extraction, but no longer expect a desktop rich result from it.
03Can I have too much schema?
You can have wrong schema. Marking up content that is not on the page, or using types that do not accurately describe the content, causes problems. Accurate markup on every relevant page does not.