Incorrect value type “@id”

I’ll be glad to help.

Could you please describe a bit more in detail what do you refer to by “Google Search Console is reporting”? what report exactly or what is Google relating this error to?

Thanks

Sure, Thank you. Google Search Console has sent me an email for several of my sites. The subject is “New Unparsable structured data issue detected for site (mysite.com). The body of the emails is as follows:

—
Search Console has identified that your site is affected by 1 Unparsable structured data issues:

Top Errors
Errors can prevent your page or feature from appearing in Search results. The following errors were found on your site:

Incorrect value type “@id”

We recommend that you fix these issues when possible to enable the best experience and coverage in Google Search.

—

I’d like to fix this, but I’m just not sure where to start. Thanks!

Hello @fmgguy

We are happy to help.
Could you please verify that the current version of our Plugin and Yoast is updated?
That just in case we need to troubleshoot the site, we better do that with the latest version.

We found this tool online; perhaps you want to take a look and check your links to see if you can see more information about that particular problem:
https://search.google.com/structured-data/testing-tool

This article about “Structure data” with Yoast is also pretty interesting.
https://yoast.com/google-search-console-and-structured-data/

Please, keep us posted.
We might need to report this back to our developers.

Yes, all plugins are up-to-date, and the site is running the latest version of WordPress.

I have used the Google testing tool, and it seems that the @id that is failing should be the domain URL (all of the @ids that pass include that). I just am not sure where to add that info so that it will pass.

I also took a look at the Yoast article, but from what I see, the Structured Data report has been moved to the new version of GSC, and the only info I see there is that I have unparsable structured data on the page in question, and that the issue is the Incorrect value type “@id”.

Just an FYI… I have posted this on the Yoast Support forum twice, with zero response (other than people posting they are having this same issue), so thank you so much for taking time to look into this. I know I’m not the only one who has this issue.

Hi @fmgguy,

Our suggestion at this moment will be to install such a plugin like SEO by Yoast and exclude “Picture Tag” (ngg_tag) from the sitemap and respectively avoid them being indexed.

Hope this helps

@mihaiimagely I certainly can exclude the picture tag from the sitemap, but that seems to me to be “hiding” the problem rather than “fixing” the problem. I was hoping to fix the problem.

Hi @fmgguy,

I see that it has been added to our list but our developers are hesitant to do any change ref ngg_tag because it may break the backwards compatibility and respectively I am afraid that this is still in waiting mode for now in absence of a “clean” solution.

Thanks for your understanding