Incorrect value type “@type”

Divi theme, Wordrpess and all plugins are updated to latest.

thanks

Hello @vikram_mann,

Thanks for reaching out!

We can see that https://www.nirandfar.com/?author=Marta+Kagan is showing Null for some part of the Yoast schema. See attached. We would expect to see a URL there. We would like some more information.

1. If you go to WordPress > SEO > Search Appearance, is the Knowledge Graph and Schema section filled out?

2. Does clearing your caching from your theme, plugin, server, CDN like CloudFlare or browser resolve the issue? If you are not sure how to clear caching from theme/plugin please speak to those authors. If you want to clear cache from the server, please speak to your host provider. To clear the cache from a browser use this guide: https://yoast.com/help/how-to-clear-my-browsers-cache/

Hi there,
I have the exact same issue as the original poster ("@type":["WebPage",null]). I was made aware of it through an email I got from the Google Search Console Team.

The issue only seems to affect pages with a certain custom post type we use for product documentation.

To answer the two questions:

1. Yes, Knowledge Graph and Schema sections are filled out in WordPress > SEO > Search Appearance
2. I cleared the cache of our caching plugin (W3 Total Cache), but that did not help.

One of the affected URLs:

• https://uberagent.com/docs/uberagent/latest/metrics/microsoft-office/

Hi @maybellyne

I checked the WordPress > SEO >Search Appearance and filled the knowledge graph. But still the issue stays. Please check the link : https://www.nirandfar.com/?author=Marta+Kagan

Thank you for the quick reply.

Regards
Bikramjit

I can confirm this issue – same situation as @hiroprot. The information in the Knowledge Graph & Schema section is complete and correct, cache has been cleared repeatedly, and this is affecting a custom post type.

In my case, I found a fix. The post type in question was publicly visible, but the “public” param was not enabled. Fixing that, then saving at Search Appearance > Content Types (where the post type was not listed before) produced valid markup confirmed in Google Search Console.

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

The same issue reported by Google here:
– affected URL example:
https://www.role-editor.com/forums/users/steve2106/

– wrong @type value:

{"@type":["WebPage",null],"@id":"#webpage","url":"","name":"","isPartOf":{"@id":"https://www.role-editor.com/#website"}

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

Hi @fpcsjames

Thanks for sharing this information. Was this only affecting the CPT that didn’t have the “public” parameter enabled and not the rest of your URLs having the null WebPage value?

Hi @vikram_mann @hiroprot @shinephp

Just to clarify, are these URLs that are having the null WebPage value being generated coming from a CPT? Are you using any forum plugin or anything of the sort? Would it be possible if you could check on the fix mentioned by @fpcsjames as well:

The post type in question was publicly visible, but the “public” param was not enabled. Fixing that, then saving at Search Appearance > Content Types (where the post type was not listed before) produced valid markup confirmed in Google Search Console.

In my case, the affected pages are a custom post type Documents (vldocs_document) that is managed by a plugin.

The corresponding settings in Yoast’s Search Appearance > Content Types are as follows:

• Show documents in search results: yes
• Show SEO settings for documents: show
• SEO title: [Title] [Page] [Separator] [Site title] documentation
• Meta description: [empty]
• Default page type: Web page (default)

Looking at the JSON I also noticed that the URLs for the affected entries are incorrect. Example:

• URL in JSON: https://uberagent.com/blog/vldocs_document/metrics/microsoft-office/
• Correct URL: https://uberagent.com/docs/uberagent/latest/metrics/microsoft-office/

Thanks for submitting all of this information. We are currently seeing the schema markup issue with the @type from several users and the issue is currently under investigation. However, we were unable to reproduce the issue on our end so far.

Therefore, we highly recommend you please submit a bug report directly at our GitHub development repository with all the information you have so that our development team can reproduce the issue and investigate it further.

Same issue here, after update.
Here are my links i’m getting incorrect value type “@type”

https://www.visionbrokers.co.za/page/3/?attachment_id=pvykghbdlo
https://www.visionbrokers.co.za/page/2/?attachment_id=pvykghbdlo
https://www.visionbrokers.co.za/page/4/?attachment_id=pvykghbdlo

Google Search Console highlighted this part of the code on the first link(page 3):

“inLanguage”:”en-US”,”potentialAction”:[{“@type”:”ReadAction”,”target”:[“”]}]}]}</script>
<!– / Yoast SEO plugin. –>

I don’t know how to fix this. Hope a new update fix this ASAP.

@enrico1vision

If you are using bbPress or BuddyPress we have an open issue related to Yoast outputting an incorrect value. We are not sure when a fix might be ready for those plugins but we are aware of an issue with them.

If you are not using one of those we ask that you please make sure all your non-Yoast plugins are updated, you are using v14.8 of Yoast SEO and are on v5.5 of WordPress.

If they are all updated, it seems to be a plugin or theme conflict. Please Check for conflicts. Install the Healthcheck plugin and enable troubleshooting. Then switch to a standard theme like 2020. Does the issue resolve? NOTE: This will not affect how users see your site.

If there is a conflict with a plugin or a theme, you can create a new GitHub issue?for our developers. Please report the issue to a third party developer as well.

If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium?and receive our Premium email support and we can help you further.

@mikes41720 Only the CPT without public = true had the null value. Other CPTs with public enabled were not affected.

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

Same issue here with the Google Search Console warning for the @type error. This seems to be rather widespread and is being discussed elsewhere.

I have found you can add:

add_filter( ‘wpseo_json_ld_output’, ‘__return_false’ );

To your theme’s functions.php and it will disable the Yoast schema output and allow you to re-validate with Google. All we can do until there is a fix.

@fpcsjames

Where exactly do you configure public = true for the custom post type?

Hi @shoplifter

Yes, adding that filter will disable the Yoast SEO plugin’s schema.org structured data output. Just to confirm, are you also encountering the ‘null’ output for the WebPage? We’d like to ask if this occurs with a URL generated by BuddyPress, bbPress, or BuddyBoss? Or is it another CPT?