Schema Markup Guide 2026: Types, JSON-LD Examples & WordPress SEO Setup
Have you ever searched Google and noticed results displaying product prices, star ratings, recipe information, or breadcrumb navigation?
Some of these enhanced search appearances are powered by structured data, commonly called schema markup.
Schema markup helps search engines understand specific information about your content. It can also make eligible pages available for supported rich result features.
However, schema markup is not a guaranteed ranking factor, indexing solution, or shortcut to higher click-through rates.
In this complete 2026 guide, you’ll learn what schema markup is, how JSON-LD works, which structured data types matter, how to configure schema using All in One SEO (AIOSEO), and how to test your implementation.
1. What Is Schema Markup?
Schema markup is structured data that describes the meaning and relationships of information on a webpage.
It uses vocabulary from Schema.org, a collaborative structured data project supported by major search engines.
For example, a blog post might contain:
- An article title.
- An author name.
- A publication date.
- A featured image.
- A website publisher.
Structured data can describe these elements in a machine-readable format.
A simple example
Suppose an article is titled:
How to Improve WordPress Website Speed
It was written by a named author and published on May 6, 2026.
Article structured data can describe its headline, author, publication date, and image.
This helps search engines interpret information that is already present on the page.
Schema markup should accurately represent real content. It should not invent ratings, reviews, authors, or other information.
2. Schema Markup vs. Rich Results vs. Rich Snippets
These terms are related but have different meanings.
| Term | Meaning |
|---|---|
| Schema markup | Structured data describing page content |
| Rich results | Enhanced search appearances supported by Google |
| Rich snippets | Common informal term for enhanced search snippets |
| JSON-LD | A format for expressing structured data |
| Schema.org | Vocabulary defining structured data types and properties |
Does schema markup guarantee rich results?
No.
Google considers several factors, including supported markup, content relevance, technical accessibility, and applicable policies.
Even correctly implemented structured data may not produce a rich result.
Also, not every Schema.org type corresponds to a supported Google Search feature.
3. Why Schema Markup Matters for SEO
Helps describe page content
Structured data provides explicit information about entities and relationships.
For example, Article markup can describe an article’s headline, author, and publication date.
Supports eligible rich results
Certain supported structured data types can make pages eligible for enhanced search appearances.
Examples include eligible product, recipe, breadcrumb, and video features.
Improves data consistency
Structured data can help ensure that important details are described consistently.
Supports content organization
Organization, Person, WebSite, Article, and BreadcrumbList markup can describe relationships between a website, publisher, author, and individual pages.
Does schema directly improve rankings?
Google does not promise a direct ranking boost from adding structured data.
Its primary value is providing structured information and supporting eligible search features.
Schema also cannot guarantee that Google will index a page.
For broader optimization, read the On-Page SEO Complete Guide 2026.
4. Important Schema Markup Types in 2026
1. Article schema
Article markup describes editorial content.
Common properties include:
headlineauthordatePublisheddateModifiedimagepublisher
It is relevant for blog posts, news articles, and other editorial pages.
Google supports Article structured data for eligible search experiences, but it does not guarantee a particular display.
2. BreadcrumbList schema
Breadcrumb markup describes a page’s position within a website hierarchy.
Example navigation:
Home → SEO → Schema Markup Guide
This helps describe the page’s navigational context.
Breadcrumb structured data is particularly useful for websites with categories and hierarchical content.
3. Organization schema
Organization markup describes a business, publisher, or organization.
Properties may include:
- Organization name.
- Website URL.
- Logo.
- Relevant social profiles.
- Contact information, where appropriate.
Use accurate information that matches the website’s identity.
4. Person schema
Person markup describes an individual.
It may be appropriate for author profile pages and other pages genuinely about a person.
Properties can include a name, profile URL, and relevant public identity information.
Person markup does not automatically establish expertise, experience, authoritativeness, or trustworthiness.
5. WebSite schema
WebSite markup describes the website itself.
It can help provide website-level information such as its name and URL.
Important 2026 update: Google’s sitelinks search box feature was discontinued in November 2024. WebSite markup may still be useful for supported website-name information, but it no longer enables that discontinued search box.
6. Product schema
Product markup can describe genuine product information.
Depending on the eligible feature, properties may include:
- Product name.
- Image.
- Description.
- Offers.
- Price.
- Availability.
- Genuine reviews or ratings.
Product markup must match actual products and comply with Google’s applicable guidelines.
Do not add Product markup to ordinary informational articles simply to obtain star ratings.
7. Review and AggregateRating schema
Review-related markup can describe genuine reviews or ratings of eligible items.
However, Google applies specific eligibility rules.
Self-serving reviews for certain organization and local business contexts are not eligible for review stars.
Never create fictional ratings or copy unsupported review statistics into structured data.
8. Recipe schema
Recipe markup is relevant to genuine recipe pages.
Depending on the content and supported feature, it may describe:
- Ingredients.
- Preparation instructions.
- Cooking time.
- Recipe images.
- Nutrition information.
Only provide properties supported by the actual recipe.
9. VideoObject schema
VideoObject markup describes video content.
It can include:
- Video title.
- Description.
- Thumbnail URL.
- Upload date.
- Video duration.
- Content or embed URL, where appropriate.
It is useful for pages with genuine video content.
10. FAQPage and HowTo schema
These types remain part of the broader Schema.org vocabulary, but their Google Search feature support has changed.
FAQ rich results: Google discontinued the FAQ rich result feature in May 2026.
HowTo rich results: Google discontinued HowTo rich results in 2023.
You can still publish helpful FAQ sections and step-by-step tutorials without expecting these discontinued rich result features.
5. Schema Markup Types Comparison
| Schema type | Suitable content | Google Search consideration |
|---|---|---|
| Article | Editorial articles | Supported Article features |
| BreadcrumbList | Website navigation | Supported breadcrumb feature |
| Organization | Publisher or company | Organization information |
| Person | Author or individual | Entity description |
| WebSite | Website homepage | Site name information |
| Product | Genuine products | Eligible product features |
| Review | Genuine eligible reviews | Restricted eligibility |
| Recipe | Recipe pages | Supported recipe features |
| VideoObject | Video pages | Supported video features |
| FAQPage | FAQ content | FAQ rich results discontinued |
| HowTo | Tutorials | HowTo rich results discontinued |
Always consult Google’s current documentation before implementing a markup type for a particular search feature.
6. What Is JSON-LD?
JSON-LD stands for JavaScript Object Notation for Linked Data.
It is a format for expressing structured information in JSON.
Google generally recommends JSON-LD for supported structured data implementations because it is relatively easy to maintain.
JSON-LD is usually included inside a script element:
<script type="application/ld+json">
The script contains structured information rather than executable JavaScript.
Example: Basic Article JSON-LD
The following is an illustrative example. Replace the example URLs and details with accurate information from the actual article.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Improve WordPress Speed",
"author": {
"@type": "Person",
"name": "Example Author"
},
"datePublished": "2026-05-06",
"publisher": {
"@type": "Organization",
"name": "Example Website"
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/wordpress-speed/"
}
}
</script>
This example demonstrates structure, not a complete implementation for every Google Search feature.
For real websites, include appropriate recommended properties where available and ensure the markup matches visible content.
7. Example: Breadcrumb JSON-LD
Breadcrumb structured data describes the navigation hierarchy.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "SEO",
"item": "https://example.com/seo/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Schema Markup Guide",
"item": "https://example.com/schema-markup-guide/"
}
]
}
</script>
Replace these sample URLs with the real, accessible URLs of your website.
For WordPress users, an SEO plugin may already generate breadcrumb markup automatically.
Do not insert duplicate markup unnecessarily.
8. How to Add Schema Markup in WordPress Using AIOSEO
All in One SEO is a WordPress SEO plugin that supports structured data functionality.
AIOSEO can output JSON-LD markup for website information, and additional schema features are available depending on the installed version and license.
Step 1: Check your active SEO plugin
Open:
WordPress Dashboard → Plugins → Installed Plugins
Confirm that All in One SEO is active.
Avoid running multiple SEO plugins that generate overlapping metadata and schema unless you have a deliberate configuration.
Step 2: Configure website identity
Open the AIOSEO settings and locate the website or Knowledge Graph information.
Depending on your installed version, the available settings may include:
- Organization or person.
- Website name.
- Organization name.
- Logo.
- Social profile URLs.
Enter genuine, consistent information.
Step 3: Review existing schema
Open a published blog post.
Inspect the page’s structured data using a validator.
Check whether Article, WebPage, BreadcrumbList, Organization, or WebSite markup is already present.
Do not assume that every schema type needs to be added manually.
Step 4: Review the AIOSEO Schema tab
In supported AIOSEO versions, the WordPress post editor provides schema-related settings.
The available options depend on your plugin version and license.
Some advanced schema generation features require AIOSEO Pro.
If your version does not offer a particular schema type, do not immediately install another schema plugin.
First decide whether that markup is genuinely necessary.
Step 5: Save and test
After making changes:
- Update the WordPress post.
- Open its public URL.
- Test it with Google’s Rich Results Test.
- Validate the structured data using Schema Markup Validator.
- Fix confirmed errors.
- Check for duplicate or contradictory markup.
Important: Do not paste an additional Article JSON-LD script into every post if AIOSEO already generates appropriate Article markup.
9. How to Add Schema Markup Without a Plugin
Advanced users can implement structured data manually.
However, manual implementation requires careful testing and maintenance.
Basic workflow
- Select the appropriate Schema.org type.
- Review Google’s supported structured data documentation.
- Prepare accurate property values.
- Create valid JSON-LD.
- Add the script through an appropriate website development workflow.
- Test the output.
- Verify that no duplicate or conflicting markup exists.
For WordPress, use a maintainable implementation such as a properly managed custom plugin or supported code-insertion solution.
Avoid editing the parent theme’s header.php directly, because updates may overwrite changes and errors can affect the website.
Manual markup should not replace functionality already handled correctly by your SEO plugin.
10. Free Schema Markup Tools
Several tools can help you create, inspect, and validate structured data.
| Tool | Main purpose |
|---|---|
| Google Rich Results Test | Test supported Google rich result eligibility |
| Schema Markup Validator | Validate general Schema.org markup |
| Schema.org | Reference structured data types and properties |
| Google Search Central | Review supported Google features and policies |
| AIOSEO | Manage structured data in WordPress |
Google Rich Results Test
Official tool:
https://search.google.com/test/rich-results
This tool evaluates structured data relevant to Google’s supported rich result features.
Schema Markup Validator
Official tool:
This validator can examine Schema.org markup beyond Google’s rich result feature set.
Schema.org documentation
Official reference:
Use it to understand supported vocabulary and property relationships.
11. How to Test Schema Markup Correctly
Step 1: Test the live URL
Open Google’s Rich Results Test and enter your page URL.
Step 2: Review detected features
The test reports supported rich result types detected on the page.
Not every valid Schema.org type will appear as a supported rich result.
Step 3: Investigate errors
Errors may indicate that required properties are missing or invalid for a particular Google feature.
Step 4: Review warnings
Warnings may indicate missing recommended properties.
Warnings do not always prevent eligibility.
Step 5: Use Schema Markup Validator
Check whether the general structured data syntax and properties are valid.
Step 6: Compare markup with visible content
Ensure that authors, dates, images, prices, ratings, and other claims match the actual page.
Step 7: Monitor Google Search Console
Where Google supports an enhancement report for your detected structured data, review the relevant report in Search Console.
Not every schema type has a dedicated enhancement report.
For more information, read the Google Search Console Complete Guide.
12. Common Schema Markup Errors
Missing required properties
Some Google-supported rich result features require particular properties.
Review the documentation for the exact feature.
Invalid JSON syntax
Missing commas, quotation marks, or braces can break JSON-LD.
Use a validator to identify syntax errors.
Incorrect canonical URLs
Structured data should use consistent, appropriate URLs.
Check whether the referenced page is the intended canonical destination.
Incorrect publication dates
Use accurate dates rather than inventing publication or modification dates.
Fake review ratings
Never create fictional star ratings or review counts.
Duplicate structured data
Multiple scripts are not automatically an error.
However, overlapping or contradictory entities and property values can create confusion.
Unsupported rich result expectations
Adding FAQPage or HowTo markup does not restore Google’s discontinued FAQ or HowTo rich results.
13. Schema Markup and Google Indexing
Schema markup and indexing are separate concepts.
A webpage can have valid structured data and still remain outside Google’s index.
Likewise, Google can index a page without rich result markup.
If Google Search Console reports:
Crawled – currently not indexed
Investigate the actual page rather than assuming schema is missing.
Relevant checks include:
- Crawl accessibility.
- Indexing directives.
- Canonical selection.
- Main content quality.
- Duplicate or overlapping pages.
- Internal linking.
- Rendering problems.
For a detailed explanation, read the Crawled Currently Not Indexed Fix Guide.
Structured data can support content interpretation, but it does not force Google to index a page.
14. Schema Markup Best Practices for 2026
Use accurate information
Every structured data property should describe the actual entity or content.
Prioritize supported features
Focus on markup relevant to your website rather than implementing every available schema type.
Keep data consistent
Ensure that author names, publisher details, dates, and URLs agree across the page.
Avoid unnecessary duplication
Review existing AIOSEO output before adding custom JSON-LD.
Validate important pages
Test your homepage, important articles, and pages using specialized structured data.
Maintain structured data
Review markup after significant theme, plugin, or content changes.
Follow Google policies
Avoid misleading, irrelevant, or manipulative structured data.
15. Practical Schema Implementation Plan for a WordPress Blog
Phase 1: Audit existing markup
Start with the homepage and three representative blog posts.
Check:
- WebSite markup.
- Organization or Person markup.
- Article markup.
- Breadcrumb markup.
- Duplicate entities.
- Incorrect URLs.
Phase 2: Correct website identity
Review the publisher name, logo, website URL, and relevant public profiles.
Ensure they are consistent.
Phase 3: Review article markup
For important blog posts, verify accurate headlines, author details, publication dates, and images where applicable.
Phase 4: Validate specialized pages
If the website publishes genuine products, recipes, or video content, consider the appropriate supported structured data types.
Phase 5: Test and monitor
Run validation tests and correct confirmed issues.
Monitor Search Console for relevant structured data reports and page indexing changes.
Do not repeatedly request indexing simply because a schema test was successful.
16. Complete Schema Markup Checklist
Website setup
-
One primary SEO plugin is configured.
-
Website name is accurate.
-
Organization or person information is correct.
-
Logo URL is valid.
-
Canonical URLs are consistent.
Article markup
-
Article headline matches the content.
-
Author information is accurate.
-
Publication date is correct.
-
Modification date reflects genuine changes.
-
Featured image information is valid.
-
No conflicting Article entities are present.
Validation
-
Important URLs tested with Rich Results Test.
-
General markup checked with Schema Markup Validator.
-
Confirmed errors investigated.
-
Relevant warnings reviewed.
-
Structured data matches actual page content.
Ongoing maintenance
-
New important content is reviewed.
-
Plugin updates are tested.
-
Unsupported rich result assumptions are avoided.
-
Search Console reports are monitored.
-
Structured data is updated when factual details change.
17. Frequently Asked Questions
Does schema markup directly improve Google rankings?
Google does not guarantee a direct ranking improvement from schema markup. Structured data helps describe content and can support eligibility for certain search features.
Is schema markup necessary for every website?
It is not mandatory for Google indexing. However, appropriate structured data can be useful for eligible website content.
What schema should a blog use?
A blog may benefit from accurate Article, BreadcrumbList, WebSite, and publisher-related markup, depending on its configuration.
Does FAQ schema still work in 2026?
FAQPage remains a Schema.org type, but Google discontinued FAQ rich results in May 2026. Adding FAQ markup does not make ordinary blog FAQs appear as expandable Google rich results.
Does Google still support HowTo rich results?
No. Google’s HowTo rich result feature was discontinued in 2023.
Can I add schema markup with AIOSEO?
Yes. AIOSEO supports structured data functionality, although specific features depend on the installed version and license.
Can schema markup fix Crawled – currently not indexed?
No. Schema markup alone cannot resolve this status. Investigate content, canonical selection, accessibility, and other relevant factors.
How long does it take for rich results to appear?
There is no guaranteed timeframe. Google must process the page, and valid markup does not guarantee a rich result.
Can invalid schema hurt SEO?
Misleading structured data can violate Google’s policies and may result in loss of rich result eligibility or other action. Ordinary syntax errors generally prevent the affected markup from being interpreted correctly.
Should I add Review schema to every article?
No. Review markup should only be used for genuine, eligible review content that satisfies Google’s guidelines.
Do I need a separate schema plugin with AIOSEO?
Usually not. First check the schema already generated by AIOSEO and determine whether additional functionality is necessary.
Conclusion
Schema markup is a useful part of technical SEO because it provides structured information about webpages, organizations, authors, products, and other entities.
In 2026, effective implementation requires understanding which Google Search features are still supported and which have been discontinued.
For WordPress websites, begin by reviewing the structured data already generated by All in One SEO.
Prioritize accurate Article, BreadcrumbList, WebSite, and publisher information where appropriate.
Use Google’s Rich Results Test and Schema Markup Validator to identify actual implementation issues.
Most importantly, remember that structured data supports search engines’ understanding of content but does not guarantee rankings, indexing, or enhanced search appearances.
For more information, consult:
- Schema.org
- Google Search Central Structured Data Documentation
- Google Rich Results Test
- Schema Markup Validator
Have questions about WordPress schema markup? Share them in the comments below.
