WordPress.org

Fixes a bug where the buttons to change the How-to steps and FAQ questions order would be only partially visible in mobile view.

Deprecates the assessment that checks if stopwords are used within the keyphrase.

Deprecates the WPSEO_Cornerstone class.

Introduces a Features tab in the network admin, which allows disabling all site-specific features for the entire network.

Optimizes and caches WPSEO_Option_Titles::enrich_defaults(). Props to <a href="https://github.com/soulseekah">@soulseekah</a>

Changes all mentions of 'keyword' to 'keyphrase'. Read more about <a href="https://yoa.st/keyword-to-keyphrase">the transition from 'keyword' to 'keyphrase'</a>.

Improves the consistency of the SEO and readability results by showing them in a fixed order.

Adds target="_blank" to the "How to connect to GSC" link to open the link a new tab. Props to <a href="https://github.com/zkan">@zkan</a>

Improves the feedback texts for all SEO and readability assessments.

Keyphrase density: checks whether there are enough keyphrase matches; a match is defined as a sentence that contains all words from the keyphrase.

Keyphrase in slug: checks whether a sufficient number of words from the keyphrase is used in the slug. The number of words required depends on the length of the keyphrase.

Keyphrase in title: still checks whether an exact match of the keyphrase is found in (the beginning of) the title, but now also recommends improvement if all words from the keyphrase are found in the title.

Keyphrase in introduction: checks whether words from the keyphrase are matched within one sentence in the introduction or, if not, whether they are present in the first paragraph at all. An exact match isn’t required anymore.

The analysis of the following assessments incorporates the new keyword recognition principles:↵ ↵ <ul>↵ <li>Image alt attributes: checks whether there’s at least one image with an alt tag that contains words from the keyphrase. An exact match isn’t required anymore.

When matching keyphrases for the various assessments, the analysis only targets content words and ignores function words (e.g., <code>the</code> or <code>and</code>). This functionality is available in English, German, Dutch, French, Spanish, Italian, Portuguese, Russian and Polish.