Who is fetching your pages?
Start with request observations and crawler identity. A claimed user agent needs supporting evidence.
WebDecoy field guides
Understand your
AI traffic.
See who fetches your content, which assistants send visitors, and what the traffic actually did. Start with the question you need to answer.
RequestsReferral visitsInvestigation
A crawler request does not establish a citation, a referred visit or a sale. Keep those records separate.
Follow the evidence
Which assistants send visitors?
Look for identifiable referrals separately from crawler requests. Missing attribution remains unknown.
What needs investigation?
Inspect the session or order evidence that supports a decision. An AI referral alone is not a fraud signal.
Before interpreting a quiet report
Check what your installation can see.
A browser embed observes clients that run it. A supported edge or server sensor can observe requests that skip JavaScript. Coverage depends on the installed integration and route. WebDecoy complements your existing controls, including Cloudflare.
Use the method. Keep the limits.
Our published traffic snapshot describes one WebDecoy-owned property during a fixed historical window. Our Shopify walkthrough uses a development store, a labeled setup test and seeded order examples. Neither establishes an industry-wide detection rate.
Use the blank Shopify review template to record your own date range, collection source, report filters and next action. Read our research and corrections policy for how we handle claims.