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

# Brand context

> Control which brand and E-E-A-T information Cliro injects into the Content Agent so generated articles sound like you.

The **Context** tab decides which brand information is injected into the **Content Agent's** prompt when it writes articles. A live preview shows exactly what gets sent to the model, so there are no surprises.

## How it works

You toggle which sections to include. Anything you turn on — and have filled in — becomes part of the context the Content Agent uses to write on-brand, credible articles.

<Steps>
  <Step title="Fill in your brand & E-E-A-T data">
    The context is built from your [Brand & E-E-A-T](/en/knowledge-base/brand-eeat) information. Complete the relevant fields first.
  </Step>

  <Step title="Choose what to include">
    Turn on the sections you want injected into the Content Agent.
  </Step>

  <Step title="Review the preview">
    The **Injected context** preview shows precisely what will be sent to the model.
  </Step>

  <Step title="Save context">
    Click **Save context** to apply it to future article generation.
  </Step>
</Steps>

## What you can include

* **Brand description** — name and description from the Brand book.
* **Entity & ownership**, **editorial responsibility**, **contributors**.
* **Experience signals**, **expertise**, **authority signals**.
* **Trust & transparency**, **knowledge freshness & scope**.
* **Optional** — testimonials, reviews and AI disclosure.

<Note>
  Contact and schema details aren't injected as prose — they're reserved for schema markup at publish time, not for the article's writing context.
</Note>

<Tip>
  Turn on the sections that make your content distinctive — expertise, experience and authority signals — so articles read as genuinely yours rather than generic.
</Tip>

<Card title="Generate content" icon="pen-line" href="/en/content-agent/overview">
  See how the Content Agent uses this context to write articles.
</Card>