When to use this
The compliance scanner at /scanner analyzes a public URL without requiring the runtime script. It is ideal for first-touch audits, competitive reviews, and periodic health checks on sites you do not manage. Free, Pro, and Growth plans all include publicScanner access; managed runtime features are separate.
Run a scan before signing up to demonstrate value to stakeholders, or after go live to see whether public view matches your protected configuration. Pro adds public/private scan comparison when you own the site—telemetry in the dashboard contrasts with what anonymous scanners see.
Scans are not legal opinions. They highlight technical signals: third-party scripts, consent banner presence, policy URLs, cookie behavior, and scoring heuristics tuned for GDPR-oriented website compliance.
Scan the URL your customers actually land on—`/blog` paths sometimes omit tags present only on homepage templates. For international sites, run scans per locale path if hreflang routes serve different heads.
Combine scanner output with Records of Processing Activities maintenance: findings tell you what fires on the wire, not whether you have lawful basis documented internally.
Saved reports support security questionnaire workflows—attach scan id and date in responses to vendor risk portals when asked for cookie or tracking evidence.
Step-by-step instructions
- Navigate to /scanner from the marketing site or dashboard link.
- Enter a full URL including https:// and optional path to scan a specific landing page.
- Start the scan and wait for the job to complete—large tag-heavy pages take longer.
- Review the compliance score summary and category breakdown at the top of the report.
- Expand tracker and script sections to see domains loaded before interaction.
- Check consent and policy sections for banner detection and link reachability.
- Export or share the report link if your workflow needs a ticket attachment.
- For sites you own on Pro, open dashboard scans to compare with runtime diagnostics.
- Create remediation tasks: install runtime, fix policies, or adjust banner per failed checks.
Expected result
You receive a structured report with score, findings list, and evidence snippets suitable for prioritization. Repeat scans over time show whether changes helped. Managed site owners use failures to drive setup wizard work; external sites may only be fixable by their operators.
Authenticated users may see scan history in dashboard depending on feature flags; anonymous users still get one-off reports.
Establish a cadence—weekly for high-change marketing sites, monthly for stable brochures—to detect tag sprawl early. Pair each scan review with owner assignment: engineering for blocking, marketing for banner copy, legal for policy updates.
Troubleshooting
Scan timed out or failed
Confirm the URL is publicly reachable without bot challenges. Reduce scope to homepage if deep paths hang on infinite scroll. Retry after outages; extremely large single-page apps may exceed limits—try canonical marketing URL.
Score differs from competitor tools
Each scanner uses different weights. Read individual findings rather than chasing an identical number. See External scanner results help for mapping Cookiebot and similar outputs.
Protected site still scores low publicly
Public scan does not see owner-only runtime signals until tags are on the page. Verify script install and go live, then rescan. Some fixes are visible only after cache clears globally.