Schema Markup Types: The Top 10 You Need to Know
Currently contains more than 800 schema types. So choosing the right one can feel overwhelming. Most businesses, publishers and ecommerce websites will never need to use all of them. In fact, a carefully selected group of schema markup types can cover nearly every important page on a typical website.
The real challenge is not finding a long alphabetical list. It is understanding which schema markup types support your content, search visibility, brand entities, rich results and emerging AI search experiences.
This guide ranks the 10 most practical schema markup types for 2026 and explains where, why and how each one should be used.
What Is Schema Markup and How Many Types Are There?
Schema markup is structured data code that explains the meaning and relationships of information on a webpage. It usually uses the Schema.org vocabulary and is commonly added through JSON-LD. Schema.org currently lists 823 types and 1,529 properties.
For example, normal webpage text may show a product name, price, rating, and stock status. A human visitor can understand those details from the page design. A search engine, however, may need additional help identifying which number is the price, which text is the product name, and whether the item is available.
Product schema provides those explicit labels.
Schema.org includes types for products, articles, organizations, people, recipes, events, local businesses, videos, job postings, books, software, courses, reviews, medical information and hundreds of other subjects.
However, the existence of a Schema.org type does not automatically mean Google will use it for a rich result. Schema.org defines the vocabulary, while Google separately determines which structured-data features it supports in Search.
What Is the Difference Between Schema Markup and Structured Data?
Structured data is the general method of organizing information in a machine-readable format. Schema markup is the vocabulary commonly used to describe that information on websites.
The two terms are often used interchangeably in SEO conversations, but they are not exactly the same.
Structured data is the broader concept. It can describe any standardized system used to organize data for machines. Schema markup normally refers to structured data written with the Schema.org vocabulary.
Think of structured data as the language system and Schema.org as the agreed dictionary of words and definitions used within that system.
What Is the Difference Between JSON-LD, Microdata, and RDFa?
JSON-LD, Microdata, and RDFa are three supported formats for placing structured data on a webpage. Google recommends JSON-LD in most situations because it is easier to implement, maintain and troubleshoot.
JSON-LD is normally placed inside a separate <script type=”application/ld+json”> element. It does not need to be mixed directly into the visible content.
Microdata adds properties to existing HTML elements through attributes such as itemscope, itemtype and itemprop.
RDFa also adds structured-data attributes to HTML, but it follows a linked-data model and uses a different syntax.
All three formats can work when implemented correctly. JSON-LD is usually the best choice for modern websites because developers can update it without modifying every visible HTML element.
Why Does Schema Markup Matter for SEO in 2026?
Schema markup helps search engines understand page content and can make eligible pages appear with enhanced search features known as rich results. These may include prices, ratings, availability, dates, images, shipping details and other useful information.
A rich result occupies more visual space and may give users more reasons to click. Google has published case studies showing significant engagement improvements for some websites. For example, Nestlé reported that pages displayed as rich results achieved an 82% higher click-through rate than comparable non-rich results. That does not mean every website will receive the same increase, but it demonstrates the potential value of enhanced listings.
Schema can also support entity disambiguation. Organization, Person, Article, and LocalBusiness markup can help Google connect names, websites, authors, addresses, logos, and profiles to the correct real-world entities.
Nevertheless, schema cannot rescue thin content, an unhelpful page, poor technical SEO, or a weak reputation. It should strengthen an already useful page rather than disguise its limitations.
Is Schema Markup a Ranking Factor?
Schema markup is not a confirmed direct Google ranking factor. Adding it does not automatically move a page from position ten to position one.
Its value is mainly indirect.
First, schema can make a page eligible for a supported rich result. A more informative and noticeable listing may attract more qualified clicks.
Second, structured data gives Google explicit information about the subject of a page. It can reduce ambiguity around a product, business, author, event, or other entity.
Third, accurate markup can connect related objects. For example, Article markup can identify the author, while the author’s profile can use Person and ProfilePage markup.
Google also warns that incorrect or misleading structured data can result in the loss of rich-result eligibility. A structured-data manual action does not normally remove the underlying webpage from standard search results, but Google may ignore the markup.
What Are Rich Results and Rich Snippets?
Rich results are enhanced Google Search listings created from eligible page content and supported structured data. “Rich snippet” is a commonly used informal term for the same general concept.
Examples include:
| Rich-result feature | Information it may display |
| Product | Price, availability, rating and shipping |
| Recipe | Cooking time, rating, calories and image |
| Event | Date, location, performer and ticket information |
| Review | Rating value and review count |
| Video | Thumbnail, upload date and duration |
| Local business | Hours, address and business details |
Rich results are different from featured snippets. A featured snippet is an extracted answer Google selects from page content, while a rich result usually depends on a supported structured-data format.
Google never guarantees that valid schema will produce a rich result. The page must meet technical, content, quality and feature-specific requirements.
How Do You Choose the Right Schema Type for Your Page?
Choose schema according to the main subject and purpose of the page. Do not select a type simply because it appears to offer an attractive search feature.
Start by asking: “What is this page primarily about?”
A product page should use Product markup. A blog article should normally use Article or BlogPosting. A page focused on one physical business location may need LocalBusiness. An author biography may use ProfilePage with Person as its main entity.
| Page or content type | Recommended schema |
| Blog post | Article or BlogPosting |
| News story | NewsArticle |
| Ecommerce product | Product, Offer or AggregateOffer |
| Editorial product review | Product with Review |
| Business homepage | Organization |
| Physical location page | LocalBusiness or a more specific subtype |
| Author biography | ProfilePage and Person |
| Individual event page | Event |
| Recipe | Recipe |
| Video page | VideoObject |
| Questions with user-submitted answers | QAPage |
| Site navigation path | BreadcrumbList |
The markup must describe information users can actually see on the page. Do not add ratings, prices, FAQs, or claims that are hidden from visitors.
What Are the Top 10 Schema Markup Types Used in 2026?
The following list ranks schema types by practical value across common business, publishing, ecommerce, local SEO, and entity-building situations. It is not an official Google ranking.
| Rank | Schema type | Main use |
| 1 | Organization | Brand identity and entity disambiguation |
| 2 | Article | Editorial and blog content |
| 3 | Product | Ecommerce and product discovery |
| 4 | Review and AggregateRating | Ratings and review information |
| 5 | LocalBusiness | Physical business locations |
| 6 | VideoObject | Video indexing and understanding |
| 7 | Event | Event discovery |
| 8 | Person and ProfilePage | Author and creator identity |
| 9 | FAQPage | Machine-readable FAQ content |
| 10 | HowTo | Structured step-by-step instructions |
1. What Is Organization Schema and Why Does It Matter for AI Search?
Organization schema identifies a business, nonprofit, institution, or other organization and provides information such as its official name, logo, website, contact details, address, and verified profiles.
Google recommends adding relevant Organization data to the website’s homepage. This markup can help Google distinguish the organization from similarly named entities and understand which logo, name, contact details, and external profiles belong to it.
A useful Organization object may include:
A stable @id, such as https://example.com/#organization, can act as the internal identifier for the business. Other structured-data objects can then reference the same identifier instead of creating separate and potentially conflicting versions of the organization.
The sameAs property should only link to pages that unambiguously represent the same entity. Suitable examples may include the organization’s official LinkedIn, YouTube, Facebook, Wikidata, or industry profile.
Do not use sameAs for loosely related articles, partners, category pages, or profiles belonging to another person or company.
Organization schema does not guarantee a Knowledge Panel or an AI Overview mention. Its main value is providing consistent, machine-readable identity information that search systems can compare with other trusted sources.
2. What Is Article Schema and When Should You Use It?
Article schema identifies editorial content and communicates details such as the headline, author, publisher, publication date, modification date and featured images.
The main subtypes are:
Use the most specific accurate subtype. A company tutorial published in its blog may use BlogPosting, while a news publication should normally use NewsArticle for reporting.
Important properties include headline, author, datePublished, dateModified, image, publisher and mainEntityOfPage.
The author should reference a real person or organization. When a named author has a dedicated biography page, the Article object can connect to that page and its Person markup.
Publication dates must reflect the visible page information. Do not change dateModified every time the page is automatically rendered. It should represent a meaningful content update.
Article markup can help Google understand article details and use more suitable titles, images, and date information in Search and Google News. It does not make low-quality content authoritative by itself.
3. What Is Product Schema and What Is the Difference Between Product Snippet and Merchant Listing Markup?
Product schema describes an item or service. Google divides its product search experiences into product snippets and merchant listings. The correct implementation depends mainly on whether customers can purchase from the page.
| Feature | Product snippet | Merchant listing |
| Main page type | Editorial or non-purchase product page | Page where customers can purchase |
| Common users | Review sites and product publishers | Ecommerce stores and retailers |
| Possible information | Reviews, ratings, pros, cons and product details | Price, availability, shipping, returns and product details |
| Purchase offered on page | Not required | Yes |
| Common nested types | Review and AggregateRating | Offer or AggregateOffer |
A product review site may use Product markup with Review, positive notes, negative notes, and AggregateRating when the information is genuine and visible.
An online store should normally provide Product data connected to an Offer. Offer properties may include price, priceCurrency, availability, url, itemCondition, shipping information, and return policy details.
For products available in multiple sizes, colors, or materials, ProductGroup and related variant properties can help Google understand the relationship among the variations.
Structured data should match the product information shown to customers. Price and stock values must remain current.
4. What Is Review Schema and AggregateRating Schema?
Review schema represents an individual evaluation, while AggregateRating summarizes ratings collected from multiple reviewers.
An individual Review may contain the reviewer’s name, review text, publication date, and rating.
AggregateRating may include:
Review markup is not valid for every subject or situation. Google currently supports review snippets for selected categories, including products, recipes, events, books, movies, software applications, and certain other eligible types.
Businesses must also understand Google’s self-serving review restriction. A local business or organization generally cannot mark up reviews about itself on pages it controls and expect star ratings to appear for that business.
Never create fake ratings, copy ratings from unrelated platforms without permission, or mark up a score that visitors cannot see. The rating count and average must accurately reflect the reviews presented on the page.
5. What Is LocalBusiness Schema and How Does It Affect Local Search?
LocalBusiness schema describes a physical business or branch and can communicate its name, address, telephone number, opening hours, service area, price range, and location-specific details.
LocalBusiness is a subtype of Organization and Place. More specific types should be used where appropriate, such as:
Use LocalBusiness markup on a page that genuinely represents a physical location or local operation. A company with several branches should normally create a unique page and distinct LocalBusiness object for each location.
The name, address, phone number, hours, and website information should be consistent with the company’s Google Business Profile and other official sources.
LocalBusiness schema can help Google understand the business, but it does not independently guarantee Local Pack rankings. Proximity, relevance, prominence, reviews, Google Business Profile quality, links and other local signals still matter.
6. What Is VideoObject Schema and Why Does It Matter for AI Crawlers?
VideoObject schema describes a video’s title, description, thumbnail, upload date, duration, content location, and embed location.
A search crawler cannot understand a video as easily as a human viewer. It may use the surrounding text, transcript, captions, metadata, thumbnail, video file information, and structured data to determine what the video covers.
Recommended properties commonly include:
The video should be prominent and watchable on the page. Its structured description must match the actual content.
For stronger accessibility and machine understanding, include a useful written summary or transcript in visible HTML. VideoObject should support that content, not replace it.
Tests of major AI crawlers indicate that many do not reliably execute client-side JavaScript. Therefore, important video descriptions and JSON-LD should ideally be available in the initial or server-rendered HTML rather than depending entirely on scripts that run after page load.
7. What Is Event Schema and How Much Traffic Can It Drive?
Event schema provides structured information about a public event, including its name, dates, location, status, performers, organizer, offers, and ticket availability.
Google recommends creating a unique page for each event rather than marking up a general schedule containing many unrelated events.
Event markup may be appropriate for:
Properties such as eventStatus and eventAttendanceMode are especially important. They clarify whether an event is scheduled, postponed, cancelled, online, offline, or hybrid.
One widely cited Google case study reported that Eventbrite experienced roughly a 100% increase in its typical year-over-year growth of Google Search traffic to event listing pages after adopting Google’s event search experience. This was a company-specific result, not a guaranteed outcome for every event website.
8. What Is Person Schema and How Does It Support E-E-A-T?
Person schema identifies an individual through information such as their name, job title, image, employer, expertise, website and verified external profiles.
Person schema is particularly useful for authors, founders, doctors, lawyers, researchers, reviewers, consultants, and other named contributors.
A dedicated author page can use ProfilePage as the main page type and Person as its mainEntity. Articles written by that author can then reference the same Person @id.
This creates a clearer relationship between:
Person schema does not create expertise or trust. Google’s E-E-A-T evaluations depend on the content, reputation, first-hand experience, credentials, transparency, and supporting evidence.
The markup simply helps systems identify the correct person behind the content.
9. What Is FAQ Schema and Does It Still Work in 2026?
FAQPage schema remains a valid Schema.org type, but Google stopped showing FAQ rich results in Search on May 7, 2026. Google is also removing FAQ reporting and Rich Results Test support during 2026.
This is an important change. Older articles may still say FAQ rich results are limited to authoritative health and government websites. That was previously correct, but Google has now announced the broader removal of the search feature.
You may still use FAQPage markup when the page contains genuine, visible questions and answers. Other search engines, applications, accessibility tools, or machine-reading systems may use the structured information.
However, website owners should no longer implement FAQPage with the expectation of gaining expandable FAQ listings in Google Search.
Use QAPage instead when users can submit multiple answers to a single question. FAQPage is intended for questions with answers supplied by the website itself.
10. What Is HowTo Schema and Why Did Its Rich Results Change?
HowTo schema describes a process involving sequential steps, tools, supplies, estimated time, costs, and step images. It remains part of Schema.org, but Google’s HowTo rich result is no longer available.
Google first reduced HowTo visibility in August 2023. On September 13, 2023, it stopped showing HowTo rich results on desktop as well, fully deprecating the search feature.
HowTo markup may still be useful as semantic information for non-Google systems, internal applications, or future integrations. However, it should not be presented as an active Google rich-result opportunity in 2026.
A practical step-by-step guide should still have:
Quality HTML structure and complete instructions are more important than adding HowTo markup solely for SEO.
Does Schema Markup Influence AI Overviews, ChatGPT, and Perplexity?
There is no reliable public evidence that schema markup is a direct ranking or citation factor for AI Overviews, ChatGPT, or Perplexity. Structured data may still help the search and retrieval systems that supply information to AI models.
The distinction matters.
An AI model may receive information from a search index, a live crawler, a product feed, a knowledge graph, or extracted webpage text. The model itself may not be interpreting Schema.org relationships in the same way as Google Search.
In Mark Williams-Cook’s “DUCKYEA” experiment, a fictional address was placed inside page-source markup rather than visible body text. ChatGPT and Perplexity could return the information, but further testing suggested that they were extracting the text rather than necessarily understanding or prioritizing its structured meaning.
Therefore, schema should not be sold as a magical generative engine optimization shortcut.
Google officially states that it uses structured data to understand pages and information about entities. That understanding may contribute to systems connected to Google Search, but Google has not publicly confirmed that a specific schema property directly triggers inclusion in AI Overviews.
The sensible approach is to use accurate structured data for search understanding while also publishing clear, visible, well-supported content that any crawler can extract.
Do AI Crawlers Like GPTBot and ClaudeBot Read Schema Markup?
Many AI crawlers appear to retrieve the original HTML without fully rendering every client-side JavaScript application. That means JSON-LD inserted only after a browser executes JavaScript may not always be available to them.
For maximum accessibility:
- Put important facts in visible HTML.
- Include JSON-LD in the initial or server-rendered page source.
- Avoid relying entirely on Google Tag Manager for critical schema.
- Provide transcripts and written explanations for video or audio.
- Test the raw HTML response, not only the browser’s rendered DOM.
Googlebot can process JavaScript and Google supports dynamically generated structured data. The static-HTML recommendation is mainly a broader compatibility measure for other crawlers and retrieval systems.
How Does Schema Markup Connect to Google’s Knowledge Graph?
Schema markup can provide explicit information about people, organizations, places, products, and their relationships, helping Google disambiguate entities and connect information from multiple sources.
Organization markup is especially useful for brand identity. Person and ProfilePage markup can clarify author identity. sameAs can point to pages that unambiguously represent the same entity.
The @id property creates a reusable identifier within your structured-data graph. For example:
Articles, webpages, products and author profiles can reference these IDs consistently.
In June 2025, external Knowledge Graph tracking reported that Google removed billions of entries during a major cleanup. This was not an official instruction to remove schema or Knowledge Graph identifiers. It did, however, reinforce the importance of relying on accurate, stable identity sources rather than fragile or invented entity connections.
What Schema Markup Mistakes Can Hurt Your Site?
The serious mistakes involve misleading, invisible, inaccurate, or spammy markup.
Common problems include:
The Rich Results Test checks eligibility for Google-supported rich results. The Schema.org Validator checks broader vocabulary and syntax.
Passing a validator does not prove that the markup is truthful or eligible. A technically valid object can still violate Google’s quality guidelines.
Is VoiceAction Schema Still Valid for Voice Search in 2026?
No recognized Schema.org type called VoiceAction currently exists.
Older tutorials sometimes describe it as a voice-search optimization method, but adding an invented type will not create a voice result.
Schema.org does contain various Action types, while Google may use specific supported structured data in voice-related experiences. The correct strategy is to implement recognized types accurately and make the visible content concise, clear, accessible, and easy to understand.
Voice search does not require a separate universal “voice schema.”
Can You Use Multiple Schema Types on the Same Page?
Yes. Google supports multiple structured-data items on one page when they accurately represent visible content and have clear relationships.
For example, a recipe page can include:
Related objects can be nested inside the main object or linked through matching @id values.
The important rule is relevance. Do not stack FAQPage, HowTo, Article, Product, and LocalBusiness on a page merely to target more search features.
Identify the page’s primary subject, add its main schema type, and then include complementary objects that genuinely belong to it.
How Do You Add and Validate Schema Markup on Your Website?
Schema can be written manually, generated through a tool, or produced by a CMS plugin.
WordPress users often use plugins such as Yoast SEO, Rank Math, AIOSEO, or Schema Pro. Ecommerce platforms including Shopify, Wix, Webflow, and Magento may generate some markup automatically.
AI tools can also draft JSON-LD, but their output must be reviewed. They may invent unsupported properties, omit required fields, use incorrect nesting, or produce information that does not match the page.
Use this implementation process:
- Identify the page’s main subject.
- Check Google’s documentation for that specific feature.
- Select the correct Schema.org type.
- Add only accurate and visible information.
- Connect related entities with @id.
- Test the page with the Rich Results Test.
- Check broader syntax with the Schema.org Validator.
- Inspect the live URL in Google Search Console.
- Monitor Search Console after deployment.
Google advises website owners to rely on Google Search Central documentation for Google-specific behavior because Schema.org includes many valid types and properties that Google does not use for rich results.
How Do You Check Schema Markup Issues at Scale?
Testing one page at a time is not practical for a large website.
Use a site crawler or audit platform to identify:
Google Search Console provides reports for supported structured-data features. Platforms such as Ahrefs, Semrush, Sitebulb, and Screaming Frog can also crawl structured data across large websites.
After correcting a template, test several representative URLs before deploying the change across the entire site.
Which Schema Markup Types Should You Implement First in 2026?
Begin with the type that represents your main website entity.
Most businesses should establish accurate Organization schema first. Publishers can then add Article or BlogPosting. Ecommerce stores should prioritize Product and Offer. Physical businesses should implement LocalBusiness on location pages.
Add Person and ProfilePage to strengthen author identification. Use Review, VideoObject, Event, Recipe, or other specific types only where the page genuinely supports them.
Do not build your strategy around discontinued FAQ or HowTo rich results. Instead, focus on accurate entity relationships, visible supporting content, server-accessible implementation, and the schema types that Google currently supports.
The best schema markup is not the largest or most complicated graph. It is the smallest complete set of accurate information that clearly explains the page to search engines and other machines.
