How can I test if my schema markup is working correctly?
Testing your schema markup ensures it's properly implemented and can lead to rich results in search engine listings. Use tools like Google’s Rich Results Test, Schema Markup Validator, and Google Search Console to validate your markup and identify any errors or issues for better SEO performance.
It's essential to note that the Rich Results Testing Tool only validates schema.org types that are eligible for rich results in search. While you can still use the tool to check the "raw" JSON-LD for crawlers if you’re using non-eligible types, it won't provide feedback on rich results.
To get a comprehensive view of all markup types on a page, it's recommended to use this tool in conjunction with other structured data testing tools.
How to Test Your Schema Markup: Step-by-Step Guide
There are several ways to test if your schema markup is working correctly. Below are the most effective methods you can use.
1. Check the Presence of Schema Markup in the Page Source
Before using testing tools, the first step is to verify that the schema markup is present on your page.
Steps:
Right-click on your webpage and select "View Page Source" (or use the keyboard shortcut
Ctrl + U
on Windows orCmd + Option + U
on macOS).In the source code, press
Ctrl + F
(Windows) orCmd + F
(macOS) and search for "LD+JSON" or "schema.org".If the markup is present, you should see the relevant JSON-LD code or microdata within the HTML.
While this method ensures that the schema markup is on the page, it doesn't validate whether it's properly implemented or if it's being read correctly by search engines.
2. Webrex SEO Schema (JSON-LD) Optimizer’s Analyzer
The Webrex SEO Schema (JSON-LD) scans up to 10,000 pages on a site, detecting JSON-LD, RDFa, and microdata, including dynamically loaded content. After the scan, it generates a comprehensive health report that categorizes analyzed items by type. By selecting "Show Details" for each item, you can view the specific URLs where it appears, along with any errors or warnings. This eliminates the need for manual URL input, offering you a dashboard overview of all products, complete with their associated errors and warnings.
This tool ensures your schema follows schema.org syntax and adheres to strict guidelines, helping you optimize your markup beyond Google’s basic requirements. It also detects potential issues that could prevent Google from reading your markup, such as site speed problems. For instance, if errors indicate “missing” properties that you’re confident are present, it’s worth checking your site speed to ensure all markup is fully accessible to search crawlers.
In essence, the Analyzer provides an in-depth, comprehensive overview of your schema’s health, pinpointing areas for improvement and optimization.
The Analyzer is available to all Webrex SEO Schema (JSON-LD) Optimizer paid users, from Pro to Enterprise.
Coming soon: Future updates to the Analyzer will introduce new features, including:
Additional Schema Markups
Support for nesting schemas in large businesses
Enhanced user experience with improved flow and a historical data view to track schema trends over time.
3. Use Google’s Rich Results Test
Google’s Rich Results Test is a dedicated tool for checking if your page is eligible for rich results, such as rich snippets, stars, and other enhanced features in search results.
Steps:
Go to the Rich Results Test page.
Enter the URL of your page or paste the raw HTML code containing the schema markup.
Click "Test URL" or "Test Code".
The tool will display the types of rich results your page can potentially qualify for and show a preview of how they might appear in SERPs.
If there are errors in the markup, the tool will highlight them, making it easy to pinpoint issues such as missing properties or incorrect data types.
The Rich Results Test only works for schema types that are eligible for rich results (such as Product, Article, Review, and Recipe schemas). If the schema is not eligible, the test will show you the raw JSON-LD data but won't validate its eligibility for rich results.
4. Use the Schema Markup Validator
Google’s Schema Markup Validator (previously known as the Structured Data Testing Tool) is a more general tool for validating all types of schema markup, regardless of whether they're eligible for rich results.
Steps:
Visit the Schema Markup Validator page.
Enter the URL or paste the raw HTML code containing your schema markup.
Click "Run" to initiate the validation.
The tool will analyze the schema and display any warnings, errors, or missing fields in your structured data.
The Schema Markup Validator is more comprehensive than the Rich Results Test because it checks all schema types (not just those eligible for rich results). It ensures that your markup adheres to schema.org standards and is properly formatted.
5. Use Google Search Console (GSC)
Once your schema markup is live on your website, Google Search Console (GSC) is an excellent tool for monitoring its performance and detecting any issues over time.
Steps:
Log in to Google Search Console.
Under the "Enhancements" section, check for reports related to structured data, such as "Rich Results" or "Structured Data".
GSC will list any errors or warnings related to the structured data on your site, such as missing or incorrectly formatted schema types.
You can also use the "Test live URL" option to test individual pages in real-time for schema-related issues.
Note that it may take several days or even weeks for the data to appear in GSC after you deploy the schema markup.
6. Check for Errors in Google’s Mobile-Friendly Test
If your website’s schema markup is dynamically generated through JavaScript, it’s crucial to test whether Google can crawl and render the markup properly on mobile devices.
Steps:
Use Google’s Mobile-Friendly Test.
Enter your page’s URL and click "Test URL".
The tool will check the page for mobile usability issues and highlight any problems with rendering JavaScript-based schema markup.
This is particularly important for websites with JavaScript frameworks like Angular, React, or Vue.js, where schema markup might not be visible in the initial HTML source code.
7. Review the Structured Data in the Search Engine Results Pages (SERPs)
Another way to check if your schema markup is working is by performing a search on Google and reviewing the search results.
Search for content that matches your schema, such as a product, review, or article.
Look for rich snippets like star ratings, product prices, or event details in the search results.
If you see the enhanced content, it means your schema markup is being processed correctly and that your page qualifies for rich results.
However, it’s important to note that rich results aren’t always displayed immediately. Google may take time to evaluate and feature your markup in SERPs.
8. Consider Using Dynamic Schema Markup Testing Tools
If your site uses dynamic schema markup (i.e., markup generated by JavaScript), you'll need to test your schema dynamically. For this, tools like Schema Markup Validator and Google’s Mobile-Friendly Test can validate dynamically loaded content.
Common Issues to Look Out For
Missing required properties: Ensure all required fields for your chosen schema type are included (e.g., for a Product schema, make sure you include
name
,price
, andbrand
).Incorrect data types: For example, if a property requires a date format, ensure the data is structured properly (e.g., use
YYYY-MM-DD
for dates).Improper nesting of schema types: When combining multiple schema types (e.g., Article with Product), ensure they are nested correctly.
Conclusion
Testing your schema markup is a critical step to ensure it’s correctly implemented and functioning as intended. By using a combination of tools like the Rich Results Test, Schema Markup Validator, Google Search Console, and manual methods, you can validate your markup, identify errors, and optimize it for better performance in search engine results. Regular testing and monitoring of your schema can help improve your site’s visibility, lead to rich results, and enhance your overall SEO strategy.
Did this answer your question?