Yoast SEO Plugin not showing readability score for posts

[Hyperbits]

Our team uses the Pro builder to write blog posts. One feature of Yoast SEO is that the plugin scores each post based on readability but on all of our posts it instead just reads “not enough content: Please add some content to enable a good analysis”:

And these are all articles with plenty of content to score. Is Yoast compatible with the Pro builder in terms of reading and scoring the text content? What can you suggest so that Yoast correctly reads the content of our blog posts?

Thank you.

[prakash_s]

Hello, @Hyperbits,

Thanks for writing to us.

Yoast SEO can now read the Cornerstone contents well. Please make sure that everything is up to date according to our version compatibility list at https://theme.co/docs/version-compatibility.

Please follow the best practices when updating your theme and plugins. See https://theme.co/docs/how-to-update for more details.

Also, contact Yoast SEO support to learn how to reanalyze the page’s content. We also suggest that you add a new page/post with some sample content and test the case, as that is what we are going to do for testing. It might be the case, that the page/post in question used old elements of some kind. You will need to use the new headline ad text elements.

If nothing is helping, please share your details in a secure note. Please provide the following details

• WordPress Login URL
• Admin level username and password

You can find the Secure Note button at the bottom of your posts

Thanks

[Hyperbits]

Thank you Prakash. It looks like everything is good in terms of version compatibility. I tried to test out a new blog post using only new elements and no “classic” elements, but I am having the same issue with Yoast. I added login credentials in a secure note. Please let me know if there is anything else you need for access.

[tristup]

Hi @Hyperbits,

It was a known issue with the Classic elements and has not been reported issue with the V2 elements. I have checked your site and found the issue there, this could be a bug related to the plugin you are using. I would suggest you to contact the plugin author on this case and please let us know the feedback from them on this.

Thanks