Hi,
the theme uses H1 as tag for the breadcrumbs. Google sees this and penalizes the page for it when the page content also contains a H1 title.
Can you please remove the H1 tag for all breadcrumbs? It doesn’t make sense anyway!
This topic has 16 replies, 4 voices, and was last updated 4 years, 1 months ago ago by Bas Kling
Hi,
the theme uses H1 as tag for the breadcrumbs. Google sees this and penalizes the page for it when the page content also contains a H1 title.
Can you please remove the H1 tag for all breadcrumbs? It doesn’t make sense anyway!
Great idea.
Not sure if staff can do anything here as I believe that’s more for the developer team.
I can see you have suggested the idea there already.
Hello,
Please check this topic – https://www.8theme.com/topic/remove-h1-from-breadcrumbs-and-add-it-to-pages/
Regards
Hi Rose,
I’ve read that post. Basically, what you’re saying is, there’s no fix.
Is 8theme planning to change the template in the (near) future on this part?
To be honest: anyone looking to tailor and manage their SEO ranking will be knocked off by this template’s limitation. Contrary to how you put it in the other post, it actually is NOT best practice for SEO purposes. It poses a major ranking threat! I’m kind of surprised by this because, up until now I find the entire template to be very professional and well thought out.
I can copy the breadcrumbs file to a templates folder inside my child theme, but then, I would probably run into problems when xstore decides to update the breadcrumbs file in the main theme. I’d rather see you guys changing it for everybody
Hello,
We change the mentioned file very rarely, so don’t think that you will face any issues with this after the future updates. Anyway, if you have a proposition to allow users to choose the tag for the page title in the breadcrumbs post it here https://www.8theme.com/taskboard/
If it takes votes from other users we’ll be able to implement it in one of the next updates.
Regards
Regards
Hi Olga,
I’ve edited the breadcrumbs file, replacing H1 with H4 (leaving the titles class), but to no effect, unfortunately. I’ve both edited the xstore/templates/breadcrumbs.php as the xstore-child/templates/breadcrumbs.php
Can you provide a step-by-step approach to fixing the issue? Is it a caching issue or do I need to change anything else?
Hello,
Could you, please, provide us with link to your site and FTP access? We’ll check and help you.
Regards
That’s great but I do agree with Bas.
A long-term solution for all users would be great! Because of this, I’ve upvoted Bas’s post in the feature request area.
Hello, @MichaelB
Thank you. Our developers took it into account. But to help the customer at this moment we asked the FTP access.
Regards
Hi,
I noticed the fix in the last update, thanks for this.
Unfortunately, the breadcrumb tag fix only applies to single pages. Breadcrumbs in category pages still use the H1 tag; this isn’t changed.
Since the bulk of our website revolves around eCommerce (and subsequently our category pages), our problem is still not solved. And as said: SEO wise this is very bad practice.
Can you please make sure that the breadcrumbs settings covers ALL breadcrumb artifacts, on ALL pages?
Hello,
I have tested the product category title on the test installation and don’t see the problem https://prnt.sc/wdlyrl
Provide us with WP Dashboard and FTP access to your site where you still have the problem.
Regards
Private
Hello,
Problem was caused by xstore-child/woocommerce/global/breadcrumb.php file of your child theme. I have renamed that and the option works fine.
Regards
Thanks!
Is there anything related to breadcrumbs functionality I need to check or consider after you renaming/deleting it?
Hello,
It depends on why you copied that file to your child theme and the changes you did there.
If you made any other special changes then copy up to date file from parent theme to child theme and add your changes. If you copied that file just in case then skip it and do nothing.
Regards
Thanks
The issue related to '‘Breadcrumbs in H1’' has been successfully resolved, and the topic is now closed for further responses