Bot identification and filtering

Basic filtering discards recognized crawler signatures and common automation clients before collection. The tracker also stops in browsers reporting automation. These checks are always active; they do not detect every bot.

Detection matches known client names such as Googlebot, GPTBot, HeadlessChrome and curl as complete tokens. A device model containing the letters “bot” is not enough to discard a visit. Unrecognized automation can still pass these basic checks.

What appears in reports

Sources → Bots groups labels present in accepted records. Historical labelled records may remain after filtering changes. A missing label is not proof that the visitor is human.

Limits

User agents can be spoofed and some automated traffic resembles ordinary browsers. Seean does not use visitor IP geolocation or prove whether a visitor uses a VPN. Traffic that never runs the tracker or sends a collection request cannot appear in the reports.

Usage and exclusions

Discarded requests do not count toward event usage. Accepted pageviews and custom events count, including any accepted event with a bot label. Use browser, path and hostname exclusions to exclude your own new activity. Rules do not rewrite previously collected history.

Ignore your own visits

Open Settings → Exclusions for browser opt-out commands and path or hostname rules. Follow the complete exclusions guide for exact matching behavior and how to resume collection.

Something unclear? Contact support.