breadcrumbs GSC error: Either “name” or “item.name” should be specified

@newbiesite We’re sorry to hear you are experiencing this issue on your site.

We understand that Google Search Console is reporting a warning saying that ‘either name or item.name should be specified’.

The Yoast SEO plugin takes the name from the page name. In this case, it could be that the name is missing from your front page. Can you please check the page you’re using as your front page and make sure you’ve added a title to this page?

If not, does adding the title resolve the issue?

I’ve added a title to the homepage and I can see that the “name” field has a value in page source, but for the next pages the value is empty:

“breadcrumb”:{“@id”:”https://xyz.com/#breadcrumb”},”inLanguage”:”en-US”,”potentialAction”:[{“@type”:”ReadAction”,”target”:[“https://xyz.com/”%5D}]},{“@type”:”BreadcrumbList”,”@id”:”https://xyz.com/#breadcrumb”,”itemListElement”:[{“@type”:”ListItem”,”position”:1,”name”:””}]}]}

@newbiesite,

It appears a fix for the breadcrumbs issue will be incorporated with Yoast SEO 16.6 (to be released soon).

Until then, you may want to read this post.

Cheers!

@newbiesite

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/

@maybellyne Checking through the 2 reasons in the link you provided, The Rich Results tester tool throws an error: `type
BreadcrumbList
id
https://xyz.com/#breadcrumb
itemListElement
Either “name” or “item.name” should be specified
type
ListItem
position
1`

But the Schema.org validator doesn’t show any errors. From what I understand, this means that it’s not the second issue that’s the problem.
I’m not sure what other third-party tool the article refers to.

Does this mean that I should ignore this error for now and wait until Yoast v16.6 is released?
Thanks.

Hello,

Some users have reported errors in third-party tools such as Semrush and Ahrefs site audit.

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