A new WPSSO User Locale (WPSSO UL) extension for WPSSO for WordPress version 4.7 (and up) has been released. This Free extension provides a user locale / language / region selector in the WordPress admin back-end and front-end toolbar menus. This allows users to easily change their preferred locale setting from the toolbar instead of having to update their WordPress profile page.
The default WordPress behavior is to apply the user locale preference to the admin back-end only — this plugin can optionally extend the user locale preference to the front-end webpage as well (enabled by default in the SSO > User Locale settings page).
When searching for a plugin on WordPress.org, I’m always surprised by the number of results — many plugins appear to be similar, or even identical, but if you look at their PHP code, those similarities quickly evaporate. This was the case recently when I was looking for a simple plugin to redirect HTTP URLs to HTTPS. Some plugins were way too basic / incomplete in their logic, while others looked like a pile of spaghetti code with the kitchen sink thrown in there somewhere. :)
JSM’s Force SSL / HTTPS is my take on a simple WordPress plugin to redirect HTTP URLs to HTTPS. ;-)
Are you using Yoast SEO in combination with WPSSO?
Have you used Yoast SEO in the past, and would like to read / import its social meta as default values for the WPSSO Social Settings metabox?
WPSSO version 3.38.1-1 (released earlier today) includes additional support for Yoast SEO — When the “Use Yoast SEO Social Meta” option is enabled under the SSO Advanced > Social / Custom Meta tab, WPSSO will read / import Yoast SEO social meta for Posts, Terms, and Users — the Yoast SEO plugin does not have to be active or even installed to use this feature.
An active Yoast SEO plugin does offer a few more integration features though, including the expansion of Yoast SEO variables and custom canonical URLs, but is not required to read / import Yoast SEO custom meta for Posts, Terms, and Users.
A new extension for WPSSO called WPSSO Tweet a Quote (WPSSO TAQ) is available to include Twitter-style quotes in your content, with an easy (and optional) Tweet link for readers.
WPSSO TAQ uses your existing WPSSO settings to shorten URLs, add the Twitter Business @username, and recommend the author’s @username after sharing — and developers / advanced users will appreciate the ability to completely re-style the quote text and Tweet link. ;-)
The NextGEN Facebook (NGFB) and WordPress Social Sharing Optimization (WPSSO) plugins offer a “Meta Property Containers” option that you can enable / disable under their General Settings > Specific Websites and Publishers > Google / Schema tab. There are several ways to include Schema markup in webpages (see an Introduction to Structured Data from Google for examples):
- JSON-LD machine-readable scripts for Google (see WPSSO JSON extension).
- Microdata and RDFa markup of HTML tag attributes in theme templates (not recommended).
- HTML meta tags in the webpage head section.
WPSSO Schema JSON-LD Markup (WPSSO JSON) version 1.11.1-1 has been released and features improved markup for the Schema item types Blog, CollectionPage, ProfilePage, and SearchResultsPage. Each of these “archive” page Schema types now include a “hasPart” property to list posts in the current view (WordPress blog home page, date / category / tag archive pages etc, and search results).
NGFB version 8.37.2-1 and WPSSO version 3.37.2-1 have also been released. The “Item Type for Home Page” option has been replaced by two new options — “Item Type for Blog Home Page” and “Item Type for Static Home Page” — allowing you to select different Schema types for each. The WordPress blog home page defaults to https://schema.org/Blog, with posts listed in the JSON-LD “hasPart” property (WPSSO JSON extension required), where-as the static home page defaults to https://schema.org/WebSite.
WordPress Social Sharing Optimization (WPSSO) version 3.37.0-2 has been released, along with updates to all its extensions. This latest WPSSO version includes several new options to fine-tune WPSSO’s internal caching features. The previous “Object Cache Expiry” option has been replaced with 7 new options:
- Head Markup Array Cache Expiry (default 3 days).
- Shortened URL Cache Expiry (default 1 week).
- List Column Content Cache Expiry (default 1 week).
- Filtered Content Text Cache Expiry (default 1 hour).
- Get Image (URL) Size Cache Expiry (default 1 day).
- Article Topics Array Cache Expiry (4 weeks).
- Schema Types Array Cache Expiry (4 weeks).
If you’re using the WPSSO Schema JSON-LD Markup (WPSSO JSON) extension (and if not, you really should), you may have noticed that Google’s Schema validation tools can pickup additional incomplete / inaccurate Schema markup from your theme templates. WPSSO JSON defines its JSON-LD markup as the “main entity” for the webpage — so Google will prefer this markup over any other found in the webpage — but you may still want to cleanup that incomplete / inaccurate Schema Microdata from your theme templates. The new WPSSO Strip Schema Microdata (WPSSO SSM) extension is a Free plugin that removes Schema Microdata markup from the webpage body section automatically, leaving the Schema JSON-LD markup as the only Schema markup in the webpage.
Wondering about the post meta your theme and/or plugins might be creating?
Want to find the name of a specific post meta key?
Need some help debugging your post meta?
The JSM’s Show Post Meta plugin displays all post meta (aka custom fields) keys and their unserialized values in a metabox at the bottom of post editing pages.
There are no plugin settings — simply install and activate the plugin.
WPSSO Schema JSON-LD Markup (WPSSO JSON) version 1.10.0-1 has been released, and includes several improvements for Pinterest and the Schema Recipe markup.
Although previous versions of WPSSO JSON included basic support for the Schema Recipe markup, finding an elegant way to manage ingredients — without duplicating existing theme and/or 3rd party ingredient management — was still on the To-Do list. Thanks to the helpful suggestions of a customer with a recipe website, I was able to include recipe integration features in this version.