Schema Markup Guide: Types, Best Practices & Examples
Updated: Sep 17
Schema markup can look more complicated than it really is.
At its core, structured data gives machines explicit information about what a webpage contains.
An article can identify its author and headline. A product page can describe a product, price and availability. A business page can identify an organization.
Breadcrumb markup can explain where a page sits within a website's hierarchy.
But there is an important distinction that many schema markup guides overlook:
A schema type existing does not mean Google provides a Search feature for it.
And even when Google supports a structured-data feature, correctly implementing the markup does not guarantee that the enhanced result will appear.
Google explicitly says structured data can make content eligible for richer Search appearances, but eligibility does not guarantee display.
This guide explains how schema markup works, which types matter, how to implement JSON-LD, how to validate your structured data and how to decide whether a schema type is actually worth implementing.
What Is Schema Markup?
Schema markup is structured data used to describe information on a webpage in a standardized, machine-readable way.
Much of the vocabulary used for this comes from Schema.org.
Structured data can be implemented in several formats. Google currently supports:
JSON-LD
Microdata
RDFa
Google recommends JSON-LD where possible.
This distinction matters because schema markup is not another term for Microdata.
Microdata is one implementation format.
JSON-LD is another.
Schema.org and Google Structured Data Are Not the Same Thing
Before implementing schema, separate four different layers.
1. Page reality
What actually exists on the page?
Is it an article, product, organization profile, recipe, event or something else?
Start here.
2. Schema.org vocabulary
Schema.org provides standardized types and properties for describing entities and their relationships.
Its vocabulary extends far beyond the structured-data features Google currently supports in Search.
3. Your implementation
You use JSON-LD, Microdata or RDFa to represent relevant information accurately.
The markup should correspond with the page rather than inventing information that users cannot see.
4. Search-engine features
Google supports particular structured-data types for specific Search experiences.
Its current gallery includes features associated with Article, Breadcrumb, Dataset, Event, Job Posting, Local Business, Organization, Product, Profile Page, Recipe, Review Snippet, Software Application, Video and other specialized content.
These layers overlap, but they are not interchangeable.
Valid Schema.org markup does not automatically mean Google offers a rich result for it.
And eligibility for a supported Google feature does not guarantee that the feature will appear.
Does Schema Markup Help SEO?
Yes, but not because adding JSON-LD automatically increases rankings.
Google says it uses structured data to understand page content and can use that information to display content in richer Search features.
That makes structured data useful for communicating explicit information about certain types of content.
But there are four different concepts here:
Understanding → Eligibility → Appearance → Ranking
Do not treat them as synonyms.
Google's structured-data guidelines make this particularly clear. A structured-data manual action can remove eligibility for rich results without affecting how the page ranks in ordinary Google web search.
Structured data is therefore better understood as a machine-readable description layer than as a direct ranking lever.
What Is JSON-LD?
JSON-LD stands for JavaScript Object Notation for Linked Data.
It allows information about entities and their properties to be represented in a structured block.
For example:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Schema Markup Guide: Types, Examples & Best Practices",
"author": {
"@type": "Person",
"name": "Chris A"
}
}
This identifies the content as a blog post and identifies its author.
It does not replace the visible headline or byline.
The markup should reinforce information already presented accurately on the page.
Which Schema Types Matter for SEO?
There is no universal package of schema types that every website should install.
Choose markup according to what the page actually contains and what supported features or data consumers are relevant.
Here are several common examples.
Article and BlogPosting Schema
Article structured data can be used for news, sports and blog articles.
Google supports Article, NewsArticle and BlogPosting.
Useful properties can include:
headline;
author;
author URL;
image;
date published;
date modified.
Google says Article markup can help it understand the page and show better title text, images and date information in relevant Search experiences.
Do not invent dates, credentials or author information simply to complete the markup.
BreadcrumbList Schema
Breadcrumb markup describes a page's position within a site's hierarchy.
For example:
Home → Blog → Schema Markup Guide
Visible breadcrumbs can also help users understand where they are and navigate to broader sections of a website.
Google continues to support BreadcrumbList structured data.
Organization Schema
Organization structured data can describe information about an organization.
That might include its:
name;
URL;
logo;
contact information;
relevant identifying URLs.
Organization markup can clarify identity.
It does not independently prove that an organization is authoritative or trustworthy.
Person and ProfilePage Schema
Person structured data can describe an individual.
ProfilePage markup can describe a page primarily focused on a person or organization affiliated with the website.
For publishers, that can make it appropriate for genuine author-profile pages.
The visible author, author page and structured data should describe the same real contributor.
For the broader editorial implications, see our guide to author bio E-E-A-T optimization.
Product Schema
Product structured data can describe genuine product information and make eligible pages available for supported product Search experiences.
Depending on the page and feature, information can include:
price;
availability;
ratings;
shipping;
returns;
product variants.
Google's product-snippet documentation says product rich results apply to pages focused on a specific product or variants of that product rather than general product-category pages.
Never fabricate reviews, prices or availability to populate structured data.
Local Business Schema
Local Business structured data can describe information about a physical business, including appropriate details such as its address, telephone number and operating information.
Use the most accurate applicable type and keep the information synchronized with the visible page.
Do not treat Local Business markup as a requirement or shortcut for ranking in Google's Local Pack.
Recipe, Event, Job Posting and Other Specialist Types
Some structured-data features apply to very specific content.
If you publish recipes, use Google's Recipe documentation.
If the page contains a genuine job vacancy, review the requirements for Job Posting.
If it describes an eligible event, examine Google's Event documentation.
The principle is straightforward:
Start with the page type, then choose the markup.
Do not start with a list of schema types and look for places to insert them.
What Happened to FAQ Schema?
FAQ content and FAQ structured data are different things.
FAQ content can still be extremely useful because readers often have predictable follow-up questions.
FAQPage also continues to exist within the broader Schema.org vocabulary.
What has changed is its value as a Google Search enhancement.
Google's current structured-data Search gallery does not list FAQ as a general supported feature.
So keep useful FAQs when they improve the page.
Do not add them because you expect expandable FAQ results underneath an ordinary organic listing.
What About HowTo Schema?
The same distinction applies to HowTo.
A step-by-step section can be useful regardless of schema.
But Google's current structured-data feature gallery does not list a general standalone HowTo Search feature.
Do not confuse useful procedural content with eligibility for a specific Google rich result.
Schema Markup and E-E-A-T
Structured data can describe facts relevant to understanding authorship and publishing relationships.
For example:
BlogPosting → author → Person
or:
BlogPosting → publisher → Organization
That can make relationships explicit.
But schema cannot create Experience, Expertise, Authoritativeness or Trustworthiness.
If someone does not possess a qualification, adding it to structured data would be misleading rather than helpful.
If a company lacks independent recognition, Organization markup does not manufacture authority.
For related entity concepts, see our guide to entity SEO and semantic search.
That existing article should itself be reviewed before relying on all of its schema/AI claims, however, because some currently go beyond what Google's documentation supports.
Does Schema Markup Help AI Overviews?
There is no documented "AI Overview schema."
Google's current Search Appearance documentation discusses AI features separately from its structured-data feature list.
Structured data may still be useful as machine-readable information, but that does not establish that adding schema causes a page to appear in AI Overviews.
Independent research provides another reason for caution.
Ahrefs examined 1,885 pages that added schema and found little subsequent movement in AI citations. The researchers specifically warned against confusing correlation with causation because sites implementing schema often also have stronger content, technical maintenance, authority and links.
So for AI-search readiness, focus first on:
accurate, useful content;
clear authorship;
primary-source citations;
crawlability;
consistent entity information;
original information where possible;
logical internal relationships;
accurate structured data where relevant.
Schema should support the content.
It should not be presented as an AI-citation shortcut.
How to Choose the Right Schema Markup
Use this four-question test.
1. What does the page actually contain?
Identify the primary content.
Do not begin with the markup.
2. Which Schema.org type accurately represents it?
Choose a type that matches the actual entity or content.
Do not select a more impressive-sounding type simply because it is more specific.
3. Does your target platform use it?
If Google Search visibility is the objective, check Google's current structured-data documentation.
Do not assume every Schema.org type corresponds with a Google feature.
4. Can you maintain it?
Structured data is only useful while it remains accurate.
If your system cannot keep price, availability, opening hours, authorship or other dynamic properties synchronized with the page, solve that problem before expanding the markup.
A Practical Schema Implementation Workflow
Step 1: Inventory Your Page Templates
Start with recurring page types rather than individual URLs.
Examples might include:
homepage;
blog articles;
author pages;
service pages;
product pages;
location pages.
Step 2: Map Templates to Appropriate Types
Determine what each template actually represents.
A blog article might use Blog Posting.
An author page may qualify as Profile Page.
A genuine physical business page may use an appropriate Local Business subtype.
Not every template requires several schema types.
Step 3: Check Current Documentation
If Google Search is the target, consult Google's documentation for the specific structured-data feature.
Schema.org explains the vocabulary.
Google's documentation explains how Google Search currently supports structured data.
Those are different jobs.
Step 4: Add Only Accurate Information
Never populate structured data with information created solely for the markup.
That includes:
fake reviews;
invented ratings;
fabricated authors;
false prices;
expired credentials;
incorrect availability;
unsupported business information.
Google requires structured data to represent the content accurately and warns against misleading markup.
Step 5: Validate the Implementation
For Google-supported Search features, use Google's Rich Results Test.
For broader Schema.org syntax and vocabulary, use the Schema Markup Validator.
These tools answer different questions.
Passing Schema.org validation does not mean a page qualifies for a Google rich result.
Step 6: Test the Published Page
Once deployed, inspect the live URL rather than only testing code in isolation.
Google recommends deploying structured data, checking the page through URL Inspection and ensuring the page is accessible to Google.
Step 7: Monitor and Maintain It
Structured data can become inaccurate when:
an author changes;
a product price changes;
inventory changes;
an event passes;
business details change;
URLs move;
Google changes feature support.
Schema implementation is therefore part of ongoing technical maintenance.
Our technical SEO audit checklist provides the broader context, although some of that existing article's AI/schema wording should also be moderated in a future refresh.
Common Schema Markup Mistakes
Adding as Many Schema Types as Possible
More structured data does not automatically mean better SEO.
Accuracy and relevance matter more than volume.
Marking Up Content That Does Not Match the Page
Google says structured data should represent the page's main content and should not describe information hidden from users or otherwise mislead them.
Treating Validation as a Guarantee
Passing the Rich Results Test does not guarantee that Google will display a rich result.
Google states this explicitly.
Confusing Schema.org Validity With Google Eligibility
A perfectly valid Schema.org type may have no corresponding Google Search feature.
Always distinguish vocabulary validation from Search eligibility.
Misusing same As
Use same As for URLs that genuinely represent the same entity.
Do not add loosely related pages simply because you want to associate an organization or author with an authoritative domain.
Incorrect identity relationships can create confusion rather than clarity.
Fabricating Reviews or Ratings
Do not create rating information for structured data that is not genuinely supported by the page and underlying reviews.
Forgetting to Update Dynamic Information
Prices, availability, events, jobs, author roles and business information can all become stale.
Treat maintenance as part of implementation.
Frequently Asked Questions
What is schema markup?
Schema markup is structured data that describes information on a webpage in a standardized, machine-readable format.
What is the best schema format for SEO?
Google supports JSON-LD, Microdata and RDFa and recommends JSON-LD where possible.
Does schema markup directly improve rankings?
Do not treat schema as a direct ranking boost.
Structured data can help Google understand information and make eligible pages available for supported Search features, but those concepts should be separated from organic ranking.
Does every page need schema markup?
No.
Implement structured data where it accurately represents the content and has a meaningful purpose.
Can you use multiple schema types on one page?
Yes.
Multiple entities can be represented when they genuinely exist on the page and their relationships are accurate.
Do not add unrelated types merely to increase the amount of markup.
Does valid schema guarantee a rich result?
No.
Google explicitly says correctly implemented structured data does not guarantee that a rich result will appear.
Does FAQ schema still generate FAQ rich results?
Do not build an ordinary site's strategy around FAQ rich results. Google's current structured-data Search gallery no longer lists FAQ as a general supported feature.
Does schema markup help AI Overviews?
There is no documented schema type that guarantees inclusion or citation in Google AI Overviews.
Structured data should accurately describe content rather than being treated as an AI Overview trigger.
Build Structured Data for Accuracy, Not Volume
The strongest schema implementation is not the one with the most JSON-LD.
It is the one that describes reality accurately.
Start with the page. Identify what it contains. Choose the appropriate vocabulary.
Check whether your target search platform supports the feature. Implement accurate properties. Validate the result. Then maintain it.
Think of the process as:
Page reality → Schema.org vocabulary → valid implementation → supported feature → eligibility
Not:
Add schema → get rankings.
If you're unsure which structured-data problems actually deserve priority alongside crawlability, internal architecture and other technical SEO work, you can book a consultation with 10x Linkbuilding.
