Breadcrumb Error in Google Search Console

Thank you for creating a new topic, @jonass1. ??

To help us troubleshoot, can you please share your Site Health information privately via this form?

Thank you for reaching out to me so quick, @shetheliving ! ??
I just submitted my ‘site health’ data

Thank you, @jonass1! Can you please share some screenshots of your Yoast SEO Breadcrumbs settings at SEO > Search Appearance > Breadcrumbs? The forums do not support screenshot uploads, so you can share one via a link generated by Imgur or JumpShare. Thank you!

Sure, here they are. ??

https://snipboard.io/tQO3J8.jpg
https://snipboard.io/jPDfvs.jpg
https://snipboard.io/uT4z3K.jpg

There is another issue, for which I wanted to start a ticket. But perhaps they are related. If not, I’ll start one later.

When I create my stories and I try to open Yoast dashboard (SEO, Readability, Schema, Social) under the central design panel of Stories, the dashboard is blank.
So once I click on the ‘Third-Party Meta Boxes’ button it expands the options, but doesn’t give me access to any of these even upon clicking. It’s just blank. See screenshot below.

https://snipboard.io/6mJeac.jpg

Thank you very much, @shetheliving ! I really appreciate your help ??

@jonass1 Thank you for these details – very helpful!

I’m still testing the Either ‘name’ or ‘item.name’ should be specified issue, but it does appear to be related to the Yoast breadcrumbs feature. I’ll report back as soon as I have more details.

When I create my stories and I try to open Yoast dashboard (SEO, Readability, Schema, Social) under the central design panel of Stories, the dashboard is blank.
So once I click on the ‘Third-Party Meta Boxes’ button it expands the options, but doesn’t give me access to any of these even upon clicking. It’s just blank. See screenshot below.

I’m able to replicate this issue, as well. I’ve created a GitHub issue here for our team to review.

@shetheliving , you are the best! Thank you so much for this!

Looking forward to hearing from you,
let me know if you need more info on anything.

Jonas

Hi Jonas,

Thanks for your patience as I’ve worked with the Yoast team to investigate this further. Can you please try the following steps and then check to see if the Search Console error still appears on your story?

1. Install and activate Yoast Test Helper plugin
2. Go to Tools → Yoast Test → Yoast SEO → Reset indexables tables & migrations options to reset it
3. Run SEO data optimization from the SEO → Tools page

Thank you!
Bethany

Hi @jonass1 Thanks for your patience as we worked to test and troubleshoot this issue. It does appear that the Either “name” or “item.name” should be specified message displaying on Web Stories in Google Search Console is related to a known issue in the Yoast SEO plugin: https://github.com/Yoast/wordpress-seo/issues/17006. As noted in that issue, they are aiming to release a fix in their next version, 16.4.

You can follow that GitHub issue for updates, but I will also update this topic when v16.4 has been released.

Thank you!

Hi @shetheliving ,

Awesome! Thank you so much for looking into this! I tried what you suggested above with the Yoast Test Helper. I’m waiting for my results from GSC.

If that’s not fixed, I’ll wait for the plugin update and see.

Thanks a lot again!
Best wishes,
Jonas

Hi @jonass1,

Yoast has released version 16.4, which includes the fix for this issue: https://github.com/Yoast/wordpress-seo/issues/17006. I just ran your Web Story through the checker and that issue has been fixed: https://search.google.com/test/amp?id=HUZ4b0Eot49dtQAS2-aMXQ.

That said, the results are now showing amp-onerror validation issues on Web Stories URLs, which appears to be related to changes in the AMP validator. We are actively investigating the issue in this GitHub ticket and anticipate having a fix out this week.

In the meantime, users can download and install this mini-plugin as a temporary workaround to the validation issue.

I’ll update here when the fix has been released and you can remove the plugin.

Thank you for your patience here!

@shetheliving Bethany,

This is perfect. I installed the work-around plugin and seems to be working for now. GSC recognises it as AMP

Thank you so much for your help so far,
Looking forward to hearing more news!
Have a nice day!
Jonas