After updating Yoast to 14.6, the pre-checks for SEO and readability are missing from the publish box when using the classic editor.
When using the classic editor, I expect to see Yoast readability and SEO checks in the "Publish" box in the sidebar on my edit page. Examples:


Please inform the customer of conversation # 632773 when this conversation has been closed.
Ok, waiting to be advised when solved.
Thank you.
Please inform the customer of conversation # 631979 when this conversation has been closed.
Please inform the customer of conversation # 633527 when this conversation has been closed.
Good afternoon,
I have the same problem. I tried uninstalling all the plugins and installing the twenty twenty theme, but nothing. Effectively the error disappears when the classic editor plugin is disabled.
I am also waiting for a solution.
Thank you.
A user is experiencing the same issue: https://wordpress.org/support/topic/indicator-under-publish-missing-in-version-14-6/#post-13173916
Please inform the customer of conversation # 633169 when this conversation has been closed.
Please inform the customer of conversation # 634395 when this conversation has been closed.
Please inform the customer of conversation # 634697 when this conversation has been closed.
Please inform the customer of conversation # 634406 when this conversation has been closed.
Please inform the customer of conversation # 634506 when this conversation has been closed.
Please inform the customer of conversation # 634339 when this conversation has been closed.
Seems to be fixed in https://github.com/Yoast/wordpress-seo/pull/15739
Seems to be fixed in #15739
Good afternoon,
The truth is that I have not seen the way to solve it in the thread, in my case I still have the same problem.
Do you have any other information about this error?
Thank you.
@emidez You can expect the issue to be fixed in v14.7 of Yoast SEO. We are not sure when we will get that released exactly but a fix is expected to be in it.
I've added a proper milestone as this fix is included in the 14.7 (august 4, 2020) release of the plugin.
Please inform the customer of conversation # 636112 when this conversation has been closed.
Fixed with the release today, closing this issue.
Most helpful comment
I've added a proper milestone as this fix is included in the 14.7 (august 4, 2020) release of the plugin.