Skip to content

See where you stand

Change it

Works withWordPressShopifyWebflowGitHubGoogleSlackAll integrations
FixesFixes now ship to WordPress, Shopify, Webflow and GitHub

By team

By goal

Done for you

Not sure where to start? Take a guided tour.Book a demo
Customer storyHow the voice AI company Futuro grew its traffic3×AI traffic in 60 days

Learn

Data and research

FreeAI Site GraderAI Query Scannerllms.txt GeneratorAll free tools
Open dataWhere AI sends people, across more than 6,000 sites

Netlify AI bot tracking

Trakkr installs a Netlify Edge Function that records matching crawler requests before browser analytics would run. Upstream blocks remain outside its view.

Explore crawler monitoringRead crawler docs
Edge Functionai-bot-log · lope.example
TimeRequestStatus
06:15:17BytespiderGET /403
06:13:40ClaudeBotGET /guides/sizing200
06:11:03GPTBotGET /guides/wide-fit200
06:09:26PerplexityBotGET /guides/wide-fit200
06:07:49OAI-SearchBotGET /guides/sizing200
06:05:12ChatGPT-UserGET /guides/wide-fit200
In Trakkr

Asked in Trakkr

“Which AI bots read our guides, and what did they get back?”

/guides/wide-fit3 bots
/guides/sizing2 bots
/guides/trailNone

/guides/trail has no AI visits in 30 days

Check its links, sitemap entry and robots rules.

A practical workflow.

Start with the source, check what it can show, then compare it with your AI visibility.

Before you start

A Netlify site and permission to authorize the Trakkr OAuth integration and deploy the generated Edge Function.

A clear list of production paths you want to verify after the function deploys.

A Trakkr workspace tracking crawler behavior, AI traffic, or visibility outcomes.

Authorize the Netlify site

Connect the site through Trakkr OAuth and select the production site that should receive crawler monitoring.

Deploy the generated Edge Function

Use the generated one-file function to classify matching request signatures and send bounded event fields to Trakkr.

Verify the live delivery path

Confirm the source check, then record a real matching request through the deployed function. A synthetic row only proves the dashboard path.

Segment important paths

Track docs, product pages, comparisons, pricing, and llms.txt separately so crawler volume does not hide missing high-intent pages.

Send findings into Trakkr reports

Use Trakkr to compare bot access with visibility, AI traffic, citations, and action status for the same pages.

Netlify is one of 29 integrations.See them all

What to measure.

Keep source signals, AI answers and business outcomes separate. Compare the same pages and time window.
SignalWhy it mattersCadence
AI-agent requestsShows server-side demand from AI systems, not just browser-visible sessions.Weekly
Top crawled pathsReveals which Netlify routes AI agents actually request.Weekly
Top pages and referrersAdds traffic context around pages that receive both human visits and AI-related requests.Monthly
Crawler signal versus share of voiceSeparates access problems from content and authority problems.Monthly

Turn the signal
into a next step.

Netlify supplies one part of the picture. Use Trakkr to investigate the answers around it.

Read crawler docs

How Trakkr fits

  1. Trakkr turns Netlify Edge Function events into a page-level request, citation and referral comparison that non-engineers can use.
  2. Crawler and traffic signals can be tied to llms.txt publishing, content actions, and stakeholder summaries.
  3. Share-of-voice and site-grader tools give teams a fast benchmark before they set up a deeper integration.

Common mistakes

  • Relying only on client-side analytics for bot and crawler questions.
  • Letting aggregate bot volume hide the pages AI systems should crawl.
  • Treating user-agent categories as perfect identity instead of a practical monitoring layer.

Sources and
further reading.

Netlify’s own documentation first, then the Trakkr data, tools and guides that sit around it.

Related workflows

Cloudflare · Crawler monitoringCloudflare AI crawler monitoringTurn Cloudflare AI Crawl Control into an AI visibility workflow: see which AI services reach your site, which paths they request, and whether crawler access lines up with Trakkr visibility changes.Open workflow Vercel · Edge logsVercel AI crawler logsUse a Trakkr project Log Drain for request delivery. Treat Vercel Bot Management and its AI-bot ruleset as a separate control surface for log or deny policy.Open workflow Google Analytics 4 · Traffic attributionGA4 AI search attributionGA4 now recognizes AI Assistant traffic for supported referrers. Use that signal carefully, then connect it to Trakkr prompts, citations, and reports.Open workflow

Questions,
answered.

The ones we hear most. Need a hand?
Talk to our team

Web Analytics is useful for human traffic context. Trakkr crawler monitoring uses the generated Edge Function for matching request evidence.

Ask anything else, like “What does Trakkr need from Netlify?”Ask anything else

The Agent answers from our docs, methods and pricing, and links to the source.

Build a server-side AI bot baseline

Start with Netlify logs and categories, then use Trakkr to explain which crawler patterns matter for visibility.

Explore crawler monitoringRead crawler docs
Netlify is connectedJust now
Authorize the Netlify siteConnect the site through Trakkr OAuth and select the production site that should receive crawler monitoring2 min
Deploy the generated Edge FunctionUse the generated one-file function to classify matching request signatures and send bounded event fields to TrakkrRunning
Verify the live delivery pathConfirm the source check, then record a real matching request through the deployed functionToday
Segment important pathsTrack docs, product pages, comparisons, pricing, and llms.txt separately so crawler volume does not hide missing high-intent pagesThis week
Send findings into Trakkr reportsUse Trakkr to compare bot access with visibility, AI traffic, citations, and action status for the same pagesOngoing