Cookie banners on static websites
A static website does not automatically need a cookie banner. What matters is what it loads and stores.
The problem
Some sites add cookie banners even though no cookies are set. Others load external fonts, maps, videos or analytics without clear consent. Both can confuse users and create risk.
Simple solution
- First check technically whether cookies, tracking or external services exist.
- Remove unnecessary analytics and trackers.
- Host fonts locally when possible.
- Use privacy-friendly alternatives for maps and videos.
- Have the final assessment reviewed by qualified legal or privacy professionals.
Common mistakes
- Treating a cookie banner as a privacy review.
- Loading Google Fonts externally without documentation.
- Keeping tracking snippets from templates.
- Loading external iframes by default.
- Publishing legal text without review.
Checklist
- No cookies in own code
- No analytics
- No tracking pixels
- Fonts local
- Maps/videos intentional
- Privacy page explains local processing
- Legal review planned
FAQ
Is this legal advice?
No. These are technical hints, not legal advice.
Do I never need a banner without cookies?
Not automatically. External services or tracking can still matter.
Can SitePreviewKit check cookies?
It looks for technical hints in static files, but it is not a full legal review.