SCANNER EXPLAINER
Cookie consent testing
A cookie list tells you what was found. A consent test also asks when it appeared and which choice the visitor had made.
Before a choice
The scanner opens a fresh browser session and observes the page. This establishes the starting behaviour without a previous consent preference. Recognised advertising storage before permission can produce a failed check. Unclassified activity needs purpose and configuration review.
After Reject and reload
Where a supported refusal control is found, the scanner clicks it, observes again and reloads. This checks whether the choice affects the observed activity. A cookie written to remember Reject can be expected; its presence alone is not evidence that advertising continued.
After Accept
A separate session tests acceptance where a supported control is available. Comparing states helps explain what changed. Different timing or a missed interaction can limit the comparison, so the report records limitations instead of inventing a result.
How to read the result
The headline groups related actions so repeated page checks do not become a long list of duplicate tasks.
- Failed check: supported technical evidence needs attention. Check the cause and retest.
- Warning: a specific observation needs verification before deciding what to change.
- Passed: the stated test passed during this observation window.
- Not tested or verification incomplete: further testing or owner information is needed.
What the scan cannot decide
A public browser visit cannot establish every purpose, exemption, internal procedure or legal obligation. Some consent interfaces, later activity, authenticated journeys and server-side processing are outside the evidence captured. The scan does not submit forms, send chatbot messages or provide a legal certificate.
What you receive
A free scan covers up to five pages, results, captured evidence and a copyable developer brief. A detailed audit is designed for broader coverage and a PDF when purchasing is enabled. It does not automatically resolve unsupported tests. Website fixes are a separate paid service: we agree the work and confirm the page-count price before payment. A detailed audit is not required to start a fix plan. Recurring monitoring is not included.
Compare free scans, audits and website fixes ↗ · Have us make fixes ↗ · Read the testing limitations ↗
Related guides
Prepared by GDPRFix, operated by Alex Player, trading as Nexus Websites. Legal claims link to official guidance; this guide is not a legal opinion.