Based on what buyers actually ask
Auto-generated tagsFeatureAI-powered
AI crawler tracking setup
AI crawler tracking, set up from where your site runs
AI crawlers only show up in server-side data, so tracking them starts at your host or CDN. WriteWorks detects where your site runs and offers the right connection: a Vercel log drain, a Cloudflare Worker or Logpush job, Netlify, Fastly, CloudFront, Akamai, a WordPress plugin, or a snippet for your own server.
7-day trial · Cancel anytime
Google Search Console
Google Analytics 4
Google Ads
Ahrefs
Semrush
DataForSEO
Firecrawl
Tavily
Exa
Parallel
G2
WordPress
Webflow
Contentful
Sanity
Payload
BaseHub
Framer
Notion
Gamma
v0
Slack
Linear
Atlassian
Monday.com
Granola
Klaviyo
Customer.io
OpenAI Ads
Claude and MCP clients The challenge
Why AI crawler tracking is hard to set up
The data lives at the server, behind each host's own tooling.
AI crawlers skip JavaScript tags
A browser analytics tag never sees most AI bots. Tracking them means reading requests at the server or CDN, which is where marketing teams usually have no access.
Every host does logging differently
Vercel log drains, Cloudflare Logpush, Netlify drains, Fastly endpoints and CloudFront log delivery all have their own setup, permissions and plan requirements.
Tracking breaks quietly
A rotated token or a changed CDN rule can stop the data without anyone noticing, until a report comes back empty.
Answers shift week to week
The same buyer question returns a different set of sources each week, so a one-off audit is stale before the fix ships.
The solution
How setup works
Pick your host, provide access, WriteWorks does the configuration.
Connect Vercel with OAuth or a token and WriteWorks adds the log drain. Paste a Cloudflare token and WriteWorks installs a Worker for you, or creates a Logpush job. Netlify, Fastly, CloudFront and Akamai work the same way: provide credentials, and WriteWorks configures the delivery.
On WordPress, download the WriteWorks Bot Tracker plugin, which connects itself and sends crawler requests in the background without slowing pages. Anywhere else, drop in the Next.js, Express or Nginx snippet.
A connection status card shows whether data is arriving, and flags when WriteWorks stops receiving data from a connection, so a silent break gets fixed quickly. Tracking keys, tracked domains and domain verification live in settings.
Customer story
How teams are winning AI search
From invisibility to category dominance across every major answer engine.
“Before WriteWorks, our content landed and disappeared. Now every asset ships citation-ready, gets cited across the engines our buyers ask, and ties back to the loop. It's the first time we've measured AI search as a real channel.”
EM
Capabilities
Supported setup methods
From managed hosts to your own server.
Vercel log drain
OAuth or token; needs Vercel Pro or Enterprise.
Cloudflare Worker
Auto-installed from a pasted token.
Cloudflare Logpush
Logpush job created for you; needs Cloudflare Enterprise.
Netlify, Fastly, CloudFront, Akamai
Log drains, logging endpoints, log delivery and DataStream, configured from your credentials.
WordPress plugin
Bot Tracker plugin that connects itself.
Next.js, Express or Nginx
A snippet for any other stack.
Time savings
What changes
From engineering project to guided connection.
TaskBeforeWith WriteWorksTime saved
Start tracking AI crawlersEngineering ticket for log exportGuided connection for your hostDays to minutes
Know tracking is still workingNotice an empty reportConnection status cardBreaks caught early
Included
Every method at a glance
Nine ways to get AI crawler data into WriteWorks.
Vercel log drain (OAuth or token)
Cloudflare Worker, auto-installed from a pasted token
Cloudflare Logpush
Netlify log drain, Fastly logging, Amazon CloudFront, Akamai DataStream
WordPress Bot Tracker plugin
Next.js, Express or Nginx snippet
Automatic host detection and connection status
Built for
Who sets it up
Marketers, developers and agencies.
Marketing teams
Get crawler data without waiting on engineering.
Developers
A clean server-side integration for your stack.
Agencies
Connect each client's host, whatever it runs on.
Featured story
Fhresh
“WriteWorks turned AI search from a black box into our most measurable channel. We can show the board how we're cited, our share of voice, and how sentiment is trending, across every engine.”
Read the full story20+
Markets tracked
Sentiment
Scored on every mention
Board-ready
AI-visibility reporting
FAQ
Frequently asked questions
Everything teams typically ask before getting started.
What is Cloudflare Logpush?+
Logpush is Cloudflare's service for pushing request logs to an external destination. It is available on Cloudflare Enterprise. With a token, WriteWorks creates the Logpush job so your request logs flow in and AI crawlers are identified automatically. On other Cloudflare plans, use the Cloudflare Worker method instead.
What is a Vercel log drain?+
A log drain forwards your Vercel deployment's request logs to an external endpoint. Log drains need a Vercel Pro or Enterprise plan. Connect Vercel in WriteWorks with OAuth or a token and the drain is added for you.
Which setup method should I use?+
WriteWorks detects your host and suggests one. Generally, use your host or CDN's native method if your plan supports it, the Cloudflare Worker if you are on Cloudflare without Enterprise, the plugin on WordPress, and the snippet for a custom server.
Will tracking slow down my site?+
Log drains and CDN logging run outside your page requests. The WordPress plugin queues crawler hits locally and sends them in the background, never during a visitor's page load.
Which plans include AI crawler tracking?+
AI crawler tracking is available on the Growth and Enterprise plans and on agency plans, not Starter.
Explore more
Keep exploring
Related solutions, adjacent use cases, and platform features.
Connect your host and see the crawlers
Nine server-side setup methods, automatic host detection, and a status card that tells you when data stops.