[Bug]: module malfunctioning on article pages

[nncrea7]

Prerequisites

• I've read and understood the contribution guidelines.
• I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened

Lost all the information of yoast analysis onto the editor article page

Step-by-step reproduction instructions

1. update yoast to version 27.1.1

Expected results

1. yoast flags on the article should correspond to the previous version (not always red) and the module should be accessible with the analysis results (both seo and readability)

Actual results

on the editor of an article page, yoast flags are always red and nothing appears into the module of seo or readability, it's empty
(but evrything seems to be ok everywhere else on the website)

Screenshots, screen recording, code snippet

on the previous version of yoast, seo flags were green and orange (could not access anymore to the previous analysis)

Which editor is affected (or editors)

• Block Editor
• Gutenberg Editor
• Elementor Editor
• Classic Editor
• Other (please specify in additional info)

Which browser is affected (or browsers)

• Chrome
• Firefox
• Safari
• Other (please specify in additional info)

Device you are using

No response

Operating system

No response

PHP version

No response

WordPress version

6.9.3

WordPress Theme

Raft

Yoast SEO version

27.1.1

Gutenberg plugin version (if relevant)

No response

Elementor plugin version (if relevant)

No response

Classic Editor plugin version (if relevant)

No response

Relevant plugins in case of a bug

No response

[josevarghese]

Hi @nncrea7

Thanks for creating the issue. The issue is not reproducible with the staging site having the default theme and the latest version of the Yoast SEO plugin. You can test over here: https://playground.wordpress.net/?plugin=wordpress-seo

It seems like another plugin or theme is conflicting with the Yoast SEO plugin. If you are using Gutenberg plugin, try deactivating it first to see if that resolves the issue. Often, we see problems occur alongside another plugin or theme. The fastest way to rule out any conflict is to deactivate all non-Yoast plugins and switch to a standard theme, like the default (Twenty Twenty-Five) or classic (Twenty Twenty-One) theme.

Please test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.

If you're unfamiliar with checking for conflicts, we'd like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.

Closing as the issue is not reproducible.

[nncrea7]

Thank you for your feedback. Indeed, this is the Gutenberg plug-in which is causing this problem. There is no solution therefore?

[josevarghese]

@nncrea7 Gutenberg is aware of this issue, and they will mostly fix it in the upcoming versions.

[nncrea7]

Thank you very much for your feedback

…

On Sun, Mar 15, 2026 at 1:19 PM Jose Varghese ***@***.***> wrote: *josevarghese* left a comment (Yoast/wordpress-seo#23069) <#23069 (comment)> @nncrea7 <https://github.com/nncrea7> Gutenberg is aware of this issue, and they will mostly fix it in the upcoming versions. — Reply to this email directly, view it on GitHub <#23069 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7XIRSOA2MTLOBMEIURJDFT4Q2NTXAVCNFSM6AAAAACWOCDQKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANRSHA4DCMBWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[josevarghese]

This bug has been fixed by the Gutenberg team in 22.8.0 RC1 and will be released in the coming days/weeks.