How to Use an Online Cookie Scanner on a Client Site

How to Use an Online Cookie Scanner on a Client Site

Run ConsentLayer’s online cookie scanner over the client site’s pages that load the most third-party code: the homepage, embed pages, forms, and ad landing pages. Manual scans are on every plan, including Free, so the client doesn’t need a paid plan for this step. Read which services and cookies the scan found and sort each one into a consent category. Then install the tag, and the trackers hold until the visitor makes a choice.

What an online cookie scan tells you, and what it leaves to you

An online cookie scanner loads the pages you give it the way a visitor’s browser would, then records the cookies those pages set and the third-party scripts that set them. The result is an inventory: analytics tools, ad pixels, chat widgets, video embeds, and the cookies each one writes, with their names and the domains they come from.

A scan only describes what’s there, so a site that sets marketing cookies on the first page load has the same problem after the scan as before it. To fix it, you sort each service into a consent category (for example, statistics or marketing) and install a consent tool that holds those scripts until the visitor makes a choice.

Two limits matter when you read any scan. A scanner sees only the pages it visits, so a pixel that fires on a single landing page stays hidden if that page isn’t in the scan. It also sees the site as a logged-out visitor at that moment. A widget that a plugin loads for some regions, or a script added next week, won’t show up.

What you need before you scan a client site

Gather four things first: the client’s domain, access to the site’s <head> code (or the name of the person who has it), the list of tools the client says they use, and a private browser window for the check at the end.

Ask the client for that tool list in plain terms, such as “Which analytics, ad pixels, chat, booking, or video tools are on the site?”, and write their answer down before you scan. The gap between what the client believes is installed and what the scan finds is the most useful thing you’ll hand back to them, since it’s the part they couldn’t have told you.

How to scan a client site and act on the results

1. Pick the pages that load the most third-party code

Start with the homepage, then add a page with a video or map embed, the contact or booking form, and the landing page that the client’s ads point to. Include that ad landing page even when the menu doesn’t link to it, because a campaign pixel often lives only there.

2. Run the scan

Give your agent one prompt, and replace the placeholder with the domain of the client site you’re setting up:

Set up cookie consent on <your-domain>

What happens: your agent calls setup_site, and that one tool call creates the site and scans it. It also configures consent categories and returns the tag with a real project key. You can run the scan from your agent with one prompt after you sign in through your browser once.

Without an agent, create the site at app.consentlayer.com and add your list of URLs before you start a scan from the site’s page.

3. Read what the scan found

Put the client’s own tool list next to the scan result and mark every service that appears in only one of them. The usual surprises are a Meta or LinkedIn pixel from a campaign that ended a year ago, a chat widget the client’s marketer added without telling anyone, and YouTube cookies from a video embed on the homepage.

A script the scanner can’t name goes to the steps under “Fix the scan results that look wrong”.

4. Sort every tracker into a consent category

Ask your agent to “Sort the trackers from the last scan into consent categories”. What happens: it calls configure_from_scan, and that single call creates the services and cookies in the right categories from the scan. Check the result against what you learned in step 3. A chat widget that also runs ad retargeting belongs with marketing, not with the tools the site needs to work.

Without an agent, open the scan in the dashboard and assign each found service to a category.

5. Install the tag so the trackers wait

Paste the tag into the <head> of every page, as the first script, with no extra attributes. The banner holds known trackers until the visitor consents and then runs them. That’s how you stop trackers firing before a visitor chooses. On WordPress, put it in the theme header or a header-scripts plugin that prints it before your tag manager.

Once it’s deployed, every service sits in a category, the banner shows, and the analytics and ad tags hold until the visitor decides.

Check that trackers wait for consent

Run two checks, as each one catches what the other misses.

First, ask your agent to “Check the installation on my client site” and read the result. It calls check_installation, which fetches the live homepage and confirms the tag is in <head> without defer or async. It reads the homepage only, so a landing page built in a separate page builder with its own header still needs your own eyes.

Second, test the pages yourself:

  1. Open the site in a private window, so no earlier consent choice is stored.
  2. Open the browser’s developer tools on the Network tab and turn on “Preserve log”.
  3. Load the homepage and the ad landing page without clicking the banner. Look at the cookies under Application (Chrome) or Storage (Firefox), and look for requests to ad and analytics domains.
  4. Accept all, reload, and look again.

Before the click, you should see no marketing or statistics cookies and no requests to pixel domains. After the click, they should appear. Fix any pixel that fires in the first load before handoff. Here’s what a pixel that fires before the banner can lead to.

Fix the scan results that look wrong

The scanner flags a script it does not know

Scripts the library doesn’t recognize go to a review queue, and nothing there is settled until you act. For each one, you either approve it with a category and blocking rule or dismiss it. Work the queue in this order:

  1. Open the script’s source URL and note the domain it loads from.
  2. Search the client’s plugin list and tag manager for that domain to find who added it.
  3. If it sets tracking cookies or sends data to a third party, approve it with the matching category and a blocking rule.
  4. If it’s a first-party file the site needs (a theme script, a form validator), dismiss it.

Cookies show up before anyone clicks

Here the tag loaded after other scripts, or with defer or async, so analytics ran before the banner could hold it. The tag must load synchronously, with no defer and no async, before other scripts.

On one client site the tag was correct in the theme, yet Google Analytics cookies still appeared on the first load. A performance plugin had a “defer all JavaScript” setting switched on, and it added defer to the tag as well. Excluding the tag from that setting fixed it, and the private-window check came back clean. If the site runs Google tags, read the load order for Google Consent Mode v2 before you move anything in the header.

Two scanners report different cookies for the same site

A scanner that crawls only the page you submit misses cookies set on other pages, so the counts differ. CookieServe crawls the page you submit, while a scan that also visits your booking form and ad landing page reports the cookies those pages add. Timing changes results too, as a scanner that runs on a different day can catch a different ad rotation or a widget that loads only in some regions.

Free online cookie scanners compared

Any of these can scan a client site, and the difference is what you can do with the result.

Cookiebot cookie checker

The cookie checker is free forever, but the tool behind it, Cookiebot CMP, is offered on a 14-day free trial. That makes fixing what the scan finds a separate buying decision. Its report is generated and emailed to you, and you wait for it in your inbox instead of reading it on the page.

CookieServe

You get results with no email required, and the tool is free forever. That suits a quick look at one page before a sales call.

ConsentLayer scanner

One scan checks up to 10 URLs of the client site and matches what it finds against the ConsentLayer service library. ConsentLayer’s cookie scanner feeds the result into the banner setup instead of leaving it in a report.

Keep the scan current on every client site

When the client launches a new ad campaign or their marketer adds a booking widget, new scripts land on the site without you hearing about it. Solo adds weekly automatic scans, so a new service shows up in the next scan rather than months later. On Free, rescan by hand after every change the client tells you about, and add a rescan to your monthly maintenance list for the sites on your roster.

Online cookie scanner FAQ

Does a clean cookie scan mean the site is compliant?

A clean scan only lists what loads. The compliance score rates a site from 0 to 100 across 10 checks and names the open items, but it measures the technical setup, not legal sufficiency. Legal questions, such as the client’s privacy policy or vendor contracts, sit outside what any score can rate.

What are the cookie categories?

Each site starts with 3 categories that can’t be deleted: Essential, Statistics, and Marketing. You can add custom categories when a client needs a finer split, such as a separate one for embedded video.

How many URLs should you scan on a large site?

Choose one URL per template, because pages sharing a template load identical scripts. A shop with 2,000 product pages needs one product, one category, the cart, and checkout. Large sites with separate subdomains, such as a help centre or a store, need those hosts scanned too.

Which laws does an online cookie scan check against?

Cookiebot checks its results against GDPR and CCPA, and CookieServe ties its scan to the same two laws. A scan reports what the site sets, and you still map those results to the laws where the client’s visitors live.

How ConsentLayer handles the next client site

The next site is the same prompt with a new domain. To set one up, give your agent the prompt from step 2 with the new client’s domain. Paste the tag it returns into that site’s <head> and deploy. To check it, ask your agent to check the installation, then run the private-window test on that site’s ad landing page. The banner records every decision, and that record is the proof of consent the client keeps.

Run your first scan on a client site and follow the steps to get it protected: the scanner guide.