Enter any public domain and get a full site-map inventory plus a tracker beacon scan — here's exactly what happens, step by step.
example.com) into the audit form. Choose a discovery mode, adjust the page budget if you want, and optionally enable browser rendering or subdomain discovery. Nothing to install, no sign-in required to run an audit.robots.txt, follows it to the sitemap.xml files, and recursively expands sitemap indexes into the full list of known URLs. In Sitemaps + link crawl mode it also follows internal links breadth-first to catch pages missing from the sitemap. When Include subdomains is on, subdomains are discovered first (see subdomain discovery) and each gets the same sitemap treatment.The default scan is static: it fetches each page over HTTP and pattern-matches the HTML. That misses trackers injected at runtime by JavaScript — most commonly tags deployed through Google Tag Manager, which only load after scripts execute. Ticking Browser-render pages runs each page through headless Chromium (one browser per audit, pages rendered sequentially, so it's slower) to catch those runtime-injected trackers. We disclose this limitation openly because it determines what the numbers mean — see why static scans miss trackers.
Every audit uses rotating realistic browser user-agent strings, randomized delays between requests, and honors Crawl-delay from robots.txt. No IP rotation is used — the tool stays within a single egress and behaves like a well-mannered browser. More on what the crawler honors.
The audit is fully deterministic: URL enumeration, HTTP checks, and regex signature matching. Zero LLM or AI tokens are consumed per run, so results are repeatable and free to scale.