Advanced Breadcrumbs for Magento 2
Test out this module for Free
Advanced Breadcrumbs
Check your email
We've sent a confirmation link. Click it to spin up your demo.
Setting up your demo...
This usually takes a few minutes. You can close this modal or wait for the result — we'll also send you an email when it's ready.
You're in the queue
Position: #
All demo slots are currently in use. You'll receive an email as soon as your demo is ready.
Your demo is ready!
Expires:
Credentials have also been sent to your email.
Something went wrong
We couldn't set up your demo. Please try again or contact support.



Advanced Breadcrumbs for Magento 2
Server-Side Breadcrumbs with Matching Structured Data
Advanced Breadcrumbs renders the breadcrumb trail of your Magento 2 store on the server and adds a Schema.org BreadcrumbList in JSON-LD that follows the same path. It has its own template for Luma and for Hyvä.
For a product in several categories you decide which path is shown: the category the customer came from, a fixed category per product, a weight per category or a selection strategy.
Since version 1.2.0 a CMS page can have its own trail, for example Home > Service > Returns. Visitors and search engines then see the page under the section it belongs to.

Server-Side Rendering
The trail is part of the HTML that Magento returns, with one template for Luma and one for Hyvä.
JSON-LD That Matches the Trail
A Schema.org BreadcrumbList is built from the same crumbs the visitor sees.
One Path per Product
The navigation path, a product override, category weights and four strategies decide which category is shown.
Custom Trail per CMS Page
Enter the crumbs of a CMS page yourself, or hide the breadcrumbs on that page.
Eleven Page Types
Choose where breadcrumbs appear, from category pages to the cart and the 404 page, with your own labels.
Mobile Collapse on Hyvä
A trail with more than three crumbs folds behind a "…" button on small screens.
The Right Category Path on Product Pages
A product that sits in several categories has several possible trails. With "Respect Navigation Path" set to "Yes", which is the default, the product page shows the category the customer navigated from, provided the product is assigned to that category. A customer who came through Furniture > Chairs sees that path.
When there is no navigation path, for example after a search or a direct link, "Selection Strategy" picks the category: "Deepest Path (most specific)", "Shortest Path (least specific)", "Highest Weight" or "First Assigned (legacy behavior)". The default is "Deepest Path (most specific)", so the trail shows the most specific place in the catalog.
"Exclude Non-Anchor Categories" leaves out categories that are not set as anchor. These settings are available at default and website level.


A Fixed Category per Product and a Weight per Category
Where the strategy does not give the path you want, you overrule it. On the product, the field "Primary Breadcrumb Category" in the section "Search Engine Optimization" lists the active categories the product is assigned to, each with its full path. Choose one and the automatic selection uses that category for this product. If that category is later disabled or removed, the module falls back to weights and strategy.
On the category, "Breadcrumb Weight" sets the priority: the category with the highest weight wins, whichever strategy is selected. A weight of 0 follows the strategy. A negative weight takes the category out of the automatic selection, as does "Exclude from Breadcrumbs". That keeps a category such as Sale out of the automatic choice, so a product shows its place in the catalog.
The order is: product override, then weighted categories, then the strategy. By default the customer's navigation path comes before all of this. Set "Navigation Overrides Product Override" to "No" to let the fixed category of the product win.
BreadcrumbList Structured Data in JSON-LD
With "Enable JSON-LD" set to "Yes", the default, the module adds a BreadcrumbList in JSON-LD to every trail it builds. The list is made from the same crumbs as the visible trail, so you do not write or maintain schema markup in your theme.
Each ListItem has a position, a name and an item with the URL. The last item, the page itself, has no item, which Google does not require for the last item. A crumb in the middle without a link gets the URL of the current page.
"Include Home in JSON-LD" decides whether the Home crumb is part of the list. On Luma the HTML of the trail also carries Schema.org microdata; the Hyvä template outputs JSON-LD only. Both settings are available at default and website level.


A Custom Breadcrumb Trail per CMS Page
A CMS page normally gets one crumb: its title. Since version 1.2.0 the CMS page form has a section "Advanced Breadcrumbs" in which you turn on "Use Custom Breadcrumb Trail" and enter the trail yourself. Each row is a crumb with a "Label" and a "URL". "Add Crumb" adds a row and you drag rows into the right order.
A relative URL such as /customer-service is completed with the URL of the store. A URL that starts with http or https is used as it is. The last row is the page itself and never becomes a link, and rows without a label are skipped. With the rows Service and Returns the visitor sees Home > Service > Returns, and the JSON-LD contains the same items with absolute URLs.
"Hide Breadcrumbs" in the same section removes the trail and the JSON-LD from that page, also when a custom trail is filled in.
Home Icon, Label and Separator
Under "Display Settings" you set how the trail looks, per store view. "Show Home Crumb" adds Home as the first crumb and "Home Label" sets its text, so each language gets its own word. "Use Home Icon" replaces the word with an SVG house icon. The label stays in the link as aria-label, so screen readers still announce it.
"Separator Character" is the character between the crumbs, with a maximum of five characters. The default is ">". "Show Current Page" decides whether the product name closes the trail on a product page, without a link.
Every field has "Use system value" to go back to the default.


Short Trails on Mobile with Hyvä
A deep category path takes up several lines on a phone. On a Hyvä store view, a trail with more than three crumbs is shortened below the md breakpoint: the first and the last crumb stay visible and the crumbs in between sit behind a "…" button. One tap shows the full path. The button has the aria-label "Show full breadcrumb path".
On larger screens the full trail is always shown. The module checks per store view whether the theme is Hyvä and picks the matching template, so an installation with both Luma and Hyvä store views needs no extra configuration. The collapse is part of the Hyvä template; Luma shows the full trail.
Breadcrumbs on Eleven Page Types
"Enable Breadcrumbs On" lists the page types the module handles: "Category Pages", "Product Pages", "CMS Pages", "Search Results", "Shopping Cart", "Checkout", "Customer Account", "Wishlist", "Compare Products", "Contact Page" and "404 Page". After installation the first three are selected and you add the others yourself. "Customer Account" also covers the order, address and newsletter pages of the account.
Under "Custom Labels" you set the text of the crumb for search, cart, checkout, account, wishlist, compare, contact and 404 pages, per store view.
"Fallback for Other Pages" is on by default. Pages of other modules that add crumbs with Magento's addCrumb() method are then rendered with the template of this module, so the trail looks the same across the store.

New in Version 1.2.0
CMS pages can have their own trail: turn on "Use Custom Breadcrumb Trail" and enter rows with a "Label" and a "URL".
Rows are added with "Add Crumb" and put in order by dragging.
The custom trail is also in the JSON-LD, with relative URLs made absolute.
"Hide Breadcrumbs" and the custom trail sit in their own section "Advanced Breadcrumbs" on the CMS page form.
getCmsBreadcrumbs() returns the custom trail as well, so a headless storefront gets the same path.
Fixed: responses in the admin pop-ups are escaped and the log viewer works again.
Advanced Breadcrumbs for Magento 2: Technical Details for Developers and Store Owners
The Advantages for Developers
- The frontend replaces
Magento\Theme\Block\Html\Breadcrumbswith a preference. When the module is off or has no trail for a page, the block returns Magento's own output. No template overrides are needed in the theme. - Each page type has its own builder that implements
BuilderInterface. The builders are passed in through thebuildersargument inetc/di.xml, so you can swap the builder of a page type from your own module. BreadcrumbsProviderInterfacereturns the trail for any product, category or CMS page withgetProductBreadcrumbs(),getCategoryBreadcrumbs()andgetCmsBreadcrumbs().getJsonLdFor()turns a trail into JSON-LD.- GraphQL for headless storefronts is available in the separate module
magmodules/magento2-advanced-breadcrumbs-graphql, which returns the same path as the store. CategoryLoaderkeeps loaded categories in memory per instance, so a category in the path is not fetched from the repository twice.- The Hyvä template is selected through Hyvä's
CurrentThemeservice and the module registers its templates for the Tailwind build onhyva_config_generate_before. - "Debug Mode" writes debug records to
debug.log. Errors are always written toerror.log. - Requires PHP 8.1 or higher and Magento 2.4.x.
Good to Know for Store Owners
- After installation the module is off. Turn on "Enable Module" under "Stores" > "Configuration" > "Magmodules" > "Advanced Breadcrumbs".
- Once enabled, breadcrumbs are active on category, product and CMS pages and JSON-LD is on. The other eight page types are yours to add.
- Display settings and labels are set per store view. Structured data, category selection and the selection of page types are set per website.
- The category weight, the exclusion of a category and the primary category of a product are set per store view.
- The module works on Luma and Hyvä, also when one installation has both. The mobile collapse is available on Hyvä.
- Every setting in the configuration goes back to its default with "Use system value".
A Clear Path on Every Page
Advanced Breadcrumbs gives products, categories and CMS pages a trail that visitors and search engines read the same way, on Luma and Hyvä.
Magmodules builds and maintains the extension, with support for every merchant who runs it.
Knowledgebase
All familiar Help articles
A list of the most frequently asked questions from the Advanced Breadcrumbs extension for Magento 2. We've tried our best to help you with the installation, configuration and troubleshooting. If you do not find the answer you were looking for, you can always send us a message through this form.
Installation articles
Installation using Composer (recommended) Installation using the Adobe Marketplace Install through FTP and SSHConfiguration
Configuration GuideChangelog 1.2.0 is released on 9 November 2026
Our plugins are regularly updated to ensure compatibility with the latest Magento release.
-
Features:
- Custom breadcrumb trail per CMS page: an Advanced Breadcrumbs section on the page form holds Hide Breadcrumbs, a Use Custom Breadcrumb Trail switch and a list of crumbs, each with a label and an optional URL. The trail replaces the single title crumb the page would otherwise show, which is the way to place a page under a section such as Service, because CMS pages have no hierarchy of their own. It feeds the JSON-LD as well, with absolute URLs, and the last crumb is the page itself and carries no link. Improvements:
- Breadcrumbs can be asked for a category or a CMS page that is not the current request, and structured data can be rendered for any trail. The GraphQL companion module uses this from 1.1.0 so a headless storefront answers with the trail the shop renders, rather than rebuilding it and drifting.
- The test suite and the static gates of the module standards: PHPUnit with the architecture set, the baseline end-to-end layer that sets every configuration field through the admin form and reads it back, PHPStan at level 8 without a baseline, and the codesniffer at the standard's own severity.
- Two settings scoped to website and store, Enabled and Debug Mode, can be restored to their default again. Bugfixes:
- The admin modals wrote the response of the self-test, the log viewers and the version check into the page without escaping it; the changelog modal now also allows only the tags its own format uses, without attributes.
- The admin log viewer dropped the first character of a short log and cut a long one a line short; it reads the tail through Magento's file driver now.
- A breadcrumb label, title or link of a category without a name no longer reaches the template as null, and a stored configuration value that is not the shape the module expects is refused instead of being used. Compatibility:
- Magento 2.4.x and up
- PHP 8.1 and up
-
Features:
- Home icon option: replace "Home" text with SVG house icon (Heroicons outline)
- Hide breadcrumbs per CMS page: toggle in CMS page SEO fieldset via `hide_breadcrumbs` column
- Mobile truncation (Hyvä): middle breadcrumb items collapse with expand button on mobile when >3 crumbs Bugfixes:
- JSON-LD: removed `item` property from last breadcrumb `ListItem` per Google structured data guidelines Improvements:
- Refactored monolithic `BreadcrumbsProvider` into dedicated page-type builder services (`BuilderInterface`)
- Instance-level category caching via `CategoryLoader` service to prevent duplicate `CategoryRepository::get()` calls
- All admin config groups (except Debug) now expanded by default per module standards
- GraphQL support moved to separate companion module (`magmodules/magento2-advanced-breadcrumbs-graphql`) Minimum requirements:
- Magento 2.4.x
- PHP 8.1
100% Unencrypted Code quality guaranteed.
Quality
Approved, Compatible and Tested

Adobe Commerce Marketplace Approved
This extension is listed on the official Adobe Commerce Marketplace and has passed their review process for code quality, performance and security.
Adobe Marketplace approval means the extension follows Magento coding standards and integrates properly with the platform. Updates go through the same review process.

Magento Cloud Support
This extension is fully compatible with Adobe Commerce Cloud (Magento Cloud). It works with the read-only filesystem, the build and deploy pipeline and cloud-specific caching layers.
No additional configuration or workarounds are needed for cloud environments. The extension handles static content deployment and config management the same way as on-premise installations.

Private Composer Repo
After purchase you get access to a private Composer repository with personal credentials. Install and update the extension with a single composer command, just like any other dependency.
Your Composer credentials are available in your account dashboard. Updates are published to the repository as soon as a new version is released, so you always have access to the latest version.
Playwright E2E Tests (68)
This extension is covered by 68 end-to-end tests using Playwright. These tests run automatically on every code change through our CI/CD pipeline.
The tests simulate real user interactions across checkout flows, configuration changes and edge cases to make sure everything works before every release.