> ## Documentation Index
> Fetch the complete documentation index at: https://elarislabs-87.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Cloudflare

> For sites behind Cloudflare. Elaris reads which AI agents and crawlers visited from your site's analytics, every hour, with read-only access.

> [!NOTE]
>
> Nothing is installed on your site and Elaris can't change any Cloudflare setting. It works on every Cloudflare plan, including Free.

## Before you start

* Your site's traffic goes through Cloudflare (the orange cloud is on for your domain's DNS records). Requests that bypass Cloudflare aren't in its analytics.
* You are an **admin** of the Elaris workspace and can approve apps on the Cloudflare account that holds your site.
* Your website is set in Elaris (**Settings → General**), so the right site is picked for you.

## Connect

![Integrations: connect Vercel or Cloudflare for AI traffic](https://mintcdn.com/elarislabs-87/dTHBKlX4xY5rVFBt/images/visibility/integrations-traffic.jpg?fit=max\&auto=format\&n=dTHBKlX4xY5rVFBt\&q=85\&s=a38929c695786750d2fc39ce142f518d)

Settings → Integrations: the Website traffic panel, where Connect Cloudflare is.

1. In Elaris Visibility, open **Settings → Integrations** and select **Connect Cloudflare**.
2. Cloudflare opens and shows what **Elaris Visibility** is asking for: read access to your sites and their analytics. Choose the account that holds your site and approve.
3. You come back to Elaris. The site matching your website is picked automatically; if Elaris can't tell which one it is, choose it from the list of sites on the account.
4. Elaris reads the last 24 hours straight away, so AI Traffic fills in within a minute or two. After that, each hour is added shortly after it ends.

## What happens behind the scenes

Once an hour, Elaris asks Cloudflare's analytics for the requests to your site whose user agent belongs to a known AI agent or crawler, counted by hour, host, page, bot, response status and country. Requests from people are never read. The counts are stored in your workspace and shown on the AI Traffic page alongside any other sources you connect.

Cloudflare's analytics are sampled on busy sites, so the counts are Cloudflare's estimates rather than an exact tally. They also don't include IP addresses, so bots seen this way show as unchecked rather than verified.

## What Elaris can access

| Permission | Why |
| - | - |
| Zone read | To list the sites on your account, so you can choose the right one |
| Analytics read | To count requests from AI agents and crawlers, by page and hour |
| Ongoing access | To read each new hour without asking you to sign in again |

All access is read-only. The access Cloudflare grants is stored encrypted, renewed automatically, and used only to read AI traffic for your workspace.

## Changing or disconnecting

* **Another site:** select **Connect Cloudflare** again and choose it.
* **Disconnect:** in **Settings → Integrations**, select **Disconnect** on the Cloudflare panel (click twice to confirm). Elaris gives the access back to Cloudflare straight away. AI traffic already collected stays in Elaris.
* **From Cloudflare's side:** revoke Elaris Visibility from your profile's authorised apps. The panel then asks you to connect again.

## Troubleshooting

| You see | What to do |
| - | - |
| You can't choose your account on Cloudflare's screen | An admin of that account needs to allow public apps under Manage Account → Members → Settings. |
| “This Cloudflare access covers no active sites” | The account you chose has no active sites. Connect again and choose the account that holds your site. |
| “Connect Cloudflare again” | The access was revoked or has expired. Select Connect again. |
| Connected, but no traffic | Check that your domain is proxied through Cloudflare (orange cloud). If AI bots haven't visited in the last day, the page fills in as they do. |

> [!NOTE]
>
> Need every request exactly, with IP checks? Open **Set it up by hand instead** on the Cloudflare panel and add the small Worker it shows. Set its route's request limit failure mode to **Fail open** so your site keeps working if the Worker's daily limit is reached.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.