Is the audit free? Do I need to sign in? Why do I see fewer trackers than my tag manager shows? Answers to common questions.
Yes — during the beta period every audit is free, with no credit card and no trial clock. A paid tier with higher limits, API access, and scheduled audits is planned, but it doesn't exist yet.
No. Anyone can run an audit anonymously. Google sign-in adds per-user run history so you can find and revisit past audits; every run (signed-in or not) is logged to our usage sheet for capacity planning. See your data and deletion below for how runs are stored.
Any public domain. The tool only fetches publicly accessible pages — it never attempts logins, never submits forms, and respects robots.txt directives including Crawl-delay. If a page blocks the crawler (403) or is dead (404), the report marks it honestly rather than guessing.
The default scan is static: it fetches each page's HTML and pattern-matches it. Trackers deployed through tag managers (Google Tag Manager, Tealium, Segment, and the like) are injected at runtime by JavaScript, so they don't appear in the static HTML. Tick Browser-render pages for a headless-Chromium render that executes the JavaScript and catches runtime-injected trackers — it's slower, but it's the only way to see them. We explain this in detail in why static scans miss trackers.
Instead of fetching raw HTML, the crawler loads each page in headless Chromium and scans the rendered DOM plus network requests. One browser is used per audit and pages render sequentially, so large audits take noticeably longer. Static fallback applies if rendering fails on a page.
Yes. The crawler reads robots.txt at the start of every audit, follows it to discover sitemap locations, and honors Crawl-delay. It also uses rotating realistic browser user-agent strings and randomized delays between requests. No IP rotation is used. More on robots.txt and this crawler.
The Max pages setting (default 5,000, up to 200,000) is shared by the domain and all discovered subdomains. Parent-domain sitemap URLs get priority; subdomain URLs fill the remainder. This keeps one sprawling subdomain from eating the whole budget.
Audit results (pages table, beacon table, job metadata) are stored on our server so you can view and download them. Every run is also logged to a usage sheet with the domain, timestamp, and requestor for capacity planning. You can delete a run at any time with the delete button on its job page; deleted runs are removed from the server and marked deleted in the usage log.
No. The pipeline is fully deterministic — URL enumeration, HTTP checks, and regex signature matching. Zero LLM or AI tokens are consumed per run, which is why results are repeatable and cheap to re-run.
Digital Interactif. Questions, bug reports, or feature requests go to the contact page on the main site.