On March 17th 2020, in response to COVID-19 self-isolation trends, Google published new Schema Event properties for virtual, postponed, and cancelled events.
The latest Premium version of WPSSO Schema JSON-LD Markup provides several customization options for these new Schema Event properties in the Document SSO metabox.
This past month, the Free / Standard versions of WPSSO Core and its WPSSO Schema JSON-LD Markup add-on have also received several new features — most notably, almost all customization options in the Document SSO metabox are now available in the Free / Standard version of WPSSO Core (except those options that require an integration feature in the Premium version to implement, like the video service APIs), and the Free / Standard version of WPSSO Schema JSON-LD Markup now includes all 495 supported Schema types!
Google has recently updated their Review snippet structured data guidelines to limit the Schema ‘aggregateRating’ and ‘review’ properties to only a select handful of approved Schema types.
The upcoming release of the WPSSO JSON v2.10.0 add-on will follow these new Review snippet structured data guidelines, instead of conforming to the official Schema standard, as the current version does.
If you notice a “not a known valid target type for the itemReviewed property” error in Google structured data validator results, the ‘aggregateRating’ and/or ‘review’ may be included in a non-approved Schema type.
The latest release of WPSSO Core v6.3.0 and the WPSSO JSON v2.9.0 add-on include new image sizes in Schema Article AMP markup for Google.
A few months ago, Google quietly updated their AMP structured data guidelines to suggest that:
For best results, provide multiple high-resolution images with the following aspect ratios: 16×9, 4×3, and 1×1.Quote from Google’s AMP with structured data
Since WPSSO Core and its add-ons already use a variety of image sizes for different markup standards (ie. Open Graph, Twitter Cards, Schema, etc.), it was fairly easy to add support for Google’s new Article AMP image sizes. You can find the new images sizes, along with all other WPSSO image sizes, under the WordPress Settings > SSO Image Sizes settings page.
Google’s Structured Data Testing Tool and/or Google’s Search Console for site owners may report the following errors for the default Schema JSON-LD markup offered by WooCommerce:
- The aggregateRating field is recommended.
- The brand field is recommended.
- The review field is recommended.
- This Product is missing a global identifier (e.g. isbn, mpn or gtin8).
I’ve written a simple Step-by-step Guide for WooCommerce and WPSSO that explains these issues, and offers a quick and easy solution.
WooCommerce manages information on product Availability (aka Stock), Prices, SKU, etc., but additional WooCommerce product attributes must be created to provide more product information for Google.
The WPSSO Core Pro plugin (and its WPSSO Schema JSON-LD Markup Pro add-on), for example, include a variety of WooCommerce product attribute values in its Schema markup, including the product Brand, Color, Condition, EAN, GTIN-8, GTIN-12, GTIN-13, GTIN-14, ISBN, Material, MPN (aka Manufacturer Part Number), Size, and Gender.
There are several ways to add Schema aggregate rating markup, but before we discuss the “How”, let’s review what a Schema aggregate rating value actually is. ;-)
The Schema.org website defines the Schema aggregateRating property value as:
The overall rating, based on a collection of reviews or ratings, of the item.
Two things to keep in mind about this:
- That an aggregate rating value is calculated from several customer ratings / reviews for the current webpage content — WooCommerce product reviews, for example.
- Google prefers, and often double-checks, that Schema markup reflects the current content of the webpage. So, if you want to manually set aggregate rating and/or review values in your Schema markup, make sure that these customer ratings and reviews also appear in your webpage content (ie. that these ratings and reviews are visible).
It’s been a very productive two weeks of coding for both the WPSSO Core plugin, and it’s WPSSO Schema JSON-LD Markup add-on.
On April 26th – just two weeks ago – WPSSO Core v4.0.0 was released, which included support for the new Gutenberg editor. Since then, WPSSO Core v4.1.0, v4.2.0, and v4.3.0 were also released (the last one just today), along with WPSSO JSON v1.25.0 and v1.26.0.
In case you missed all the update notices and posts about those versions, the following is a quick summary of the big changes and improvements in both WPSSO Core and its JSON-LD add-on. And at the end of this post, you can also find a summary of our release schedule philosophy, and why we chose to release four big improvements, in four different versions, in just two weeks. ;-)
The upcoming WPSSO JSON Premium v1.18.0 release (ETA Nov 11-12th) includes new Schema Job Posting options in the Social and Search Optimization metabox and support for the Simple Job Board plugin (along with pre-existing support for the WP Job Manager plugin from Automattic). See the WPSSO JSON changelog for more details.
You’ll find three new Schema Job Posting options in the Social and Search Optimization metabox:
- Job Title
- Employment Type
- Job Posting Expires