Shipping Delivery Time for Google Rich Results

WPSSO + WooCommerce

In September, Google announced support for shipping details in Schema Product Offers and how shipping details would be presented in search results. Adding the new shippingDetails property to your Schema Product markup is especially important if you offer free or low-cost shipping, as this will make your products more appealing in search results.

In October, Surnia Ulula announced support for shipping details in the WPSSO Core Premium plugin, to provide both the Google recommended Schema OfferShippingDetails shippingDestination and shippingRate properties for WooCommerce products. Although these two properties are enough to satisfy Google’s recommended shipping details markup, the Google validator now warns that an additional deliveryTime property is recommended.

The deliveryTime property should be a Schema ShippingDeliveryTime type that includes businessDays, cutoffTime, handlingTime, and transitTime properties. The data for these four properties can be managed with a new WPSSO Shipping Delivery Time for WooCommerce add-on.

Continue reading


Google Shipping Details for WooCommerce Products

WPSSO + WooCommerce

In September, Google announced support for shipping details in Schema Product Offers and how shipping details would be presented in search results. Adding the new shippingDetails property to your Schema Product markup is especially important if you offer free or low-cost shipping, as this will make your products more appealing in search results.

WPSSO Core Premium v8.7.0 can now retrieve shipping information for WooCommerce products, including shipping zones, methods, rates, and locations (continents, countries, states, and postal / zip codes). If you’re using postal / zip code wildcards or ranges for shipping, WPSSO Core Premium can also create the proper PostalCodeRangeSpecification markup suggested by Google.

Continue reading


Google Schema for COVID-19 and More Free Features!

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!

Continue reading


Google Limits ‘aggregateRating’ and ‘review’ Properties

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.

Continue reading


Schema Article AMP 1:1, 4:3, and 16:9 images for Google

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.

Continue reading


[Solution] Sharper Thumbnails for Facebook, Google, Open Graph, Pinterest, Schema, SEO, Twitter, etc.

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?

Continue reading


[Solution] Google Reports Missing “Product Identifier” for WooCommerce Products

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.

Continue reading


Why WordPress Image Sizes for Social Sharing and SEO?

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. og:image, twitter:image, etc.), and/or adding images to Schema JSON-LD markup for the webpage. This can be problematic for several reasons…

  1. The image resolution may be too small.
  2. The image resolution may be too large and the file size too big.
  3. The aspect ratio (width or height) may exceed a maximum value.
  4. The image displayed on the social / search site is center cropped.

Continue reading