Rich Results Test

Put structured data on your page to enable special features in Google Search results, then test it with the Rich Results test. The full information you can find here:

Rich Results Test – Search Console Help

Run the test

For a URL

Submit the full URL of the page to test. Important: All page resources must be accessible by an anonymous user accessing the code from the internet. Any resources that are behind a firewall or password-protected will not be available to the test. If your page is behind a firewall or hosted on your local machine, you can test it by exposing a tunnel.

For a code snippet

You can test an arbitrary code snippet using this tool. In the tool landing page, choose Code instead of URL for the test, then paste the code to be tested. You can modify the code and rerun the test by clicking Run test as often as you like.

Optionally choose a user agent

You can choose which user agent to use when testing your page: that is, test your page with a smartphone or a desktop computer. Choose a user agent from the list below the URL or code entry textbox.

The default user agent is smartphone, because of Google’s mobile-first initiative, which reflects the increased use of mobile devices to access web pages. If your site is mobile-first, we recommend using the smartphone user agent for your testing, unless you have specific reasons to use the desktop user agent. For all sites, we recommend using the mobile user agent because this is how the majority of users browse the web today.

You can see if your site is mobile-first on your property’s settings page.

Supported structured data formats

The Rich Results test supports structured data in JSON-LD, RDFa, and Microdata

Review the results

The test shows which rich result types were found on the page, as well as any errors or suggestions for your structured data.

If there are errors or warnings, expand the individual item to see details, and click the description to open the code explorer in the corresponding location. The explorer uses the rendered source code.

The test results cover the following areas:

URL status

The tool can report any the following status values for a tested URL where N depends on the number of items found.

Crawling

This section describes whether Google is permitted to crawl the page. If Google is prevented from crawling the page as part of its regular crawl cycle (for example, is prevented from crawling by a robots.txt rule or noindex directive), the page cannot be tested with this tool.

• Crawled successfully / Crawl failed: 
• Crawled as: Shows the type of user agent used for the crawl (smartphone or desktop)
• Crawl allowed? Tests whether a robots.txt rule on the site prevents this page from being crawled.
• Page fetch: Whether the page could be fetched by the test. If crawling failed, this will always fail.

Detected Items / Detected structured data

Whether any structured data items were found on the page. If structured data was found but could not be parsed, that will be indicated here. Any items found, whether good, with warnings or errors, or unparseable, will be listed here, along with a description of the item and any issues.

• Page can’t be reached
• Page has unloadable resources
• Syntax errors in items of unknown type

Save test history

Search Console saves your code and test state each time you run the test. To save a version history of your code and tests, bookmark the page URL after running a test. Test history is saved for approximately 90 days. These bookmarks are accessible by anyone.

Share test results

You can use the Share button to share the test results browser link with anyone; permissions are not required to view the results. Test result links are valid for approximately 90 days.

See how your page might look in Google Search results

For some rich result types you can preview how the result might appear in Google Search or Google Assistant. If your page is eligible for multiple Search result layouts, this tool will include selectors to let you view the different layouts, including layouts for desktop and mobile searches.

You can experiment with your page by changing the code and rerunning the test to generate new layouts. You can share the URL in your browser with other users to share your rendered results.

Depending on what the tool finds on the page, you can choose a result type to view and select a desktop or mobile version.

Google does not guarantee that your page will appear exactly as shown here, or that any of the views shown will be applied to your page result; Google tries to show the best result for a search request, based on the user’s search history, location, and many other variables.

What is the Search Appearance report?

The Search Appearance report in Search Console shows all the types of rich results your content has earned. What’s more, it gives you data on how people interacted with those rich results, which helps you improve the content for those rich results. 

The performance report looks at two things:

• Clicks: the number of clicks from a search query on a search result page that ended up on your site.
• Impressions: how many times a user saw a mention of your search result. Every visit to the search results page counts as an impression, and your result doesn’t have to be in view to be counted. Of course, if your listing appears on the next page and the visitor doesn’t get there, it won’t count as an impression.

 

How to use the Performance report for your rich results

Want to get a sense of how your rich results are doing? The least you can do is regularly check Search Console. Go to Performance > Search results to open the report. Then, you can find the Search Appearance reports in two ways: by adding a new filter from the top bar called Search appearance or by clicking the Search Appearance tab below the graph.

Looking at a performance chart for FAQ rich results 

Picking a particular rich result — the FAQ in this case —, you can start to look at the data a little more clearly. In the screenshot below, you’ll see the overview data for this content type over a three-month period. This concerns all the content where you’ve added valid FAQ structured data.

You’ll notice the total clicks, impressions, CTR, and average position of your FAQs. This way, you’ll get a sense of how this type of content is performing on your site, and you get a rough idea of the way people are interacting with it.

Checking the performance of FAQ listings in Google

Drilling down

Of course, it gets more interesting when you start drilling down. In the screenshot below, we are looking at a particular page that shows strange behavior — something we can all see, right?

This page had an FAQ rich result that went from nothing to something to nothing. If you find something like this, it might be that Google’s behavior for this type of result has changed. It could be that it no longer shows an FAQ rich result for that term or page.

This is just a simple example of what you can find if you monitor your rich results in Google Search Console. Using this data, you can start improving your content to make your rich results perform even better. Of course, you can also use the data to target new ones!