The ‘Home’ value of Breadcrumb is recognized as empty by Google.

[stan1781]

The default ‘Home’ for Breadcrumbs is set as an icon, which causes Google search to not recognize the website’s schema. The error message is as follows:
‘Either “name” or “item.name” should be specified (in “itemListElement”). Items with this issue are invalid. Invalid items are not eligible for Google Search’s rich results.’

Can the icon for ‘home’ be changed to ‘Home’?”

To address the issue, you can indeed change the icon to a text label ‘Home’ in your schema markup. This will provide a ‘name’ value for the home item, which should resolve the error and make your items eligible for Google’s rich results.

[crftwrk]

Of course, you can edit the breadcrumb https://bootscore.me/documentation/functions/#Example_Changing_the_breadcrumb

But in general it might be a good idea to add a visually-hidden Home text to the icon to fix that. Are you able to create a PR?

[stan1781]

I’m sorry, I would like to submit a ‘PR’ as well, but I’m just a hobbyist programmer and don’t know how to submit a ‘PR’.

[stan1781]

This modification is good, but there are still bugs in the WooCommerce product categories and product pages. I modified the code in woocommerce/inc/wc-breadcrumb.php, but it seems that it cannot output the tag.
// Remove "Home" and add Fontawesome house icon (_wc_breadcrumb.scss) 'home' => '<span class="visually-hidden">' . _x('Home', 'breadcrumb', 'woocommerce') . '</span>', //'home' => ' ',

[crftwrk]

Yes, WooCommerce breadcrumb is different and Woo escapes the HTML. That's why the icon is solved the CSS way here. Think we should fix the default breadcrumb first and find a solution for Woo breadcrumb in a second step. Maybe ChatGDP has an idea.

[crftwrk]

I see that you have created main...stan1781:bootscore:main. Do you want to simply press the green "Create pull request" button? Then we have this fixed and can search for a solution for WC breadcrumb.

[crftwrk]

It seems that the WC breadcrumb is harder to handle than expected. I've added a note to v.6.1 to fix it there.

[crftwrk]

#821