Yoast Console Missing

We are sorry to hear that you’re still having the blank meta box issue on Firefox and other browsers except the meta box work fine on Google Chrome at this moment. We can imagine how that could give you a pause. Let’s see what else we can do here to help you resolve the issue.

First thing first, Yoast SEO free comes with basic troubleshooting support available on the WordPress forum (here). We always try shortening our response timeline and currently working on hiring more support engineers but support on the forum is still limited.

That said, if the blank meta box issue is now appearing on Firefox and other browsers at this moment except Google Chrome, can you please try reproducing the issue on Firefox incognito mode to make sure that no browser extensions are enabled to see whether this resolves the issue for you? If the issue persists, can you please try using a different device to see whether this is something specific to the current device?

We look forward to hearing from you.

I always use a Firefox private window. Same with Safari.

No change…it’s not showing

Hello…can you please address this issue

Team…I have the following error in my JS console when looking at the yoast plugin within my posts on Firefox, Chrome, and Safari.

It all seems to have the same thing in common pointing to an error in the “Search-Metadata-Preview” file which seems to me like it would be responsible for the lack of metadata preview in my Yoast console.

If this is a simple syntax error can you please address it with an update. These are the errors…nothing with Mod security, nothing with outdated framework. These are the errors in three of three browsers

ERRORS IN JS FIREFOX CONSOLE

” ” literal not terminated before the end of script
https://ibb.co/jHNwX5r

https://ibb.co/GMtFBPD

ERRORS IN JS CHROME CONSOLE

Syntax error Invalid or unspecified token
https://ibb.co/9ckKQ2z

And finally this in SAFARI…
https://ibb.co/8zLZgfp

• This reply was modified 3 years, 6 months ago by cutrano.
• This reply was modified 3 years, 6 months ago by cutrano.

Thanks for sharing the relevant information with us. The javascript errors you’ve highlighted in your provided screenshots are a result of the conflict. So, we recommend you please perform a full conflict check by following the steps given here to see whether this resolves the issue for you: https://yoa.st/3vq

Please read through my entire thread. I have performed all the troubleshooting steps recommended by yoast. You guys are going in circles

As I mentioned 5 days ago I performed these steps the conflict exists at base level with the default theme and just your plugin installed. The problem is with your plugin. You’ve led me back to steps I took before I contacted you

Please…can we do some real troubleshooting. I’ve found the error for you. Please …next step

I dont suspect a syntax error is due to a conflict…rather I suspect its due to an error in the javascript . I’ve attached a screen cap that point directly to the error and the specific line of code its occuring on. What more do you need?

Hi,

If you are getting these JS errors on all 3 of your browsers (Safari, Chrome, and Firefox) with a default set-up with the Health Check & Troubleshooting plugin (default WP theme such as TwentyTwenty and only Yoast SEO v16.2 as the sole plugin enabled) and are still getting the blank meta box (which eliminates the possibility of another plugin or theme causing the conflict), we do know that the search-meta-data-previews-1620.js file is getting cut off when loading on the browser side (as per your last screenshot) and based on what we’ve investigated so far, it’s due to a mod_security rule, or if you are using SiteLock/Imperva as a CDN/WAF.

If you try and load the specific file in your browser https://domain.com/wp-content/plugins/wordpress-seo/js/dist/yoast/search-metadata-previews-1620.js, can you check the headers and confirm if the X-CDN is Imperva?

Please subscribe to the open issue on GitHub here for more updates.

I’ve repointed my A record to my Hosts IP to disable Site Lock and Imperva. I added a small piece of code to the htaccess file to disable mod security

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

Still no Yoast panel. Where do we take it from here?

My client is pushing me to find an SEO solution for them that works. Id’ rather not abandon ship with Yoast but my client wants this fixed. It’s been over a week and we’re still doing the same troubleshooting we did a week ago. It’s not working.

Please advise thoughtfully

Hi @cutrano

We’ve tried to suggest all possible causes based on the error messages that are appearing in the browser’s console. We might need to take a closer look at your set-up specifically in order to investigate this further, but we are unable to do so on these forums. You might want to consider Yoast SEO Premium for one year of updates and support, and so we can possibly log in to your website and take a closer look at this.

Otherwise, we can only recommend to subscribe to the GitHub issue mentioned and add your findings there as well and check for updates from time to time, or if some other users on this forum can suggest and help provide any other suggestions in order to fix this.

Got rid of Yoast. Installed Rank Math. Everything is good now.

Hi,

While we’ve tried our best to help address the issue regarding the Yoast SEO meta box, we understand if you’ve ultimately decided to go with another plugin for your website’s needs. We wish you good luck in further optimizing your website and its content.

We’ll be closing this forum thread and setting it to resolved.

Whatever you guys did with the latest release of Yoast 16.4 fixed the issue. there are no errors in the javascript console anymore.

I know you don’t think it was on your side and kept trying to say it was my mod security but we literally did nothing but enable rank math for 2 weeks and wait for you to update your plugin.

Lo and behold, new version of Yoast, no issue

Who knew…
(besides me)

Cheers