• Installation
• Usage
• Gotchas
  • Give these a quick read to see common issues you might face while using this plugin!

This plugin should work fine on Gatsby v2, v3, and v4.

yarn add gatsby-plugin-breadcrumb

or

npm install gatsby-plugin-breadcrumb

There are two ways to use gatsby-plugin-breadcrumb to add breadcrumbs to your Gatsby site: Click Tracking and AutoGen.

Click tracking creates a breadcrumb of out of the path taken (clicked) by the user. The two ways to use click tracking are:

• Using the <Breadcrumb /> component:

  • Add the plugin gatsby-plugin-breadcrumb to your gatsby-config.js

  • Import and use the <Breadcrumb /> component, passing the required props, on pages you wish to see the breadcrumb.

    • Click Tracking example
    • Breadcrumb props
    • Breadcrumb with Layout component
    • Breadcrumb with default crumb
    • Styling the Breadcrumb

• Using the useBreadcrumb hook: The useBreadcrumb hook enables you to control your own breadcrumbs, by calling useBreadcrumb and passing the required object properties. Using the hook enables you to pass the breadcrumbs to your own custom Breadcrumb component, but still take advantage of gatsby-plugin-breadcrumbs click tracking logic.

  • Add the plugin gatsby-plugin-breadcrumb to your gatsby-config.js

  • Import and use the useBreadcrumb hook, passing the required object properties.

    • useBreadcrumb example
    • useBreadcrumb props/returns

AutoGen (Auto Generated) will generate breadcrumbs for each page and inject them into Gatsby page pageContext prop under the breadcrumb property.

• Add the plugin gatsby-plugin-breadcrumb to your gatsby-config.js and define the useAutoGen plugin option to true

• Get crumbs array from breadcrumb object in pageContext

• Import and use the <Breadcrumb /> component, passing the required props on pages you wish to see the breadcrumb

  • AutoGen example
  • Breadcrumb props
  • Styling the Breadcrumb

Use of the <Breadcrumb /> component is not a requirement. If you want to create your own breadcrumb component, and pass it the breadcrumb data from pageContext, this is always an option.

CodeSandbox.io Demo

gatsby-config.js

{
  // optional: if you are using path prefix, see plugin option below
  pathPrefix: '/blog',
  plugins: [
    {
      resolve: `gatsby-plugin-breadcrumb`,
      options: {
        // defaultCrumb: optional To create a default crumb
        // see Click Tracking default crumb example below
        defaultCrumb: {
          location: {
            pathname: "/",
          },
          crumbLabel: "HomeCustom",
          crumbSeparator: " / ",
        },
        // usePathPrefix: optional, if you are using pathPrefix above
        usePathPrefix: '/blog',
      }
    }
  ],
}

/pages/aboutus.js

import React from 'react'
import { Breadcrumb } from 'gatsby-plugin-breadcrumb'

export const AboutUs = ({ location }) => {
  ...
  return(
    <div>
      <Breadcrumb location={location} crumbLabel="About Us" />
      ...
    </div>
  )
}

The <Breadcrumb /> component provides default breadcrumbs, while also allowing you to customize those breadcrumbs if you wish.

Instead of adding the <Breadcrumb /> component to every page, another option would be to add it to a layout component.

CodeSandbox.io Demo

/pages/aboutus.js

import React from 'react'
import Layout from './layout'
...

export const AboutUs = ({ location }) => {
  return (
    <Layout location={location} crumbLabel="About Us" >
      ...
    </Layout>
  }
}

/pages/contact.js

import React from 'react'
import Layout from './layout'

export const Contact = ({location}) => {
  return (
    <Layout location={location} crumbLabel="Contact" >
    ...
    </Layout>
  }
}

/components/layout.js

import React from 'react'
import { Breadcrumb } from 'gatsby-plugin-breadcrumb'

export const Layout = ({location, crumbLabel}) => {
  return (
    <div>
      <Header>
        <main>
          <Breadcrumb location={location} crumbLabel={crumbLabel} />
          ...
        </main>
      </Header>
    </div>
  }
}

While using the Click Tracking option with the <Breadcrumb /> component, if a user goes directly to a page, your breadcrumb will start with that page. You may want to always provide a default or "Home" breadcrumb. You can do this by adding a defaultCrumb plugin option. We must structure the defaultCrumb breadcrumb we provide in a way our context is expecting, see below for an example using all available options.

  {
    resolve: `gatsby-plugin-breadcrumb`,
    options: {
      defaultCrumb: {
        // location: required and must include the pathname property
        location: {
          pathname: "/",
        },
        // crumbLabel: required label for the default crumb
        crumbLabel: "Home",
        // all other properties optional
        crumbSeparator: " / ",
      },
    },
  },

To use the default styles please import the gatsby-plugin-breadcrumb.css file into your gatsby-browser.js file.

gatsby-browser.js

import 'gatsby-plugin-breadcrumb/gatsby-plugin-breadcrumb.css'

If you would rather style your own breadcrumb, here is a list of the classes used with the <Breadcrumb /> component:

gatsby-config.js

{
  plugins: [
    `gatsby-plugin-breadcrumb`,
  ],
}

/pages/about-us.js

import React from 'react'
import MyCustomBreadcrumb from './my-custom-breadcrumb'
import { useBreadcrumb } from 'gatsby-plugin-breadcrumb'

export const AboutUs = ({ location }) => {
  const { crumbs } = useBreadcrumb({
    location,
    crumbLabel: 'About Us',
    crumbSeparator: ' / ',
  })
  return (
    <div>
      <MyCustomBreadcrumb crumbs={crumbs} />
      ...
    </div>
  )
}

The useBreadcrumb hook takes an object with the following properties:

useBreadcrumb returns the following:

The useBreadcrumb hook will determine if it needs to add, remove, or do nothing with the breadcrumbs based on the location you pass. You only need to pass it the required props (location, crumbLabel).

Codesandbox.io Demo

AutoGen (Auto Generated, previously Sitemap) used to rely on gatsby-plugin-sitemap, which creates a sitmap XML file in the /public folder of your site at the end of the site build. This caused problems when deploying to services like Netlify, as the XML file was not created when we needed to try to read from it, causing the build to fail. Now AutoGen generates the breadcrumbs as pages are created. We also no longer require the gatsby-plugin-remove-trailing-slashes plugin.

Add the following to your gatsby-config

gatsby-config.js

{
  // optional: if you are using path prefix, see plugin option below
  pathPrefix: '/blog',
  siteMetadata: {
    // siteUrl: required (Gotcha: do not include a trailing slash at the end)
    siteUrl: "http://localhost:8000",
  },
  plugins: [
    {
      resolve: `gatsby-plugin-breadcrumb`,
      options: {
        // useAutoGen: required 'true' to use autogen
        useAutoGen: true,
        // autoGenHomeLabel: optional 'Home' is default
        autoGenHomeLabel: `Root`,
        // exclude: optional, include this array to exclude paths you don't want to
        // generate breadcrumbs for (see below for details).
        exclude: [
          `**/dev-404-page/**`,
          `**/404/**`,
          `**/404.html`,
          `**/offline-plugin-app-shell-fallback/**`
        ],
        // isMatchOptions: optional, include this object to configure the wildcard-match library.
        excludeOptions: {
          separator: '.'
        },
        // crumbLabelUpdates: optional, update specific crumbLabels in the path
        crumbLabelUpdates: [
          {
            pathname: '/book',
            crumbLabel: 'Books'
          }
        ],
        // trailingSlashes: optional, will add trailing slashes to the end
        // of crumb pathnames. default is false
        trailingSlashes: true,
        // usePathPrefix: optional, if you are using pathPrefix above
        usePathPrefix: '/blog',
     },
  ]
}

• As of v11 the exclude array option in the config of this plugin uses wildcard-match library. You can write wildcard strings to exclude paths you don't want to create breadcrumbs for. Please review the wildcard-match library for further details on how to write new exclude strings.

  To upgrade to v11 and keep similar behavior to your old excluded paths simply add ** to the start and end of your exclude strings

  example:

  // old
  exclude: [ '/books/', '/chapters/' ]
  
  // new
  exclude: [ '**/books/**', '**/chapters/**' ]
  

• The excludeOptions object option is used to pass options to configure the wildcard-match library. Please see the wildcard-match library for more details. Omitting this option will use the default options.

/pages/about-us.js

import React from 'react'
import { Breadcrumb } from 'gatsby-plugin-breadcrumb'

export const AboutUs = ({ pageContext, location }) => {
  const {
    breadcrumb: { crumbs },
  } = pageContext

  // Example of dynamically using location prop as a crumbLabel
  // NOTE: this code will not work for every use case, and is only an example
  const customCrumbLabel = location.pathname.toLowerCase().replace('-', ' ')

  return (
    <div>
      <Header>
        <main>
          <Breadcrumb
            crumbs={crumbs}
            crumbSeparator=" - "
            crumbLabel={customCrumbLabel}
          />
          ...
        </main>
      </Header>
    </div>
  )
}

For an example on using disableLinks/hiddenCrumbs see https://github.com/sbardian/books

To use the default styles please import the gatsby-plugin-breadcrumb.css file into your gatsby-browser.js file.

gatsby-browser.js

import 'gatsby-plugin-breadcrumb/gatsby-plugin-breadcrumb.css'

If you would rather style your own breadcrumb, here is a list of the classes used with the <Breadcrumb /> component:

Here are a few gotchas. If you notice any more you think should be mentioned here submit a PR or create an issue.

• In your gatsby-config.js option siteMetaData.siteUrl be sure to remove any trailing slashes

• The Gatsby <Link />'s throughout your site need to have to properties that match your breadcrumb to properties for the breadcrumb__link__active class to be applied. The URLs in your site also need to match the to properties of the breadcrumb for active classes to take effect.

  • Your sites URLs might have trailing slashes, and the breadcrumb to URLs might not. One option is to use the gatsby-plugin-remove-trailing-slashes plugin to ensure your URLs match and the breadcrumb__link__active class is applied.

  • You can also pass the <Breadcrumb> component the Reach Routers getProps prop a function to fine tune when the active class is applied.

    Reach Router getprops example

    /pages/about-us.js

    import React from 'react'
    import { Breadcrumb } from 'gatsby-plugin-breadcrumb'
    
    export const AboutUs = ({ pageContext }) => {
      const {
        breadcrumb: { crumbs },
      } = pageContext
    
      const isPartiallyActive = ({ isPartiallyCurrent, isCurrent }) => {
        return isPartiallyCurrent && isCurrent
          ? { className: 'breadcrumb__link breadcrumb__link__active' }
          : {}
      }
    
      return (
        <div>
          <Header>
            <main>
              <Breadcrumb
                crumbs={crumbs}
                crumbSeparator=" - "
                crumbLabel="About Us"
                getProps={isPartiallyActive}
              />
              ...
            </main>
          </Header>
        </div>
      )
    }