Skip to content

How to check a website for privacy compliance

Key idea:

A website privacy check comes down to five observable facts: which cookies and trackers are written before the visitor consents; whether a consent banner with an equal Reject option is shown; whether data-collection forms carry a consent checkbox and a policy link; whether an up-to-date privacy policy is published; and whether data leaves for services in other jurisdictions. Each item takes minutes to verify in a browser — or one automated scan.

Check your site →

What an audit actually looks at

An auditor cares less about the policy text than about the site's behaviour: processing must start after consent, not before. In practice the order is reversed — analytics counters, ad pixels and chat widgets initialise on page load and ship visitor identifiers to third parties before the banner even appears.

  • Cookies and third-party requests before consent — the headline fact
  • The banner: an equal Reject, or an Accept-only design
  • Forms: an unchecked consent checkbox and a policy link next to the form
  • The privacy policy: published, current, reachable from every page
  • Cross-border transfers: which services receive data and where they are based

Checking by hand with DevTools

Open the site in an incognito window with DevTools → Application → Cookies visible. Touch nothing in the banner. Everything that appears in the cookie list and on the Network tab before your first click is processing-before-consent. Then repeat after pressing Accept and compare: the difference shows what the banner actually controls versus what loads unconditionally.

# Quick third-party host list from the console:\nperformance.getEntriesByType('resource')\n  .map(r => new URL(r.name).hostname)\n  .filter((h, i, a) => a.indexOf(h) === i && h !== location.hostname)

Automating the check

A manual check covers one page and one scenario. The compliance scanner does the same in a real browser across multiple pages and three scenarios — no action, banner accepted, banner rejected — then folds the observations into an A–F grade with 152-FZ and GDPR projections and a per-page fix list. For a quick single-page registry-and-cookie check there is the 152-FZ aggregator.

Related

Cookies Before ConsentWhat is written without permission
Consent BannerIs there an equal Reject option
PII FormsConsent and policy at the form
Projections152-FZ and GDPR grades

Why teams trust us

A–F
grade + 152-FZ/GDPR
3
browser sessions per page
PDF
integrity-signed report
Free
scan without signup

How it works

1

Enter your site URL

2

The scanner opens pages in a browser

3

Get a grade and a fix list

Why check your site for privacy compliance?

Regulators fine sites for processing personal data without consent — and a site starts processing earlier than it seems: analytics, pixels and widgets write cookies the moment the page loads. The scanner shows the auditor's view: what leaves for third parties before consent, whether the banner works, and whether forms collect data correctly.

Real Browser

Three sessions per page: no action, banner accepted, banner rejected.

Trackers and Jurisdiction

Service catalogue: who receives visitor data and in which country.

Policy at Collection Point

The policy link and consent element are checked next to the form, not in the footer.

Signed PDF

Report with an HMAC integrity stamp — hand it to your lawyer or contractor.

Who uses this

Business

preparing for an audit

Lawyers

technical facts for an opinion

Web Studios

client site handover

DevOps

consent regression monitoring

Common Mistakes

Loading analytics before consentA counter in writes cookies before any banner. This is exactly what an audit records.
Banner without a Reject buttonConsent is voluntary only when refusing is as easy as agreeing.
Policy only in the footerThe visitor must see who receives their data at the moment of submission — next to the form itself.
Checking once and forgettingA new widget or tag manager quietly adds trackers. Only a re-check catches the regression.

Best Practices

Delay trackers until consentInitialise analytics from the CMP accept callback, not on page load.
Offer an equal RejectAccept and Reject buttons — same size, same level.
Consent checkbox at every formUnchecked by default, with the processing policy linked right there.
Turn on monitoringA standing watch alerts you when the grade drops — before an auditor notices.

Monitor compliance automatically

Scheduled re-checks with an alert when pre-consent trackers appear on your site.

Sign up free

Learn more

Frequently Asked Questions

Is this check a legal opinion?

No. Both the manual and the automated check record technical facts: what is written, what is shown, how forms are built. It is the groundwork for counsel, not a substitute.

Where do I start if the grade is low?

With the most measurable item: move counter and pixel initialisation into the consent banner's accept callback. That usually clears the bulk of before-consent findings.

How often should I re-check?

After every new widget, tag manager or marketing pixel — they change the picture silently. A standing watch does this automatically and alerts on a grade drop.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.