Schema Markup Validator vs. Rich Results Test
-
I am working on a schema markup project. When I test the schema code in the Schema Markup Validator, everything looks fine, no errors detected. However, when I test it in the Rich Results Test, a few errors come back.
What is the difference between these two tests? Should I trust one over the other? -
@Collegis_Education
Step-1
The Schema Markup Validator and the Rich Results Test are two distinct tools that serve different purposes in the context of schema markup. The Schema Markup Validator primarily focuses on validating the syntactical correctness of your schema code. It checks if your markup follows the structured data guidelines and is free from any syntax errors. This tool is useful during the initial stages of schema implementation to ensure that your code aligns with the schema.org specifications.Step-2
The Role of Rich Results Test
On the other hand, the Rich Results Test is designed to provide insights into how Google interprets your schema markup and whether it generates rich results in the search engine. It simulates Google's search results and displays how your content may appear as a rich result. This tool not only checks for syntactical correctness but also evaluates how well your schema markup aligns with Google's guidelines for generating enhanced search results. Therefore, it focuses more on the practical impact of your schema markup on search engine results.Step-3
Trusting the Results
Both tools are valuable in their own right. During the implementation phase, it's crucial to use the Schema Markup Validator to ensure your code's correctness. However, for a comprehensive understanding of how your schema markup will perform in search results, the Rich Results Test provides a more dynamic analysis. Trusting one over the other depends on your specific goals – the Schema Markup Validator for code validation and the Rich Results Test for evaluating the potential impact on search results. To illustrate, in my recent post I utilized schema markup, and both tools played a role in ensuring its accuracy and potential visibility in rich results. -
@Collegis_Education said in Schema Markup Validator vs. Rich Results Test:
I am working on a schema markup project. When I test the schema code in the Schema Markup Validator, everything looks fine, no errors detected. However, when I test it in the Rich Results Test, a few errors come back.
What is the difference between these two tests? Should I trust one over the other?When working with schema markup, it's important to understand the purpose of different testing tools and what aspects of your markup they're evaluating.
Schema Markup Validator (formerly known as Structured Data Testing Tool):
This tool focuses on checking the syntax and vocabulary of your schema markup against Schema.org standards.
It ensures that your markup is logically structured and semantically correct.
It does not necessarily check for compliance with Google's guidelines for rich snippets or rich results.
Rich Results Test:This tool is provided by Google and specifically checks for compatibility with Google Search's rich results.
It not only checks the validity of the schema markup but also whether it meets the specific guidelines and requirements set by Google to display rich results in its search engine.
It simulates how your page might be processed by Google Search and whether your schema can generate rich results.
The difference between the two tests lies in their scope. The Schema Markup Validator checks for general correctness according to Schema.org, which is broader and platform-agnostic. The Rich Results Test is more specific and checks for compatibility with Google's search features. I have used schema for internet packaging website and I found usful.Should you trust one over the other? It depends on your goals:
If you want to ensure your markup is correct according to Schema.org and potentially useful for a variety of search engines and platforms, the Schema Markup Validator is the way to go.
If your primary concern is how your markup will perform on Google Search and you're looking to leverage Google's rich results, then the Rich Results Test is more pertinent.
Ideally, your markup should pass both tests. It should be correctly structured according to Schema.org standards (which you can ensure using the Schema Markup Validator), and it should also be optimized for Google's rich results (which you can check using the Rich Results Test). If you're encountering errors in the Rich Results Test, it's likely because your schema markup doesn't meet some of Google's rich result guidelines, and you should adjust your markup accordingly. -
The Schema Markup Validator checks the syntax and structure of your schema code, ensuring it aligns with schema.org specifications. It's crucial for catching initial errors. On the other hand, the Rich Results Test specifically focuses on how your schema markup qualifies for rich results in Google Search, providing insights into how it appears in search results. For Google integration and visual representation, prefer the Rich Results Test. Use both tools together to ensure technical correctness and effective integration with Google's search algorithms.
-
The Schema Markup Validator primarily checks the technical correctness and adherence to schema.org standards of your structured data markup. It ensures that your markup is syntactically correct and follows the specified schema guidelines.
On the other hand, the Rich Results Test goes beyond syntax validation. It assesses how well your page qualifies for rich results (enhanced search results) in Google's search listings. This includes checking if your markup meets the specific requirements for generating rich snippets, knowledge panels, or other enhanced search features.
In essence, while the Schema Markup Validator focuses on the technical aspects of your markup, the Rich Results Test evaluates its potential impact on search results appearance. Both tools are valuable, and it's recommended to use them in conjunction to ensure comprehensive testing of your schema markup. If the Rich Results Test identifies errors, addressing them can enhance your chances of achieving rich results in Google's search listings.
-
@Hazellucy I will create the different Schemas for my movies related website. I will use the Rich result test tool that is work for me. But that is depend on you which one you want to use for creating schema code. Rich result is google official tool. So I recommend you to use this one.
-
I will create schemas for my movie related website. I will create different type of schema like FAQs and content schema and I will use more rich result test tool that is work for me.
-
This post is deleted! -
The primary difference between the Schema Markup Validator and the Rich Results Test from Google is that the Rich Result test is restricted to testing only the markup of structured data that's used in Google's results for the search. However, the Schema.org markup validation is more intended for "general purposes" and is geared towards debugging various other types of structured data in addition to the ones that Google supports.
Currently Google supports only a limited number of Schema Markups that includes:
Article, Breadcrumb, Carousel, Course, COVID-19 Announcements, Dataset, Employer, Aggregate Rating, Estimated Salary, Event, Fast Check, FAQ, Home Activities, How-To, Image License, Job Posting, Job Training, Local Business, Logo, Math Solvers, Movie, Practice Problems, Product, Q&A, Recipe, Review Snippet, Sitelinks, Search Box, Software App, Speakable, Video, Subscription and Paywalled Content, Article / Blog Posting, etc.This means that the markup validator may be showing that there are no issues with the way your schema is written syntactically, but Google may still have an issue generating a particular type of search result based on that schema.
Both of the tools can still be used for better SEO and achieving featured results in the SERPs. The Rich Result Testing tool doesn’t offer the code editing option though, so the Schema Markup Validator tool can come in handy for troubleshooting any Schema markup issues.
There are a number of Data Types supported by the Google Rich Result Testing Tool for existing Schema Libraries supported by Google and those Data Types can be used when testing different types of the Schema markup through Schema Markup validator tool.
-
@kavikardos thank you, that's helpful!
-
Hey @collegis_education! The primary difference between the two tools is that the Rich Results Test shows what types of Google results can be generated from your markup, whereas the schema markup validator offers generic schema validation. So the markup validator may be showing that there are no issues with the way your schema is written syntactically, but Google may still have an issue generating a particular type of search result based on that schema.
Be sure to take a close look at the errors the Rich Results Test is throwing, as some are more like warnings - not every aspect of the schema is necessary in order for Google to generate a rich result, but obviously if there's a particular piece of the markup that's missing (i.e. In-Stock status), it won't be included in that result.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Anyone come accross a completely random site name displayed in the SERPs?
Hello SEO friends, I am looking at a site that has a completely random site name displayed in the serps. The site in question is a hypnotherapy service and the site name is displaying as a commercial cargo airline! See the screen shot. Any ideas? There is 'local business' structured data on the site and it IS showing the correct business name. Is this a hack? Negative SEO attack? Random Google stuff up? Help! Very confused! Thank you for any advice! Sean!Untitled.jpg
Intermediate & Advanced SEO | | sean.e0 -
What Schema would a Web design/development/seo ageny use and what is the schema.org link?
What Schema would a Web design/development/SEO Ageny use, and what is the schema.org link? I cannot for the life of me figure it out. ProfessionalService has been deprecated.
On-Page Optimization | | TiagoPedreira0 -
Unsolved Duplicate LocalBusiness Schema Markup
Hello! I've been having a hard time finding an answer to this specific question so I figured I'd drop it here. I always add custom LocalBusiness markup to clients' homepages, but sometimes the client's website provider will include their own automated LocalBusiness markup. The codes I create often include more information. Assuming the website provider is unwilling to remove their markup, is it a bad idea to include my code as well? It seems like it could potentially be read as spammy by Google. Do the pros of having more detailed markup outweigh that potential negative impact?
Local Website Optimization | | GoogleAlgoServant0 -
Bolded words in search results
are those synonyms or semantically related keywords ? Thank you,
Intermediate & Advanced SEO | | seoanalytics0 -
JSON Schema with Multiple Affiliations
I have an attorney that has multiple affiliations that I want to mark up with JSON schema. What is the best way to do this?... Option #1: "affiliation": "Example 1, Example 2", Option #2 "affiliation": "Example 1",
Intermediate & Advanced SEO | | seo_columbus
"affiliation": "Example 2", Or, is there another way to do this that I haven't considered?0 -
Google Is Indexing My Internal Search Results - What should i do?
Hello, We are using a CMS/E-Commerce platform which isn't really built with SEO in mind, this has led us to the following problem.... a large number of internal (product search) search result pages, which aren't "search engine friendly" or "user friendly", are being indexed by google and are driving traffic to the site, generating our client revenue. We want to remove these pages and stop them from being indexed, replacing them with static category pages - essentially moving the traffic from the search results to static pages. We feel this is necessary as our current situation is a short-term (accidental) win and later down the line as more pages become indexed we don't want to incur a penalty . We're hesitant to do a blanket de-indexation of all ?search results pages because we would lose revenue and traffic in the short term, while trying to improve the rankings of our optimised static pages. The idea is to really move up our static pages in Google's index, and when their performance is strong enough, to de-index all of the internal search results pages. Our main focus is to improve user experience and not have customers enter the site through unexpected pages. All thoughts or recommendations are welcome. Thanks
Intermediate & Advanced SEO | | iThinkMedia0 -
Does anyone have any experience using GoodRelations Snippet Generator for E-Commerce versus markup from Schema.org?
I am trying to implement Structured Data markup on a large e-commerce site that has ancient code and is not on any standard e-commerce platform. It is a Webstore we self-host that was developed for us and heavily customized. What's worse is that I don't have access to the source code. I have to somehow instruct our IT Director how and where to place everything. So I'm going to need to be meticulously specific. As I began wading through our code and determining where to insert code as instructed by Schema.org I ran across this on one of their pages: "This class contains derivatives of properties from the GoodRelations Vocabulary for E-Commerce, created by Martin Hepp. GoodRelations is a data model for sharing e-commerce data on the Web that can be expressed in a variety of syntaxes, including RDFa and HTML5 Microdata. More information about GoodRelations can be found at http://purl.org/goodrelations/." I went to check it out and it appears that this could be a great resource as it has a snippet generator and several "cookbooks" for adding micro data to our site. Here's a link to their snippet generator: http://www.ebusiness-unibw.org/tools/grsnippetgen/ However, with a catalog of 5,000 SKUs, needless to say we aren't going to plug in our products into this generator one-by one. Has anyone here successfully used GoodRelations to help them implement micro data into a large E-commerce site that isn't a standard platform (not Magento, WP, Joomla or Volusion) ?? I would be very greatful to anyone who can share their experiences and or make suggestions on how we might best proceed. Thanks! Dana
Intermediate & Advanced SEO | | danatanseo0 -
Domain vs Subdomain for Multi-Location Practice
I have a client who has 2 locations (Orlando & Tampa) and would like to keep the current domain for both locations (DA 29). We want to target additional cities within each service area (Orlando & Tampa). Each service area would target 2 cities on the main pages and 4-5 cities with "SEO" pages which contains unique content specific to the given city. Would I be better off creating sub domains (www.orlando.domain.com & www.tampa.domain.com), creating subfolders (www.domain.com/orlando, etc) or keeping the domain as is and create SEO pages specific to each city? We want to spread the domain authority to both locations.
Intermediate & Advanced SEO | | Red_Spot_Interactive0