Blog breadcrumbs display “false” instead of “blog”

Hi,

Thanks for that information! We think the issue is specific to your site. We would be happy to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium?and receive our Premium email support and we can help you further.

Alternatively, we will keep this thread open for one week in case someone else from the community or a developer watching these forums can chime in. After which we will close in order to keep the overview.

In <script type=”application/ld+json” class=”yoast-schema-graph”> there is a problem : “,”url”:”https://…&#8221;,”name”:”false”}”. So in the json, blog page name is “false”. Where an I change that ?

ok I solved the problem. In the blog page, go to “Yoast SEO/advanced settings/title for breadcrumbs”. I don’t know why, but “false” was written there. I don’t understand why this word was written by itself here. I would like to have an explanation to understand.

Hi @matwp,

Thanks for getting back to us. Can you send us a link to a screenshot that shows the settings for posts under SEO > Search Appearance > Breadcrumbs?

For example, is the option for “Enable Breadcrumbs for your theme” set to “Enabled”?

https://zupimages.net/up/21/09/v21h.png

Hi @matwp,

Thanks for your patience. It’s very strange to hear that the breadcrumbs are working on other pages and not your blog posts. If you didn’t find any conflicts or errors, we think the issue is something specific to your site.

We would need to investigate further by looking at your specific site but we’re not able to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.`

If you’re able to find the source of the conflict or if you can give us the steps to reproduce this problem on a test site, we ask you to create a new bug report for our developers. You’ll need a GitHub account to create a new issue.

If this is your first bug report, please check out:?How to write a good bug report.

We’re sorry that we haven’t found a solution, but we’re happy to investigate further.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.