> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/brand-page-creation-and-editing/how-brand-page-urls-work.md).

# How Brand Page URLs work

Every Brand Page has a unique URL on the retailer's website, constructed from a URL prefix and the page's slug.

**URL pattern:** <https://www.retailer-site.com/{prefix}/{url-slug}>

For example, if the prefix is /brands/ and the slug is summer-essentials, the full URL would be: <https://www.retailer-site.com/brands/summer-essentials>

{% hint style="success" %}
The URL slug is all you need to set when creating a Brand Page. Everything else is handled by the retailer's integration.
{% endhint %}

Select your URL slug directly in the UI when creating a Brand Page:

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FBvcW3wXeiLi5HcHQ52zB%2FCleanShot%202026-05-13%20at%2018.21.38%402x.png?alt=media&amp;token=4cae81b8-2b65-4c32-8557-69869491c47a" alt=""><figcaption></figcaption></figure>

#### Slug rules

| Rule           | Details                                                                                                                                    |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Characters** | Lowercase letters, digits, hyphens, and underscores only.                                                                                  |
| **Uniqueness** | Each slug must be unique within the catalogue for a given time period. No two active Brand Pages can share the same slug at the same time. |
| **Permanence** | Slugs cannot be changed after the Brand Page is published. Choose carefully.                                                               |

{% hint style="info" %}
**Tip:** The URL prefix (e.g. /brands/) is configured at the retailer level and is consistent across all Brand Pages for that retailer.
{% endhint %}


---

# 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://help.citrusad.com/retail-media-interface/brand-page-creation-and-editing/how-brand-page-urls-work.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.
