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] Better Schema Markup for WooCommerce

Woo logo.

Google’s Structured Data Testing Tool or Google’s Search Console for website owners may report the following errors for the default Schema 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).
  • No global identifier provided (e.g. gtin mpn isbn).
  • Missing field “businessDays”.
  • Missing field “cutoffTime”.
  • Missing field “deliveryTime”.

I’ve written a step-by-step guide for WooCommerce users that explains these issues and offers an easy solution.

Continue reading


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

WPSSO + WooCommerce logos.

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


Free Plugins for Organization / Local SEO Markup

Google reads a variety of structured data from webpages, including e-commerce Product details, Recipes, Reviews, etc. — along with three standard Schema types from a website’s homepage: WebSite, Organization, and Person.

In this post we’ll focus on the Organization markup — using Google’s preferred LD+JSON structured data format — which Yoast SEO, WPSSO Core, and most SEO plugins add to a WordPress site’s homepage.

Google uses the Organization markup to enrich its Knowledge Graph information for the website’s Organization (aka Business, Corporation, etc.).

See Google My Business, Your business information in the knowledge panel, and Improve your local ranking on Google for more information on Google’s Knowledge Graph and local business markup.

See Google’s About Search Features and Structured Data General Guidelines for more information about the current Schema types recognized by Google.

WPSSO Core (and its complementary add-ons) can be used by themselves, or in combination with Yoast SEO and other popular SEO plugins — WPSSO Core will warn of any conflicting plugin settings and the Pro version of WPSSO Core includes integration modules to read post / term meta from all the popular SEO plugins. The following examples were created using the Free versions of Yoast SEO, WPSSO Core, and its Free complementary add-ons.

Continue reading


4 Big Improvements in WPSSO Core in the Last 2 Weeks

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 agoWPSSO 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. ;-)

Continue reading


WPSSO Ditches WordPress & Gutenberg Notifications

The release of WordPress 5 and the new Gutenberg editor are just around the corner, and Gutenberg developers still have not tackled a serious design issue with the current Gutenberg notification system — notices in Gutenberg are being displayed over the content area, forcing users to dismiss notifications to gain access to their content — and in some cases, where several non-dismissible notices are displayed, users may not have access to the content area at all.

The notification system in the current version of WordPress is nothing fancy — and can feel a bit intrusive when several notices are displayed at once — but it’s a lot more flexible and functional than the proposed Gutenberg notification system. :-) As an example, here are some typical SSO (Social and Search Optimization) notifications when editing a test post in the current version of WordPress, in the Gutenberg editor, and with the upcoming release of WPSSO Core v4.2.0 that moves SSO notices into the admin toolbar.

Continue reading


WPSSO Core v4 with Support for Gutenberg

The new Gutenberg editor for WordPress v5 may not be ready yet — and I can certainly attest to that, lol — but it’s coming soon, and WPSSO Core is ready for Gutenberg!

This latest version of WPSSO Core (scheduled for release this week) includes several key changes aimed specifically at integrating WPSSO Core with the new Gutenberg editor. The Document SSO (Social and Search Optimization) metabox is now refreshed when the Gutenberg post is saved, and any SSO notices are displayed using the new Gutenberg notification system. The notices themselves have also been improved by including more information about the dismiss button — either simply hiding the notice (Gutenberg default), temporarily dismissing it for 1 hour, 3 months, etc, or dismissing it permanently.

Have you tried the Gutenberg editor yet?

WordPress v5 is coming soon, and if you haven’t tried the new Gutenberg editor in a staging environment (contact your hosting provider for details), then you could be in for a major surprise! Many plugins will not be compatible with Gutenberg, and for those few and rare plugin authors that are still actively maintaining their plugins, updates to support the Gutenberg editor may take some time. Save yourself the headache – install the Gutenberg editor in a staging environment now, and make sure all your plugins are compatible. ;-)

WPSSO Core v4.0.0 beta is available now.

If you’re a WPSSO Core Pro user — and have a staging environment — you can select the “Beta and Up” version filter for WPSSO Core in the SSO > Update Manager settings page, to install and test the latest beta version. You can also re-select the “Stable / Production” version filter at any time to re-install the last stable / production version.

Continue reading