Configuration Guide for Advanced Breadcrumbs Magento 2

Turns the module's server-side breadcrumbs on or off. When disabled, Magento falls back to its default JavaScript-rendered breadcrumbs. This is useful if you need to temporarily disable the module without uninstalling it.

When enabled, pages that aren't directly handled by the module (e.g. pages from custom or third-party modules) still get the module's template styling for their breadcrumbs. These are pages that add breadcrumbs the traditional Magento way via addCrumb(). Without this, those pages would render with Magento's default breadcrumb template, creating a visual inconsistency.

Enabled by default. Only visible when the module itself is enabled.

Displays the currently installed version of the module. Use the update check button to verify whether a newer release is available.

Controls whether "Home" appears as the first item in the breadcrumb trail. Most stores keep this enabled — it gives visitors a clear starting point and is standard UX practice for breadcrumbs.

Sets the text used for the home breadcrumb item. This field is only relevant when Show Home Crumb is set to Yes.

Because this setting is configurable per store view, you can translate it for multi-language stores — for example "Home" on your English store and "Start" or "Startpagina" on your Dutch store.

When enabled, the name of the current page appears as the last item in the breadcrumb trail (without a link, since you're already on that page). When disabled, the trail ends at the parent level — the current page is not shown.

The character displayed between breadcrumb items. Common choices include >, /, |, ›, and →. The field accepts up to 5 characters, so you can also use a short string or a spaced character like /.

When enabled, the module outputs a BreadcrumbList structured data block in JSON-LD format. This is the format search engines use to display breadcrumb trails as rich results in search engine result pages (SERPs).

Recommended: Keep this enabled. Structured data breadcrumbs can improve how your pages appear in Google Search and other search engines without any downside.

Controls whether the "Home" item is included in the structured data output, independent of whether it's shown visually.

Google's guidelines say the home page can be omitted from breadcrumb structured data, since it's implied. That said, some SEO practitioners prefer to include it for completeness and consistency with the visual breadcrumb. Either approach is acceptable — this comes down to your SEO team's preference.

Determines how the module picks a category when a product is assigned to more than one.

• Deepest Path — picks the category with the longest path, meaning the most specific one. For example, for a jacket assigned to both "Jackets" and "Clothing > Men > Outerwear > Jackets", this option would use the longer path. Best for stores with detailed category structures where you want search engines to see the full hierarchy.
• Shortest Path — picks the category with the fewest levels. Good for flat, simple navigation structures where shorter paths are preferred.
• Highest Weight — uses the weight values you've set on individual categories (see the Category Weight System section below). Only meaningful if you've actually assigned weights.
• First Assigned — uses whichever category Magento returns first. The result is unpredictable and depends on internal category ordering, so this is generally not recommended.

Recommended: Most stores should use "Deepest Path". It gives search engines the most context about your site structure and tends to produce the most useful breadcrumb trails. Switch to "Highest Weight" only if you need manual control over which category is shown for specific products.

When enabled, categories that are not configured as anchor categories are excluded from breadcrumb path selection.

In Magento, anchor categories display products from their child categories. Non-anchor categories only show products directly assigned to them. If your store uses anchor categories to define your main navigation, enabling this setting ensures breadcrumbs reflect only those categories — keeping paths clean and consistent with your site structure.

A multiselect that controls which page types display breadcrumbs. By default, breadcrumbs are enabled for Category Pages, Product Pages, and CMS Pages.

Additional options you can enable: Search Results, Shopping Cart, Checkout, Customer Account, Wishlist, Compare Products, Contact Page, and 404 Page.

Enable only the page types that make sense for your store. Adding breadcrumbs to Checkout, for example, may interfere with a focused checkout experience — but on Search Results or Customer Account pages they can be a useful navigation aid.

The breadcrumb label shown on search result pages. Defaults to "Search Results".

The label for the shopping cart page breadcrumb. Defaults to "Shopping Cart".

The label shown in the breadcrumb on checkout pages. Defaults to "Checkout".

Used as the parent breadcrumb for all customer account pages — so sub-pages like order history, address book, and account details all show this as their parent crumb. Defaults to "My Account".

The breadcrumb label for the wishlist page. Defaults to "My Wishlist".

The label for the product comparison page breadcrumb. Defaults to "Compare Products".

The breadcrumb label for the contact page. Defaults to "Contact Us".

The breadcrumb label shown on 404 (page not found) pages. Defaults to "Page Not Found".

When enabled, the module writes detailed information about breadcrumb generation to the log files in var/log/. This is useful when troubleshooting unexpected breadcrumb output — for example, when the wrong category is being selected or a breadcrumb isn't appearing on a specific page type.

Only enable debug mode while actively investigating an issue. It adds processing overhead and produces a lot of log output, so it should be turned off again once you're done.

An integer value that controls how much priority this category gets when the module is choosing which breadcrumb path to show for a product. The weight system is only used when the Selection Strategy is set to "Highest Weight".

• A positive value (e.g. 1, 10, 100) increases the likelihood of this category being chosen. Higher numbers take priority over lower ones.
• Zero (the default) means no explicit weight is set — the module falls back to the configured selection strategy.
• A negative value (e.g. -1) excludes this category from breadcrumb selection entirely for products assigned to it.

Weight is configurable per store view, so you can set different priorities per language or store.

A toggle to completely exclude this category from appearing in product breadcrumbs. This has the same effect as setting a negative weight, but is more explicit and easier to spot when reviewing category settings.

A dropdown showing all categories the product is assigned to, with their full paths. When you select a category here, the module uses that category for this product's breadcrumb trail — overriding the weight system and selection strategy entirely.

Use this for edge cases where the automatic selection keeps picking the wrong category for a specific product, and you need a reliable, manual fix without changing your site-wide strategy settings.