Glossary · Rich Results Test
Google's tool to test and preview structured data: it shows the rich result features it detected and whether the markup is valid. It tests either a URL or a pasted code snippet.
Google’s documentation 2
Documented in
Search Console Help separates critical issues, which make a structured-data item invalid and stop it from appearing as a rich result, from non-critical issues, listed under 'Improve item appearance'; the Rich Results Test reports valid items that have warnings.
Google Search Console Help · Day 1 · Lightning session A: Automation and AI
Google's Rich Results Test help says the tool tests either a page's full URL or a pasted code snippet (Code instead of URL); all page resources must be reachable by an anonymous user on the internet, so resources behind a firewall or a password are not available to the test unless exposed, for example through a tunnel.
Google Search Console Help · Day 1 · Lightning session A: Automation and AI
Said at the event 6
Slide and stage claims that name it, the ones Google’s documentation does not cover first.
Not in docs 1
Google's planned validation workflow has five steps: download the rules from the feature guide, generate the JSON or embedded microdata or RDFa, run the rules against the generated server-side markup as a first check, deploy and test in the Rich Results Test, and monitor ongoing performance in Search Console.
Day 2 · What is Structured Data and why we need it on the internet.
Consistent with docs 2
A community demo's script used both input modes of Google's Rich Results Test: the URL mode for public pages, which Google fetches itself, and the code mode, into which the script pasted the page's HTML, for private pages and pages Google cannot fetch (best reading of a largely unintelligible recording; the second kind of page was heard as 'dead', possibly 'dev').
Day 1 · Lightning session A: Automation and AI
In a community demo, the structured-data problems Google's Rich Results Test reported on the test page included an empty name, a breadcrumb problem and a price of zero, with errors shown in pink and warnings in orange (best readings of a largely unintelligible recording; each item is heard in only one of the two recordings).
Day 1 · Lightning session A: Automation and AI
Nothing to verify 1
A community demo showed a script that opens Chrome with a saved session, pastes a URL into Google's Rich Results Test, waits about 15 seconds, then screenshots and saves the result and retries on failure (the demo's recording is largely unintelligible; the tool name is a best reading).
Day 1 · Lightning session A: Automation and AI
Press and analysis 2
Because Web Fragments monkey-patches core browser APIs such as document, history and location, test pages that use it in Google's rendering (the rendered HTML in Search Console's URL Inspection tool or the Rich Results Test), not only in a normal desktop browser.
Ibrahim Anjro · Day 2 · Lightning session D: Rendering and JavaScript
Audit CMS templates for duplicate markup by running one page per template through the Rich Results Test and checking whether an SEO plug-in and a theme or events plug-in emit the same type twice; 'more markup never hurts' covers relevant, non-duplicated markup only.
Ibrahim Anjro · Day 2 · What is Structured Data and why we need it on the internet.
Connected things 7
Most often named with it
Things named in the same claim, with the number of claims they share.
Topics that feature it