In order to better assist you, we’ll need more information. Can you try and gather as much information for us as possible? Please perform the following:
1. Check for conflicts.
2. Check for JavaScript errors with your console.
If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers. Please report the issue to a third party developer as well.
If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.
The same thing happens to me from version 6.0.0 with several analysis flaws and I report it and I still wait for repairs, also try everything that the friend Md Mazedul Islam Khan says, but there is no answer and according to that guide everything is correct . here the report: https://wordpress.org/support/topic/version-de-yoast-6-1-1-con-bug/#post-9924515
@shadows23
If you are still encountering the issue with the prompt to change language, we would recommend reporting it here:
https://github.com/Yoast/YoastSEO.js/issues/1353
The issue you linked to is specific to a bug with the focus keyword not being analyzed correctly until the page is updated, so is a separate issue.
Also, please note that issue 8724 is still open, however, currently there are more pressing issues which affect more users and have a higher priority for our developers at the moment. This doesn’t mean the issue won’t be resolved. It means that the issue is in a queue and takes longer before our developers have the time to investigate the issue.
Hi,
many thanks for your answer. for the moment I’m not able to access the website due to a third party supplier blocking the accesses for my customer. I’ll get back to you asap.
Rgds,
Hello,
Please do let us know if you continue to encounter the issue after performing the conflict check. If so, you can create a new GitHub issue here.
Setting to resolved as there has been no further response.
