Yoast V11 destroyes our site by echoing schema.org metadata in the header

  • Resolved Blackbam

    (@blackbam)


    5 years, 12 months ago

    Unfortunatly I can not link to the page because we have to use an older version of the Plugin now. Anyway the output from the wp_head hook is like this:

    <meta property="og:image:height" content="1200" />{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id": [..................................]}]}</script>

    The schema.org metadata is echoed directly behind the og:image:height meta property and end with a closing script-tag which is never opened. This seems to be some bug though I can not tell exactly why it happens.

    This problematic bug came with 11.0 and is not fixed yet. Can you please have a look on this?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter Blackbam

    (@blackbam)

    5 years, 12 months ago

    Btw: I just noticed that all this mess happens within the (object) WPSEO_Frontend -> head (1) within wp_head at priority 1.

    Plugin Support amboutwe

    (@amboutwe)

    5 years, 12 months ago

    This may be a plugin or theme conflict. Please disable all plugins except Yoast SEO, and use one of the default (Twenty*) themes. If the problem goes away, enable plugins one by one to identify the source of your troubles.

    If you can install plugins, the Health Check & Troubleshooting plugin offers a troubleshooting mode that will disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site. Once in the troubleshooting mode, please activate only Yoast SEO and attempt to reproduce the issue you described.

    If you are unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts

    Thread Starter Blackbam

    (@blackbam)

    5 years, 11 months ago

    Hi thank you very much for your fast answer. We have an enterprise setup with a local testing system and a lot of mu-plugins (mandatory plugins), therefore I can not just enable/disable plugins.

    As the error was introduced with Yoast 11.0 there must have been some major changes in the Plugin, I guess the problem happens because some new WordPress internal function. Most probably you are using some action / filter hook which is causing the problem.

    Do you have a change history for developers? A list of hooks you are using? Any idea which might cause the problem? Because if not I would have to go through the whole Yoast codebase :-/

    Pcosta88

    (@pcosta88)

    5 years, 11 months ago

    Hi,

    New versions of Yoast include schema. You may wish to disable the Yoast schema and see if the issue resolves. This guide explains more about the schema we output https://developer.yoast.com/schema-documentation/yoast-seo/ and this one has filters to disable it https://developer.yoast.com/schema-documentation/api/

    For the changelog you can see it here https://yoast.com/wordpress/plugins/seo/change-log-wordpress-seo/

    Thread Starter Blackbam

    (@blackbam)

    5 years, 11 months ago

    Hi there,

    indeed the schema was the reason for the unexpected output and I can get rid of the broken output by using:

    add_filter( 'wpseo_json_ld_output', '__return_false' );

    Also thank you very much for the great article on how to change the schema output, I might need this for other projects.

    So the most important part of the problem is solved, I can make updates again. Still I wonder why the schema output is broken – is there some possibility to debug that?

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    5 years, 11 months ago

    In order to debug this, the first thing we’d like you to do is the conflict check. We understand that you have an enterprise setup where you cannot simply perform the conflict check. In this case, we recommend you to use a staging site. Some popular web hosts offer quick setups for a staging site so please contact your web host for assistance. They will probably be able to help you out.

    Thread Starter Blackbam

    (@blackbam)

    5 years, 11 months ago

    In this project indeed has a staging site. The process for the website like:

    1. local
    2. staging
    3. live

    So we can deploy to staging and I can send you the URL if you want? Staging environment is in heavy use though, we would have to agree on a timeframe for this.

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    5 years, 11 months ago

    Unfortunately, we’re unable to perform the conflict check or investigate the issue further for you by looking at your website since it is a public forum. However, if you’d like us to do the investigation directly by going through your site, we’d be happy to do so if you have a premium subscription as premium subscription grants you access to the personal support.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Yoast V11 destroyes our site by echoing schema.org metadata in the header’ is closed to new replies.