Schema.org lists over 800 types of structured data. Most of them do nothing for your search visibility. Google only supports rich results for a small subset, and even within that subset, some types deliver dramatically better results than others.
This guide focuses on the schema types that actually produce visible changes in search results: the ones that generate rich snippets, knowledge panels, carousels, and enhanced listings. For each type, you will see what it looks like in search, what properties are required, and how to implement it correctly.
How Schema Markup Creates Rich Results
When you add structured data to a page, you are giving Google machine-readable information about your content. Google uses this data to generate rich results: enhanced search listings that include ratings, prices, images, FAQs, breadcrumbs, or other visual elements beyond the standard blue link.
Rich results get higher click-through rates than standard results. The exact lift varies by type, but studies from Milestone Research and others consistently show CTR increases of 20% to 40% for pages with rich results compared to plain listings. Schema markup is also one of the key factors in winning featured snippets, which occupy the most prominent SERP position.
Not every page with schema gets a rich result. Google treats structured data as a signal, not a guarantee. But without schema, you are never eligible. The markup is table stakes.
The Schema Types That Matter
1. FAQPage
What it looks like: Expandable question-and-answer pairs directly in the search result. Each question is clickable, revealing the answer inline without visiting your page.
Why it matters: FAQ rich results dramatically expand your SERP real estate. A listing with three or four FAQ items can take up as much vertical space as two or three normal results, pushing competitors further down the page.
Required properties:
mainEntity: An array of Question items
Each Question needs name (the question text) and acceptedAnswer with text (the answer)
ChatGPT for SEO strategy means using the model to accelerate the research, analysis, and planning stages of SEO, not to replace the strategic thinking that makes a plan worth executing. You can build a complete quarterly SEO plan in a few hours instead of a fe
An Ahrefs alternative is any SEO tool that covers keyword research, site auditing, or competitive analysis without requiring an Ahrefs subscription. AI-native alternatives like Ooty SEO connect directly to your AI assistant via MCP, replacing the dashboard wor
AI for SEO means using large language models and machine learning tools to handle repeatable SEO tasks faster: keyword clustering, content briefs, technical audits, competitor analysis, schema generation, internal link mapping, and reporting. The practical val
Implementation notes: The questions and answers in your schema must be visible on the page. Google will not show FAQ rich results for hidden content. Keep answers concise in the markup, even if the on-page answer is more detailed. Google truncates long answers in the SERP.
Best for: Service pages, product pages, and informational content where users commonly have specific questions.
2. Article and BlogPosting
What it looks like: Enhanced listings in Google News, Top Stories carousel, and Discover. Can include the article image, publication date, and author information.
Why it matters: Article schema is particularly valuable for publishers and content-heavy sites. It helps Google understand your content's freshness, authorship, and topic, which feeds into news and Discover placements.
Required properties:
headline: The article title
image: At least one image (Google recommends multiple sizes)
datePublished: Publication date in ISO 8601 format
author: The author's name and URL
Recommended properties:
dateModified: When the article was last updated
publisher: Organization name and logo
description: A summary of the article
Implementation notes: Use BlogPosting for blog content and NewsArticle for news. The author property should point to a real person or organization page. Google increasingly uses author information for E-E-A-T assessment.
3. Product
What it looks like: Price, availability, review rating, and review count displayed directly in the search listing. Can also show shipping information and return policies.
Why it matters: Product rich results put buying-decision information right in the SERP. A listing showing "$49.99, 4.6 stars, 238 reviews, In Stock" converts clicks into purchases far more effectively than a plain blue link.
Required properties:
name: Product name
image: Product image
At least one of: review, aggregateRating, or offers
Implementation notes: Prices in the schema must match prices on the page. Mismatches will result in manual actions. If your price varies (by size or configuration), use AggregateOffer with lowPrice and highPrice. Review data must come from genuine customer reviews on your site, not imported from third parties.
4. LocalBusiness
What it looks like: Enhanced Knowledge Panel in search results, improved Google Maps listing, and potential placement in the Local Pack.
Why it matters: For any business with a physical location, LocalBusiness schema reinforces the information in your Google Business Profile and strengthens your local search presence. It connects your website to your map listing.
Required properties:
name: Business name (must match your GBP exactly)
address: Full postal address using PostalAddress type
telephone: Phone number
Recommended properties:
openingHoursSpecification: Days and times you are open
geo: Latitude and longitude coordinates
image: Business photos
priceRange: General price level (e.g., "$$")
url: Website URL
Implementation notes: Use the most specific subtype available. Instead of generic LocalBusiness, use Restaurant, Dentist, Plumber, LegalService, or whichever specific type matches. Google uses this for category matching. Hours should be accurate and updated for holidays. For more on local ranking factors, see our local SEO guide.
5. BreadcrumbList
What it looks like: A breadcrumb trail replacing the URL in search results. Instead of seeing example.com/products/shoes/running, users see "Home > Products > Shoes > Running."
Why it matters: Breadcrumbs make your listing more readable and give searchers context about your site structure. They also help Google understand your site hierarchy, which can improve crawling and indexing.
Required properties:
itemListElement: An array of ListItem objects
Each ListItem needs position (numeric order), name (label), and item (URL)
Implementation notes: The breadcrumb schema should match the visible breadcrumbs on your page. Every page above the current one in the hierarchy should be included. The last item (the current page) can omit the item URL.
Best for: Every site with hierarchical navigation. This is one of the easiest schema types to implement and has near-universal applicability.
6. HowTo
What it looks like: A step-by-step guide displayed directly in search results, with numbered steps, images for each step, and estimated time and materials.
Why it matters: HowTo rich results are extremely prominent in search. They can show a visual, multi-step guide without the user needing to click through to your site. While this can reduce clicks for simple queries, it builds massive brand visibility and trust.
Required properties:
name: Title of the how-to guide
step: An array of HowToStep items, each with text describing the step
Recommended properties:
totalTime: How long the entire process takes (ISO 8601 duration)
estimatedCost: Approximate cost
supply: Materials needed
tool: Tools required
image on each step: Visual for that specific step
Implementation notes: Each step should be a distinct, standalone instruction. Do not lump multiple actions into one step. Images per step significantly increase the likelihood of Google showing the rich result.
Best for: Tutorial content, DIY guides, recipes (though Recipe has its own schema type), and any instructional content.
7. Event
What it looks like: Event name, date, time, location, and ticket information displayed in search results. Events can also appear in Google's Events experience.
Why it matters: Event schema helps your events surface in Google's event search features, which pull from structured data across the web. For event organizers, venues, and ticketing platforms, this is a significant discovery channel.
Required properties:
name: Event name
startDate: Start date and time in ISO 8601
location: Where the event takes place (physical Place or VirtualLocation)
Recommended properties:
endDate: When the event ends
description: What the event is about
image: Event image
offers: Ticket pricing and availability
performer: Who is performing or presenting
organizer: Who is hosting
Implementation notes: Events must have a specific start date in the future (or very recent past). Ongoing events without specific dates do not qualify. Virtual events should use VirtualLocation with the url of the stream or meeting.
8. Recipe
What it looks like: A rich recipe card in search results with an image, rating, cook time, calorie count, and sometimes a carousel of recipe steps.
Why it matters: Recipe is one of the most mature and visually prominent rich result types. Food and cooking queries almost always show recipe cards, and listings without them are buried.
Required properties:
name: Recipe name
image: Photo of the finished dish
recipeIngredient: List of ingredients
recipeInstructions: Step-by-step instructions
Recommended properties:
cookTime and prepTime: In ISO 8601 duration format
nutrition: Calorie and nutrient information
aggregateRating: User ratings
author: Who created the recipe
recipeYield: Number of servings
recipeCategory: Meal type (dinner, dessert, etc.)
recipeCuisine: Cuisine type (Italian, Mexican, etc.)
Implementation notes: Recipe schema is strictly for recipe content. Do not use it on non-recipe pages hoping for rich results. Google actively monitors for misuse. High-quality images significantly improve your chances of getting the visual recipe card.
Priority Ranking: Which Types to Implement First
Not all schema types deliver equal value. Here is a practical priority ranking based on implementation effort vs. CTR impact.
High priority (implement immediately):
BreadcrumbList on every page. Minimal effort, universal benefit.
FAQPage on service and product pages. Large SERP real estate gain.
Article/BlogPosting on all editorial content. Required for news and Discover eligibility.
Medium priority (implement when relevant):
4. Product on all product pages. Essential for e-commerce.
5. LocalBusiness on your homepage or contact page. Essential for local businesses.
6. HowTo on tutorial content. High visibility when triggered.
Lower priority (implement when you have the content):
7. Event on event pages. Important for event businesses, less relevant otherwise.
8. Recipe on recipe pages. Critical for food sites, irrelevant for everyone else.
Common Schema Mistakes
Missing required properties. Google will simply not generate a rich result if required fields are missing. Always validate before deploying.
Data mismatches. The structured data must match the visible content on the page. If your schema says the product costs $29 but the page shows $39, Google will penalize this with a manual action.
Using schema on irrelevant pages. Adding FAQPage schema to a page without any questions and answers, or Product schema on a blog post, violates Google's guidelines. Schema should describe the content that actually exists on the page.
Duplicate schema types. Having two FAQPage schemas on the same page, or conflicting Product schemas, confuses Google. One schema block per type per page.
Not keeping schema updated. Prices change, hours change, events end. Stale schema data triggers warnings in Search Console and can lead to rich result removal.
Testing and Validation
Google provides two official testing tools:
Rich Results Test (search.google.com/test/rich-results): Tests whether your page is eligible for rich results and shows exactly what Google can extract from your structured data.
Schema Markup Validator (validator.schema.org): Validates your markup against the full schema.org specification, not just Google's subset.
For a faster workflow, you can run your pages through Ooty's free schema validator, which checks both schema.org compliance and Google's rich result requirements in a single pass. It flags missing recommended properties that the official tools do not always surface.
Implementation Approaches
There are three ways to add schema to your pages:
JSON-LD (recommended). A script block in the page head or body containing the structured data in JSON format. This is Google's preferred method because it separates the data from the HTML and is easier to maintain.
Microdata. HTML attributes added directly to your existing markup. This is more fragile because it ties the structured data to your HTML structure. Changes to the layout can break the schema.
RDFa. Similar to microdata but uses a different attribute syntax. Rarely used for SEO purposes today.
Use JSON-LD. It is the standard, it is the easiest to implement and debug, and it is what Google recommends.
Monitoring in Search Console
After deploying schema, monitor the Enhancements section in Google Search Console. Each supported schema type gets its own report showing:
How many pages have valid structured data
How many have errors (which prevent rich results)
How many have warnings (which may limit rich results)
Fix errors first. Then address warnings. Check this report monthly. Schema issues can appear when pages are updated, templates change, or content management systems push updates that break the markup.
Structured data is not glamorous work, but it is one of the highest-ROI activities in SEO. The sites that implement it correctly get more visible, more clickable listings in search results. The ones that skip it leave that advantage to competitors.
For a broader look at what else to check on your site, our SEO audit checklist walks through 40 items across technical, on-page, and off-page SEO, including structured data validation.
