See which AI crawlers fetch your site, then inspect the visits AI platforms send back. WebDecoy puts those observations in AI Traffic, alongside the sensor coverage behind them.

On our own webdecoy.com property, the seven-day dashboard captured on November 10, 2026 UTC showed:

Dashboard measureCaptured value
Pages crawled by AI-only crawlers3,789
Additional crawling shared between search and AI629
Observed AI referral visits6
Distinct referral landing pages5

These are one property’s dashboard observations, not an industry benchmark or a result caused by a marketing campaign. Crawling volume does not measure visitors acquired. The capture includes the current UTC day, which was incomplete.

Install WebDecoy on your site to inspect your own bot traffic, AI crawling and observed referrals.

Watch the 32-second walkthrough

Silent walkthrough built from the actual app captures below, with English captions. The seven-day snapshot is dated; it is not a live counter.

Transcript: AI crawlers found your site. See what came back. Track crawling and observed referral visits separately. Our own seven-day dashboard showed 3,789 AI-only crawls and six observed referral visits, with 629 additional crawls shared between search and AI. Five landing pages received observed AI referrals. Open AI Traffic → Referrals to inspect destinations. A page’s platform label shows its leading source; its visit count combines sources. Install WebDecoy, confirm sensor coverage, and use server or edge collection for non-JavaScript crawlers.

Read the actual dashboard

WebDecoy AI Traffic for webdecoy.com, showing the selected seven-day view, collection coverage, 3,789 AI-only crawls, six observed referrals and five landing pages.

Actual own-site app capture. The collection panel includes a warning about sensors reporting without proving their type; these figures do not establish verified edge coverage for every source.

Start with the selected property and time window. Then read three different questions:

  1. Which crawlers reached the site? Crawling shows automated fetch activity that the installed sensors observed. WebDecoy keeps crawlers shared between search and AI separate from the AI-only headline.
  2. Did we observe any AI referrals? A qualifying arrival carries a recognized AI-platform referral signal. Without that signal, the visit can remain unattributed.
  3. Where did those visits land? Open the Referrals tab to see the pages receiving observed traffic. In this capture, the five destinations included the FCaptcha demo and our JA4 format guide, alongside other technical resources.

The landing-page row’s platform label names its leading platform. The visit count combines platforms for that page, so summing row counts by their displayed labels will not reconstruct the platform totals.

A crawl does not prove a citation. A referral does not reveal the user’s prompt, prove the visitor is human, or identify the exact answer they saw. The app’s crawl-to-referral ratio is an observed comparison, not a conversion rate.

Install the sensors that can see the traffic you care about

What you want to observeCollection to consider
Browser visits and supported referral signalsBrowser tag
Requests handled by your application, including non-JavaScript crawlersSupported server integration or WordPress plugin
Requests handled at the edge, including cache-served requestsSupported edge integration configured for that traffic path

A browser tag cannot observe a crawler that never executes it. An origin plugin cannot observe a cached page request that never reaches WordPress. Check WordPress and Cloudflare cache coverage before interpreting an empty origin log.

Use the collection panel to confirm which sources reported and when. A source name alone is not proof of an authenticated sensor or complete traffic coverage.

Set up your own AI traffic view

  1. Create a WebDecoy account and add your site.
  2. Follow the integration guide for your deployment. WordPress users can start with the free WordPress plugin; Shopify merchants can add WebDecoy from the Shopify App Store.
  3. Confirm reporting before drawing conclusions from an empty dashboard. Install the appropriate request-level collection if non-JavaScript crawling is part of your question.
  4. Open AI Traffic, select the property, and choose a 7-, 14- or 30-day window.
  5. Inspect Crawlers and Referrals separately. Review the referring platforms and landing pages before deciding which pages deserve more attention.

Keep your existing Cloudflare protection and acquisition analytics. WebDecoy adds bot and crawler evidence; it complements those tools.

Reconcile AI referrals with your other analytics

Google Analytics can identify traffic when source information is available. It does not need to classify every AI arrival as Direct. For example, OpenAI documents that ChatGPT search referral URLs include utm_source=chatgpt.com.

Before comparing dashboards, align the property, date range, timezone and counting unit. A WebDecoy observed visit, a GA4 session and a page view are different measurements. Missing referrers, redirects, consent choices, collection coverage and campaign parameters can also change what a tool records. See Google’s Traffic acquisition documentation.

For the next content decision, look at the actual destination. A technical tool receiving an observed visit gives you a specific page to inspect for a useful installation path. A crawler fetching that tool gives you a separate observation about automated access. Neither alone establishes sales or signup impact.

Put the evidence next to the installation path

WebDecoy’s value starts with seeing what reaches your site: bots, crawlers and the referral traffic you can identify. Install the right collection, confirm it reports, and inspect your own activity.

Choose your WebDecoy integration →

Updated November 2026 with an actual dashboard walkthrough. This replaces the original launch copy’s blanket claims about other analytics tools and guaranteed human referral traffic.

Frequently Asked Questions

Can WebDecoy track AI crawlers and AI referral traffic? +

Yes. AI Traffic shows observed crawling and recognized AI referrals for a selected property and time window. Collection depends on the installed sensors. Server or edge coverage can observe non-JavaScript crawlers; the page tag observes browser activity.

Does an AI crawler visiting my site prove it sent visitors? +

No. A crawler request, a citation and a referred visit are separate events. Crawling alone does not establish that your page appeared in an answer or that someone clicked it.

Does WebDecoy replace Google Analytics or Cloudflare? +

No. Use WebDecoy's bot and crawler evidence alongside your acquisition analytics and existing Cloudflare protection. Compare the same property, period and attribution definitions before comparing counts.

Want to see WebDecoy in action?

Get a personalized demo from our team.

Request Demo