If a blocked resource is important, it could have a big effect on how Google understands the page. If the resource is important (see below), if it is on your own site, you might want to unblock the resource to Googlebot if it is on another site, you might want to contact the site's webmaster and ask to have it unblocked. The resource is blocked to Googlebot by a robots.txt file.The test accesses the page as an anonymous user ensure that all resources are accessible to anonymous users. The resource is inaccessible to non-logged-in users.The resource does not exist at the URL referenced (404 error).If it continues to happen, consider hosting the resource somewhere else, or else try to discover and fix the reason for lack of response from the host. In this case, try running the test again. The resource wasn't loadable in a reasonable amount of time.Here are some common reasons for resource loading issues: The Rich Results test tries to load only certain types of resources others that won't affect the test are ignored. Resources are external elements included by the page, such JavaScript files. If a test cannot load certain resources used by a page, you will get a warning. 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. If structured data was found but could not be parsed, that will be indicated here. Whether any structured data items were found on the page. If crawling failed, this will always fail.ĭetected Items / Detected structured data Page fetch: Whether the page could be fetched by the test.Crawl allowed? Tests whether a robots.txt rule on the site prevents this page from being crawled.Crawled as: Shows the type of user agent used for the crawl (smartphone or desktop).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. This section describes whether Google is permitted to crawl the page. Structured data with syntax errors detected.N valid items detected: Some have warnings.N valid items detected: All have warnings.The tool can report any the following status values for a tested URL where N depends on the number of items found. The test results cover the following areas: URL status The explorer uses the rendered source code.
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 test shows which rich result types were found on the page, as well as any errors or suggestions for your structured data. Be sure to remove any comments from JSON-LD before publishing your final page.
However, that behavior is not supported by the JSON-LD standard and so might result in errors in actual usage.
The Rich Results test tool ignores comments within JSON-LD blocks. The Rich Results test supports structured data in JSON-LD, RDFa, and Microdata
You can see if your site is mobile-first on your property's settings page.
For all sites, we recommend using the mobile user agent because this is how the majority of users browse the web today. 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. 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. Choose a user agent from the list below the URL or code entry textbox. You can choose which user agent to use when testing your page: that is, test your page with a smartphone or a desktop computer. You can modify the code and rerun the test by clicking Run test as often as you like. In the tool landing page, choose Code instead of URL for the test, then paste the code to be tested. You can test an arbitrary code snippet using this tool. If your page is behind a firewall or hosted on your local machine, you can test it by exposing a tunnel. Any resources that are behind a firewall or password-protected will not be available to the test. Important: All page resources must be accessible by an anonymous user accessing the code from the internet. Put structured data on your page to enable special features in Google Search results, then test it with the Rich Results test.