Meteoria

Getting started

Meteoria AI crawler analytics lets you detect AI crawlers and agents hitting your site. Forward edge or origin request metadata to Meteoria so your dashboard can show bots, top pages, and trends.

Overview

Setup takes a few minutes. You choose how to send data (Cloudflare Worker, Vercel middleware, Nginx, WordPress, Node, PHP, browser snippet, or a custom HTTPS integration). Your project receives a secret token; all server calls go to a single endpoint.

Prerequisites

  • A Meteoria account
  • Access to your hosting or CDN settings (Cloudflare, Vercel, Nginx, etc.)

Onboarding

  1. Open your Meteoria project → **Actionable** tab → **AI crawler analytics** (same idea as other products’ “Agent analytics” hub).
  2. If you already track another hostname, use the workspace/project switcher; otherwise continue in the same project. Add any **tracked site URLs** Meteoria should attribute (apex or `www`, marketing domains, etc.).
  3. Meteoria highlights common hosting stacks (Cloudflare, Vercel, WordPress, etc.). Pick the card that matches yours — it does not auto-reconfigure your DNS; it only opens the right snippet checklist.
  4. Copy the **`mt_…` crawler token** and the integration snippet, deploy to your edge or origin, then run **Verify installation**. Expect a few minutes before charts move; if nothing after 24 hours, re-read the integration doc for your stack.
  5. Need help? Open this documentation from the doc icon in the setup card or browse sections in the left menu.
Meteoria exposes one HTTPS ingest path per environment (`/crawler-analytics/server-track`) and a per-project crawler token (`mt_…`) from the dashboard. Send the token in the JSON body, via `X-API-Key` / `Authorization: Bearer`, HTTP Basic (password = token), query `?token=`, or whatever your CDN UI exposes (some mirror it as `header_X-API-Key` on the URL). **GET** on the same path returns **200** for provider validation probes; real hits are always **POST** JSON.
Server-side integrations POST JSON to: https://app.meteoria.ai/api/crawler-analytics/server-track. Required fields include token (from the dashboard) and userAgent; include path or requestUrl, ip, and source when possible.