JS Morisset

WPSSO gets the published and modification times from WordPress. Here’s a page with more info on managing your post/page modification times: https://codecraftwp.com/get-post-modified-date-wordpress/

js.

I can have a look at the Schema markup. What is the URL of an example product page on your site?

js.

Storing each metadata key individually in the database has an impact on performance, so good plugins and themes store their settings as a single array instead. Unfortunately the WordPress ‘meta_query’ doesn’t handle array element matching since the ‘meta_query’ value creates an SQL query, and arrays are stored serialized in the database, so using LIKE as you’ve done is pretty much the only way to match a string within the serialized array.

WPSSO creates several ‘_wpsso_head_info_*’ entries in the post/term/user/comment metadata tables, which are created dynamically based on the meta tags and Schema markup. I’ve added a new ‘_wpsso_head_info_schema_review_rating’ metadata value in WPSSO Core v18.14.0-dev.1 that should be easier/faster to use for database queries.

js.

FYI, since WordPress transients are stored in the options table, you may want to make sure that table is optimized (ie. cleaned and defragmented). See https://www.ads-software.com/plugins/advanced-database-cleaner/ for an example plugin that may help. Make sure you have a database backup before you start. ?? If a transient query is flagged by the Query Monitor as slow, then you may have more serious issues with general database performance – you may also want to report the issue to your hosting provider.

js.

If getting a transient from WordPress is being highlighted as a “slow query” then you definitely have a problem with your database – getting a transient, even dozens of them, should not be “slow” – this is a standard basic WordPress feature. See here for more info: https://developer.www.ads-software.com/reference/functions/get_transient/

js.

It sounds like WPSSO may be highlighting a performance issue with your database, theme, or plugins. You may want to activate and use the Query Monitor plugin as suggested here https://wpsso.com/docs/plugins/wpsso/installation/troubleshooting-guide/#query-monitor-plugin.

js.

Google requires that all products have at least one image (and product variations are products). If a child post/page/custom post type, like a product variation, does not have an image, it will inherit the parent’s featured image by default. See the SSO > Advanced > Integration > Inherit Featured Image option.

js.

These are CSS classes for the speakable (ie. text) parts of Schema WebPages and Articles – .wp-block-post-title should be a standard part of your WP templates, and .speakable can be added to paragraphs etc. If you use the Premium edition, you can customize these classes in the SSO > Advanced > Integration > Speakable CSS Selectors option.

js.

You would create a function in your child theme’s functions.php file and hook that function to the filter. There are lots of examples and tutorials on Google about using WordPress filters – here’s just one https://www.hostinger.com/tutorials/wordpress-add-filter.

js.

FYI, I’ll have a look at creating a few more filters for shipping methods within zones, etc.

You can find the complete list of filters here: https://wpsso.com/docs/plugins/wpsso/notes/developer/filters/. The ones you’d be looking for contain “_wc_” in the filter name. I’ll see about adding a few more before the next stable release.

js.

Starting with WPSSO Core v18.9.0-dev.4, you can hook the ‘wpsso_wc_shipping_zones’ filter, which filters the output from WC_Shipping_Zones::get_zones( $context = 'admin' ).

js.

I don’t know which add-on you’re using, but both the https://www.ads-software.com/plugins/wpsso-wc-shipping-delivery-time/ and https://www.ads-software.com/plugins/wpsso-google-merchant-feed/ will add shipping information to the markup and/or the XML feed. The shipping information is provided by WooCommerce and WPSSO formats the shipping information for the standard required (Schema or XML).

js.

Meta tags and Schema markup are cached – if you updated/replaced images in the library, that woudl not have refreshed the cache for your posts/pages/products. You can update a post/page/product to update the meta tags and Schema markup for that post/page/product, or refresh the cache under the SSO > Tools and Actions page.

js.

Then RankMath probably includes an image that is too small.

js.

If WPSSO is disabled, there is no markup, thus no error in the markup, as there is no markup.

js.