On March 17th 2020, in response to COVID-19 self-isolation trends, Google published new Schema properties for virtual, postponed, and cancelled events. The Premium version of WPSSO Schema JSON-LD Markup v3.1.0 released this morning provides several customization options for these new 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 for those options that require an integration module from the Premium version to implement, like video service APIs), and the Free / Standard version of WPSSO Schema JSON-LD Markup now includes all 495 supported Schema types!
When you share a URL on a social site like Facebook, Twitter, LinkedIn, etc., that social site crawls the webpage in background to read the meta tags and structured data markup (aka Open Graph meta tags, Twitter Card meta tags, Schema JSON-LD, Schema microdata, etc.).
Social sites like LinkedIn generally require an image, a title, and a description to display a share. A few social sites like Pinterest and Twitter can also display additional information for products, recipes, mobile apps, videos, and more.
Until recently, the LinkedIn crawler read only Open Graph meta tags to get the webpage image, title, and description, but recently they’ve started reading oEmbed data as well, and if oEmbed data is available, LinkedIn prefers those values over the Open Graph values.
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.
Pop quiz! Did you know?
1) WordPress creates thumbnails automatically?
WordPress uses the larger / full-size image you upload to create smaller thumbnail images (see your WordPress Settings > Media page for the complete list of sizes).
For example, a photo gallery page will show small thumbnails of the larger / full-size images you uploaded. Themes will often include the featured image you selected in a predefined image size and location in the webpage.
2) All images must be sharpened after resizing?
This is such a standard process that Photoshop, for example, automatically applies a default amount of sharpening when resizing any image — you must specifically uncheck an option in Photoshop to avoid sharpenning an image during the resize process!
3) WordPress does not sharpen resized images?
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.
All social and SEO plugins – except one that I know of – use the full size image URL from the WordPress media library when adding image meta tags to the webpage (ie.
twitter:image, etc.), and/or adding images to Schema JSON-LD markup for the webpage. This can be problematic for several reasons…
- The image resolution may be too small.
- The image resolution may be too large and the file size too big.
- The aspect ratio (width or height) may exceed a maximum value.
- The image displayed on the social / search site is center cropped.