Cookie Scanner Tools for Checking Client Sites

Cookie Scanner Tools for Checking Client Sites

For client sites, pick ConsentLayer, where you can run manual scans on Free and every paid plan and each scan checks up to 10 URLs and names the known services it finds. For a single site of your own, the ConsentLayer Free plan covers 1 site and includes the same manual scans. Look at Cookiebot Premium only when a site must run IAB TCF, because ConsentLayer has no IAB TCF support.

What a cookie scanner does and where it stops

Take a client’s shop where the homepage loads only an analytics script and the checkout loads the payment provider’s fraud-check script. A scan of the homepage alone reports one tracker and misses the checkout script. You’d then sign off a banner that knows nothing about the cookies set at checkout. A cookie scanner loads the pages you give it and lists the cookies, local storage items, and third-party scripts each page sets. That list is what the consent banner has to control.

The list on its own changes nothing on the site. A scanner reads and reports but doesn’t stop any script from firing; blocking is the consent tool’s job. In ConsentLayer, the banner holds known trackers until the visitor consents and then runs the held scripts.

Scripts that the ConsentLayer service library doesn’t recognize go to a review queue. There you approve each one with a category and a blocking rule, or dismiss it. On client sites, a custom script that a previous developer pasted into the footer won’t match any library entry, and the queue is where it still gets a decision.

How we chose these cookie scanners

Each tool here had to work on a site you build or maintain for someone else and pass five tests that matter once you look after more than one client site. The same tests help when you’re choosing a consent management platform for client sites. You configure that platform with the scan result.

  • It scans the client’s own live site, not a demo or a sample report.
  • You can see how many pages one scan checks, so you know what a clean result covers.
  • Results come back sorted into categories you can map to a banner.
  • It can scan again after launch, by hand or on a schedule.
  • Its cost stays readable as your roster grows from two sites to twenty.

Five cookie scanners for client sites

ConsentLayer

One scan per client site checks up to 10 URLs and matches what it finds against the ConsentLayer service library, which gives you a list to sort before launch. Say you scan a brochure site with a booking form. The result names each known service it matched, such as Google Analytics, with its consent category and the cookies it sets. Your agent reads that list back to you in the chat, or you read it in the dashboard at app.consentlayer.com.

See what the scanner found on a new Replit app for a full result on a real build. For a roster, Studio pools 500,000 pageviews per month across 10 sites for $29 per month. One allowance covers every site in the organization, and the plan adds 5 team members and a 1-year consent log. ConsentLayer covers GDPR, CCPA/CPRA, and LGPD, and the limit to plan around is the 10-URL cap. That cap means that on a large shop you have to choose which pages go into the scan.

CookieYes

On the free plan, CookieYes checks 100 pages per scan but allows 5 cookie scans a month and no scheduled scan. That’s enough to audit a mid-size client site once, but not to watch it. All CookieYes prices are per domain, billed monthly or annually, so the bill grows with every client site you add.

  • The free cookie checker matches cookies against a database of more than 100,000 cookies and groups them as Necessary, Functional, Analytics, Performance, and Advertisement.
  • Every plan has a GDPR template (opt-in) and a US State Laws template (opt-out).
  • Five scans a month run out fast when you rescan after each fix. Save at least one for the final check before handoff.

Cookiebot

Cookiebot’s Premium bill follows the number of domains and the number of subpages within each domain. A large client site costs more to cover than a small one. The Cookiebot free plan covers up to 50 subpages on 1 domain, with an initial scan for cookies and trackers only, so the free plan doesn’t rescan the site after that first pass.

Free and Premium both name GDPR, CCPA/CPRA, VCDPA, LGPD, and POPIA. To install it, you copy the banner code into the site header, and Cookiebot also lists a WordPress plugin. On a large client site, get the price for its full subpage count before you put Cookiebot in a quote.

Secure Privacy

The free plan covers up to 10 domains but caps consents at 500 a month. On a roster of small sites, you’ll reach the consent cap before the domain limit. Web plans are priced per domain once you leave Free, and the free plan includes a domain scan report and 1 language.

Every plan names GDPR, CCPA/CPRA, and more than 55 global privacy laws. Watch the consent cap more than the domain count. A shop with steady traffic can pass 500 consents well before the month ends.

ComplyDog free cookie checker

You paste a URL and get a report with no account and no email. You can check as many sites as you want. A check on a client site takes four steps in the ComplyDog tool:

  1. Paste the live URL of the client site into the ComplyDog checker.
  2. Read the report’s count of cookies and localStorage items.
  3. Check each cookie’s name, domain, and expiry, and its Secure and HttpOnly values.
  4. Compare the cookie names with your banner’s categories, and note any cookie with no category.

ComplyDog names GDPR as the law it checks against. Treat the result as a GDPR check and nothing wider.

Rescan client sites after launch

A client site changes after handoff when the client adds a chat widget or a marketing contractor drops a pixel into Google Tag Manager, and nobody tells you. One scan at launch goes stale the first time that happens. The tool you pick needs a repeat scan and a way to read what changed.

  • ConsentLayer: a scan diff shows which services and cookies are new or gone since the previous scan, and the Solo plan adds weekly automatic scans.
  • CookieYes: scheduled scans run monthly on Pro and weekly on Ultimate, with none on Free or Basic.
  • Cookiebot: Premium scans monthly, and daily scans are a paid add-on.
  • Secure Privacy: monthly domain scanning starts at the Small plan.

Look for the diff, because a full cookie list every week hides the one new pixel among dozens of known ones, while a list of changes puts it first. Weekly suits a shop that a marketing team edits, and monthly is enough for a brochure site nobody touches after launch. Put the rescan into the care plan you sell, so it runs on a fixed date and doesn’t wait for the client to mention a new widget. For the wider workflow, see cookie consent for the client sites you maintain.

Cookie scanners compared

ToolWhat one scan coversHow the next scan runs
ConsentLayerUp to 10 URLs, with known services namedBy hand on all plans; weekly and automatic on Solo
CookieYes100 pages per scan on Free5 manual scans a month on Free; scheduled monthly on Pro, weekly on Ultimate
CookiebotUp to 50 subpages on 1 domain on FreeInitial scan only on Free; monthly on Premium, daily as a paid add-on
Secure PrivacyA domain scan report on Free, for up to 10 domainsMonthly from the Small plan
ComplyDogThe URL you paste, on as many sites as you wantBy hand, with no account

Cookie scanner questions

Does a cookie scanner click the banner before it reads cookies?

The CookieYes checker activates the cookies a server sets and also detects some cookies that appear while a user interacts with a cookie banner. Its report includes part of what loads after a click. For the opposite test, check a site for pixels that fire before consent.

Can a cookie scanner check pages behind a login?

On its Advanced plan, Secure Privacy adds scanning behind login. That matters for membership sites and customer account areas, where an embedded video or a support chat loads only after sign-in and a public scan never sees it.

What can I give the client after a cookie scan?

ConsentLayer builds a hosted cookie policy from the site’s categories, services, and cookies, and rebuilds it when they change, so the page you link from the client’s footer stays current. It’s on every plan, including Free.

How many pages should a cookie scan cover?

Cover one page of every template, plus any page with its own embed, such as a map or a booking widget. On Cookiebot, watch the scan size: its billing uses the highest page count in the scan history, and one oversized scan keeps the higher count on the bill.

Does a cookie scan show whether the banner works?

A scan lists what the site sets, and a separate check tells you whether the setup holds up. ConsentLayer’s compliance score rates a site from 0 to 100 across 10 checks and names the open items. It measures the technical setup, not legal sufficiency, so don’t present it to a client as legal sign-off.

Scan a client site with ConsentLayer

Setup works in two ways: by prompt through your AI agent, or from the dashboard at app.consentlayer.com. With an agent, send this prompt with the client site’s domain in place of the placeholder:

Set up cookie consent on <your-domain>

Your agent then creates the site, scans it, and sets up its consent categories in one step, and it returns the install snippet with the site’s real project key. When a later scan finds new services, one more request to your agent adds those services and their cookies to the right categories. Without an agent, sign in at app.consentlayer.com and add the site, then run the scan on that site from the dashboard.

Paste the snippet into the <head> of every page with no defer and no async, then deploy. To check it worked, ask your agent to check the installation, which fetches the live homepage and confirms the snippet is in <head> without defer or async. The site is protected once the snippet is live on the real domain, blocking is on, and decisions are recorded. For the rest of the toolset, read about ConsentLayer’s scanner and blocking features.

Scan your first client site free and get its consent snippet in the same step.