Thread Starter
Zacher
(@zacher)
FYI:
Yoast 16.4
Webstories 1.7.2
Mini plugin 0.1
Hi there @zacher, thank you for your report. To confirm, have you tried updating and republishing your story without making any changes, then checking it again?
To rule out any other conflicting plugin/setup, could you provide your Site Health information? You can share privately if you prefer.
As for the mini-plugin, you don’t need that anymore, as the testing tool has already been updated.
Thread Starter
Zacher
(@zacher)
Hi @luckynasan
Responded privately as per your invitation.
Yes, I ran tests with and without the mini-plugin (just in case) and put the webstory to draft and republished it. Retested in GSC and same error.
Thanks for your help.
Thread Starter
Zacher
(@zacher)
@zacher The breadcrumbs schema markup issue you’re currently experiencing is on Yoast’s radar and they’ve written a detailed article on Yoast.com about it that explains why the issue occurs and what can be done to fix this. You can find the relevant article here: https://yoast.com/help/breadcrumb-changes-yoast-seo-16-2/.
I ran your story in the test tool at https://search.google.com/test/amp?id=fe6jG5CdCBTPt-Iv7YATNg and it passed. These warnings can be safely ignored, but if you have more questions it may be best to open a support topic in the Yoast support forum. Thank you.
@zacher As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thank you!
Hello, I’m getting a breadcrumbs issue also, specifically:
Missing field “item”
Is there a fix?
Thanks!
Hi @melissassk,
It looks like Yoast SEO is again facing several issues with breadcrumbs, see https://github.com/Yoast/wordpress-seo/issues/17175 for example. Please open a new topic on the Yoast SEO support forums or report this on their GitHub repo, as this is this is an issue in Yoast, not the Web Stories plugin.
If this still happens with Yoast SEO deactivated, feel free to open a new topic here (instead of replying on an already resolved one).
Thank you!
Thread Starter
Zacher
(@zacher)
The issue remains. Sorry for delayed response.
@zacher Can you please create a new topic? This one is older and marked as resolved, so want to make sure we have a good new place for an active discussion. Thanks!
