Google’s tool for checking supported rich-result structured data and implementation issues in a URL or code snippet.
Google’s Rich Results Test checks a URL or code snippet for structured data associated with supported Google rich-result features. It identifies detected items and reports relevant errors or suggestions. This helps diagnose implementation issues before or after publication.
The tool is narrower than a general Schema.org vocabulary validator. A page can contain valid structured data that is not a supported rich-result type. Conversely, passing the technical checks does not establish that every content policy is satisfied or guarantee that a rich result will be shown.
A URL test and a pasted-code test answer different questions. Code testing can help isolate a markup issue, while testing the live page helps show what is actually available to the test. Neither should be described as proof that Google has indexed the page or will display it in a specific form.
Takeaway: Use the test to resolve supported structured-data issues, then separately review policy eligibility and the accuracy of the visible content.
Example
A business corrects a malformed opening-hours value in its markup and the test no longer reports that error. The repair is useful evidence about the implementation. It is not a promise that the page will immediately receive an enhanced search appearance.
What to check
Inspect the individual detected item and its messages rather than only the top-level label. Retest the deployed page after changes and keep feature requirements current. Do not relabel an entity inaccurately just to obtain a passing result.
For more detail, see Rich Results Test.