> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replyful.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Audiences & languages

> Answer each visitor with the content that applies to their market

If your site serves more than one market, you can tag your knowledge so the chatbot answers each visitor with the content meant for them — and greets them in the right language.

<Note>
  **Most sites don't need this.** If one set of answers serves everyone, skip this page. The chatbot already replies in whatever language the visitor writes in.
</Note>

## Two separate things

<CardGroup cols={2}>
  <Card title="Audience" icon="users">
    **Who** the content is for — a market, region or site that you define. Germany and Austria are two audiences.
  </Card>

  <Card title="Language" icon="globe">
    **What** the text is written in. Those two audiences share one language: German.
  </Card>
</CardGroup>

<Tip>
  Anything you leave untagged is used for **every** visitor. That's how one shared English page keeps working in every market.
</Tip>

## Set up markets

Say your site is English at `example.com`, German at `example.com/de` and Swedish at `example.com/sv`.

<Steps>
  <Step title="Create one audience per market">
    Go to **Settings → Audiences** and create one audience per market — a code, a label, and the language that market reads:

    | Code | Label   | Language |
    | ---- | ------- | -------- |
    | `de` | Germany | German   |
    | `sv` | Sweden  | Swedish  |

    Don't create one for English. English is the shared default that everyone gets.
  </Step>

  <Step title="Tag your knowledge">
    Under **Knowledge → Web pages**, add one entry per market pointing at that market's address:

    | Address          | Audience      | Language     |
    | ---------------- | ------------- | ------------ |
    | `example.com/de` | Germany       | German       |
    | `example.com/sv` | Sweden        | Swedish      |
    | `example.com`    | All audiences | Any language |

    Crawling never leaves the address you give it, so the German entry can't wander into `/sv`. The last entry starts at the root, so list the market paths in its **Exclude paths**, one per line, to keep it English-only:

    ```text theme={null}
    /de
    /sv
    ```

    Files, articles and Q\&As carry the same two fields on the form where you create them.
  </Step>

  <Step title="Detect the visitor">
    On your chatbot's **Localization** tab, under **Detect language or audience from URL**, add a rule per market:

    | Match                  | Target  |
    | ---------------------- | ------- |
    | Path starts with `/de` | Germany |
    | Path starts with `/sv` | Sweden  |

    Rules are checked top to bottom, and the first match wins.
  </Step>

  <Step title="Decide what everyone else sees">
    **Unmatched visitors** covers anyone no rule matched — here, everyone reading English.

    * **Answer from all knowledge** — the default.
    * **Answer only from untagged knowledge** — choose this when showing the wrong market's content is worse than a shorter answer. English visitors then never get pointed at a German page.
  </Step>
</Steps>

## What each visitor gets

With **Answer only from untagged knowledge** selected:

| Visitor is on | Answers come from                        | Widget greets in |
| ------------- | ---------------------------------------- | ---------------- |
| `/de/preise`  | German pages **+ shared English pages**  | German           |
| `/sv/priser`  | Swedish pages **+ shared English pages** | Swedish          |
| `/pricing`    | Shared English pages only                | English          |

## Which language the widget speaks

Your greeting, teaser and suggested questions come from the first of these that applies:

1. A language your detection rule targeted directly
2. The default language of the audience the rule matched
3. The visitor's browser language, if you've enabled that language
4. Your default widget language

The AI's replies ignore this list — they follow the language the visitor actually writes in.

## Common questions

<AccordionGroup>
  <Accordion title="Should a rule target an audience or a language?">
    An audience, unless the only difference is what the text is written in.

    An audience rule adds that market's content to your shared content. A language rule filters on the written language instead, which leaves out anything written in another language — including your shared English pages.
  </Accordion>

  <Accordion title="Why is Delete greyed out on an audience?">
    Because knowledge is still tagged with it — the **Usage** column on that row is the count.

    Open those items and set them back to **All audiences**, then delete.
  </Accordion>

  <Accordion title="My market's language isn't in the widget language list">
    Two different lists. Knowledge can be tagged in any language we support, but the widget's own greeting and teaser text covers a shorter list.

    A visitor in a market without widget text still gets answers from that market's knowledge, in their language — only the greeting falls back to your default.
  </Accordion>
</AccordionGroup>