Know every cookie on your site — before your visitors do.
CookieLet crawls your website on a schedule, catches every cookie your pages actually set, sorts them into categories, and keeps your banner and cookie policy in sync. You review. You publish. That's the job.
No code changes to get started Results in minutes Nothing goes live until you publish
| Scan Date | Status | URLs | Categories | Cookies | |
|---|---|---|---|---|---|
| 05 Aug 2026, 11:27 | finished | 29 | 2 | 3 | More Info |
| 01 Aug 2026, 11:30 | finished | 29 | 2 | 3 | More Info |
| 31 Jul 2026, 07:00 | finished | 27 | 3 | 5 | More Info |
| 30 Jul 2026, 10:58 | finished | 29 | 4 | 8 | More Info |
The problem
Cookie lists go stale quietly
Nobody sets out to run an inaccurate banner. It happens the ordinary way. Marketing drops a pixel in for a campaign. A plugin update ships a new tracker. An embedded video starts setting a cookie it wasn't setting last month. None of it lands in a changelog, and none of it announces itself — your banner just keeps promising visitors a list that stopped being true weeks ago.
Tags nobody told you about
A campaign pixel goes in through the tag manager on Tuesday. It sets three cookies. Your banner still lists last quarter's.
Third-party embeds
Videos, maps, chat widgets, fonts, social feeds. Each one is somebody else's code setting somebody else's cookies on your domain.
Plugin and theme updates
You approve a routine update. It ships a new analytics dependency. Your cookie inventory changed and no one on the team knows.
How it works
Four steps, then it runs itself
Set it up once. After that, the only thing that needs your attention is a scan result that found something new.
Point it at your site
Add your domain. CookieLet crawls it the way a visitor would — loading pages in a real browser and watching what gets set.
Get a sorted list
Every cookie found comes back grouped into categories, with its ID and the domain that set it.
Review and adjust
Rename categories, rewrite descriptions, move a cookie, add one the crawl couldn't reach.
Publish
One press sends the approved list live. Your banner and cookie policy update from the same source.
What's inside
Built for the part after setup
A real crawl, not a guess
CookieLet opens your pages in a real browser and records what actually gets set — on load, and after your scripts have had a chance to fire. It follows your internal links, so a tracker living on one checkout page doesn't stay hidden just because nobody thought to look there. Every scan reports exactly how many URLs it covered, so coverage is a number you can see rather than a promise.
- Renders pages properly instead of reading source code
- Catches first-party and third-party cookies alike
- Follows internal links across the whole site
- Reports the URL count for every single run
Scans that keep running after launch day
Set a schedule and let it go. CookieLet re-crawls on its own and always shows you when the next run is due, so nobody has to remember. Shipping something big? Hit Scan Now and get a fresh read immediately instead of waiting for the calendar. New cookies show up in a scan result — not in a complaint.
- Recurring automatic scans, no reminders needed
- Reschedule to match your release cycle
- On-demand scans right after a deploy
- Last-scan and next-scan dates always in view
Categories your visitors can actually understand
Every cookie lands in a category, and every category carries a description that shows up on your banner — the text a visitor reads before deciding. CookieLet starts you with sensible defaults, including a Strictly Necessary group that stays on and can't be switched off, then gets out of your way. Rename a category, rewrite its description in your own words, build a new one, or move a cookie you understand better than the scanner does.
- Standard categories ready on day one
- Every name and description is yours to edit
- Add custom categories for anything unusual
- Enter cookies by hand when a crawl can't reach them
Every scan stays on the record
Scan History keeps the full run of every crawl you've done — date, status, URLs covered, categories found, cookie count — with a drill-down on each one. When somebody asks "when did this tracker turn up?", you don't guess. You scroll to the run where the number changed and read the answer off the row. It doubles as a record of what your site looked like at any point, which is exactly what you want when a question arrives months later.
- Complete scan-by-scan timeline
- URLs, categories and cookie counts per run
- More Info opens the detail behind any scan
- Pinpoint the exact run where something changed
| Scan date | Status | URLs | Cookies |
|---|---|---|---|
| 05 Aug 2026 | finished | 29 | 3 |
| 01 Aug 2026 | finished | 29 | 3 |
| 31 Jul 2026 | finished | 27 | 5 |
| 30 Jul 2026 | finished | 29 | 8 |
| 23 Jul 2026 | finished | 29 | 8 |
Nothing goes live until you say so
Every change is staged first — a renamed category, a hand-added cookie, a fresh set of scan results. Your live banner carries on showing the last version you approved while you work. When you're satisfied, one press of Publish Changes pushes the whole set live together. No half-updated banner, no surprise text appearing in front of visitors mid-edit.
- Draft edits stay off your live site
- Review everything before a visitor sees any of it
- Banner and policy publish in one action
- A clear signal when you have unpublished work
FAQ
Questions people ask first
How long does a scan take?
Most sites finish in a few minutes. The time depends on how many pages get crawled and how heavy they are — a 30-page marketing site is quick, a large catalogue takes longer. You don't have to sit and watch; the result lands in Scan History either way.
Do I have to change my code to run a scan?
No. Scanning works from the outside, the same way a visitor's browser reaches your pages. You only add CookieLet's snippet when you're ready to show the banner and start recording consent.
What if the scanner misses a cookie?
Add it yourself. Any category has an Add Cookies option for exactly this — cookies behind a login, ones that only fire after checkout, or region-specific tags a crawl won't trigger. Manually added cookies behave like discovered ones everywhere else in the product.
Will scanning slow down my site?
No more than a handful of ordinary visits. The crawler loads pages the way a browser does, at a modest pace, and it runs on our infrastructure rather than yours.
How often should I scan?
Weekly suits most sites. Scan more often if you're changing tags or shipping regularly, less often if the site is stable. Whatever you pick, run a manual scan straight after any launch that touched scripts, embeds or plugins.
Does my banner change the moment a scan finishes?
No. Scan results and edits are staged as drafts. Your live banner keeps showing the version you last approved until you press Publish Changes, so you always get to look before anything reaches a visitor.
Can I manage more than one website?
Yes. Switch properties from the site picker in the sidebar. Each one has its own scan schedule, its own categories and its own history — nothing is shared between them unless you set it up that way.
Does my cookie policy update too?
It's generated from the same cookie list, so the two can't drift apart. Publish the list and the policy reflects it — no second document to remember to edit.
See every cookie on your site today
Run your first scan in minutes, categorise what it finds, and publish a cookie list your visitors can actually understand.