Database table encoding

ничего страшного, если только вы не используйте эмодзи в ссылках
—
nothing bad there, unless you’re using emoji in url’s

I have no errors in my database table?

If you like you can convert encoding from Operations menu of PHPMyAdmin

@sfuma

Yoast did make some changes to the database in terms of how the plugin is storing data. It could be you need to update it. If you use the Yoast Helper Tool does the issue resolve? Please try the steps below:
– i. Install & activate the Yoast Test Helper plugin:?https://www.ads-software.com/plugins/yoast-test-helper/
– ii. Go to Tools -> Yoast Test
– iii. Locate the Yoast SEO section and select the “Reset indexables tables & migrations” button
– iv. Click the “SEO Data” button in the SEO->Tools section.

I install the latest version of your plugin on the new site and the seo links table encoding is not generated correctly. I was exhausted with your plugin. It feels like your programmers are bad. You are introducing new features that don’t work as expected. If you don’t change your code quality policy, you will lose customers. You have made a Frankenstein monster out of a plugin. It seems that you yourself are confused and do not understand what you are doing.

Hi,

We’re sorry to hear that you’re having issues with the latest version of Yoast SEO for WordPress v15.7. We’ve introduced the SEO data optimization feature (which can be found under SEO > Tools) that combines several helpful features in the Yoast SEO plugin (text link counter, internal linking suggestions (premium), indexables). You are only expected to run this feature once, and then the data will be stored in the appropriate tables in your database.

Were you able to reset the data and re-run the SEO data optimization by using the Yoast Test Helper plugin?

If you continue to encounter any issues, could you perhaps provide us with specific information regarding the encoding or what it is with how the data is stored that is causing a problem for you, so we can work together to help resolve it.

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