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).
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. ;-)
WPSSO Breadcrumbs Markup (aka WPSSO BC) version 1.0.0 for WPSSO Core was released yesterday. You can install and activate the extension from the SSO > Extension Plugins settings page, download it from the WPSSO website, wordpress.org, or GitHub.
Uses Google’s preferred Schema JSON-LD format.
Most comprehensive Schema BreadcrumbsList markup of any plugin.
Adds Schema BreadcrumbList markup to posts, pages, and custom post types.
Select between using ancestors (page parents, grand-parents, etc.) or categories for breadcrumbs.
No theme function or template files to modify!
Simply activate / deactivate the plugin to enable / disable the addition of Schema BreadcrumbList markup.
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 NextGEN Facebook (NGFB) and WPSSO plugins offer a “Meta Property Containers” option that you can enable / disable under their General Settings > Specific Websites and Publishers > Google / Schema tab. There are several ways to include Schema markup in webpages (see an Introduction to Structured Data from Google for examples):
- JSON-LD machine-readable scripts for Google (see WPSSO JSON extension).
- Microdata and RDFa markup of HTML tag attributes in theme templates (not recommended).
- HTML meta tags in the webpage head section.
If you’re using the WPSSO Schema JSON-LD Markup (WPSSO JSON) extension (and if not, you really should), you may have noticed that Google’s Schema validation tools can pickup additional incomplete / inaccurate Schema markup from your theme templates. WPSSO JSON defines its JSON-LD markup as the “main entity” for the webpage — so Google will prefer this markup over any other found in the webpage — but you may still want to cleanup that incomplete / inaccurate Schema Microdata from your theme templates. The new WPSSO Strip Schema Microdata (WPSSO SSM) extension is a Free plugin that removes Schema Microdata markup from the webpage body section automatically, leaving the Schema JSON-LD markup as the only Schema markup in the webpage.
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.
WPSSO version 3.18.0 and 3.18.1 have been released. The latest versions include a new “Schema Item Type by Post Type” option to select the Schema item type for each post type (and custom post types). Since version 3.16.0 WPSSO has offered an automated process to check and modify templates to add schema attributes for
NextGEN Facebook (NGFB) version 8.10 and WordPress Social Sharing Optimization (WPSSO) version 3.10 have been released. The Photo Card, Gallery Card, and Product Card were deprecated by Twitter on July 3rd, 2015. NGFB and WPSSO continue to support all current Twitter Card formats, including the Summary Card, Summary Card with Large Image, App Card (exclusive to WPSSO), and Player Card — in both the Free (New) and Pro versions.
NextGEN Facebook (NGFB) version 8.9 and WordPress Social Sharing Optimization (WPSSO) version 3.9 have been released. These latest versions include a new “Theme Integration” tab on the Advanced settings page to help provide better Schema markup support for Developers and/or power-users. By default, Schema itemprop / itemtype markup is added to the
<html> element in webpages, but a better location for this markup would be in the
<head> element. Unfortunately, WordPress does not have a standard filter for the
<head> element (like it does for the
<html> element attributes). If your theme provides a filter for the
<head> element attributes, and/or you feel confident enough to edit your theme’s header.php template, you will find the settings under the “Theme Integration” tab very useful.