Schema.org defines more than eight hundred types. Google supports a few dozen for rich results, and only a handful of those change anything visible for most sites. Implementing the rest is not harmful, but it is not why your result looks different either.
Here is the split that matters when you are deciding what to spend implementation time on.
Types that produce visible rich results
These change how your listing looks in the SERP, which is where the click-through gain comes from.
Product — price, availability and rating in the result. The highest-impact type for ecommerce by a wide margin. Requires Offer, and ratings need real, on-page review data.
Review and AggregateRating — star ratings. Powerful and heavily policed: the reviews must be visible on the page and genuinely collected. Self-serving markup on your own homepage is a manual-action risk, not a shortcut.
FAQPage — expandable questions beneath your result. Google narrowed eligibility substantially, and it now mostly displays for authoritative government and health sources. Still worth adding for the AI-answer legibility, but do not budget for the SERP accordion.
HowTo — step-by-step display. Similarly narrowed. Implement if you genuinely publish procedures; do not restructure content to chase it.
Event — dates, venue and ticket availability. Consistently displayed and consistently under-implemented by venues and organisers.
Recipe — cook time, calories, ratings, image carousel. Effectively mandatory in that vertical.
JobPosting — inclusion in Google’s jobs experience. High impact if you post roles regularly.
BreadcrumbList — replaces the raw URL with a readable hierarchy. Small, reliable, and one of the easiest wins available.
VideoObject — thumbnails and key moments. Worth it if video is a real part of your content.
Types that help understanding rather than appearance
No visible change, real underlying value.
Organization — your name, logo, contact details and sameAs links to official profiles. This is how Google connects your website, your social accounts and your knowledge panel into one entity. Increasingly it is also how AI answer engines decide who you are when they cite you.
Person — author entities. Combined with sameAs, it links an author’s work across every site they publish on, which is the practical mechanism behind demonstrating experience and expertise.
LocalBusiness — address, hours, service area, geo coordinates. Supports local pack eligibility and reconciles against your Google Business Profile. Pairs with the work in our local SEO guide.
Article / NewsArticle — clarifies content type, publication date and author. Rarely visible on its own, foundational for news and discovery surfaces.
Service — describes what you sell and where. No rich result, but it is how a services business becomes legible as a provider rather than a blog.
Types that mostly do nothing
WebPage, WebSite, SiteNavigationElement and similar wrappers are harmless and near-universally ignored. The one exception is WebSite with SearchAction, which can produce a sitelinks search box — though Google has scaled that back too.
Do not let a plugin’s “100% schema coverage” score convince you these are achievements.
Rules that apply to all of it
Mark up what is on the page. Structured data describing content a user cannot see is a guidelines violation, and it is the most common reason for a structured-data manual action.
Use JSON-LD. Google’s stated preference. Keep it in a single script block per page and out of your HTML attributes.
Validate before and after deploying. The Rich Results Test tells you what Google can use; the Schema.org validator tells you whether the syntax is correct. You want both.
Expect eligibility, not display. Valid markup makes you eligible for a rich result. Google decides per query whether to show it. Anyone promising guaranteed rich results is overselling.
Keep it accurate as content changes. Hardcoded prices and stale hours are worse than no markup. Wire schema to live fields.
Where to start
If you have nothing today: Organization, BreadcrumbList, and whichever of Product, Article, LocalBusiness or Event matches your primary template. That covers the majority of the available benefit for a fraction of the work.
The schema markup guide walks through writing the JSON-LD itself. If you would rather have it selected, written, deployed and validated for you, that is our schema implementation service.
