Wrong breadcrumb order Yoast 16

Hello,

Thanks for reaching out.

A breadcrumb is a small text path, often located at the top of a page indicating where the user is on the site. On yoast.com, for instance, the path to our Yoast SEO plugin page is Home > WordPress Plugins > Yoast SEO for WordPress. What you have shared in the screenshot is your page hierarchy in the page overview.

We checked the page, https://www.resmed.pt/profissionais-de-saude/apneia-do-sono/opcoes-de-tratamento-para-aos/ and there is no visible text path as described. It will be helpful if you can send us screenshots of the wrong breadcrumb path as it appears on the front end of the page.

Hi Maybellyne and thank you for your quick reply.

Our breadcrumb is located at the bottom of the page, here is a screenshot: https://paste.pics/CFWY9

Thanks!

Thanks for sharing the screenshot and we can see the breadcrumbs at the bottom of the page!

To resolve the breadcrumb path issue, we recommend you please reset the Indexables tables and migrations:
1. Install and activate the Yoast Test Helper plugin;
2. Go to Tools → Yoast Test → Yoast SEO → Reset Indexables tables & migrations options to reset it;
3. Run the SEO data optimization from the SEO → Tools page.

Does this resolve the issue?

Thanks Maybellyne.
I’ve done exactly what you said but the issue is still here…

Do you have other solutions?

Thank you ??

We are sorry to hear that the issue still persists after performing the above suggestions. Due to the nature of the issue, we’ll need to take a look at your setup. However, we are unable to do it here as this is a public forum.

So, if you have an active Yoast SEO Premium subscription or if you can consider buying one, we can investigate the issue further directly on your setup privately through email.

However, if you don’t wish to get the Yoast SEO Premium subscription, that’s completely fine. In this case, you’ll need to troubleshoot the issue further on your setup as we are literally out of any clue at this moment without taking a look at the setup. So, someone from the community might step forward as well who has experienced or familiar with the issue.

Thanks for your understanding!

The issue was coming from our code.

Thanks for your help!