> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/theme-settings/breadcrumbs.md).

# Breadcrumbs

Show the navigation path on product and collection pages (e.g. Home → Collections → Product). Helps customers orient themselves and improves SEO.

{% hint style="info" %}
**Theme Editor → Theme settings → Breadcrumbs**
{% endhint %}

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FknfBukBlgMzSBioGqWJj%2FGroup%2018.jpg?alt=media&amp;token=04534f24-1800-48bb-89a6-e205bf8b5e84" alt=""><figcaption></figcaption></figure>

{% hint style="warning" icon="triangle-exclamation" %}
**Note:** Breadcrumbs create multiple URLs for the same product, which can affect SEO. In most cases the UX benefit outweighs the SEO impact.
{% endhint %}

***

### Navigation context — for customers and search engines

A breadcrumb trail (Home → Jackets → Wool Coat) does two things at once: it shows customers where they are in your store, and it creates internal linking structure that search engines use to understand your site hierarchy.

***

### For customers: a path back — and forward

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FxmYBFReUTZWzTZ6nseJw%2FGroup%2014%20(19).png?alt=media&amp;token=b323bfd9-f7e7-45a1-95bf-42f4d4304c5b" alt=""><figcaption></figcaption></figure>

A customer who lands on a product page from Google has no visible way to explore the collection it belongs to — unless breadcrumbs are enabled. With breadcrumbs, every product page has a clear path back to its category. This is one of the lowest-effort additions you can make to reduce bounce rates on organic traffic pages.

***

### How to enable

{% hint style="success" icon="sparkles" %}
**Pro tip:** Breadcrumbs require two steps — enable them in Theme settings **and** add the Breadcrumbs block in the Product overview section in Theme Editor. The setting alone is not enough.
{% endhint %}

{% stepper %}
{% step %}

#### **Step 1 — Configure in Theme settings**

Go to **Theme settings → Breadcrumbs** and enable the toggle.
{% endstep %}

{% step %}

#### **Step 2 — Add the block to your template**

1. Open **Theme Editor → Default product** (or any product template)
2. Inside **Product overview** section, click **Add block → Breadcrumbs**
3. Save

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FqC0rmOZX16V8x1dt0L3S%2FScreenshot%202026-06-19%20at%2016.34.57.png?alt=media&amp;token=26b98566-acb8-48eb-b21b-cdc7b13e3607" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Note:** Adding the block without enabling **Theme settings → Breadcrumbs** will show nothing.
{% endhint %}
{% endstep %}
{% endstepper %}

***

### What the trail is made of

A breadcrumb trail is assembled from three parts, and only the middle one is optional:

1. **Home** — always the first crumb, on every page that shows breadcrumbs
2. **Collections** — a link to the collections listing page, controlled by **Path style**
3. **The page itself** — the collection the customer came through, then the product, article or page name, controlled by **Show current item**

{% hint style="info" %}
**Home cannot be removed.** Setting **Path style** to **Disable** drops the Collections link, not the Home link — so the shortest trail Avante can produce is Home → Product rather than the product name on its own. If you need breadcrumbs gone entirely, turn off **Enable** at the top of this group or remove the block from the template.
{% endhint %}

***

### Path style — choose what to show

**Path style** has exactly two options, and both of them keep Home in place:

<table data-search="false"><thead><tr><th>Option</th><th>What appears</th><th>When to use</th></tr></thead><tbody><tr><td><strong>Show collections page</strong> (default)</td><td>Home → Collections → Category → Product</td><td>Store with clear department structure</td></tr><tr><td><strong>Disable</strong></td><td>Home → Category → Product</td><td>Stores where the Collections listing page is not something you want customers landing on</td></tr></tbody></table>

The **Category** crumb is not part of Path style — it appears whenever the customer reached the product through a collection, and it is the collection they came from.

**Dim path** — a separate toggle that reduces the visual weight of the path so the current product name stands out. The trail stays readable but doesn't compete with the product title.

**Show current item** — includes the current product, collection, blog or article name as the last crumb in the trail. Turn it off and the trail stops at the level above.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/theme-settings/breadcrumbs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.