Track AI crawler visits on Cloudflare

1. Deploy the Worker

The one-click template creates an isolated Worker project and asks for your publishable workspace identifier. Cloudflare cannot infer your production hostname, so you will attach the route in step 3.

Prefer the CLI? Start a Worker project and install the published adapter:

npm install @foglift/sensor@^1.0.0

2. Add the generated Worker

Open AI Traffic while signed in to copy this entrypoint with your workspace identifier filled in. The adapter reports a matched request and passes the original request through to your origin unchanged.

// src/worker.ts
import { senseAITrafficWorker } from "@foglift/sensor/cloudflare";

export default {
  fetch: senseAITrafficWorker({
    siteToken: "YOUR_WORKSPACE_ID",
  }),
};

Matched reports stay alive through ctx.waitUntil, so Foglift reporting does not delay the response.

3. Assign the route safely

Use this path only when you control an active, proxied Cloudflare zone. Configure the Worker route for your hostname, such as example.com/*. Do not replace an existing Worker route or overwrite its bindings, compatibility settings, or fetch behavior. If a Worker already owns that route, review the integration before deployment. Cloudflare's route documentation explains how patterns attach Workers to proxied hostnames.

npx wrangler dev
npx wrangler deploy

4. Verify the server signal

1. Confirm the Worker route is active on the intended production hostname.
2. Open AI Traffic and choose Verify install.
3. Foglift sends a unique workspace-bound request and confirms when the Worker reports it. The CLI verification command remains available as a fallback.

The Sensor sends the matched agent role, request path, and referrer hostname only. Query strings, request bodies, cookies, and page content are not reported. Cloudflare security products can block traffic before a Worker runs, so this covers recognized requests that reach the Worker. A crawler request does not prove indexing or citation.