Title: Breadcrumbs &#8211; Root Name
Last modified: February 8, 2017

---

# Breadcrumbs – Root Name

 *  Resolved [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/)
 * Hi there,
 * at the moment, for the **breadcrumbs**, the plugin retrieve the wordpress blogname
   as “name” of the first entity in the JSON-LD code.
    I was wondering if there 
   is any filter to change the “blogname” into “home”.
 * Thanks in advance for the response.
 * Cheers

Viewing 13 replies - 1 through 13 (of 13 total)

 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8783418)
 * Hi [@mr_pa](https://wordpress.org/support/users/mr_pa/),
 * If you manually fill in the homepage title option(s), then that title will be
   used.
    <[The code](https://github.com/sybrew/the-seo-framework/blob/31a63fdc03c7c1fe7caf6a67fe8a206d1c82c16c/inc/classes/generate-ldjson.class.php#L669-L681)
   >
 * Please note that the output of the scripts are bound to an one-week cache, so
   you’d either have to disable the cache, or wait patiently. But Google doesn’t
   crawl pages _that_ often anyway 🙂
 * If you’d wish to use “Home” as the title — it exactly being: “Home” — then I’m
   afraid you can’t do so, and this is also highly discouraged. Read my stance on
   this issue [here](https://github.com/sybrew/the-seo-framework/issues/65#issuecomment-277526839).
 * Schema.org requires each entry to be exactly as-is, changing the output might(
   and probably will) yield a data conflict due to inconsistency (i.e. a sign for
   spamdexing). Also, the home page may even be omitted from the breadcrumb-list,
   even more so: it’s currently not even shown in the SERP pages.
 * In any case, the visitors don’t see the output publicly, anywhere. _Except in
   the code_.
 * I hope this clears things up! Cheers 🙂
    -  This reply was modified 9 years, 4 months ago by [Sybre Waaijer](https://wordpress.org/support/users/cybr/).
 *  Thread Starter [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8784683)
 * Hi Sybre,
 * in my opinion the current set up of the JSON-LD “name” parameter in incorrect.
 * As you can see in the Google reference [https://developers.google.com/search/docs/data-types/breadcrumbs](https://developers.google.com/search/docs/data-types/breadcrumbs)
   the “name” parameter retrieve the label field.
 * In wordpress, this should accomplished filling the field “name” of the JSON-LD
   markup with the wordpress title of post/page/cpt and not with the title tag field
   filled up through your plugin.
 * What do you think?
 * Thanks,
    Paolo
    -  This reply was modified 9 years, 4 months ago by [mr_pa](https://wordpress.org/support/users/mr_pa/).
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8792264)
 * Hi Paolo,
 * I’m not quite sure what’s going wrong here.
 * Google clearly states:
 * > **name:** Text, required
   >  The title of the breadcrumb displayed for the user[
   > within the SERP].
 * The SEO title _is_ the title when filled in, not the other way around per your
   suggestion.
    The SEO Framework is a layer on top of WordPress, which enhances
   SEO. Evidently, when data is supplied for The SEO Framework, it should be used
   everywhere. The data should be for the (potential) user/visitor. Let me explain
   in the following paragraphs…
 * Please see [this code](https://github.com/sybrew/the-seo-framework/blob/5ffda769c76bd51e5d7dc0c0e9d7865d1c2eeb70/inc/classes/generate-ldjson.class.php#L522-L523)(
   excuse my nested ternary), which does exactly as described.
 * `$data['doctitle']` is the Term SEO title, which has priority over:
    `$cat->name`,
   which is the default WP Term title.
 * In any case, the SEO title is used because it’s actually displayed in the `<title
   >` output, hence also for the user.
    Changing any of this behavior will lead 
   into misnomers, data-conflict and cavernous suggestions, apart from what’s displayed.
 * For example, the title tag consists of a title _and_ the website’s name. Given
   all the data, especially with [Schema.org Articles](https://github.com/sybrew/the-seo-framework/issues/21)
   coming soon, there surely will be conflict if doing things wrongfully.
 * Essentially, this is what I try to maintain: a stable SEO environment, where 
   perfection is key. This can’t be achieved when mixing data.
 * You’re generating **Knowledge** for Google and the user with The SEO Framework,
   so using different tags everywhere is misleading and might result in catastrophe;
   surely, this isn’t the case as of now, but chances might have it that Google 
   will accumulate all website data to test results’ output and then you suddenly
   have a massive **Penguin** to feed and keep happy once more.
 * Creating massive titles just to have and generate long-tail keywords have been
   a nice and proven concept, but it should always be **users first**. Google knows
   this, and continuously strives to improve the latter.
    Applying this concept 
   to categories is in any notion quite weird, because they aren’t prominently shown
   in Search Results — ever, from my experience.
 * This plugin does not condone or even think about anything but white-hat SEO techniques,
   and it costs extreme amounts of time just to support anything but (implying black/
   grey-hat maintenance). If you wish to go grey-hat or even black-hat: please use
   a plugin that allows you to, or feel free to fork mine.
 * **With all that, it’s still an open door:**
    As always, I’m open to suggestions.
   So feel free to open a new [GitHub Issue](https://github.com/sybrew/the-seo-framework/issues)
   to let your voice heard, you might not be alone in this matter and I’ll happily
   consider it when there’s enough demand. As such I’ve also added the option for
   removing the website name from the title, which actually is a very bad practice.
 * It’s a lot to process, but I hope this clears things up on how I proceed with
   and tackle SEO in TSF; at least given this scenario.
 * Cheers!
 *  Thread Starter [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8795651)
 * Hi Sybre,
    thanks for the prompt explanation.
 * I agree with you when you talk about “home” schema field that must be the same
   of blog name. So forget my previous request.
    I am a seasoned SEO consultant 
   and usually when i suggest any implementation about breadcrumbs this is my suggestion:
   _Domain Name > Label (1 level) > Level (2 level) > and so on…_
 * At the moment the SEO Famework plugin makes this (as you now):
    _Title Tag Home
   > Title Tag (1 level) > Title Tag (2 level)_
 * In my opinion this last set up doesn’t send a correct semantic signal to the 
   search engine.
 * have a look of the following plugin on how it builds breadcrumbs JSON-LD markup:
 * [https://wordpress.org/plugins/wp-structuring-markup/](https://wordpress.org/plugins/wp-structuring-markup/)
 * I consider your plugin light and far better that others here in the wordpress
   repository and it’s a shame not fix this bug.
 * Let me know if you need more clarifications.
    Best, Paolo
    -  This reply was modified 9 years, 4 months ago by [mr_pa](https://wordpress.org/support/users/mr_pa/).
    -  This reply was modified 9 years, 4 months ago by [mr_pa](https://wordpress.org/support/users/mr_pa/).
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8796211)
 * Hi [@mr_pa](https://wordpress.org/support/users/mr_pa/),
 * I’m now confused, we’re jumping from root crumb, to category crumb, and now to
   the current page crumb.
 * So, in order:
    [Root (homepage) Crumb title](https://github.com/sybrew/the-seo-framework/blob/31a63fdc03c7c1fe7caf6a67fe8a206d1c82c16c/inc/classes/generate-ldjson.class.php#L669-L679)
   [Cat Crumb title (single)](https://github.com/sybrew/the-seo-framework/blob/31a63fdc03c7c1fe7caf6a67fe8a206d1c82c16c/inc/classes/generate-ldjson.class.php#L566)/
   [Cat Crumb title (plural)](https://github.com/sybrew/the-seo-framework/blob/31a63fdc03c7c1fe7caf6a67fe8a206d1c82c16c/inc/classes/generate-ldjson.class.php#L522)
   [Current Page crumb title](https://github.com/sybrew/the-seo-framework/blob/31a63fdc03c7c1fe7caf6a67fe8a206d1c82c16c/inc/classes/generate-ldjson.class.php#L740)
 * Each takes the Custom SEO Title first, and then the WordPress title as fallback.
   
   All exclude the title additions, like the separator and blogname/tagline.
 * I wish to know: What is the current output, and what output do you wish to have?
 * **For example (a live example works best):**
 * What I have now:
    `The SEO Framework > Docs > API > Filters`
 * What I want:
    `The SEO Framework > Docs > API > Something else`
 * Thanks!
 *  Thread Starter [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8796291)
 * Hi there,
 * what i like to have is always **WordPress title** because the Custom SEO Title
   trough the plugin is always different (for SEO purpose).
 * `The SEO Framework > WordPress Title > WordPress Title 2 > and so on...`
 * I hope to have clarified a bit better what i need to achieve.
 * Thanks a lot for the support.
    Paolo
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8798025)
 * Hi [@mr_pa](https://wordpress.org/support/users/mr_pa/),
 * Perfectly clear!
    I’m going to add a true/false filter for that in the upcoming
   version! I’ll keep you updated here on the progression.
 * But please be aware of my statement made earlier:
 * > In any case, the SEO title is used because it’s actually displayed in the `
   > <title>` output, hence also for the user.
   >  Changing any of this behavior will
   > lead into misnomers, data-conflict and cavernous suggestions, apart from what’s
   > displayed.
 * Cheers 🙂
 *  Thread Starter [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8834439)
 * Hi Sybre,
    it sounds great!
 * Do you have any ETA for the next plugin update?
 * Thanks for your great support!
    Best, Paolo
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8836027)
 * Hi Paolo,
 * History has shown that I release a major update every 3 to 6 months.
 * The new filters are going to be released in the early dev-version, and I’ll ping
   you here on that 🙂
    It requires a new method so I’m a bit hesitant on its implementation,
   because it might add unwanted technical debt.
 * Cheers!
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8860419)
 * Hi [@mr_pa](https://wordpress.org/support/users/mr_pa/),
 * The filter has been put in place:
 *     ```
       add_filter( 'the_seo_framework_use_breadcrumb_seo_title', '__return_false' );
       ```
   
 * Please note that the JSON scripts are cached through transients, the output can
   be tested whilst disabling them in the General SEO settings.
 * Commit: [ede6a8a](https://github.com/sybrew/the-seo-framework/commit/ede6a8aa29e54ed0a651bb7999422a1d16e99306)
 * Until that commit only bugfixes and performance enhancements have been applied,
   so it’s pretty much identical to 2.8.2, feel free to use it on your sites.
 * Enjoy!
 *  Thread Starter [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8861153)
 * Hi Sybre,
 * thanks to alert me!
    Just a stupid question: where could i find the latest dev
   versione of the plugin?
 * At the moment i copied the changed files form Github.
 * IS it the right way?
 * Thanks again,
    Paolo
 *  Thread Starter [mr_pa](https://wordpress.org/support/users/mr_pa/)
 * (@mr_pa)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8861180)
 * Hi Sybre,
 * the filter works like a charm in a standard blog post but i am not able to activate
   it in a custom post type.
 * Is there any othere filter the i need to copy in the functions.php file in order
   to enable it?
 * Thanks,
    Paolo
    -  This reply was modified 9 years, 3 months ago by [mr_pa](https://wordpress.org/support/users/mr_pa/).
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8861602)
 * Hi [@mr_pa](https://wordpress.org/support/users/mr_pa/),
 * That’s the correct way 🙂
    There’s also a download link further down below the
   GitHub plugin front-page that links to the master version: [https://github.com/sybrew/the-seo-framework](https://github.com/sybrew/the-seo-framework)
 * The filter doesn’t care for the post type, so the issue you’re facing is quite
   peculiar.
 * Do the custom post types have their own theme template files?
    If so, try adding
   the filter in there too and see if that works.
 * Cheers!

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Breadcrumbs – Root Name’ is closed to new replies.

 * ![](https://ps.w.org/autodescription/assets/icon.svg?rev=3000376)
 * [The SEO Framework – Fast, Automated, Effortless.](https://wordpress.org/plugins/autodescription/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autodescription/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autodescription/)
 * [Active Topics](https://wordpress.org/support/plugin/autodescription/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autodescription/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autodescription/reviews/)

 * 13 replies
 * 2 participants
 * Last reply from: [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/breadcrumbs-root-name/#post-8861602)
 * Status: resolved