Tracker & cookie scanner

1. Scan your URL above to list the tracking scripts and any consent-banner code in your markup.
2. Identify consent-requiring trackers - analytics, advertising pixels, and session recorders that need opt-in in the EU/UK.
3. Add or fix a consent banner (CMP) that blocks non-essential trackers until the visitor opts in.
4. Gate trackers behind consent - load them only after consent (e.g. Google Consent Mode) instead of on page load.
5. Disclose and re-scan - list the trackers in your privacy and cookie policies, then re-scan to confirm the gap is closed.

Cookie and tracker compliance has teeth. Regulators across the EU have issued substantial fines for loading analytics and advertising cookies before consent, and "reject all" must be as easy as "accept all." Beyond fines, there's a trust cost: visitors increasingly notice (and resent) sites that drop a dozen trackers on arrival. And there's a performance cost - every third-party script adds weight and latency that hurts Core Web Vitals and conversions. Auditing what you actually run is the first step to fixing all three.

There's also a data-quality angle: if your consent setup is misconfigured, you may be collecting analytics you legally can't use, or - just as common - blocking analytics you're allowed to collect, leaving you flying blind. Knowing exactly which trackers fire, and when, is the foundation of a setup that's both compliant and useful.

If the scan flags consent-requiring trackers with no detected banner, the fix is a consent management platform (CMP) configured to block by default. Route your trackers through it (or through Google Tag Manager with Consent Mode) so nothing non-essential fires until the visitor opts in, offer an equally prominent "reject all", and document every tracker in your cookie policy. Test it by reloading with cookies cleared and confirming no analytics or pixel requests go out before you click accept.