Consent release testing

Catch cookie consent regressions after every risky release.

A CMS update, CMP configuration change, or tag-manager publish can silently change the default and reject paths. ScanBell provides a fast public-page comparison before client handoff.

A focused QA loop

1. Scan a representative URL before the release.
2. Publish the CMP, CMS, frontend, or tag change.
3. Rerun default, reject, and accept states in clean contexts.
4. Review evidence and confidence—not a compliance badge.

Add the check to CI

The public ScanBell GitHub Action runs the same bounded check against a deployed public URL and writes stable outputs to the job summary. It is non-blocking by default.

Designed for agencies and implementers

The proposed €49 evidence pack covers three representative URLs, confidence-labelled remediation, a shareable report, and one verification rerun. The free scanner validates the narrow signal before any purchase decision.