Hi @itons
Can you confirm you are using the latest version of Yoast SEO for WordPress v16.5?
We do know there was an issue regarding this specific error for the breadcrumbs when we made a change in an earlier version of the Yoast SEO plugin (v16.2) and you can learn more about it here – https://yoast.com/help/breadcrumb-changes-yoast-seo-16-2/
It should have also been addressed in the latest version of Yoast SEO v16.5. Otherwise, could you provide us with an example URL where this issue is occuring in v16.5, so we can check on this further?
Thread Starter
itons
(@itons)
Updated to version 16.5 of Yoast SEO plugin.
And I found a bug and downgraded it to version 16.4.
I'm not sure if the answer you're looking for is correct.
Hi @itons,
To see if the Google Search Console error still applies or if there is a bug, can you upgrade to 16.5 and test the pages mentioned in the report using the Google Rich Results test?
You can test the upgrade on a staging site if you don’t want to upgrade on a production site. Do you see any errors?
If you see an error or find a bug, please send us more details. You’re welcome to send us a link to a screenshot or an example URL.
Thread Starter
itons
(@itons)
Google Rich Result Test results screenshot image.
site : https://itons.net/page/2/ ~ https://itons.net/page/101/
https://1drv.ms/u/s!Av8vt0tjw3NLgcl5nGDkqKiPnoxPfA?e=YClszm
https://1drv.ms/u/s!Av8vt0tjw3NLgcl6yUUHxShYnsbfug?e=15nhfB
So I downgraded the plugin version again.
Hope this helps.
-
This reply was modified 3 years, 10 months ago by
itons.
-
This reply was modified 3 years, 10 months ago by itons.
Hi @itons
Thanks for providing those screenshots. It looks like the name field was indeed missing for page 2 and onwards for your homepage paginated archives.
If you were to upgrade temporarily to Yoast SEO for WordPress v16.5, could you check if the same issue occurs for just the homepage (https://itons.net/) itself and not page 2 in the series?
It looks like there’s something that is preventing our plugin from generating the ‘name’ field schema for the breadcrumb list for the paginated archives of your website.
Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict, is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty.
Please test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts
If you were to test this with a default WP theme such as TwentyTwenty, and only Yoast SEO v16.5 enabled, could you check and confirm if the name field then generates for the paginated archives in the homepage?
Thread Starter
itons
(@itons)
Thank you for your reply.
There were no problems with the homepage (itons.net).
Is this really my problem? (themes, plugin conflicts?)
-
This reply was modified 3 years, 10 months ago by itons.
-
This reply was modified 3 years, 10 months ago by itons.
@itons
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 next update i.e. v16.6 update.
Thread Starter
itons
(@itons)
Looking forward to an improved version and always waiting.
Thank you.!
@itons Thanks for your reply and you’re welcome. If you should need any further assistance in this matter, please do not hesitate to let us know.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
Thread Starter
itons
(@itons)
When is the next update coming out?
