Schema priority: which types Google uses for rich results

Schema.org has over 800 types and thousands of properties. Google supports a small subset of them for rich results, and the support is uneven: some types produce visible rich features in search, others provide context Google may use internally, others are ignored entirely. Knowing which schema types matter most prevents the common pattern of marking up everything and seeing no impact.

The schema universe is large because schema.org is a general vocabulary for structured data on the web. Google’s rich results system is a smaller universe focused on specific search features: review stars, recipe cards, FAQ accordions, How-to steps, Product price displays, Event listings, Job postings, and a few dozen others. Schema types outside this list can still be marked up correctly, but they won’t produce visible search features.

The schema types that produce visible rich results:

Google’s structured data documentation lists the specific types that can produce rich results. As of 2026, the most impactful are:

Schema type	Rich result	Visibility impact
<strong>Product</strong>	Price, availability, rating stars	High for ecommerce; appears in shopping and standard results
<strong>Review/AggregateRating</strong>	Star ratings inline	High; visible across many result types
<strong>Recipe</strong>	Recipe cards with image, time, rating	High; transforms result presentation
<strong>HowTo</strong>	Step-by-step expanded display	Reduced in 2023; still appears for some queries
<strong>FAQPage</strong>	Expandable Q&A in results	Reduced; primarily for government and health sites since 2023 update
<strong>Article/NewsArticle</strong>	Top stories, news carousels	High for news publishers
<strong>VideoObject</strong>	Video thumbnails, key moments	High for video content
<strong>Event</strong>	Event listings with date/location	High for event sites
<strong>JobPosting</strong>	Google for Jobs integration	Essential for job boards
<strong>Course</strong>	Course listings with provider	Medium; appears in education-focused queries
<strong>LocalBusiness</strong>	Knowledge panel integration	High for local SEO
<strong>Organization</strong>	Knowledge panel for brand queries	High for brand recognition
<strong>BreadcrumbList</strong>	Breadcrumb display in results	Universal small lift

Google has reduced visibility for some types over time. FAQ rich results were widely available in 2020 but largely removed for non-government, non-health sites in 2023. HowTo rich results were similarly reduced. The list isn’t static; Google adjusts which types produce rich results based on quality and abuse patterns.

The schema types Google uses internally without rich results:

Some schema types don’t produce visible search features but still help Google understand the page:

Person properties on author bylines help Google’s E-E-A-T evaluation for the page
Organization properties on publisher information help with attribution and authority signals
WebPage type with author, datePublished, dateModified provides freshness and authorship context
ImageObject properties help with image search and licensing display
SoftwareApplication for app pages helps with app indexing

These don’t transform the search result presentation but contribute to ranking and feature decisions. Sites with strong implementation of context-providing schema often see indirect benefits that don’t appear as visible rich snippets.

The schema types Google ignores:

The majority of schema.org types don’t produce search features and don’t appear to influence ranking in detectable ways. Examples:

CreativeWork subtypes for niche content (Diet, ExercisePlan, MedicalProcedure variants)
Action types for marking up user actions
Service types for general service descriptions (specific service types like FinancialProduct have more support)
Most of the long tail of schema.org’s vocabulary

Marking up these types doesn’t hurt (Google ignores rather than penalizes), but it doesn’t help either. The time spent implementing them is better spent on the supported types or on other technical SEO work.

Priority order for implementation:

For sites starting from scratch, the priority order is:

First priority is the schema types that match the site’s primary content:

Ecommerce sites: Product with Offer, AggregateRating, Review
News sites: NewsArticle with author Person, publisher Organization
Recipe sites: Recipe with rating, cooking time, nutrition
Service businesses: LocalBusiness with hours, address, services
Job boards: JobPosting with all required properties

Second priority is the schema types that apply to most sites:

Organization on the home page or footer
BreadcrumbList on every page that has breadcrumb navigation
WebPage type with proper author and date properties

Third priority is schema types that help search features beyond the primary content:

VideoObject when video appears on key pages
Event for any time-bounded content
FAQ where appropriate (with awareness of reduced visibility outside health/government)

Fourth priority is everything else, where the cost-benefit is less clear. For most sites, this tier is optional.

Common implementation mistakes:

The patterns that recur in schema audits:

Marking up content that isn’t visible on the page. Schema must describe content that users can see. Marking up reviews in the schema when no reviews appear on the page is a manual action trigger.
Using AggregateRating without real reviews. The aggregate rating must be based on actual review data shown on the page. Made-up ratings are an aggressive manual action category.
Marking up the wrong type. Using Article when Product is correct, or LocalBusiness when Organization is more accurate.
Required properties missing. Each schema type has required properties (e.g., Product needs name and image; JobPosting needs title, hiringOrganization, jobLocation). Validators flag missing required properties.
JSON-LD that doesn’t match the rendered HTML. When JavaScript modifies the page after schema is rendered, Google may see different content from what users see. The schema should reflect the final rendered state.
Recipe schema on non-recipe pages. Common when teams add schema speculatively. Google’s spam systems detect mismatched schema and may reduce rich results eligibility site-wide.
Schema on pages blocked by robots.txt. A subtle failure mode: the page has perfect schema, but robots.txt prevents Google from crawling the page. Schema can only produce rich results if Google can fetch the page and read the markup. The audit step that catches this: cross-check pages with schema against robots.txt rules to confirm crawlability.

The validators that catch most problems:

Google’s Rich Results Test shows what Google sees and flags errors
Schema.org’s validator checks vocabulary correctness
Search Console’s enhancement reports track schema health over time

A note on robots.txt and schema interaction:

# Pages with critical schema must be crawlable
User-agent: *
Allow: /products/
Allow: /recipes/
Allow: /jobs/
Disallow: /products/admin/

If product pages, recipe pages, or job listings carry schema but the directories are disallowed in robots.txt, the schema produces zero rich results regardless of correctness. Verify with Search Console URL Inspection: a URL that reports “blocked by robots.txt” cannot produce rich results.

The decision between general and specific types:

Schema.org has hierarchies. Article has subtypes like NewsArticle, BlogPosting, TechArticle. Product has subtypes like IndividualProduct, ProductModel. Organization has subtypes like LocalBusiness, Corporation, EducationalOrganization, NewsMediaOrganization.

The general rule: use the most specific type that accurately describes the content. NewsArticle for news content provides more signal than the parent Article. LocalBusiness for a physical business provides more signal than the parent Organization. Recipe is more specific than CreativeWork.

The trade-off: more specific types sometimes have stricter required properties. NewsArticle requires more properties than Article. Recipe requires nutritional info to be complete for some rich result eligibility. Sites should use the specific type if they can meet its requirements, and fall back to the parent type if they can’t.

The wrong approach: using the most general type (Thing or CreativeWork) when a specific type would describe the content better. Google’s schema processing prefers specificity.

How schema priority connects to ranking:

Schema markup doesn’t directly cause higher rankings. Google has stated multiple times through John Mueller and others that schema isn’t a ranking factor in the traditional sense. What schema does:

Enables rich results, which can increase click-through rate from search
Provides context that Google’s algorithms use in understanding the page
Connects entities through sameAs links to authoritative knowledge sources
Distinguishes content types in ways that help Google select the right SERP features

The indirect effect on traffic can be substantial even without direct ranking lift. A product page with a 4.5-star rating displayed gets more clicks than the same page without the rating shown, which over time produces user signals that may influence ranking. The mechanism is indirect but real.

The rich results landscape has been actively shifting through 2024 and 2025. Google deprecated several rich result types during this period (How-To rich results dropped from desktop in 2023 and from mobile in 2024; FAQ rich results restricted to authoritative health and government sources in 2023; the change was clarified further in 2024 updates). New rich result types have appeared on the same timeline (Vehicle Listings expanded in 2024, Course Info and Discussion Forum rich results stabilized for broader eligibility in 2025). The implication: priority decisions made in 2022 may need revisiting in 2026 because the underlying ranking and CTR economics have shifted. Sites running schema audits every 12-18 months catch these changes; sites running them less often work with outdated priority assumptions.

Testing and validation tooling:

Schema implementation that doesn’t validate produces errors that block rich results from appearing. The tooling landscape has matured significantly:

Google’s Rich Results Test (search.google.com/test/rich-results) checks specific URLs against the rich result types Google supports. It shows which rich result types the page is eligible for and what errors or warnings exist. This is the authoritative test for Google-specific behavior.
Schema.org Validator (validator.schema.org) checks markup against the schema.org vocabulary without Google-specific filtering. Useful for verifying markup correctness independent of which search engine consumes it.
Search Console Enhancement reports show site-wide schema performance: how many pages with each schema type, how many have errors, how many produce rich results. The reports update on Google’s crawl cadence, not in real time.
Bulk schema validators. Screaming Frog (with custom extraction or the structured data validator extension), Sitebulb, and Ahrefs Site Audit all check schema across full site crawls. Useful for catching schema problems at scale rather than one URL at a time.
CI/CD schema validation. Tools like schema-org-validator (npm) and pyld (Python) let teams validate schema as part of build pipelines. Schema-related deployment failures get caught before going to production rather than after errors accumulate.

The discipline that catches schema problems early: validate during build, audit at scale during deploys, monitor the Search Console reports weekly. The cadence catches issues before they affect rich result eligibility for significant traffic.

Accurate, validated, prioritized, not comprehensive:

Schema priority work is part of the technical SEO foundation. The goal isn’t comprehensive markup of every page with every available type; the goal is accurate, validated, prioritized markup of the types that matter for the site’s primary content and the search features that Google supports.

For sites with no current schema, the right starting point is the highest-impact types for the site’s category (Product for ecommerce, NewsArticle for news, Recipe for cooking content). For sites with existing schema, the priority is auditing what’s there: validating correctness, removing markup for unsupported or ignored types, expanding coverage for high-impact types.

The schema landscape changes as Google adjusts which types produce rich results and as schema.org evolves. The right discipline is periodic review (annual minimum for active sites), not one-time implementation followed by never touching it again.

The fundamentals stay stable: prioritize what Google uses, validate before deploying, keep schema aligned with visible page content, use specific types where they apply. The implementation details change; the principles don’t.

The traffic impact is measurable through Search Console. Pages with proper schema typically see 5-15% CTR lift in their SERP positions through rich result enhancements; specific schema types (Product, Recipe, FAQ) sometimes produce 20-40% CTR lift when they trigger high-prominence SERP features. The implementation cost is small (template-level work measured in engineering days, not months); the ongoing maintenance cost is modest if schema generation is automated rather than manual.

Related posts: