Smart Breadcrumbs

No. When the final page or its headers say noindex, or a page is marked schema-ineligible, it emits no breadcrumb schema and removes its own and recognised native breadcrumb data, while preserving unknown third-party data. You still get the on-page trail for visitors.

There are dedicated trails for products, categories, CMS pages, manufacturers, suppliers and search. When the matching mypresta.rocks modules are installed it also covers your blog, FAQ, knowledge base and documentation, and it connects account and checkout pages that themes usually leave without a trail. You choose which page types are active from the settings screen.

That is exactly what it prevents. On eligible pages it keeps one breadcrumb list, reusing an existing one if it already matches what visitors see, otherwise emitting its own, and safely removes the parseable duplicates from your theme or other modules while leaving Product and Organization data intact. Anything it cannot safely read is preserved untouched, so it never damages unknown data.

The module officially targets PrestaShop 1.6 through 9.x, and it is built to run on PHP 7.1 and up. It also carries legacy code paths for 1.6, if you are on 1.6 or an unusual setup, order it and we will make sure your install works.

For chosen product pages you can author the exact ancestor path, for example to place a campaign or landing product under a specific category route. A rule matches by product, category or SEO filter page, then either replaces the ancestors or inserts your own category, CMS, filter or custom-link steps. Home and the current product always stay locked in place, and an invalid definition simply falls back to the normal trail.

It follows the WAI-ARIA disclosure pattern: a real button with aria-expanded and aria-controls, ordinary link lists, visible focus states, and keyboard support (Enter and Space, arrow keys, Home/End and Escape). The current page uses aria-current, reduced-motion is respected, and the menu works with a screen reader and on touch.

It is careful, but let us be honest: building a trail and checking the page's structured data does a little work. Category, product-switcher and Home lookups are cached with targeted invalidation so the result is computed once and reused, and the storefront code sets no cookies or tracking. We do not publish a magic “zero impact” number because that would not be truthful.

The visible trail and the JSON-LD come from one ordered source, so they always match. The schema uses an absolute, fragment-free URL and sequential positions for each step, is encoded with HTML-safe flags, and contains only the linear trail, never the sibling dropdown links. If fewer than two steps remain, or the page is not eligible, no schema is emitted.

Yes. When it can identify a single safe breadcrumb in your theme, or your theme uses the standard breadcrumb hook, it takes over cleanly. It recognises Hummingbird, Classic, Warehouse and legacy markup out of the box and supports a custom selector for bespoke themes. If the target is missing or ambiguous, it leaves your theme's breadcrumb alone rather than risk breaking the page.

Yes. It uses logical CSS properties, reverses directional separators and edge fades, aligns dropdown panels by computed direction and scrolls correctly in RTL.

Category crumbs can show sibling categories, child categories or both; the Home crumb can list your top-level categories; and a product crumb can show other active, catalog-visible products from its category. Manufacturer, supplier and content-section peers can appear too. Everything respects the current shop, language and customer-group access.

Yes, from one screen: pick a display preset (Minimal, Boxed, Pill or Underline), choose the separator (chevron, slash, arrow, dot, pipe, dash or none) and the dropdown indicator, decide whether the current page is shown, truncated or hidden, and set the alignment wrapper for your theme. No template editing required.

Yes. They are rendered as real server-side links, so search engines crawl them without opening the menu, which adds genuine internal linking between sibling pages. At the same time they never enter your BreadcrumbList schema, that stays a clean, linear trail.

The storefront breadcrumb sets no cookies, no browser storage and no tracking identifiers. It only reads your existing PrestaShop customer and group context to avoid showing links a visitor cannot access, so it does not add any new consent requirement.

Yes. Labels, entity links, group headings, trail overrides and custom URLs are all language-aware, and configuration, dropdown groups, definable trails and caches are scoped per shop.