Schema markup is structured data code added to web pages to help Google understand page context and qualify content for rich results such as products, reviews, events, breadcrumbs, local business details, videos, and articles. In 2026, the best schema type depends on the page type: LocalBusiness for local pages, Product and AggregateRating for ecommerce, Article or BlogPosting for content pages, Event for event pages, Person or Physician for professional profiles, and BreadcrumbList for site hierarchy. Use JSON-LD, Google’s recommended and easiest-to-maintain format.
Schema markup is one of the most practical technical SEO opportunities for websites in 2026. Businesses implementing structured data should also follow a broader technical SEO complete guide to improve crawlability, indexing, and overall site architecture. Many businesses add basic Organization or LocalBusiness schema and stop there, but the real value comes from matching the right structured data to the right page. This schema markup types complete guide 2026 explains which schema belongs on homepages, service pages, product pages, blogs, local landing pages, events, FAQs, and professional profile pages.
Key Takeaways
- Implement schema in JSON-LD format because Google recommends it as the easiest format to maintain.
- Use the LocalBusiness schema for physical businesses, service-area businesses, and local landing pages.
- Use Product, Offer, Review, and AggregateRating schema for ecommerce pages.
- Use Article or BlogPosting schema for blogs, guides, and editorial content.
- Use the FAQPage carefully because FAQ rich results are no longer appearing in Google Search as of May 7, 2026.
- Use the BreadcrumbList schema to clarify page hierarchy and improve search understanding.
- Test every implementation with Google’s Rich Results Test and Schema Markup Validator before publishing.
What Is Schema Markup and Why It Matters in 2026
Schema markup is a structured data vocabulary that helps search engines understand what a page is about. Instead of forcing Google to interpret raw page content alone, schema gives direct clues about the page’s entity, topic, author, product, location, price, review, event, or business details.
Schema.org is much larger than Google’s rich result system. The current Schema.org vocabulary includes hundreds of types and thousands of properties, but not every valid schema type produces a Google rich result. That difference matters. A schema can be technically valid and still not create a visible search enhancement.
In 2026, schema matters for three reasons. First, it helps search engines understand page context. Second, it makes pages eligible for supported rich results. Third, it gives AI-driven search systems cleaner entity and answer signals to interpret. Google’s official position is still clear: structured data helps Google understand page content and may power richer search appearances, but it must follow quality guidelines and match visible page content.
The best answer to how to add schema markup to website pages is simple: use JSON-LD. Google supports JSON-LD, Microdata, and RDFa, but JSON-LD is recommended because it is easier to add, update, troubleshoot, and scale across templates. Before deployment, validate implementation against a technical SEO checklist to avoid indexing or structured data errors.
A basic JSON-LD block looks like this:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Company",
"url": "https://www.example.com",
"logo": "https://www.example.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/example",
"https://www.facebook.com/example"
]
}
</script>
You can place JSON-LD in the <head> or <body> of a page. The important point is accuracy. Do not mark up content that is hidden from users. Do not add fake reviews. Do not use an irrelevant schema just because a competitor uses it. The structured data guidelines from Google make it very clear that poor quality or irrelevant structured data can make it impossible for rich results to display.
LocalBusiness Schema — For Every Local Page
If your business has a physical address or service area, then you need to use the LocalBusiness schema. It enables search engines to comprehend the business name, address, phone number, opening hours, geo coordinates, service area, nature of the business, and website URL.
Apply local business schema to these:
- Homepage
- Contact page
- Location landing pages
- Service-area pages
- Store pages
- Clinic, office, branch, or franchise pages
Example:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Plumbing Services",
"image": "https://www.example.com/plumbing-team.jpg",
"url": "https://www.example.com",
"telephone": "+1-555-123-4567",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "Dallas",
"addressRegion": "TX",
"postalCode": "75201",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "32.7767",
"longitude": "-96.7970"
},
"openingHours": "Mo-Fr 08:00-18:00",
"areaServed": {
"@type": "City",
"name": "Dallas"
}
}
</script>
If you have more than one location, make a unique LocalBusiness schema for each location page. Avoid repeating the address schema on all city pages when the business doesn't have a physical presence in the city.
FAQPage Schema — The AI Overview Feed
FAQ content is still useful, but faq schema markup needs careful framing in 2026. Google’s FAQ documentation now says that as of May 7, 2026, FAQ rich results are no longer appearing in Google Search. Google will remove the FAQ search appearance, rich result report, and Rich Results Test support in June 2026, with Search Console API support ending in August 2026.
That means the FAQPage schema should not be sold as a way to win FAQ dropdowns in Google Search. Rather, use it to formulate questions and answers comprehensible to users and for machine understanding.
Example:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is schema markup?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema markup is structured data code that helps search engines understand the meaning and context of a web page."
}
},
{
"@type": "Question",
"name": "Which schema format is best?",
"acceptedAnswer": {
"@type": "Answer",
"text": "JSON-LD is the recommended format because it is easier to implement and maintain."
}
}
]
}
</script>
Only use FAQPage if there is FAQ content visible on the page. Don't overload the page with a hundred or more general questions at the end of each page.
Article and BlogPosting Schema — For Content Pages
Article and BlogPosting schema are suitable for blogs, news updates, guides, research pages, opinion pieces and editorial resources. These schema types contribute to defining a headline, an author, a publisher, an image, date published, date modified, and the main content entity. Structured content performs better when paired with a strong header tags SEO guide 2026 strategy that improves topical hierarchy and content clarity.
Use Article schema for:
- Blog posts
- News articles
- SEO guides
- Research articles
- Thought leadership pages
- Industry updates
Example fields to include:
- headline
- description
- image
- author
- publisher
- datePublished
- dateModified
- mainEntityOfPage
For E-E-A-T, the author should not be an empty name. Add a real Person entity where possible, then connect it to an author profile page, sameAs links, job title, credentials, or organization. This is especially important for finance, legal, healthcare, technical, and professional advice content.
Product and AggregateRating Schema — For E-Commerce
Product schema markup is one of the most valuable ecommerce schema types. Google’s supported Product structured data can show product information such as price, availability, and review ratings in search results.
For broader product-page optimization strategies, businesses should also follow an e-commerce SEO complete guide covering category structure, internal linking, and product-page SEO.
To use Product schema on:
- Product detail pages
- Product variant pages
- Software product pages
- Digital product pages
- Bookable product pages
- Marketplace listings
Product, Offer, AggregateRating, Review, and Brand schema are all common elements of a good ecommerce page.
Example:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Wireless Security Camera",
"image": "https://www.example.com/camera.jpg",
"description": "A smart wireless security camera with night vision and motion alerts.",
"sku": "CAM-1001",
"brand": {
"@type": "Brand",
"name": "SecureView"
},
"offers": {
"@type": "Offer",
"url": "https://www.example.com/wireless-security-camera",
"priceCurrency": "USD",
"price": "129.99",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.7",
"reviewCount": "128"
}
}
</script>
If ratings are not real, visible and from users, they should not be added. Structured data quality can be caused by fake or hidden ratings.
Person and Physician Schema — For Professional Sites
Person schema works well for a variety of professionals including author pages, experts, founders, consultants, lawyers, doctors, accountants, coaches, and public-facing persons. Physician schema is more specific, and should only be used when the page is clearly a medical page, in the context of a medical professional.
Healthcare businesses implementing Physician schema should also review this medical SEO guide 2026 for E-E-A-T, local visibility, and healthcare-specific optimization strategies.
Person/Physician schema on:
- Doctor profile pages
- Lawyer profile pages
- Author pages
- Consultant pages
- Leadership pages
- Expert contributor pages
Useful properties include:
- name
- jobTitle
- worksFor
- alumniOf
- affiliation
- knowsAbout
- sameAs
- medicalSpecialty, where relevant
- url
- image
In the healthcare industry, by helping to establish expertise, specialization, and affiliation, the Physician schema can complement E-E-A-T. Nonetheless, schema will not substitute actual trust signals like qualifications, review quality, medical accuracy, citations and transparent editorial review.
Event Schema — For Events and Ticketed Experiences
Event schema is designed for pages promoting concerts, webinars, workshops, conferences, meetups, festivals, classes, and ticketed experiences. Google’s search gallery lists Event as a supported structured data feature that can show organized events in rich results.
Use the Event schema for the page that contains:
- Event name
- Start date
- End date
- Location or virtual event URL
- Ticket or registration offer
- Organizer
- Event status
- Event attendance mode
Use eventAttendanceMode to specify if the event is online, offline or mixed. Use the eventStatus when the event is postponed, canceled, rescheduled or moved online.
BreadcrumbList Schema — For Every Page
BreadcrumbList schema is used to communicate with the search engine the context of a page within a site’s hierarchy. It's helpful for nearly any page that is indexable, except for one-page websites.
Example:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.example.com"
},
{
"@type": "ListItem",
"position": 2,
"name": "SEO Services",
"item": "https://www.example.com/seo-services"
},
{
"@type": "ListItem",
"position": 3,
"name": "Technical SEO",
"item": "https://www.example.com/seo-services/technical-seo"
}
]
}
</script>
Breadcrumb schema is easy to implement and beneficial for content structure. It provides search systems with cleaner hierarchies, even if the rich result display evolves over time.
HowTo and Recipe Schema — For Instructional Content
HowTo or Recipe schema are used for the description of step-by-step instructions pages or recipes, respectively.
If using the HowTo schema for:
- DIY guides
- Repair steps
- Setup tutorials
- Installation walkthroughs
- Process-based instructional pages
For use with Recipe schema use:
- Cooking blogs
- Food publisher pages
- Recipe databases
- Nutrition-focused food content
But in 2026, HowTo should not be viewed as a huge opportunity for Google because of its large numbers. HowTo rich results had been reduced and eventually scrapped from Google search previously. Use it where appropriate and in line with the page's architecture and not for the sake of something ranking. In addition, Google has simplified less popular rich results in its search results and reporting in Search Console, dropping support for some types of structured data.
Schema Types by Page — Quick Reference Table
| Page Type |
Recommended Schema Types |
Main Benefit |
| Homepage |
Organization, WebSite, WebPage |
Defines brand entity, logo, social profiles, and official website |
| About Page |
AboutPage, Organization, Person |
Builds trust and explains brand background |
| Contact Page |
ContactPage, Organization, PostalAddress, ContactPoint |
Clarifies contact and location details |
| Service Page |
Service, Organization, LocalBusiness, FAQPage |
Defines the service, provider, and user questions |
| Local Landing Page |
LocalBusiness, Service, Place, BreadcrumbList |
Supports local relevance and service-area clarity |
| Blog Post |
BlogPosting, Article, Person, BreadcrumbList |
Defines author, headline, date, and topic |
| News Article |
NewsArticle, ImageObject, Person, Organization |
Supports editorial and timely content understanding |
| Product Page |
Product, Offer, AggregateRating, Review, Brand |
Enables product details, price, availability, and ratings |
| Product Category Page |
CollectionPage, ItemList, BreadcrumbList |
Explains grouped products and page hierarchy |
| FAQ Page |
FAQPage |
Structures visible questions and answers, but no Google FAQ rich result after May 7, 2026 |
| Q&A Page |
QAPage, Question, Answer |
Best for pages with one question and multiple user answers |
| Video Page |
VideoObject |
Helps Google understand video content, thumbnail, duration, and clips |
| Event Page |
Event, Offer, Place, Organization |
Supports event discovery and ticket visibility |
| Recipe Page |
Recipe, NutritionInformation, AggregateRating |
Adds recipe details such as ingredients, time, nutrition, and ratings |
| Job Page |
JobPosting, Organization, Place |
Supports job listing visibility |
| Course Page |
Course, CourseInstance, Organization |
Defines course provider, title, and learning details |
| Author Profile |
ProfilePage, Person |
Strengthens expert identity and author trust |
| Medical Profile |
Physician, Person, MedicalOrganization |
Clarifies healthcare expertise and specialty |
| Software Page |
SoftwareApplication, Offer, AggregateRating |
Supports app details, price, rating, and platform |
| Real Estate Page |
Accommodation, Place, Offer |
Clarifies property, rental, or accommodation details |
Common Schema Mistakes to Avoid
The most serious schema problem is to insert extra markups not found on the page. Google has guidelines for quality, and they prohibit the following from being displayed: hidden content, misleading content, fake reviews, irrelevant markup, and incorrect structured data.
There are some common errors, such as:
- Adding the LocalBusiness schema to each page that has different fake locations
- Using Product schema on a service page
- Adding AggregateRating without displaying reviews
- Remembering the sight, cost, or availability of products on pages, etc.
- When you do not publish news and you mark your blog posts as NewsArticle, it will be ignored.
- If there are no FAQs available online, add FAQPage markup.
- Employing old schema types as a key SEO strategy
- Avoid ignoring warnings in Search Console after deployment.
The schema should make the page clearer, not more complicated. Large websites often rely on technical SEO services to audit structured data issues, fix markup conflicts, and maintain compliance with Google’s structured data guidelines.
Conclusion
A schema markup guide for 2026 isn't about using as many schema types as you can on every page. It is the art of choosing the right markup for the intended use. All local businesses must have the LocalBusiness and Service schema. It is important that ecommerce websites include the product schema, offer schema, review schema and aggregateRating schema. Blogs must have an Article or BlogPosting schema. A person or Physician schema is needed for professional sites. Well-structured, accurate and visible data should be present on all relevant pages to help search engines and AI to understand the confidence of the page.
