Hello @chiki83!
We have a global support team, so we’re only able to answer your questions in English. It’s likely that you were not aware of this. We’d still like to help you as fast as possible, therefore, we’ll make a one-time exception. We’ve put your message through GoogleTranslate. For future communications, please keep in mind to reply in English.
Regarding your concern, we understand that the SEO traffic light doesn’t match on the page overview screen and on the individual page itself.
First, can you please make sure you’re running the latest version of WordPress (5.6.2), Yoast SEO (15.9) as well as the latest version of your theme and ALL other plugins?
If everything’s updated on your end, we need you to clear all your cache from your theme, plugin, server, CDN like Cloudflare, and browser and see if it resolves the issue. If you are not sure how to clear cache from theme/plugin, please speak to their developers. If you want to clear the cache from the server, please speak to your host provider. To clear the cache from your browser, please refer here.
Let us know the result.
Perfect, thank you very much for the exception.
As for the solution to the problem, I have everything updated to the latest versions and the cache cleared but it remains the same.
@chiki83 Thanks for your reply.
We’re sorry that you are experiencing problems that might be caused by our plugin!Just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Nineteen. Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.As we can imagine that 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.`
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.