Either “name” or “item.name” should be specified error

Hi @tuanyk

Just to clarify, we do see that for the homepage https://dicasdecor.com/, there doesn’t seem to be a missing “name” field in the breadcrumb schema. However, for the respective subsequent pages (e.g. /page/2/ and /page/5/), we do see a missing “name” field in the final breadcrumb output.

Just to clarify, you’ve set your homepage as a static page, correct?

If so,

Thank you for bringing this issue to our attention!

We apologize?for the trouble you are currently experiencing with our plugin. Luckily, a so-called “bug report” (a description of the issue, so we can fix it) is filed already.

What’s next?
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report.

If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic.

Hi Michael,

Yes, my homepage is set up as a static page.
Is there anything else that I can do?

Hello,

We’ve checked with our developers and in-house SEO experts, and they’ve confirmed that this is not an actual error being reported by Google’s Rich Results and Google’s Structured Data Testing Tool.

We’re aware of the reported errors you’re currently seeing in the Google Search Console, SEMrush, and Ahrefs site audit due to the Yoast SEO schema markup for the breadcrumbs.

Our development team is currently working on enhancing the breadcrumbs schema output to bring the relevant missing properties back. This fix will likely be available in the next update i.e. v16.6 update. Please also do refer to this article regarding the breadcrumb changes we made in v16.2 – https://yoast.com/help/breadcrumb-changes-yoast-seo-16-2/

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.