Hello!
We ran the URL you provided in both Google Structured Data Testing Tool and Google’s Rich Result Test but we don’t see any errors.
As for the “Unnamed item”, it is related to how Google Search Console labels items in the interface, not an error in your pages. Please refer to the discussion here. It’s also discussed in this forum thread, that the ‘unnamed item’ message is just a reporting issue rather than an actual error.
Since your URL is returning a green checkmark where each item is named on the Rich Results Testing tool, then there’s nothing to worry about.
Sorry for my late reply
I might tell you be a bit wrong about the tool that using to check the error.
I used the tool in search console and found that it is reported as an error !
I have included the below link to the image screenshot shows that google reports this as an error for the breadcrumb.
https://drive.google.com/file/d/1N2_v2nCrCSImSFEOswjaFSPd9l0ReXbR/view?usp=sharing
thanks
Methee
Thanks for sharing the relevant screenshot with us. We see that Google Search Console is reporting against 39 URLs due to the lack of item or item.name schema properties in the schema markup.
Can you please share a few more example URLs so that we can test them on our end? You can find them by clicking on the relevant error that you’re seeing in Google Search Console and it will show you the relevant URLs.
Thanks for sharing the relevant page here with us. We have tested the relevant page using the Google Structured Data Testing Tool and were able to reproduce it this time. We see the name property is missing the breadcrumbs schema and as such, you’re seeing the relevant warning in Google Search Console.
The issue you’re currently experiencing typically occurs when the relevant page has no name. Can you please confirm whether you have defined the name of the relevant page? If yes, we’d like you to please reset the Yoast SEO Indexables by following the steps given below to see whether this resolves the issue for you:
- Install and activate Yoast Test Helper plugin;
- Go to Tools → Yoast Test → Yoast SEO → Reset indexables tables & migrations options to reset it;
- Run SEO data optimization from the SEO → Tools page.
Let us know whether the issue persists after performing the above steps.
Hi thank you fro your reply
I can confirm that the post (textblock) has a title name.
By resetting the Yoast SEO Indexables, will I lost any plugin configurations that I am currently have at this moment? after reseting do i need to re-configure the plugin ?
will there be any bad effect on SEO
* More information:
Those posts having errors are created by using th “Reusable Text Blocks Plugin”.
Best Regards,
Hi,
Resetting the Indexables and Migrations table of the Yoast SEO plugin does not make you lose your existing SEO settings nor bad for your SEO.
Hi
I have done [Resetting the Indexables and Migrations] and [Run SEO data optimization] but the problem is not solved.
Thanks
Methee
Hi @pingbara
We understand that resetting the indexables and running the SEO data optimization process has not resolved the issue. Upon checking https://www.xn--72c0amvsjca4a5b9cwc.com/text-blocks/%E0%B8%A3%E0%B8%B2%E0%B8%A2%E0%B8%8A%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B8%A7%E0%B8%B1%E0%B8%94%E0%B9%83%E0%B8%99%E0%B8%88%E0%B8%B1%E0%B8%87%E0%B8%AB%E0%B8%A7%E0%B8%B1%E0%B8%94%E0%B8%AD%E0%B8%B3%E0%B8%99/, we do see that the ‘name’ field is missing, which by default, should just be the ‘title’ for the WebPage. If you were to edit this page and modify the page title and save the changes, can you check if the issue resolves itself?
Also, just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Nineteen.
Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.
As we can imagine that 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.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
