Skip to main content
← Back to changelogs overview

Yoast SEO 14.8

Get ready for a brand new version of Yoast SEO! In this version you'll find new Schema functionality, an improved readability analysis for Portuguese & Indonesian, and improved keyword recognition for right-to-left languages. Read more about those changes in our release post!

Enhancements​

  • Adds a Schema section to the metabox and sidebar. This section allows the user to change their Schema settings on posts, pages and custom post types.

  • Adds a new section to the Search Appearance settings. This section allows the user to change their Schema defaults for posts, pages and custom post types.

  • Fixes an inconsistency in the feedback strings that are produced by the keyphrase in SEO title assessment.

  • Improves the accuracy of the following assessments for right-to-left languages: sentence length, keyphrase in introduction, keyphrase distribution, keyphrase density, and keyphrase in meta description.

  • Improves all keyphrase-based assessments for Arabic by filtering function words and by allowing keyphrases to be recognized in a text when preceded by a prefix (e.g., "ل" or "ب").

  • Adds the following assessments for Indonesian: sentence beginnings, transition words and passive voice.

  • Adds the following assessments for Portuguese: Flesch reading ease and passive voice.

  • Cleans up Schema @type values:

  • If it's an array with multiple values, only output unique values.

  • If it's a single value, output it as a string instead of an array.

Bugfixes​

  • Fixes a bug where the Yoast Dashboard widget would trigger an error when other plugins or temporary conditions would make the Yoast API response fail.
  • Fixes a bug where block editor dependencies would be loaded unnecessarily on classic editor, causing issues with NextGEN gallery. Posts with NextGEN galleries that have been broken due to this bug will need to be re-saved.

Other​

  • Sets the minimum WP version to 5.4.
  • Optimizes the logic involved in default filters for our options. This should lead to a very small increase in performance as well as avoiding an edge case where the default filter would be removed.