What’s New in WPSSO Core v15

February 9, 2023Updated on March 30, 2023 JS Morisset Leave a comment WPSSO Core

The common way to create Schema markup for WooCommerce product variations in the past has been to create multiple Schema offers for a product – one offer per variation. Unfortunately, the Google merchant crawler has always been very unreliable when reading offers, sometimes being able to read product offers, and sometimes not. Even now, after Google added merchant validation to their Rich Results Test tool, it does not guarantee that the Google merchant crawler will be able to read Schema markup as predicted by Google’s test tool.

Some structured data plugins have attempted to work around the limitations of Google merchant’s crawler by offering different Schema markup when URL query arguments for variation attributes are present. WooCommerce creates a single webpage for a product (like a WordPress does for a single Post or Page), and javascript is used to adjust the information displayed based on URL query arguments for variation attributes – but there still is only one HTML webpage for a product. Some structured data plugins break this single product webpage by adjusting the Schema markup to include only the variation offer when URL query arguments for variation attributes are present, but this has some serious drawbacks as the WooCommerce product webpage can no longer be cached, the canonical URL value is now invalid (ie. points to the main product page, which has different markup), and search engines traditionally ignore query arguments, which means they are seeing different markup for the same URLs. Breaking the WooCommerce product webpage might help fix Google merchant’s limitations, but it does so at the expense of search engine ranking.

So, how do we preserve the single webpage for a WooCommerce product with variations?

Better Schema Markup for WooCommerce

December 30, 2022Updated on March 30, 2023 JS Morisset Leave a comment Schema, WooCommerce, WPSSO Core

WooCommerce is a popular e-commerce plugin, with a solid and well designed code base, but WooCommerce is not an SEO plugin – its Schema markup for search engines is minimal and it does not provide any social meta tags for Facebook, Pinterest, Twitter, etc. This guide provides a quick and easy solution to fix your WooCommerce product Schema markup and meta tags.

Warnings for WooCommerce Markup

The Google Rich Results Test Tool, Schema Markup Validator, or the Google Search Console may report one or more of the following errors for the Schema markup provided by the WooCommerce plugin:

SEO Plugin Performance Report for Q2 2022

April 12, 2022Updated on March 30, 2023 JS Morisset Plugins, SEO

In June 2021, and then again in September 2021, we compared the performance of the most popular SEO plugins for WordPress. To continue what has become a bit of a tradition, we present the latest SEO performance report for April 2022.

We’ve classified the performance of each SEO plugin into one of three categories (best, average, and worst) and included a baseline chart for WordPress and the 2021 theme. This gives us a good baseline reference for the performance of each SEO plugin – as you will see, the best performing SEO plugins have almost no effect, while the slowest SEO plugin almost doubles the page load time and the number of database queries.

Remove WordPress Action / Filter Hooks by Name

February 24, 2022Updated on March 30, 2023 JS Morisset PHP, WordPress

The WordPress remove_action() and remove_filter() functions are useful, but they require the original hook priority and a function name, a class object and method name, or a class name and static method name.

Providing the class object in particular may be difficult or impossible, as plugin and theme classes may be extended and instantiated any number of ways. The following SucomUtilWP::remove_filter_hook_name() static method can be used to remove WordPress action and filter hooks using their class name instead of requiring a class object.

For example, if an action hook like this one has been added within a class object that was not saved, saved in a private/protected variable, or cannot be re-instantiated, then removing it might be impossible.


add_action( 'action_name', array( $this, 'method_name' ), 1000, 2 );

add_action( 'action_name', array( $this, 'method_name' ), 1000, 2 );

If you know the class (or extended class) name (‘Plugin_Namespace\Class_Name’ for this example), you can remove it using the following static method:


SucomUtilWP::remove_filter_hook_name( 'action_name',
    'Plugin_Namespace\Class_Name::method_name' );

SucomUtilWP::remove_filter_hook_name( 'action_name',

'Plugin_Namespace\Class_Name::method_name' );

Refresh a Metabox in the WordPress Block Editor

December 2, 2021Updated on March 30, 2023 JS Morisset JavaScript, WordPress

The WordPress block editor shows registered metaboxes under the post / page content, but since it does not reload the webpage when saving content, metaboxes are not refreshed or reloaded when you save a draft or publish the post / page.

If your metabox needs to be refreshed, to show the new saved content (like the WPSSO Core or JSM’s Show Post Metadata plugins, for example), you need to add a change listener in javascript and refresh your metabox (using an ajax call) after the block editor has finished saving the metaboxes.

New WPSSO Google Merchant Feed Add-on

November 11, 2021Updated on March 30, 2023 JS Morisset Google Merchant Feed, WooCommerce, WPSSO GMF

Just released, the new WPSSO Google Merchant Feed add-on retrieves product information from WPSSO Core Premium and provides maintenance free XML feeds for each WordPress language (aka locale).

There are no add-on settings to configure — the WPSSO Google Merchant Feed add-on automatically retrieves all product information in the language (aka locale) requested.

A supported e-commerce plugin, like WooCommerce or Easy Digital Downloads, is suggested but not required — the WPSSO Google Merchant Feed add-on can also retrieve custom product information entered in the WordPress editor Document SSO metabox. WooCommerce variations and additional WooCommerce product attributes are fully supported.

SEO Plugin Performance Report for Q4 2021

September 27, 2021Updated on March 30, 2023 JS Morisset Plugins, SEO

In June of 2021 an SEO plugin for WordPress boasted they were “one of the fastest SEO plugins” available, so using the Query Monitor plugin, we tested the performance of several SEO plugins to see if their claim was true (spoiler alert, it wasn’t).

In the months since that article, there has been a new version of WordPress and new versions of several SEO plugins, so we were curious to see if the SEO plugin performance results had changed for Q4 2021. The WPSSO Core plugin, for example, has integrated their Schema JSON-LD add-on into their Core plugin, so the features of WPSSO Core have increased significantly – would it also affect its performance?

WPSSO Core Integrates the Schema JSON-LD Add-on

September 24, 2021Updated on March 30, 2023 JS Morisset WPSSO Core, WPSSO JSON

Years ago, when support for Schema meta tags was added to the WPSSO Core plugin, an add-on was created to express more complex Schema markup using JSON-LD encoding. At the time, most WordPress themes still offered Schema markup using RDFa and Microdata in their templates, and in those cases, adding JSON-LD markup automatically in the webpage would only create duplicate and confusing markup. Google was also one of the few (if not the only) search engine capable of reading JSON-LD markup, and still promoted the use of meta tags, RDFa, and Microdata (read by most social sites and other search engines at the time).