• Resolved fob

    (@fob)


    I have discovered a few problems which occur after activating the widget in the sidebar of a custom post type:

    There seems to be a conflict with the Yoast SEO Tool (which works well together with Schema & Structured Data for WP & AMP, if the plugin widget is not active).

    • Some schema data is gone for blog articles (posts and post archives) as well as for the custom post type where the tool should be placed.
    • The schema data output of the tool itself is not embedded on the review page (the custom post type archive) but can be found on the front page instead.
    • Would be cool to load header stuff (scripts and styles) only in those archives where the widget is embedded and schema data on the same post/page/archive.

    I tested the tool for the first time and like it, by the way. Very nice customization options, although currently without blocks for the block editor, if I’ve seen that correctly.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Design Extreme

    (@designextreme)

    @fob Where is the conflict with the Yoast SEO Tool?

    As stated at schema.org, the Structured Data for Local Business only needs to be present once per website. If there are multiple businesses, then I do not recommend using Structured Data through this plugin because only one location is properly supported (otherwise, there is data missing for subsequent businesses).

    This plugin does not remove any other Structured Data. All other output remains intact. It is permissible to have multiple instances of the JSON output; it is cumulative and can build up a complete picture of a business or a web page’s content.

    The Structured Data is for Local Business and has relevant information for this only. The reviews are for the business and not products, so having this on the home page (you can override this) is more logical than having it elsewhere on the website. Only one instances of Local Business Structured Data is recommended according to Schema.org.

    The widget and the Structured Data do not need to exist on the same page. Structured Data is to inform external websites in a structured way, so placing this according to best practice is probably better advised than trying to match any given page’s content.

    I am considering adding support for Gutenburg, but having all the functionality of the Shortcode (which is extensive) will require quite a bit of development time.

    Thread Starter fob

    (@fob)

    Thank you for the detailed answer.

    I found an option to additionally allow post formats for search engines in Yoast SEO that seem to have resolved some of the issues.

    Regarding the structured data I would like to suggest comparing the things with Google views. They want you to promote nothing in the JSON part of a page that can not be seen by a real user. Crawlers should be able to find a match.

    I appreciate your thoughts and understand the update effort quite well. Thanks a lot.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with Yoast SEO Tool’ is closed to new replies.