Anomaly Radar

Your website changes. CookieHug notices.

Ordinary monitoring checks whether your site responds. The anomaly radar checks whether it responds with what it should: it compares today's state with yesterday's — scripts, cookies, content, response codes and the Googlebot view.

Yesterday vs today

The same nightly scan that detects cookies compares your site against its previous state.

Yesterday

  • Google Analytics
  • Meta Pixel
  • Stripe

Today

  • Google Analytics
  • Meta Pixel
  • Stripe
  • TikTok PixelNEW

New tracker detected — alert sent before anyone had to ask "what is that?"

What the radar detects

Seven anomaly types — from cosmetic to the kind that costs you Google rankings or sales.

A new tracker or unknown script

A domain appeared in your code that wasn't there yesterday. A plugin, a tag deployed without your knowledge — or a breach.

Tracking after "Reject all"

The radar also visits your site with consent rejected and verifies the trackers actually stay silent. If not — you hear it first, not the regulator.

Consent Mode configuration changed

Consent signals stopped firing or changed values — e.g. after a plugin update overwrote your setup.

Cloaking

Your site shows Googlebot different content than users — a classic breach symptom and a fast track out of search results.

HTTP 500 on key subpages

The cart returns 500 where it worked yesterday at the same hour. You know before the first customer calls.

Vanishing subpages

A URL that returned 200 yesterday serves 404 today. A plugin, a redirect or deleted content.

Content swaps and slowdowns

Changed titles and meta descriptions, or response times several times above average — alert in the dashboard and your inbox.

Zero extra configuration

The radar uses the same script and the same nightly scan as cookie consent. Since we read your site every night anyway, it might as well tell you when something odd is going on — no second tool, no second bill.

What the radar is not

It doesn't replace backups, updates or a firewall — it won't prevent a breach. But when someone injects a foreign script, swaps content for Googlebot or your shop starts throwing errors, you'll know within hours, not after a week.

Frequently asked questions

How is this different from uptime monitoring?

Uptime monitoring checks for a 200 response. The radar compares content, scripts, cookies, headers and the Googlebot view against previous scans — catching problems where the site technically "works": cloaking, foreign scripts, tracking despite rejected consent.

How do I get alerted?

By e-mail and in the dashboard. Alerts carry severities (critical / warning / info), so you know what needs action right away.

Does it work on any CMS?

Yes — WordPress, WooCommerce, PrestaShop, Shopify, Joomla, Drupal, Webflow and fully custom sites. The radar looks at your site from the outside, like a visitor.

Deploy in 30 seconds. Sleep well.

GDPR- and Consent Mode v2-compliant consent plus an anomaly radar — in a single script.