Hello @ashfaqurrrr
Can you confirm you are using the latest version of Yoast SEO for WordPress v14.3? When you say there is nothing to edit or nothing to change, do you mean the Yoast SEO meta box isn’t loading fully as expected? Does it show as a blank box?
If so, please feel free to refer to this article for more information — https://yoast.com/help/yoastseo-meta-box-is-blank
Hello,
Thanks for the fast response.
My meta box is not showing and and it’s shows a blank box. How can I solve this issue.
Kindly let me know.
Thanks in advance
@ashfaqurrrr
Can you confirm you are using the latest version of WordPress 5.4.2 and Yoast SEO for WordPress 14.3? If not, could you please update to the latest versions and see if this resolves the issue of the blank meta box.
Otherwise, it could be one of the reasons stated in this article here — https://yoast.com/help/yoastseo-meta-box-is-blank/
If that doesn’t apply, we recommend performing a conflict check to see if it’s a conflicting plugin and/or theme that is causing the blank meta box.
Hello,
Thanks for the response again.
I have tried all the ways you have instructed me.
I have the latest update of Yoast Seo.
WordPress is latest updated.
JavaScipt enabled.
Tried the troubleshoot as well.
Still the plugin is showing a blank space
What were the results of the conflict check? Did you enable the ‘troubleshooting mode’ of the Health Check & Troubleshooting plugin? This should deactivate all plugins and revert to a default theme like TwentyTwenty. You would then activate the Yoast SEO plugin. Does the issue of the blank meta box occur?
If not, you would then activate your plugins one by one, until you are able to replicate the issue. If you managed to activate all of your plugins and the issue doesn’t occur, please then revert back to your preferred theme and then see if the issue occurs. This is so we can identify if there is a plugin or theme that is conflicting with Yoast SEO and as to why the meta box isn’t loading — https://yoast.com/help/how-to-check-for-plugin-conflicts/#plugin
Thank you so much, it was conflicting with another plugin.
I have solved the issue.
Thanks man
@ashfaqurrrr Thanks for confirming that you were able to solve the issue. We are going ahead and marking this issue as resolved but please let us know if you require any further assistance.