11.3
High-time for another release, namely Yoast SEO 11.3. This release features enhancements and bug fixes aimed at improving the way your favorite SEO plugin performs. Read more about the release in our 11.3 release post.
Subscribe through this plugin's RSS feed or follow us on Twitter to stay up-to-date with new releases!
High-time for another release, namely Yoast SEO 11.3. This release features enhancements and bug fixes aimed at improving the way your favorite SEO plugin performs. Read more about the release in our 11.3 release post.
$context argument in the deprecated wpseo_json_ld_output filter would result in a fatal error when using PHP 7.1 or higher.filesize to whitelisted properties on $image. Props to cmmarslender.aria-current to the active item.We've made huge changes to the schema.org markup we output, adding multiple different types of Schema. Be sure to check our posts on yoast.com about this release!
Schema changes:
Adds Person markup for author pages.
Adds WebPage markup for all pages.
Adds Article markup for posts, with Person markup for the author.
Changes the ‘Organization or Person’ section of the Knowledge graph settings to allow selecting an author that is the ‘Person’ that the website represents.
Adds MySpace, SoundCloud, Tumblr and YouTube URL input fields to people’s profiles.
rel="publisher" Google+ tag was being output on the frontend if that profile was provided in the past.Content analysis recalibration (beta):
As there are already a lot of users who are participating in testing, we currently have enough input to start preparing for the release of the improved analysis.
Removes the ability to enable beta testing for new installations.
When the feature is disabled, the ability to re-enable it will disappear.
Content analysis recalibration (beta):
Adds a toggle feature for subscribing to the recalibration beta under SEO -> General -> Features.
When the recalibration feature is enabled:
The single title assessment is added. This assessment makes sure that you don't use superfluous H1s in your text.
Assessments changes:
Keyphrase density: changes scoring schema to account for the length of the keyphrase and changes feedback strings so that we give feedback about the number of occurrences rather than a percentage.
Outbound links assessment: changes the scoring schema so that red bullet instead of an orange bullet is shown when you have no outbound links.
Image alt attributes: if there are at least 5 images, checks whether the alt tags contain the keyphrase or synoynyms in 30-70% of all images. If there are less than 5 images, 1 image with the keyphrase or synonym in the alt tag is still scored as good.
Keyphrase in title: function words preceding the exact match keyphrase are ignored when determining the position of the keyphrase in the title.
Keyphrase length: makes the scoring scheme less strict for languages that don't have function word support, so that for these languages keyphrases with 1-6 words are scored as green, 7-9 as orange, and more than 9 as red.
Keyphrase in subheading: only takes H2 and H3 level subheadings into account and changes the scoring schema so that 30%-75% of these subheadings need to include the keyphrase or its synonyms. In languages without function word support, a match is only counted if all the words from the keyphrase/synonym appear in the subheading.
Text length: on taxonomy pages, the recommended minimum text length is increased from 150 to 250 words.
Assessment removals:
The assessment checking the length or your URL.
The assessment checking whether your URL contains stopwords.
$ in wp-seo-admin-media.js. Now we use jQuery instead.wpseo_taxonomy_content_fields filter to add additional fields to the taxonomy metabox.og:url would not be set to the canonical URL if the canonical URL is explicitly set on Post types, Terms or Tags.slug, it would not be updated in the Snippet Preview directly.og:image tag. That is now fixed.wpseo_opengraph_image_size filter. This will completely override any automatic size determination our code does. This filter now also applies to all ways an og:image can be determined: In the content, as a featured image or as set in our Facebook image setting.og:image tag. SVG images are not allowed by Facebook, so these should never be used in the og:image tag.noindex through the wpseo_robots filter did not properly remove the canonical element.Go Premium notice.wpseo_sitemap_entries_per_page is not being applied as expected.