Schema Markup Examples: 7 Types That Work in 2026
Key Takeaways
- Schema markup does not guarantee rich results but significantly increases the chance of being selected for enhanced SERP features, including AI Overviews.
- JSON-LD is the preferred format for all schema types because it separates code from content and is easier to maintain.
- The most high-impact schemas for 2026 are FAQPage, HowTo, and Product because they directly answer user questions — a core signal for AI Overviews.
- Every schema must be tested in Google’s Rich Results Test before publishing. Errors or warnings can block eligibility.
- Schema alone is not a ranking factor. It helps with visibility, click-through rates, and eligibility for enhanced search features.
- Use the “Article” schema for blogs, news, and guides. Do not use it for product pages or local business pages — use Product or LocalBusiness instead.
Table of Contents
- Introduction
- 1. Article Schema Example
- 2. FAQPage Schema Example
- 3. HowTo Schema Example
- 4. Product Schema Example
- 5. BreadcrumbList Schema Example
- 6. LocalBusiness Schema Example
- 7. Review Schema Example
- Schema Comparison Table
- Common Mistakes When Using Schema Markup
- Schema Implementation Checklist
- How This Applies in Practice
- Frequently Asked Questions
- Article Summary
- Conclusion
Introduction
Schema markup examples are everywhere, but most lists show outdated code or unrealistic scenarios. If you’re an SEO or content manager trying to improve how your pages appear in search results — especially in AI Overviews — you need examples that work today.
This article covers 7 schema types that are actively supported by Google Search Central and Schema.org as of mid-2026. Each example includes the JSON-LD code, a real use case, and a placement tip. You’ll also learn which schemas to skip and how to test everything before going live.
1. Article Schema Example
The Article schema tells Google that a page is a news article, blog post, or editorial piece. It helps with rich results like top stories carousels and headline display improvements.
When to use Article schema
Use Article schema for any page that is a blog post, news article, or in-depth editorial guide. Do not use it for product pages, landing pages, or category pages — those need different schema types.
The code
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Schema Markup Examples: 7 Types That Work in 2026",
"author": {
"@type": "Person",
"name": "Your Name"
},
"datePublished": "2026-06-24",
"image": "https://example.com/image.jpg",
"description": "See 7 schema markup examples that actually work in 2026."
}
Placement tip
Place this inside a <script type="application/ld+json"> tag in the <head> or near the end of the <body>. Google prefers it in the head section. Always include at least headline, datePublished, and author.
2. FAQPage Schema Example
FAQPage schema marks up a list of questions and answers. This is one of the most effective schemas for AI Overview optimization because it directly answers user queries with structured Q&A content.
When to use FAQPage schema
Only use FAQPage if the page contains a real FAQ section with clear questions and answers. Do not use it for single questions or non-FAQ content. Google’s guidelines require the content to be visible to users — not hidden behind tabs or accordions.
The code
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is schema markup?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema markup is structured data added to HTML to help search engines understand page content."
}
},
{
"@type": "Question",
"name": "Does schema markup help SEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema markup helps with rich result eligibility and click-through rates, but is not a direct ranking factor."
}
}
]
}
Placement tip
Place the entire FAQPage block in a single script tag in the head. Each Q&A pair must be visible on the page exactly as written in the schema — mismatched content can cause validation errors.
3. HowTo Schema Example
HowTo schema marks up step-by-step instructions. It generates rich results that show step previews directly in SERPs, which is ideal for tutorials, recipes, guides, and workflows.
When to use HowTo schema
Use HowTo for any page that explains a multi-step process. This includes cooking recipes, software tutorials, assembly guides, and even onboarding flows. Each step must be clearly numbered and visible on the page.
The code
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Add Schema Markup to HTML",
"step": [
{
"@type": "HowToStep",
"position": 1,
"name": "Choose your schema type",
"text": "Decide which schema type matches your content. Use Article for blogs, Product for items, and so on."
},
{
"@type": "HowToStep",
"position": 2,
"name": "Generate the JSON-LD code",
"text": "Use Schema.org’s documentation or a generator tool to create valid JSON-LD."
},
{
"@type": "HowToStep",
"position": 3,
"name": "Test with Google Rich Results Test",
"text": "Paste your code into the Rich Results Test to check for errors."
}
]
}
Placement tip
Include a totalTime and image when possible — these improve eligibility for step previews in search results. Keep step descriptions concise and under 150 characters each for best visibility.
4. Product Schema Example
Product schema marks up ecommerce products with details like price, availability, and ratings. It can generate product rich results that show pricing directly in search results.
When to use Product schema
Use Product schema on individual product pages, not on category or listing pages. Include at least name, description, offers (with price and currency), and image.
The code
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Wireless Headphones Pro X",
"description": "Noise-canceling wireless headphones with 30-hour battery life.",
"image": "https://example.com/headphones.jpg",
"offers": {
"@type": "Offer",
"priceCurrency": "USD",
"price": "89.99",
"availability": "https://schema.org/InStock"
}
}
Placement tip
Keep the price and availability data synced with your actual inventory. Outdated pricing in schema can result in warnings from Google Search Console. Use dynamic generation for this schema type rather than hardcoding.
5. BreadcrumbList Schema Example
BreadcrumbList schema marks up navigation breadcrumbs. It helps Google show a breadcrumb path in search results, which improves click-through rates and user understanding of page hierarchy.
When to use BreadcrumbList schema
Use this on any page that has visible breadcrumb navigation. This is especially useful for ecommerce sites, large content sites, and any site with deep page hierarchy.
The code
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com"
},
{
"@type": "ListItem",
"position": 2,
"name": "Products",
"item": "https://example.com/products"
},
{
"@type": "ListItem",
"position": 3,
"name": "Wireless Headphones",
"item": "https://example.com/products/headphones"
}
]
}
Placement tip
Make sure the schema breadcrumbs match the visible breadcrumbs on the page exactly. Mismatched URLs between schema and actual navigation can confuse crawlers and reduce eligibility.
6. LocalBusiness Schema Example
LocalBusiness schema tells Google about a physical business — its name, address, phone number, opening hours, and more. It is essential for local SEO and can generate local rich results with map pins and contact info.
When to use LocalBusiness schema
Use LocalBusiness schema on the homepage or contact page of any business with a physical location. Do not use it for online-only businesses — use Organization schema instead.
The code
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Downtown Bookstore",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "Portland",
"addressRegion": "OR",
"postalCode": "97201"
},
"telephone": "+1-503-555-0142",
"openingHours": "Mo-Fr 09:00-18:00",
"image": "https://example.com/bookstore.jpg"
}
Placement tip
Include openingHours and telephone — these are the most commonly displayed fields in local rich results. Use the same NAP (name, address, phone) across all directories to maintain consistency.
7. Review Schema Example
Review schema marks up user reviews and ratings for products, services, or content. It can generate review snippets in search results with star ratings.
When to use Review schema
Use Review schema when a page contains a single review of a product, book, movie, or service. Do not use it for aggregate ratings alone — use AggregateRating (nested inside Product schema) for that purpose.
The code
{
"@context": "https://schema.org",
"@type": "Review",
"itemReviewed": {
"@type": "Product",
"name": "Wireless Headphones Pro X"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": 4.5,
"bestRating": 5
},
"author": {
"@type": "Person",
"name": "Jane Doe"
}
}
Placement tip
Always include the actual review text and author information in the visible page content. Google may verify that the schema matches visible content. Hide reviews behind tabs at your own risk — they may not qualify.
Schema Comparison Table
| Schema Type | Best For | Rich Result Type | Complexity | AI Overview Relevance |
|---|---|---|---|---|
| Article | Blog posts, news, guides | Top stories, headline enhancements | Low | Medium |
| FAQPage | FAQ sections, Q&A content | FAQ rich results | Low | High |
| HowTo | Tutorials, recipes, workflows | Step previews | Medium | High |
| Product | Ecommerce product pages | Product rich results with pricing | Medium | Medium |
| BreadcrumbList | Navigation hierarchy | Breadcrumb paths | Low | Low |
| LocalBusiness | Physical businesses | Local rich results with map pins | Medium | Low |
| Review | Single reviews | Star ratings and snippets | Low | Medium |
Common Mistakes When Using Schema Markup
Even experienced SEOs make these errors. Avoid them to prevent schema markup from being ignored or causing errors.
- Using multiple schema types on one page incorrectly — You can combine types (e.g., Product + Review), but do not use Article and Product on the same page. Google will treat them as conflicting signals.
- Hiding schema content from users — Google’s guidelines require schema content to be visible and accessible. Accordion or tabbed content may not qualify.
- Copying schema from other sites without adaptation — Schema must match your actual page content. Copying someone else’s schema with different details causes validation failures.
- Not testing before publishing — Always run the Rich Results Test. Even one missing required field can disqualify the entire schema.
- Using outdated schema properties — Schema.org updates types and properties. For example,
ratingValuein Review requiresbestRating. Missing it is a common error.
Schema Implementation Checklist
- [ ] Choose only one schema type for the page’s primary content.
- [ ] Generate JSON-LD code using Schema.org or a trusted generator.
- [ ] Ensure all required properties are included (check Schema.org documentation for the specific type).
- [ ] Verify that schema content matches visible page content.
- [ ] Test with Google Rich Results Test.
- [ ] Fix all errors and warnings before publishing.
- [ ] Add schema script tag to the
<head>section. - [ ] Monitor Google Search Console for schema-related issues after indexing.
- [ ] Review schema quarterly for outdated or inaccurate information.
- [ ] If using HowTo or Recipe, include images for each step.
How This Applies in Practice
The same schema markup does not work the same way for every website. Here is how the advice changes depending on your situation.
For a beginner website
Start with Article schema for blog posts and BreadcrumbList for navigation. These are low-complexity and provide visible improvements without risk. Avoid Product or LocalBusiness until you have a clear use case.
For a SaaS website
Focus on Article for blog content, FAQPage for support or product FAQ sections, and HowTo for onboarding guides. Avoid Product schema unless you sell physical items. Use Organization schema for the homepage.
For an ecommerce store
Product schema is your priority. Add it to every product page with accurate pricing and availability. Use BreadcrumbList for category navigation. Do not use FAQPage on product pages — use it on a separate FAQ page.
For a local business
LocalBusiness schema on the homepage is essential. Include opening hours, address, and phone. Use Article schema for any blog posts. Avoid Product schema unless you sell physical goods online.
Frequently Asked Questions
What is the easiest schema markup to start with?
Article schema is the easiest to implement. It requires only a few properties (headline, datePublished, author) and works for most blog or news content. You can generate it manually or use a plugin if you are on WordPress with a schema plugin like Yoast or Rank Math. Always test with the Rich Results Test after adding it to ensure no errors. If you want a quick win, Article schema takes about 10 minutes to implement and test.
Does schema markup guarantee I will get rich results?
No. Schema markup makes your page eligible for rich results, but Google decides whether to show them based on content quality, relevance, and user intent. You could have perfect schema and still not get rich results if your content does not match what users are looking for. The best approach is to combine schema with high-quality, well-structured content that directly answers the searcher’s question. Monitor Google Search Console to see if your pages are generating impressions with rich result enhancements.
Can I use FAQPage schema if my FAQ is hidden behind an accordion?
Google’s guidelines state that FAQPage content must be visible to users without requiring interaction like clicking or scrolling an accordion. If the content is hidden and not immediately visible, it may not qualify for FAQ rich results. If you must use an accordion for design reasons, ensure that the content is still accessible and indexed — but know that eligibility is not guaranteed. Many sites lose FAQ rich results after updates because their content was hidden or mismatched.
What is the difference between schema markup and microdata?
Schema markup is the vocabulary (the types and properties defined by Schema.org). Microdata and JSON-LD are formats for implementing that vocabulary. JSON-LD is the recommended format because it keeps schema code separate from HTML, making it easier to maintain and less likely to break during content updates. Microdata and RDFa are older formats that embed schema directly into HTML attributes. JSON-LD is preferred by Google and easier to test.
How often should I update my schema markup?
Review your schema markup at least once per quarter. Update it whenever you change page content, add new products, update pricing, or change business hours. Stale schema — such as old prices in Product schema or outdated FAQ answers — can cause warnings in Google Search Console. If Google detects inaccurate schema, it may ignore the entire markup on that page. Set a recurring quarterly reminder to audit schema across your site.
Can schema markup help with AI Overviews?
Yes, indirectly. AI Overviews pull information from well-structured, authoritative content. Schema markup helps Google understand the structure of your content, which can improve the likelihood of your content being used as a source. FAQPage and HowTo schemas are especially useful because they directly match the question-and-answer format that AI Overviews display. However, schema alone is not enough — your content must also be clear, accurate, and written for the user’s intent. Think of schema as the foundation, not the entire strategy.
Article Summary
This article covered 7 schema markup examples that work in 2026 — Article, FAQPage, HowTo, Product, BreadcrumbList, LocalBusiness, and Review. Each example included the JSON-LD code, a use case, and a placement tip. You learned common mistakes to avoid, a 10-point implementation checklist, and how to apply schema differently for beginners, SaaS sites, ecommerce stores, and local businesses. The key takeaway is that schema helps with eligibility for rich results and AI Overviews, but only if your content is high-quality, accurate, and user-focused.
Useful Tool for This Task
If you want to create valid structured data for this topic, use the SMARTCHAINE Schema Markup Generator to build JSON-LD markup for your website.
Conclusion
Schema markup examples are not just code snippets — they are tools for communicating with search engines. Used correctly, they increase your content’s chances of being selected for rich results and AI Overviews. Used incorrectly, they waste time and can cause indexing warnings.
The seven examples in this article cover the most common and effective schema types for 2026. Start with the type that matches your primary content, test it, and monitor results. Then expand to other types as needed.
No schema markup will fix poor content. But good schema on good content is one of the most reliable ways to improve visibility in modern search.
Recommended Resources
- Google Search Central — Official documentation on structured data and rich results.
- Schema.org — The complete schema vocabulary with all types and properties.
- Google Search Console — Use this to monitor schema errors and rich result performance.
- Ahrefs Blog — Practical SEO guides including schema markup deep dives.
- Moz Blog — Community-tested advice on schema implementation and testing.
About the Author
The SMARTCHAINE Editorial Team specializes in SEO, AI Search Optimization, GEO (Generative Engine Optimization), AI Overviews, Structured Data, Technical SEO, and search visibility strategies for modern search engines and AI-powered discovery platforms.