schema.org lists hundreds of types, which is intimidating. The good news: only a handful earn rich results in Google, and those are the ones worth your time. Here is the short map.
Types that earn rich results
- Article / BlogPosting — news and blog content
- Product with Offer — price, availability and review stars
- FAQPage — expandable Q&A
- HowTo — step lists
- BreadcrumbList — the path shown under the URL
- Event — event listings
- LocalBusiness — local packs and knowledge panels
- Organization — brand knowledge panel
- VideoObject — video rich results
- Review / AggregateRating — star ratings
- Recipe — recipe carousels
- Course — course carousels
Identity vs content
Two categories matter. Identity types (Organization, LocalBusiness, Person, WebSite) describe who you are. Add them once, site-wide. Content types (Article, Product, FAQ, HowTo) describe this page. Add them per page.
Mixing them is a common error: putting Organization on every page, or putting Product on a blog post.
Choosing the right type in 4 questions
1. Is this a product being sold? → Product + Offer
2. Is this an article or post? → Article / BlogPosting
3. Does the page contain a visible Q&A? → FAQPage
4. Is this a business location? → LocalBusiness
If none apply, you probably do not need structured data beyond BreadcrumbList and Organization.
Rules that keep you out of trouble
- Mark up only what users can see
- Never fake reviews or ratings
- Use absolute URLs for images and pages
- One primary entity per page where possible
- Validate with the Rich Results Test before shipping
- Keep the
@typespelling exact (BlogPosting, notBlogposting)
Combining types with @graph
You can publish several entities in one block. A blog post commonly combines BlogPosting + BreadcrumbList:
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "BlogPosting", "headline": "..." },
{ "@type": "BreadcrumbList", "itemListElement": [ ... ] }
]
}What to skip
Skip exotic types with no rich-result support, and avoid piling every type onto every page. Relevance beats volume.
Validate
1. JSON parses — JSON-LD validator
2. Required fields present for the type
3. Rich Results Test shows eligibility
4. Search Console → Enhancements has no new errors
Worked example
A SaaS pricing page might use Product (the plan) + FAQPage (billing questions) + BreadcrumbList. A blog post uses BlogPosting + BreadcrumbList + Organization (once, in the layout). A local dentist uses LocalBusiness + FAQPage. In each case, every marked-up element is visible on the page.
Generate it
Our free generators cover the common types — Organization, Article, Product, FAQ, Breadcrumb and LocalBusiness. Paste your fields and copy clean JSON-LD.