How to find it
Go to app.trybluemoon.com and select Agent Analytics in the left sidebar. If the selected domain isn’t connected yet, the page shows the setup steps instead of the dashboard. Once it is connected, the line under the title shows your platform and serve mode, and the Setup button brings the steps back.Connecting your domain
1
Connect the edge
In Agent Analytics, pick your domain, answer What is your site built with?, and click Connect edge. You get an edge token (format
aen_…). It is shown once, works for that one site only, and can be replaced with Regenerate under Setup (the old token stops working immediately). It is not your account API key.2
Add the token to your host
In your host (for example Vercel → your project → Settings → Environment Variables), add the edge token as
AEN_EDGE_TOKEN:3
Install the Agent Edge Network
For Next.js, add the Bluemoon middleware (
middleware.ts) at the root of your app and deploy. It has no dependencies and runs on the Vercel Edge runtime. Other stacks are listed below.Every install starts in shadow mode: everyone gets your normal page, and AI crawler visits are only logged. There is no risk to visitors or SEO while you check that it works.4
Trigger a real crawl
Open ChatGPT or Perplexity with browsing enabled and ask a question that makes it fetch one of your pages. The visit should appear under Recent activity, marked Verified.
5
Switch your serve mode when ready
Once verified hits come in, switch to
default to start serving the optimized version. With the middleware.ts file, change SERVE_MODE from "shadow" to "default" and redeploy. With the WordPress plugin, choose Live under Setup → How much to serve. See Serve modes for the other installs.Available installs: Next.js / Vercel, Cloudflare Worker, WordPress / PHP, and a custom integration for any other stack.
What the dashboard shows
AI requests
The number of AI crawler visits logged in the window, verified or not, with the change against the previous period and a Requests over time chart. The sentence under it names the busiest crawler.Key figures
Who crawls your site
Requests by crawler over the window, each with its share of all requests.Most crawled pages
Requests per page. Each page is marked Cited or Not cited: cited means an AI used the page in at least one answer Bluemoon collected, at any time. See all pages opens the full list.Why they came
Requests by purpose (see below). It tells you whether your AI traffic is people asking an assistant in real time or answer engines fetching pages.Recent activity
The latest visits, newest first: the time, the crawler, the page, whether it was Verified, and the Result: Optimized served or Passthrough.Pages
See all pages opens two tabs:- Crawled: every page AI crawlers requested in the window. Search by path.
- Your pages: the pages of your site, read from its sitemap, with the status of each optimized version, its citability score, and Generate missing to build the ones not generated yet or stale. Open a page to see its optimized version and Regenerate it. See Optimized pages.
Verification levels
- Verified (
IP_VERIFIED): the request comes from an IP address the AI vendor publishes for its crawler. Can be served the optimized version. - Unverified (
UA_ONLY): the request claims to be a known AI crawler, but its IP address could not be verified. It is logged, but always gets your normal page.
Purpose classes
By default, only
USER_TRIGGERED and RETRIEVAL can be served the optimized version.
Result
- Optimized served: the crawler got the optimized version of the page.
- Passthrough: the crawler got your normal page. This happens when the serve mode is
shadow, the crawler is unverified, the page has no ready optimized version, or the crawler’s purpose isn’t enabled.
Reading Pages served to AI, later cited
This figure connects what you served to what gets cited. It takes the pages you served the optimized version for in the window and shows what percentage of them also appear among this domain’s citations. The label shows how many pages were served. It does not claim the citation happened after the page was served, or because of it. It shows a dash until enough pages have been served to give a percentage, and0% if none of the served pages is cited yet.
Search crawlers
Googlebot, Bingbot and Applebot always get your normal page, and their visits are not logged here. Serving a different page to a search index is cloaking, which search engines penalize, and Google AI Overviews run on the same index as Google Search. See Cloaking firewall.What your install sends to Bluemoon
For each AI crawler visit, your install sends Bluemoon details including the crawler name, the page path, the user agent, the IP address, the verification level, the purpose and whether the optimized version was served. It is sent in the background and never delays the response. Visits from people and from anything that isn’t a known AI crawler are not reported.Troubleshooting
No hits appear in the dashboard
No hits appear in the dashboard
Check that (1) your install deployed successfully, (2)
AEN_EDGE_TOKEN is set and matches the token from the app, and (3) you actually got an AI crawler to fetch a page, not just your own browser. The dashboard shows at most the last 30 days.A page shows Passthrough even in default mode
A page shows Passthrough even in default mode
The optimized version is only served when the crawler is verified, its purpose is enabled, and the page has a ready optimized version. Find the URL under See all pages → Your pages and click Regenerate if it is not Optimized. See Detection and verification if crawlers you expect to be verified show as Unverified.
Is this safe for SEO?
Is this safe for SEO?
Yes. Googlebot, Bingbot and Applebot always get your normal page, whatever the serve mode. The optimized version only goes to verified AI answer-engine crawlers.
Can I use this outside of Vercel / Next.js?
Can I use this outside of Vercel / Next.js?
Yes. There are installs for Cloudflare and WordPress / PHP, plus a custom integration with copy-paste snippets for Node, PHP, Ruby, nginx and Apache.