Either I don’t understand or there is something wrong with the plugin

Hi Eggeno,

I’m sorry to see that the indexation is not working as expected.

Can you please try the following steps to see if that solves the issue:

1. Install & activate the Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Hit the “Reset indexables & migrations” button
4. Try the optimize button again

Please let us know if that solved the issue

Hi Patrick I followed your suggestion. But it does not work ??

Yoast SEO continue to process objects!
How should I do it?

Hi Eggeno,

There are a few cases where disabling all other plugins and then using the “Reset indexables & migrations” button has worked. So if you could try that, that would be great.

Alternatively, if you don’t want to disable all your plugins you can use the Health Check plugin, follow steps 1-10 of this article and then click the “Reset indexables & migrations” button.

I hope that makes sense

Hi Patrick!

I followed all your advice: I disabled all the plugins and switched to the default theme. Then I clicked on the “Reset indexables & migrations” button and then I clicked on the “Click here to speed up your site now” button.

Everything seemed to work but as soon as I reactivated the plugins and my theme, the “Click here to speed up your site now” button appeared again. I clicked on it but nothing to do. Always the same bug! But then once the reindexation is done, shouldn’t that alert disappear?

Also, now on the backend dashboard, there is a jquery error (see screenshot)
Jquery Error!

In addition, the site is really slow. If I disable Yoast SEO my site is a bomb.
This is truly frustrating! I hope you can solve all these bugs. I am also a your premium customer and in many of my sites, I have not updated to version 14 given all the problems that are occurring.

Best Regards!

@eggeno If you have purchased SEO Premium you would need to contact us directly at [email protected] for assistance as this forum is reserved for support of the free version of Yoast SEO.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.