> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-navigation-and-trust-markers.md).

# Store navigation and trust markers

Several features are enabled by default on every AI-generated store. They require no setup, but they're worth understanding — both because they shape how your store reads to a player, and because some of them are adjustable.

## Category banners

Immersive banners sit between categories, acting as dividers that also introduce what the next section of your catalogue contains.

Structurally this stops your store reading as one long undifferentiated list of SKUs and starts it reading as a store with curated sections. Practically, it gives players a scannable landmark as they scroll.

Category banners are generated for you and enabled by default.

## Category menu in the navigation bar

The top navigation bar carries a menu listing all of your categories.

This does two things. It lets players jump directly to the part of your catalogue they came for, rather than scrolling to find it. And a navigation bar with real structure behind it signals a store with depth — a sparse nav reads as a thin, hastily assembled page, which is not the impression you want in the first second.

Enabled by default on all AI-generated stores.

## The Official Store marker

Your navigation bar displays an **Official Store** trust marker, translated into every language your store supports, by default.

This one does more work than its size suggests. Players have been trained over years to be wary of third-party top-up sites, and often with good reason. Your store has to distinguish itself from that category immediately — before a player weighs up whether to enter their player ID or payment details. A clear marker in the navigation bar, in the player's own language, is the most direct way to say that this is the publisher's own store.

## Country and language switching

Players can switch country and language without leaving the page.

Selecting a country or language opens a selector in place. The player makes their choice and carries on from where they were — no redirect to a separate international page, no full page reload, no losing their position in the purchase flow.

This matters for two reasons. Country and language are a single decision to a player: they aren't thinking "change my country" and "change my language" as separate intentions, they're thinking "show me this store the way I expect to see it." And every full page load is a moment where a player can reconsider whether they want to be here at all — a cost that's minor on a fast desktop connection and significant on a patchy mobile one.

This is the default behaviour on all AI-generated stores.


---

# 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://docs.coda.co/coda-webstore/coda-webstore-builder/store-navigation-and-trust-markers.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.
