01
Start with the technology, not the banner
Identify what loads on first visit and which services can store or access device information. Analytics, advertising and some embedded services commonly need attention.
02
A banner must create a real choice
Accept and reject choices should be clear, optional technologies should respect the choice, and detailed settings should be understandable without manipulation.
03
Strictly necessary is a narrow category
A cookie is not necessary merely because the business finds it useful. It must be required for a service explicitly requested or for relevant communication functions.
04
Test implementation and withdrawal
Use browser tools or an appropriate audit to verify requests before consent, after rejection and after acceptance. Provide a persistent route to change the choice later.
Practical next steps
Checklist
- 01Audit first load
- 02Classify each technology
- 03Block optional tools before consent
- 04Offer clear rejection
- 05Record consent appropriately
- 06Allow withdrawal
Common questions
Questions and answers
Does Google Analytics need consent?
In typical UK implementations analytics cookies are not strictly necessary; obtain current legal advice for the actual configuration.
Is displaying a banner enough?
No. The underlying scripts must respect the choice.
Can a site work without optional cookies?
Core requested functions should remain available where practical.
Need a considered recommendation?
Discuss the website, not just the symptom.
AHANIX reviews each requirement manually. Technical recommendations may depend on access to the website, hosting or DNS configuration.
Continue learning