• Resolved blaagrrrl

    (@blaagrrrl)


    I get an
    Incorrect value type "@type"
    error from Google crawler and have no idea what is wrong. That is from the JSON schema that is generated by Yoast. I followed Yoast recommendations and used the recommended Health Check & Troubleshooting plugin. According to the Health check, the site is in Good and has 0 critical issues. The theme being used is a twentythirteen child theme (it is an older site). In addition the Troubleshooting mode didn’t let me access the website over secure protocol, but had no problem over http. My htaccess file only contains the default directives. Can you point me in the right direction?
    Thanks!

Viewing 9 replies - 16 through 24 (of 24 total)
  • Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @gocastaway58

    Yes, if you want to disable the schema output of the Yoast SEO plugin, you can refer to the Schema API documentation here — https://developer.yoast.com/features/schema/api

    Just to clarify, are you also encountering this issue where the WebPage output is showing as ‘null’ for one of your CPTs? We’re investigating this further so we can have it fixed and have the correct schema output.

    Thread Starter blaagrrrl

    (@blaagrrrl)

    @pcosta88 thanks.

    @gocastaway58 I’ve added the code to functions.php and the site is now validating without any problems. Thank you. But does that mean that YoastSEO is not optimizing readability for search engines anymore?

    I am getting this error as well. Did the recent update fix this issue?
    screenshot: https://share.getcloudapp.com/5zuGnx2G

    @blaagrrrl The code is to stop the new Schema-graph, i can’t tell you if Yoast is not optimizing the readability for search engines anymore, i got this code from the developer of the theme i am using on my sites.

    What i can tell is that Yoast update 14.8.1 is not resolving the @type parse error. On 1 site i updated Yoast and did not put the code in functions.php, and just got mail from Google that the parse error validation failed, so i think Yoast has to come with a better fix

    Hi @blaagrrrl,

    The option @gocastaway58 is giving is to completely disable our Schema on every page of your site. This is quite a heavy workaround for now. Our development team is still looking into details about this issue and the scope of it.

    We know that plugins like bbPress, BuddyPress, and buddyBoss are having this issue on specific pages. The URL you mentioned before is from a group page in buddyPress, so this is also coming from this.

    Just got the 14.9 update, is this error now fixed?

    Hi @gocastaway58,

    Thank you for updating to our latest release. Unfortunately, no. We are still investigating the scope of the issue to get this right. It appears not to be only related to using bbPress, BuddyPress, or buddyBoss plugins, but it’s a bigger scope. Our development team is still investigating. Thank you for your patience while we figure this out.

    Plugin Support devnihil

    (@devnihil)

    @gocastaway58 The fix for the this issue is expected to be released in the 15.0 version of the plugin. You can also follow the status of the issue here: https://github.com/Yoast/wordpress-seo/issues/15936

    That would be nice, then we can remove the code we have added to disable the scheme function.

    I must say that the organic hits are going down since this problem occured and the code we added.

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Unparsable structured data detected by Google crawler’ is closed to new replies.