A website privacy checker that shows what your site tracks and where consent falls short
Start with what your website sends to a visitor's browser, then work out which privacy choices fit the way you use that data.
GET / HTTP/2set-cookie: visitor_id=4f1c9a; Max-Age=31536000<head> <script src="https://www.googletagmanager.com/gtag/js"></script> <script src="https://connect.facebook.net/en_US/fbevents.js"></script></head>No cookie consent banner found<footer> <a href="/terms">Terms</a>No privacy policy link found</footer>The free scan reads your home page's source and response headers. It doesn't run JavaScript, so it can tell whether the server sets cookies, but it doesn't see cookies set by scripts. Hosted scans also look for your privacy policy and terms pages.
What a scan can flag, and what you decide
A scan can flag
- Cookies your server setsThe free scan reads your home page's response headers. It doesn't run JavaScript, so it doesn't see cookies set by scripts.
- Known tracker and consent markersFound in your home page's source.
- Your privacy policy and terms pagesHosted scans also look for them.
What you decide
- Whether a cookie needs consentThat depends on what the cookie is for, which a scan can't check.
- Whether you still need a trackerFind the script or setting that sets it and who added it.
- Which privacy choices fit your siteThey depend on the way you use the data your website collects.
Explore website privacy questions
Handle visitors' tracking choices
3 guides
Understand Google's consent signals and test the tag behavior behind your banner.
How to fix
- Inspect the default consent stateOpen your site in Tag Assistant and inspect the earliest Consent event. Confirm the defaults appear before tags fire and match your site's policy.
- Follow a consent updateMake a choice in the banner and inspect the latest Consent event. Check the updated state for each consent type and which tags fired.
- Repeat for regional settingsIf the site uses regional defaults, repeat the test with the simulated locations those settings cover.
Privacy and policies
Google tags may ignore consent choices (Consent Mode)
Google's tracking tags on this site do not appear to change what they collect based on a visitor's consent choice.
Fix with your agent
# SiteCMD Fix Brief: Google tags may ignore consent choices (Consent Mode) Site: https://yoursite.com ## What is wrong Google's tracking tags on this site do not appear to change what they collect based on a visitor's consent choice. ## How to fix Treat this as a Google-product configuration review: identify which Google tags receive data and which visitors require a choice under your policy. If Consent Mode applies, send the v2 consent types with regional defaults set before measurement commands (Google's example values are not a universal instruction), update consent state when a visitor changes the choice, and verify the actual behavior with Tag Assistant plus Network and Storage inspection. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Work out when a banner needs consent controls and when a consent exception may apply.
How to fix
- Ask your privacy or legal advisor whether the places your visitors come from require consent before cookies or tracking run, since the rules differ.
- If they do, tracking has to wait until a visitor says yes, and a banner by itself doesn't hold it back.
- This usually needs a change to your site's code or tracking setup, so set it up.
- Our check can spot a consent banner but not whether it holds tracking back, so confirm on a fresh visit that nothing tracks before a visitor says yes.
Privacy and policies
No cookie consent banner found
Cookies and tracking scripts appear to run before a visitor has made any consent choice, which some privacy laws forbid.
Fix with your agent
# SiteCMD Fix Brief: No cookie consent banner found Site: https://yoursite.com ## What is wrong Cookies and tracking scripts appear to run before a visitor has made any consent choice, which some privacy laws forbid. ## How to fix Inventory which cookies, storage, and vendor requests actually fire before and after interaction, and confirm with your privacy owner which jurisdictions and purposes require prior consent; the answer is not universal. Where consent is required, gate scripts at the real execution boundary, not with a banner alone, and verify each choice by inspecting Network and Storage on fresh visits. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Learn how browsers send an opt-out signal and which state laws require honoring it.
How to fix
- Do Not Track and Global Privacy Control are browser settings that ask sites not to track someone, and some laws treat Global Privacy Control as a real request to opt out.
- With your privacy or legal advisor, decide what your site should stop doing for each signal, and make that change using the steps below.
- In your privacy policy, describe what your site really does with these signals, without promising more.
- Our check only looks for a mention of these signals on the page itself, so confirm the fix by testing the site with Global Privacy Control turned on and off.
Privacy and policies
No sign the site honors browser privacy signals
This site does not appear to change its behavior for a visitor's Do Not Track or Global Privacy Control signal.
Fix with your agent
# SiteCMD Fix Brief: No sign the site honors browser privacy signals Site: https://yoursite.com ## What is wrong This site does not appear to change its behavior for a visitor's Do Not Track or Global Privacy Control signal. ## How to fix Separate the signals: DNT is generally a voluntary browser preference, while GPC can be a legally recognized opt-out for covered businesses in some jurisdictions. Determine which activities each recognized signal must change, process it at server, tag-manager, and SDK boundaries rather than checking one browser property, and describe the actual behavior in the privacy notice without promising more than the implementation does. Test requests with and without Sec-GPC. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Explain how your website uses personal data
1 guide
Find out what makes a website need a privacy policy, and what the policy should cover.
How to fix
- List what your site collects, such as form entries, accounts, payments and analytics, and which outside services receive it.
- Write a privacy policy that matches that list, usually covering who you are, how to reach you, why you collect it, who gets it, how long you keep it and what rights visitors have.
- Have a privacy or legal advisor review it, then publish it and link to it from your site's footer or menu.
- Then run the check again.
Privacy and policies
No privacy policy link found
This site has no privacy policy telling visitors what data it collects and why, which most privacy laws require.
Fix with your agent
# SiteCMD Fix Brief: No privacy policy link found Site: https://yoursite.com ## What is wrong This site has no privacy policy telling visitors what data it collects and why, which most privacy laws require. ## How to fix Confirm which privacy laws apply and inventory the data the site actually collects across forms, accounts, logs, analytics, payments, and vendors. Publish a notice that matches that reality (identity and contact, purposes, recipients, retention, and user rights to the extent the governing rules require), avoid templates naming tools you do not use, link it from persistent navigation, and have the privacy or legal owner review it. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Do cookie rules cover tracking pixels and other trackers?
| Where | What the rules cover | Source |
|---|---|---|
| EU | The consent rule for storing or reading information on a visitor's device isn't limited to cookies. EDPB guidelines apply it to tracking pixels and tracking links, even when nothing is stored for long. | EDPB Guidelines 2/2023 |
This information isn't legal advice. Consult a lawyer about the requirements that apply to your organization.
Frequently asked questions
Can a GDPR checker tell me whether my website is compliant?
No. The EDPB's cookie banner taskforce notes that cookie scanning tools can list the cookies a site sets but can't check their nature, and whether a cookie needs consent depends on what it's for.
What should I do when a website privacy checker flags a cookie or tracker?
Find the script or setting that sets it and who added it. Then decide whether you still need it before changing your banner or your policy.