Does Reject all work – including after the next update?
A visible consent banner is not itself a check of website behaviour. This workflow gives developers, agencies and privacy consultants a technical basis for review.
1. Start in a clean browser
Record the time, pages and network requests before touching the banner. Use separate fresh browser sessions for different choices.
2. Document the choice itself
Activate an explicit Reject all or Only necessary control. A clicked button alone does not prove a rejection was stored. Check both the interface and available CMP state.
3. Inspect traffic after the choice
Identify services sending new requests after the interaction. Separate necessary services from tracking-related services. Network traffic alone does not determine the legal basis.
4. Compare the disclosures
Look for observed services in readable privacy and cookie policies. Missing matches can reflect generic descriptions, unreadable sources or alternative names; review the sources before concluding.
5. Fix, check and follow up
After an implementation change, repeat the test with the same scope. Document whether the signal remains, is no longer observed, or the test is incomplete. Enable monitoring for subsequent changes.
StackPatrol's free scan inventories the front page. Paid plans add consent tests and monitoring. Tests can be incomplete, and results are not legal conclusions.