> 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
{% hint style="info" %}
**Theme Editor → Theme settings → Breadcrumbs**
{% endhint %}
{% 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
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
{% hint style="warning" %}
**Note:** Adding the block without enabling **Theme settings → Breadcrumbs** will show nothing.
{% endhint %}
{% endstep %}
{% endstepper %}
***
### Path style — choose what to show
**Path style** controls how much of the navigation path is shown:
| Option | What appears | When to use |
| ------------------------- | --------------------------------------- | ----------------------------------------------------- |
| **Show collections page** | Home → Collections → Category → Product | Store with clear department structure |
| **Disable** | Product name only | Minimal stores where the full path would be redundant |
**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 or page name as the last crumb in the trail.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://staylime.com/docs/avante-themes/theme-settings/breadcrumbs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.