Same here.
This is what my hosting support responded:
As mentioned in the debug information, the table ‘wp_yoast_indexable’ already exists and this query is trying to create this table.
This is something that your developer should be able to resolve.
Seems it is not a server issue but more like Yoast plugin issue.
But Yoast already covered themselves in their documentation 😀
I have deleted Yoast and dropped the Yoast tables in the database, still no go.
Also, tried this. Still didn’t work – https://wordpress.org/support/topic/something-went-wrong-while-optimizing-the-seo-data-of-your-site-please-try-agai-4/#post-12790432
@vapili2098
We apologize. A different user on that topic: https://wordpress.org/support/topic/something-went-wrong-while-optimizing-the-seo-data-of-your-site-please-try-agai-4/#new-topic-0 had an error message that matched a bug report here https://github.com/Yoast/wordpress-seo/issues/15082.
It is not clear to use if you also have that same error. We need your help. We understand that when you run the feature you get:
“Something went wrong while optimizing the SEO data of your site. Please try again later.”
If you were to review your debug or error logs do you see any errors which contain:
wordpress-seo
yst
yoast
yoast-seo
wpseo
in them? If so, can you let us know what those errors are?
If you are not sure how to get those logs your host provider can help.
@peterbutler
We are happy to help you! If you are still experiencing the issue per the forum guidelines, we ask that you please create separate topics for the issues you are experiencing.
That way it’s easier to track issues and provide assistance on your specific concerns on your specific site. Plus, you will get your own alerts for the issue rather than someone else’s. You may make a new topic here: https://wordpress.org/support/plugin/wordpress-seo/#new-post.
Thanks!
Ok, so I updated to Yoast 14.2, disabled and reactivated the plugin and now it worked, finally!
Just one question: is it normal that all my database tables are utf8mb4_unicode_ci, except:
– wp_yoast_indexable
– wp_yoast_indexable_hierarchy
– wp_yoast_migrations
– wp_yoast_primary_term
which are utf8mb4_unicode_520_ci?
Why do these 4 tables need a different collation?
@vapili2098 Thanks for confirming it’s working for you now. Regarding utf8mb4_unicode_520_ci, that collation type was introduced in MySQL 5.6, which is listed as a requirement of the plugin: https://yoast.com/help/plugin-requirements/
Hi!
We’re closing this thread because we haven’t heard back from you in a while. Should you have further questions, please open a new thread.
