• Resolved rozsarak

    (@rozsarak)


    Hi guys

    (For my client who has concerns about the poor readability scores due to Yoast reading the code as text etc)

    Am just wondering if you have any reassurance that I can give to my client or experience of addressing the poor score on readability using Yoast plugin, that Salient theme gets due to the code structure that is read by Yoast on any page eg when using list items or rows/cols.. 

    Paragraph length: 6 of the paragraphs contain more than the recommended maximum of 150 words. Shorten your paragraphs!

    (it’s reading the letters of the code as text)

    [nectar_icon_list_item icon_type=”icon” text_full_html=”html” title=”List Item” id=”1723822391-1-74″ icon_fontawesome=”fa fa-arrow-right” header=”Estate Planning”]Estate planning<span>?</span>involves deciding what will happen to your money and assets after you pass away. This can include<span>?</span>creating a will, setting up trusts, and making decisions about who will inherit your wealth.[/nectar_icon_list_item]

    Consecutive sentences: The text contains 3 consecutive sentences starting with the same word. Try to mix things up!

    [testimonial star_rating=”100%” title=”Testimonial” id=”1722696839-1-63″ name=”Norma Pratt” quote=”Really great service, thanks for the advice it is very appreciated.”][testimonial star_rating=”100%” title=”Testimonial” id=”1722696839-1-63″ name=”Paula Dunne” quote=”Excellent presentation, well explained, well informed.”]

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @rozsarak

    Thanks for reaching out. I understand the Yoast SEO plugin is detecting your page builder shortcode content as real text. Yoast SEO analyzes the default WordPress content areas like the title, URL, the main content box (WordPress editor). If you are adding your content through other plugin 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.

    If 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.

    If you are using a plugin or theme that doesn’t send or incorrectly sends their content to our page analysis, please reach out to the author or developer regarding the integration feature. Our development team provides information about creating a custom integration here. In the meantime, you can create a draft post without using the page builder and copy the content section from the frontend of your site into the default editor. The Yoast analysis will run on the draft’s copy of the content so you can review and change the content in both editors. Once you’ve optimized the content, you can discard the draft copy.

    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.

    Plugin Support Mushrit Shabnam

    (@611shabnam)

    This thread was marked resolved due to a lack of activity by the original poster. The original poster can change the status to Not Resolved to re-open the issue or open a new topic.

    If you are not the original poster but have a similar issue, please open a new topic.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.