Google New Rich Results Testing Tool

Google announced at 21/12/2017 that they have released a new-and-improved version of its Structured Data Testing Tool, available in beta as the Rich Results Test. The name of the tool "rich results" reflects – as noted in the announcement post – the fact that what Google had previously referred to as "rich snippets, rich cards, or enriched results" will now be called "rich results" as their official documentation moving forward.

Google said the new testing tool “focuses on the structured data types that are eligible to be shown as rich results.” This new version enables you to test all data sources on your pages, including the recommended JSON-LD, Microdata or RDFa. Google said this new version is a “more accurate reflection of the page’s appearance on Search and includes improved handling for Structured Data found on dynamically loaded content.”

The new Rich Results Testing tool currently only supports tests for Job posting, Recipe, Course, and Movie. Google said it will be adding support for other rich results over time.

The new google tool also has a drawback that, this tool does not currently show schema.org syntax errors, which currently used by millions of website.

Eligibility for rich results

The Structured Data Testing Tool never explicitly states whether a given page (or code block) is eligible for rich snippets. The closest the tool comes is to provide a "PREVIEW" link when results are capable of generating a rich result, and only then after you click through to the eligible data type.

Eligibility is now front-and-center in the Rich Results Test response, with pages that are eligible for rich results clearly labelled as such, along which data type ("Detected structured data") for which the page is eligible.

It's equally obvious when a submitted page isn't eligible for a rich result.

There is also a third category pertaining to rich result eligibility, seemingly triggered when a page could be eligible for rich results if errors were corrected.

Details on these errors are provided in a pane on the "Detected structured data" section of the test results.

Again, be cognizant that only job postings, recipes, courses and movies are currently supported by the tool, as per the prominent message at the top of a test results page.

Google's Mobile-Friendly Test API

Google Introducing the Mobile-Friendly Test API

Tuesday, January 31, 2017 at Webmaster Central Blog Google Introduced the Mobile-Friendly Test API. As You already know that from last year, Google is pushing to promote and reward mobile-friendly websites continues today with the news that it’s opening up its mobile-friendly test tool to developers via an application programming interface (API).

Google first launched the tool back in 2014 as an easy way to help businesses, bloggers, and developers figure out whether their website fit Google’s “mobile friendly” criteria. These include whether the site avoids software such as Flash, uses text that can be easily read on a small screen, and has content that adapts to suit a screen without requiring the user to “scroll” horizontally or zoom. With the mobile-friendly test tool, all you need to do is plug your web address into the search box, and Google will tell you if it passes the Google’s “mobile friendly” criteria.

Google’s John Mueller Wrote,

"With so many users on mobile devices, having a mobile-friendly web is important to us all. The Mobile-Friendly Test is a great way to check individual pages manually. We're happy to announce that this test is now available via API as well. 

The Mobile-Friendly Test API lets you test URLs using automated tools. For example, you could use it to monitor important pages in your website in order to prevent accidental regressions in templates that you use. The API method runs all tests, and returns the same information - including a list of the blocked URLs - as the manual test. The documentation includes simple samples to help get you started quickly.  

We hope this API makes it easier to check your pages for mobile-friendliness and to get any such issues resolved faster. We'd love to hear how you use the API -- leave us a comment here, and feel free to link to any code or implementation that you've set up! As always, if you have any questions, feel free to drop by our webmaster help forum."

The testing tool is a useful way to manually check whether a specific Website or URL plays nice with mobile phones, but by introducing an API, Google is enabling webmasters and developers to integrate the tool with automated software. So, for example, this could be used to automatically track specific pages on a website to avert accidental changes that make a page not-so-suitable for small screens.

The API launch fits in with Google’s broader push to treat websites that have been built with mobile users in mind more favorably. Last year, the search giant revealed it would begin ranking “mobile-friendly” sites even higher in their organic search results, though it had been labeling sites as mobile-friendly for some time already. And back in November, Google announced it would “eventually” switch to using the mobile versions of websites, rather than desktop versions, in search result rankings.