- 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).
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 aggregate ratings — as I’ll explain below — but first, before we dive into the “How”, let’s talk about what an “aggregate rating” 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:
- An aggregate rating value is calculated from several customer ratings / reviews for the current webpage content (an e-commerce product review, 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/or reviews also appear in your webpage content (ie. the ratings and reviews are visible).
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 Pro 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
The WPSSO Schema JSON-LD Markup (WPSSO JSON) v1.13.0-1 extension for WPSSO has been released (see the complete Changelog here) — this latest version adds several custom Recipe Instructions and Nutrition Information options to the Social Settings metabox, along with including some new integration modules for WP Recipe Maker and WP Ultimate Recipes.
WPSSO Schema JSON-LD (WPSSO JSON) extension v1.12.0-1 has been released — this new version adds WooCommerce product reviews to the Schema Product markup, along with adding WordPress comments and threaded replies to the Schema CreativeWork markup and its sub-types (Article, BlogPosting, WebPage, etc.).
WPSSO Schema JSON-LD Markup (WPSSO JSON) version 1.11.1-1 has been released and features improved markup for the Schema item types Blog, CollectionPage, ProfilePage, and SearchResultsPage. Each of these “archive” page Schema types now include a “hasPart” property to list posts in the current view (WordPress blog home page, date / category / tag archive pages etc, and search results).
NGFB version 8.37.2-1 and WPSSO version 3.37.2-1 have also been released. The “Item Type for Home Page” option has been replaced by two new options — “Item Type for Blog Home Page” and “Item Type for Static Home Page” — allowing you to select different Schema types for each. The WordPress blog home page defaults to https://schema.org/Blog, with posts listed in the JSON-LD “hasPart” property (WPSSO JSON extension required), where-as the static home page defaults to https://schema.org/WebSite.
WPSSO Schema JSON-LD Markup (WPSSO JSON) version 1.10.0-1 has been released, and includes several improvements for Pinterest and the Schema Recipe markup.
Although previous versions of WPSSO JSON included basic support for the Schema Recipe markup, finding an elegant way to manage ingredients — without duplicating existing theme and/or 3rd party ingredient management — was still on the To-Do list. Thanks to the helpful suggestions of a customer with a recipe website, I was able to include recipe integration features in this version.
WPSSO version 3.33.1-1 has been released, along with updates for the WPSSO JSON, WPSSO ORG, and WPSSO PLM extensions.
One of the big features for this new release is the added support for the Schema http://schema.org/Event type and its sub-types (DanceEvent, MusicEvent, etc.), along with integration of The Events Calendar plugin. The Events Calendar plugin already includes basic JSON-LD support, but the WPSSO Organization Markup (WPSSO ORG) and WPSSO Place / Location and Local Business Meta (WPSSO PLM) extensions allow you to include much more detail about the organizer (as an actual Organization instead of a Person), select a performer for the event, along with WPSSO’s standard support for images, videos, etc. The combination of WPSSO Pro and all three Pro extensions can provide extensive Schema markup about your event — see the following Schema JSON-LD markup for an example.