Resources · Tool · Free, no email · Updated
SITE AND TRACKING HEALTH CRAWLER
Run a bounded scan after a launch, a redesign handover, or when the channel numbers stop agreeing with each other. It reads public pages and reports dead paths, head problems and which tracking snippets are actually present, in language you can forward to a developer.
How it works
- Enter the site address, or the section you changed.
- Choose how far the scan goes and what you want reported.
- Run it and wait. It reads a bounded number of public pages and then stops.
- Send the high items to whoever owns the code, and read the limits before you draw a conclusion.
Findings will appear here after a scan.
Send the high items first, as written. If the problem turns out to sit across tools rather than on the site, the MarTech stack audit is the wider inventory, and the AI visibility checker is the one to run if the question is whether assistants can read and cite you.
Automated checks on publicly reachable pages, not a guarantee of tracking correctness, privacy compliance or security. This is not a penetration test and it does not attempt to bypass anything. robots.txt is respected. Confirm every finding in your own tag manager, analytics and consent tool before acting on it.
Goes well with
You are probably paying for software nobody logs into.
Get the worksheetIf you would rather have this done with you than to you, this is the work I do. See services
Run it the day after a launch
The expensive version of this problem is the fortnight nobody notices. A template ships without the container, a page is renamed without a redirect, a canonical points at http, and the reporting quietly undercounts while everyone argues about channel performance. A scan the day after a change costs a few minutes and catches the ones that would otherwise be found in a monthly report, by which point the month is gone.
Inconclusive is a real answer
Tags loaded by a consent tool, injected by the tag manager itself, or fired server-side will not show up in served HTML. That is why this tool says not detected rather than not installed, and why the limits are printed under every result. It reads public pages, respects robots.txt, and does not attempt anything a security scanner would. If the question is whether AI assistants can read and cite you, the visibility checker answers that one instead.
COMMON QUESTIONS
Will this log in to my analytics?
No. It reads publicly reachable pages and reports which tracking snippets appear in the HTML that was served. It has no access to your analytics, your tag manager or your accounts.
Is this a security scan?
No. It does not test for vulnerabilities, it does not attempt to bypass anything, and it should not be used as a penetration test.
Why is the number of pages limited?
To keep it fast, free and hard to abuse. It reads up to twenty-five pages in quick mode and up to sixty in standard, then stops and says so.
It says no tag manager was detected, but we have one. Why?
Most often because the tag loads after the page renders, or through a consent tool. Check in your tag manager preview before treating it as a fault. That is why the result is worded as not detected.
Do I need to give my email?
No. The scan is free and there is no form.