> ## 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.

# Actions overview

> Make your website easy for AI models to read, understand and cite — with llms.txt, robots.txt, a sitemap, the Ask AI widget and the Site Check.

Tracking your visibility is half the job. **Actions** is the other half: practical tools that make your site more discoverable and quotable by AI assistants.

## What's in Actions

<CardGroup cols={2}>
  <Card title="llms.txt" icon="file-text" href="/en/actions/llms-txt">
    Give AI models a structured guide to your site's content.
  </Card>

  <Card title="robots.txt" icon="bot" href="/en/actions/robots-txt">
    Control which crawlers and AI agents can access your pages.
  </Card>

  <Card title="sitemap.xml" icon="map" href="/en/actions/sitemap">
    Help crawlers discover every page on your site.
  </Card>

  <Card title="Ask AI widget" icon="message-circle" href="/en/actions/ask-ai">
    Add a floating button that opens AI chats pre-loaded with your prompt.
  </Card>

  <Card title="Site Check" icon="search-check" href="/en/actions/site-audit">
    Audit whether your site has the recommended AI-readiness artifacts.
  </Card>
</CardGroup>

## How the file tools work

The file generators (`llms.txt`, `robots.txt`, `sitemap.xml`) follow a similar flow:

<Steps>
  <Step title="Generate">
    Cliro creates a draft — with AI for `llms.txt`/`robots.txt`, or by discovering your URLs for `sitemap.xml`.
  </Step>

  <Step title="Edit">
    Review and adjust the draft in the built-in editor.
  </Step>

  <Step title="Confirm">
    Lock the content. A confirmed file becomes available to download.
  </Step>

  <Step title="Publish & verify">
    Upload the file to your site's root, then use **Verify publication** to confirm it's live and up to date.
  </Step>
</Steps>

<Note>
  You manage these files per brand. Select your brand first if you have more than one.
</Note>

<Tip>
  Run the [Site Check](/en/actions/site-audit) after publishing to confirm everything is in place and matches Cliro's recommendations.
</Tip>