Structured data helps search engines better understand the content and information on your website. When implemented appropriately, structured data can make a page eligible for certain types of enhanced search results, such as product details, recipes, or frequently asked questions. Google Rich Results Test is a useful tool for checking this data and identifying issues that need attention.
This article explains how to test a URL or code, interpret the results, distinguish errors from warnings, and fix common issues. The process is useful for website owners, SEO professionals, marketers, and development teams who need to review structured data before or after updating a page.
What Is Google Rich Results Test and What Is It Used For?
Google Rich Results Test is a Google tool for checking structured data on a web page and determining whether the page is eligible for certain types of rich results. It analyzes data that Google can read, then reports valid items, errors, and related warnings. This is a technical check, not a guarantee that the page will appear with a special format in search results.

Structured data is often written in JSON-LD, although websites can also use other formats supported by Google. This data provides organized information about entities on a page, such as a product name, price, availability, business name, article author, or publication date. When the data matches what users can actually see on the page, it gives search engines additional context to understand it.
Businesses can use the tool to:
- Check structured data on a published URL.
- Test a code snippet before deploying it to a live environment.
- Identify missing required properties or invalid values.
- Review sample pages after changing a design, plugin, or content management system.
- Recheck a page after the technical team updates its structured data.
A valid result means the data passed the tool’s relevant checks at the time of testing. However, whether rich results appear depends on other factors, including Google’s policies, content quality, page relevance, and how the system evaluates the website. Passing the test should not be considered a promise of rankings or traffic.
How to Test a URL or Code
Test a Live URL
To check a published page, open Google Rich Results Test, select the URL testing mode, and enter the page’s full address. Use the exact URL that users can access, including the https protocol if the page uses it. Start the test and wait for the tool to load the page and analyze its data. Processing time may vary depending on server responsiveness and page complexity.

When testing a URL, remember that the tool needs to be able to access its content. If a page requires a login, is blocked by a firewall, returns a server error, or prevents crawlers from accessing essential resources, the results may not reflect what users see. For a newly launched website, also make sure you test the public environment rather than a test URL that is only accessible internally.
Test a Code Snippet
If you do not want to edit the live website yet, select the code testing mode and paste the structured data snippet into the tool. This is useful when the development team is writing JSON-LD, when a marketer needs to check data generated by a content management system, or when comparing a snippet before and after an update. Make sure the code includes its opening and closing parts and uses valid JSON syntax.
Testing code helps identify issues in the data provided, but it does not prove that the code will be output correctly on the page after deployment. A website may add, modify, or remove some fields when rendering content. A good process is to test the code first, deploy it to the appropriate environment, and then test the live URL.
Before testing, identify the page’s content type and determine which structured data is actually appropriate. Do not add a schema type simply because a competitor uses it. The data should accurately describe the content on the page and comply with Google’s current guidelines. Adding irrelevant data or creating information that users cannot see may be misleading, undermine trust, and fail to make the page eligible to appear.
Interpreting Results: Valid Items, Errors, and Warnings
After analysis, the interface typically shows the data items it detected and their status. Review each item rather than relying only on the summary message. A URL may contain multiple types of structured data; one valid item does not mean all the others are correct. Open each item’s details to see what type of data the tool is reading and which fields need attention.

- Valid: The data item meets the requirements applied by the tool. This means no blocking errors were found that would make the item ineligible, but it does not guarantee that Google will display a rich result.
- Error: There is an issue that needs to be addressed, usually involving a required property, data type, syntax, or incorrect structure. An error may make the item ineligible for the corresponding result type.
- Warning: The tool has identified missing or less-than-optimal data that does not necessarily make the item fail. However, warnings should be reviewed to improve completeness and avoid issues if Google’s requirements change.
Read the detailed message and note the property it identifies, then compare it with the guidelines for that data type. For example, the tool may report a missing required field, an incorrectly formatted value, or inconsistent information. Do not make sweeping changes based on guesswork; determine where the field comes from, whether users can see it, and which system generates it.
It is also important to distinguish the test results from data that Google has indexed. The tool evaluates content at the time of the test, while search systems may need time to recrawl the page. A URL that is valid today may not remain valid if its content, code, access permissions, or policies change.
How to Fix Common Structured Data Errors
Missing Required Properties or Incorrect Data Types
If the tool reports a missing field, first check the requirements for that data type and determine whether the information actually exists on the page. If it does, update the JSON-LD template or plugin settings to output the correct field. If the information does not exist, do not invent a value just to pass the test. Consider using a schema type that better fits the actual content.

Data types must also be correct. A field that expects a date, URL, number, or nested object cannot be replaced arbitrarily with text in an unsuitable format. Read the error message, identify the structure the tool expects, and fix the data at its source. On a CMS website, the source may be a plugin, custom field, theme template, or separately added code.
Invalid JSON-LD Syntax or Inconsistent Data
Common syntax errors include missing brackets, extra commas, incorrect quotation marks, or misspelled property names. If the code is lengthy, check it block by block or reformat it to make it easier to read. For automatically generated data, also check edge cases such as empty fields, titles with special characters, inconsistently formatted prices, or pages missing certain fields.
Compare the structured data with the visible page content. Product names, prices, availability, business addresses, authors, and publication dates should accurately reflect the page. If information has changed but the schema still contains old data, fix the synchronization process instead of updating just one URL. For websites with multiple page templates, check several representative pages to identify template-level issues.
Test Again After Making Changes
- Fix the data at the source that generates it, such as a plugin, CMS, or source code template.
- Deploy the changes to the environment you need to test, and clear the cache if the website uses caching.
- Run the test again using code or a URL, depending on the deployment stage.
- Open the details to confirm the errors are gone, and review any remaining warnings.
- Record the URL, data type, issue, and changes made for easier tracking.
If no data appears after you have added the code, check whether the code is actually present on the page, whether the URL is accessible, and whether the content is blocked. Some optimization tools, plugins, or caching layers may alter the output code. In complex cases, SEO specialists and developers should work together to determine whether the issue lies in the content, configuration, or page rendering.
A Regular Website Testing Process
Schema should not be checked just once when a website launches. Changes to the design, a CMS migration, the installation of an SEO plugin, product template updates, or URL structure changes can all affect structured data. Businesses should include testing in their release process and conduct regular reviews, particularly for important pages that generate revenue or attract leads.

For large websites, group URLs by content template rather than checking every page manually. Choose representative pages for the homepage, articles, categories, products, or locations, then test additional URLs with special configurations. Tracking results alongside technical changes helps teams catch new issues early and avoid duplicating work across departments.
LilyTech can help businesses review their websites, content structures, and technical SEO factors. By combining structured data checks with assessments of crawlability, speed, and page experience, businesses can gain a more complete picture instead of focusing on a single error message.
Conclusion
Google Rich Results Test checks structured data using a URL or code, identifies errors, and highlights areas that need improvement. To use it effectively, choose schema that fits the actual content, read each message carefully, fix the data at its source, and test again after deployment. A valid result is an important check, but it does not guarantee that a website will appear as a rich result.
If your business needs a structured data review, website platform optimization, or a technical SEO plan, contact LilyTech for advice tailored to your current setup and business goals.
Đoàn Lê Minh Anh