Problem with Yoast-Readability-Plugin

Hello Maxi,

I’m sorry to learn that the SEO & readability of your content always gives red feedback even when you do all to improve it. I don’t believe this has anything to do with your PHP version.

Is it possible to share screenshots of the content and the Yoast SEO analysis for it? You can use any image-sharing service like https://pasteboard.co/, https://snag.gy/, https://imgur.com/, https://snipboard.io/, or even upload the screenshot to your website. Once you upload it to an image-sharing service, please share the link to the image here.

Hi Maybellyne.

Sure, so the article-Link would be https://www.maxenergy.at/magazin/energiemarkt/
and the Link to the Screenshots of the readability-optimizations would be https://www.maxenergy.at/magazin/wp-content/uploads/2022/08/Screenshot-Energiemarkt-Yoast.png
It’s in German, but in general it says that i would be using the same word to start a sentence three times in a row (which I didn’t) or that one paragraph would be longer than 300 words and has no headings in between (which is also not the case).

Thank you for your help!

Thanks for the clarification and screenshots.

About using the same word to start a sentence three times in a row, that must be consecutive sentences in English. I suspect this is due to the content under Energiemarkt – FAQ. Our analysis reports the bullet points as consecutive sentences. Writing consecutive sentences starting with the same word can lead to monotony in a narration. But altering your content, in this case, is not recommended. Therefore, you may ignore this warning since this is a valid use of repetition in your text. It will not cause any problems with your article and search engines.

Regarding the second issue, can you let me know how you add the content? Are you using a page builder or the default WordPress content editor?

Thank you for your feedback. The weird thing about the FAQ-section is that until july or august the readablity-bullet has always been green – even if there were FAQs in those articles. Did you have any updates since then?

Regarding the second issue, we are using the “Avia layout architect” and the theme Enfold. I hope that this is what you’re asking for.

I see that Avia layout architect is a page builder.

Yoast SEO analyzes the default WordPress content areas like the title, URL, and the main content box (WordPress editor). Since you are adding your content through other plugins or theme content boxes (as most page builders do), Yoast SEO may not be able to detect it by default. Currently, we are compatible with the Elementor page builder. The?Yoast SEO Elementor integration?is free to use for everyone; no premium or add-on is required for core functionality.

Since you are using another page builder, please understand that page builders commonly use a custom editor designed by their team. Because plugins rely on the default editor, some page builders make the data entered into their editor available in the default editor. In these cases, Yoast SEO will see and analyze the content as if created with the default editor. When this is not the case, an integration feature must be available to parse the page builder content into Yoast SEO for analysis.

It’s like opening a room to find a safe inside it. Unless you have the code to unlock the safe, you can only see the inside of the room. To get the code to open the safe, you must contact the person who set the unlock code. We have tried to automatically unlock and parse content from other plugins and themes with inferior results in the past. Therefore, we opted to provide an API that developers can use to unlock their content and pass it to our page analysis.

Although our plugin does not detect your content and shows an incorrect analysis report, this does not affect how search engines crawl and analyze your site. Search engines process the front end of your site and will detect your content.

This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.