Google Rich Results Test: Complete Structured Data Testing Guide
Google Rich Results Test helps you check whether structured data on a webpage is technically eligible for rich-result features supported by Google Search. You can test a live URL or individual code, inspect detected structured data, identify critical errors and preview certain supported search appearances. This guide forms part of our broader Google playbook.
What Does the Rich Results Test Actually Test?
The Rich Results Test is focused on structured data that Google currently uses for supported search features rather than every type defined by Schema.org.
Detect Supported Markup
The tool identifies structured-data items that correspond to Google-supported rich-result features and shows how Google interprets the markup on the page.
Check Eligibility
Required properties and structural requirements are checked so you can see whether the detected item is technically eligible for its relevant Google Search feature.
Preview Supported Results
For selected rich-result types, Google can provide a preview showing how the enhanced search appearance could look. A preview is illustrative rather than a promise that the result will be shown.
Test a Live URL or Test Structured Data Code
The Rich Results Test supports both live-page diagnosis and pre-deployment code testing.
Test a Live URL
Enter a publicly accessible page URL when you want to see how Google can retrieve and interpret the structured data currently deployed on that page.
- Useful after publishing schema to a live page.
- Confirms whether Google can fetch the tested page.
- Shows detected eligible structured-data types.
- Helps identify deployment-specific issues.
- Useful before requesting recrawling in Search Console.
Test Code Before Publishing
Paste structured-data code directly into the tool when you are developing or debugging markup before it is deployed to the live website.
- Useful while creating JSON-LD.
- Test changes before touching production.
- Isolate schema from unrelated page code.
- Experiment with required and recommended properties.
- Retest repeatedly while fixing errors.
JSON-LD, Microdata and RDFa
Google supports three structured-data formats for rich-result eligibility, with JSON-LD recommended for most implementations.
JSON-LD
JSON-LD usually lives inside a dedicated
<script type="application/ld+json">
block and can represent structured data without embedding properties
throughout individual HTML elements.
Microdata
Microdata adds structured-data attributes directly to HTML elements. It remains supported, but can be harder to maintain when markup becomes complex or templates change frequently.
RDFa
RDFa extends HTML with attributes that describe entities and relationships. It is also supported for Google structured-data features where the relevant markup requirements are satisfied.
Valid Items, Warnings and Critical Errors
Not every message in the test has the same consequence. Critical errors should be prioritised before recommended-property warnings.
Valid Item
The detected structured-data item contains the required information needed for technical eligibility under the relevant Google feature guidelines.
Non-Critical Warning
A recommended property or additional piece of information may be missing, but the item can often remain technically eligible for the supported feature.
Critical Error
A required property, invalid value or structural problem prevents the item from meeting Google's technical eligibility requirements for that rich-result feature.
Valid Structured Data Does Not Guarantee a Rich Result
Technical validity is only the first requirement. Search appearance remains an algorithmic decision.
“Valid” Means Eligible — Not Guaranteed
Even correctly implemented structured data can appear as an ordinary search result rather than a rich result. Google selects search features according to the query, page, device, location, overall search experience and other systems.
Structured data must also accurately describe the visible content of the page and comply with both Google's general structured-data policies and the specific policies for the feature being targeted.
Examples of Google-Supported Structured Data Types
Google supports a defined set of structured-data search features. This is not the same as supporting every type available on Schema.org.
Article
Structured information describing eligible article and news-style content.
Breadcrumb
Describes a page's position inside the website hierarchy.
Event
Describes eligible events with information such as dates, venue and event details.
Job Posting
Describes employment opportunities that satisfy Google's JobPosting requirements.
Local Business
Describes supported business information associated with a physical or local entity.
Organization
Helps describe an organisation and relevant business identity information.
Product
Can describe products, offers, availability, pricing and other supported product information.
Recipe
Describes eligible recipe content including ingredients, instructions and related recipe details.
Review Snippet
Supports eligible review and aggregate-rating information under Google's review policies.
Video
Describes video content using supported properties that help Google understand the media.
Q&A Page
Supports qualifying pages where users submit answers to a question, subject to current feature policies.
Dataset
Structured information for datasets that meet Google's dataset feature requirements.
Do Not Rely on Old Structured Data Tutorials
Google changes which structured-data features it uses in Search, so valid Schema.org markup is not automatically a currently supported Google rich result.
Google Removed FAQ Rich Results in 2026
FAQ markup is a useful example of why structured-data advice must be kept current. Google reduced FAQ rich-result visibility substantially in earlier years and then removed the FAQ rich-result feature from Google Search in May 2026.
That means an older guide telling every website to add
FAQPage purely to earn FAQ dropdowns in Google Search is now
outdated.
The same principle applies to every structured-data type: check Google's current Search Gallery and feature documentation before investing in markup for a search appearance that may no longer be supported.
A Practical Rich Results Test Debugging Workflow
Fix schema methodically. Avoid randomly adding properties until the test turns green.
Run the Test
Test the live URL or paste the structured-data code you are currently debugging.
Confirm the Fetch
When testing a URL, first make sure Google can retrieve and render the page as expected.
Open the Invalid Item
Inspect the exact detected type and identify which property is missing, invalid or incorrectly nested.
Fix & Retest
Compare the markup against the current Google documentation, make the specific correction and rerun the test.
Deploy & Monitor
Publish the fix and use Search Console where an applicable structured-data report exists.
Structured Data Errors Worth Checking First
The exact errors depend on the rich-result type, but several implementation patterns cause problems repeatedly.
Missing Required Property
A feature-specific required property has not been supplied. Check Google's documentation for the exact structured-data type and add the property only when it accurately exists for the page.
Wrong Value Type
A property may expect a URL, number, date, object or another defined value type. Supplying the wrong format can make otherwise sensible markup invalid.
Incorrect Nesting
Nested entities must be connected correctly. Reviews, offers, ratings, videos and other entities cannot simply be inserted anywhere in the JSON-LD tree without the proper relationship.
Markup Does Not Match the Page
Do not describe prices, ratings, products, jobs, events or other information that visitors cannot actually find on the visible page.
Uncrawlable Image or URL
URLs referenced by structured data may need to be accessible to Google. Blocked, invalid or inaccessible resources can reduce the usefulness of the markup.
Using Obsolete Feature Guidance
The schema may be technically valid while the Google Search feature you are targeting has changed or been retired. Always verify current support.
Can One Page Have Multiple Structured Data Types?
Yes. A page can legitimately contain several structured entities when each one describes visible content and the relationships are represented correctly.
Describe the Real Structure of the Page
For example, a product page might include Product information together with Offer data and supporting review information. An article might also contain a VideoObject when the page genuinely includes a relevant video.
The goal is not to add as many schema types as possible. The goal is to help machines understand the entities and relationships that actually exist on the page.
For complex sites, structured data should also fit into the wider website architecture rather than being added inconsistently to isolated URLs.
Rich Results Test vs Schema Validator vs Search Console
These tools overlap, but they answer different structured-data questions.
Rich Results Test
Use it to test Google-supported rich-result structured data, identify technical eligibility problems and preview selected Search appearances.
Schema Markup Validator
Use a generic Schema.org validator when you want to validate broader Schema.org vocabulary, including types and properties that Google may not use for a dedicated Search rich result.
Google Search Console
Use Google Search Console for ongoing monitoring after deployment, including applicable rich-result or enhancement reports and URL Inspection for how Google sees a specific page.
Use Search Console After the Rich Results Test
The Rich Results Test is excellent for a particular test. Search Console is better suited to understanding what Google sees across the verified site over time.
Testing Is Not the Same as Google's Indexed View
After fixing and deploying structured data, Google still needs to crawl and process the updated page. Search Console's URL Inspection tool can help you investigate how Google sees a specific URL and request recrawling where appropriate.
Where Google provides an enhancement or rich-result report for the relevant type, Search Console can also surface groups of valid and invalid items across the property.
For broader indexing diagnostics, canonical issues, sitemaps and crawl problems, use our complete Google Search Console guide.
Where Structured Data Testing Becomes Especially Important
Different page types require different structured-data strategies and different Google Search policies.
Ecommerce & Product Pages
Product markup can describe information such as offers, pricing, availability and reviews where those properties satisfy Google's Product requirements. Ecommerce sites should also coordinate structured data with their wider Google Merchant Center setup rather than treating schema as the entire shopping strategy.
Local Businesses
LocalBusiness and Organization data can help Google understand business information, but markup should not be confused with managing or ranking a Google Business Profile. The two systems serve related but different purposes.
Articles & Content Sites
Article, Breadcrumb, Video and other applicable markup can provide useful machine-readable context. Structured data should support high-quality content rather than substitute for the on-page SEO work required to satisfy search intent.
Avoid Misleading or Manipulative Schema Markup
Technically valid markup can still violate Google's structured-data quality policies.
Structured Data Must Describe the Real Page
Do not create fake reviews, fictitious ratings, misleading offers, false business information or markup for content users cannot actually see. Structured data should accurately reflect the page's primary subject and visible information.
Google can apply a structured-data manual action that removes eligibility for rich-result appearance. This is distinct from saying that the ordinary page must disappear from normal web ranking.
Structured Data Is Useful — But It Is Not Your Entire SEO Strategy
A technically perfect rich-result test cannot compensate for weak content, poor indexing, bad architecture or insufficient relevance.
Technical Eligibility
Structured data helps search engines understand entities and makes supported features technically possible. It does not guarantee rankings or replace the wider factors explained in our Google ranking factors guide.
Audit the Whole Page
Combine structured-data testing with crawling, indexation, content, performance and internal-link analysis through a broader SEO audit or automated SEO Checker.
Use the Right Diagnostic Tool
Rich Results Test diagnoses structured data, not site speed, backlinks, keyword difficulty or complete indexability. Explore additional platforms in our SEO tools hub.
Common Questions About Google Rich Results Test
Answers to common questions about validity, JSON-LD, schema warnings, eligibility and Google Search appearance.
01 What is Google Rich Results Test?
Google Rich Results Test is Google's structured-data testing tool for checking which supported Google rich-result features may be generated from the structured data on a page or in a supplied code sample.
02 Does passing the Rich Results Test guarantee a rich result?
No. Passing confirms technical eligibility for the detected supported feature. Google does not guarantee that a rich result will actually appear for a particular query.
03 What is the best structured-data format for Google?
Google supports JSON-LD, Microdata and RDFa. Google recommends JSON-LD for structured-data implementation in most situations.
04 What is the difference between an error and a warning?
A critical error normally means a required property or technical condition prevents eligibility. A non-critical warning often concerns a recommended property that can improve completeness but may not prevent eligibility.
05 Why does the test say no items detected?
The page may not contain structured data recognised for a currently supported Google rich-result feature, the markup may be invalid, or the structured data may use Schema.org vocabulary that Google does not expose as a dedicated rich result.
06 Can I test structured data before publishing a page?
Yes. The Rich Results Test allows structured-data code to be tested directly, which makes it useful during development before the markup is deployed to a public URL.
07 Can one page contain several schema types?
Yes, when the entities genuinely exist on the page and the structured-data relationships are represented correctly. Adding unrelated schema purely to increase the number of detected items is not a useful strategy.
08 Is Schema Markup Validator the same as Rich Results Test?
No. Rich Results Test focuses on structured data used for Google-supported rich-result features. A generic Schema.org validator can validate a much broader range of Schema.org vocabulary.
09 Do FAQ pages still get FAQ rich results?
Google removed the FAQ rich-result feature from Google Search in May 2026. Older SEO tutorials recommending FAQPage markup specifically to obtain FAQ dropdowns in Search are therefore outdated.
10 Should I use Search Console after fixing structured data?
Yes. After deployment, use Google Search Console to inspect the URL and monitor relevant enhancement or rich-result reports where Google provides them.
Use Structured Data to Describe the Page — Not to Manufacture a Search Feature
The Rich Results Test is most useful when structured data is treated as a machine-readable description of genuine page content. Start with the rich result that actually applies to the page, implement the required properties, add useful recommended information where it exists, fix critical errors and confirm that the deployed page remains accessible to Google. A green test means the implementation has cleared an important technical hurdle; it does not mean Google is required to show an enhanced result, and it does not replace strong content, crawlability, architecture or wider SEO.
