Unparsable structured data detected by Google crawler

Hello @blaagrrrl!

Can you please provide us the URL where this issue occurs so we can test on our end?

Hm….

Where is the discussion and my link to the screenshot of my Google page with the error?

EDIT: I see it’s moved to NSFW ??

• This reply was modified 4 years, 3 months ago by gocastaway58.

Yes @gocastaway58, we’ve answered into a separate topic.

Hi @blaagrrrl,

Please feel free to reply with the specific URL you got this error with. If possible, please share a screenshot (using a service like https://snipboard.io/) of the Google Search Console error you got as well, so we can further investigate. Thanks!

Here is the link to the screenshot https://drive.google.com/file/d/1p526JkdMzBdg7cONOCwy1uTW0aZZpjOf/view?usp=sharing. I am not sure I captured the information you need to see. Let me know if you need another view. One of the URL’s affected: https://heritagespanish.coerll.utexas.edu/groups/heritage-spanish-cafe/
This page is generated with the Buddypress plugin.
Thanks

The issue I had was related to a buddypress member page.

Hi @andrewmcbride

Thanks for providing that information. Do you mean that when enabling BuddyPress and Yoast SEO, there was an issue with regard to the schema.org structured data?

Hi @blaagrrrl

Upon checking the page source of https://heritagespanish.coerll.utexas.edu/groups/heritage-spanish-cafe/, we do see that the schema is showing an added ‘null’ value for the @type and WebPage schema. Could you please let us know what sort of page this is? Is this from BuddyPress or another plugin?

Could you also try and see if you’ve selected a page or article type as per the schema settings here — https://yoast.com/help/selecting-content-types-in-schema-settings/

@mikes41720,
@blaagrrrl ‘s page as well as mine are both BuddyPress pages.
I think it may be related.

Mine was for “member” pages and theirs is for “groups”.

Didn’t see a way to change the schema type for users

Both pages flagged by Google crawler are BuddyPress plugin generated pages. The first link (see screenshot) is a BuddyPress member profile page and the second link is a BuddyPress group page. We have been using the BuddyPress plugin for years without any Google crawler issues. We just added Yoast SEO very recently.

I have the issue without Buddypress….

Hi @blaagrrrl, @andrewmcbride, and @mseb,

We’d like you to make sure that you’re using the latest version of Yoast SEO and BuddyPress and then check for conflicts. This means we’d like to know if the pages still show a structured data error in the Google Structured Data Testing tool if you only have Yoast SEO and BuddyPress activated while using a WordPress default theme like Twenty Nineteen.

See how to check for conflicts.

If there is still an error or if you find a conflict with a plugin or a theme, you can create a new GitHub bug report for our developers. Please also report the issue to the third-party developer as well.

Hi,

I do not have an account in GitHub and no idea how it works… But this was the only update I made at this time and the issue came after the Yoast Update…

Brgds
Mirko

@mseb If you don’t have a GitHub account, you can create one from here. Once you have a GitHub account, you’ll need to go to the https://github.com/Yoast/wordpress-seo/issues/new?template=Bug_report.md and write about the bug report with all the information you have.

@priscillamc we are running the latest versions of the plugins, BuddyPress 6.2.0 (released Aug 6 2020) and YoastSEO 14.8 (released Aug 18 2020).

The Google crawler issues didn’t start with the BuddyPress plugin update, but with the YoastSEO update.

In the YoastSEO changelog for Version 14.8 I read that the schema @type values were cleaned up. Obviously a bug was introduced with this change.

We have many teachers relying on the website, especially now that the academic semester is starting (this week), so I can’t just change the theme or disable the BuddyPress plugin which would render the website useless even if it is just for a brief moment.

I do have a GitHub account and will report the problem there.

• This reply was modified 4 years, 3 months ago by blaagrrrl.
• This reply was modified 4 years, 3 months ago by blaagrrrl.
• This reply was modified 4 years, 3 months ago by blaagrrrl.

@blaagrrrl

We have an open issue with BuddyPress that is causing that behavior. Thank you for bringing this issue to our attention. We apologize for the trouble you are experiencing with our plugin. Our developers are aware of the issue and a report is currently open with our development team for this issue.

We are not sure when a fix will be ready only that our developers are aware of the issue.

In the meantime, we suggest signing up for our newsletter as that is where we will announce product changes and updates. You can sign-up for it here https://yoast.com/newsletter/.

You can disable the Yoast schema output and allow you to re-validate with Google by adding this code to your themes functions.php
It will check first if Yoast is running and then it disables the schema output

// Check if Yoast is enabled
if( in_array(‘wordpress-seo/wp-seo.php’, apply_filters(‘active_plugins’, get_option(‘active_plugins’)))
|| in_array(‘wordpress-seo-premium/wp-seo-premium.php’, apply_filters(‘active_plugins’, get_option(‘active_plugins’))) ){

// Remove yoast-schema-graph
add_filter( ‘wpseo_json_ld_output’, ‘__return_false’ );
}

• This reply was modified 4 years, 3 months ago by gocastaway58.
• This reply was modified 4 years, 3 months ago by gocastaway58.