Scout Site Audit Free
Free, no signup. Crawl up to 150 exact-origin HTML pages, then check response status and headers for up to 100 exact-origin assets. Group raw-HTML SEO findings, inspect affected URLs, and export Pages, Links, Redirects, Assets, or Issues CSVs.
Manual URL seeds and local watchlists
Configurations and up to ten previous run summaries stay in this browser. Nothing runs on a schedule or in the background. Do not put secrets in URLs.
Checks run from our server; we fetch the URL you enter and don't keep the results. Up to 150 public HTML pages and status/header evidence for up to 100 exact-origin assets are retrieved through bounded, rate-limited proxies. Asset bodies are cancelled and never retained. Results stay in this browser unless you export them. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report Static report-shape example
82/100 raw-HTML site score
Crawled 24 of 31 discovered URLs (partial — page cap or policy exclusions would be named here).
title/missing · warn · 2 affected · checked on 24/24
Not evaluated: rendered JavaScript and AI checks.
This is illustrative output, not an audit of a real site and not a search-engine score.
How to use it
- Enter an HTTPS root, or an XML sitemap and select the sitemap option.
- Complete the anti-abuse check and start the bounded page crawl and asset-status phase.
- Read page and asset coverage separately, then expand issue rows.
- Export Pages, Links, Redirects, Assets, or Issues CSV evidence, print, or save a bounded snapshot.
- Use Page Report for a deeper single URL; Smart JS and Full Render are the rendered tiers.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Audit dashboard
Affected share uses detector-page pairs where each check had enough evidence. Crawl depth uses the bounded pages observed in this run.
Issues by category
Crawl depth
Segment × issue matrix
Cells show observed affected URLs inside each inferred URL cohort. A zero means no finding was observed in the bounded cohort, not that every possible check passed.
Site-wide and asset findings
These findings depend on relationships across pages, crawl inventory, or asset responses, so they appear before the page-detector ledger.
Audit comparison
Detector changes
Inferred cohort changes
Pages
Links
Redirects
Assets
Page checks by category
Problems is the default view. All checks adds passes, notices, and checks that lacked enough evidence.
Scout only scores evidence-backed problems whose likely intent and consequence can be established from this bounded raw-HTML crawl. Configuration choices, informational opportunities, uncertain intent, and missing evidence stay visible without becoming penalties. “Not evaluated” never means “passed.”
Outside this tier: rendered JavaScript, authenticated pages, and AI checks are intentionally not run. Smart JS and Full Render are the rendered tiers.
Rate this tool
What the results mean
- Coverage — completed pages versus discovered inventory, with caps, aborts, exclusions, and trap sampling exposed.
- Severity — detector-level pass/warn/fail prioritization.
- Affected — pages with a non-pass finding among the pages where that detector ran.
- Not checked / unavailable — missing evidence or deliberately excluded detector classes.
- Cross-page findings — issues requiring crawl inventory or link relationships rather than one page.
How it works
A protected queue crawls exact-origin HTTPS pages from a root or bounded sitemap inventory, checks robots policy, normalizes discovered links, and caps trap patterns. Each usable raw response becomes a page record for deterministic detectors. The rollup preserves evaluation coverage and creates exportable issue evidence.
Features
- Up to 150 fetched raw-HTML pages plus 100 status-only asset checks with abort support.
- Root or sitemap seeding, robots checks, crawl-trap guards, and bounded asset extraction.
- Grouped page, cross-page, and asset findings with separate coverage.
- Pages, Links, Redirects, Assets, and Issues CSVs plus printable and comparable bounded snapshots.
Limitations
The crawl is bounded, raw-HTML only, and exact-origin; it cannot prove full site coverage or orphan status from a root crawl. Asset checks do not download or analyze file bodies, calculate transferred bytes, or evaluate third-party resources. Scout does not render JavaScript, honor crawl-delay, authenticate, run AI checks, call GSC, or emulate a search crawler’s index. Security findings are conservative review prompts, not proof that a site is exploitable.
Frequently asked questions
How many pages and assets does Scout Site Audit Free check?
It fetches up to 150 exact-origin HTML pages, then runs status-only checks for up to 100 exact-origin HTTPS assets extracted from complete raw HTML. Page and asset coverage are reported separately.
Does the audit render JavaScript?
No. Findings use fetched raw HTML. JavaScript-rendered content and links are explicitly not evaluated.
Does it obey robots.txt?
The page crawler applies Allow and Disallow rules for its crawl policy. This tool does not honor crawl-delay, which it states in the scope note.
What is the raw-HTML site score?
It is a technical condition score derived from the impact and affected scale of evaluated, score-eligible page issues in the bounded sample. Asset findings are reported separately. It is not a Google score or a complete measure of site quality.
Can I compare audits over time?
Yes. Export a bounded local JSON snapshot and import it after another run. Coverage shifts can affect the comparison.
Feature requests for Site Audit Lite
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Über das Tool
Crawle bis zu 150 exakte Same-Origin-HTML-Seiten und prüfe anschließend bis zu 100 exakte HTTPS-Assets nur auf Status und Header. Scout gruppiert Raw-HTML-SEO-Befunde, hält Seiten- und Asset-Abdeckung getrennt und exportiert Pages-, Links-, Redirects-, Assets- oder Issues-CSV sowie begrenzte Snapshot-/Befundpakete.
Der Crawl ist begrenzt und rendert kein JavaScript; ein technischer Condition-Score ist keine Google-Bewertung und keine vollständige Site-Qualitätsmessung.
Funktionen
- Bis zu 150 Raw-HTML-Seiten plus 100 Status-only-Asset-Prüfungen
- Root- oder Sitemap-Seeding, Robots-Prüfung, Crawl-Trap-Schutz und begrenzte Asset-Extraktion
- Gruppierte Seiten-, seitenübergreifende und Asset-Befunde mit separater Coverage
- CSV-Exporte, druckbare und vergleichbare begrenzte Snapshots
Funktionsweise
Gib eine HTTPS-Root- oder XML-Sitemap-URL ein oder nutze bis zu 150 optionale Same-Origin-Seeds. Schließe den Anti-Abuse-Check ab und starte Seiten-Crawl sowie Asset-Statusphase. Lies Seiten- und Asset-Coverage getrennt, öffne Issue-Zeilen und exportiere gewünschte CSVs oder einen begrenzten Snapshot. Nutze Page Report für eine tiefere Einzel-URL; Smart JS und Full Render sind gerenderte Tiers.
Einschränkungen
- Root-Crawls beweisen weder vollständige Site-Abdeckung noch Orphan-Status; Assets werden nicht heruntergeladen und Dateibodies, Bytes oder Drittanbieter nicht ausgewertet.
- Scout rendert JavaScript nicht, berücksichtigt keinen Crawl-delay, authentifiziert nicht, führt keine KI-Checks aus, ruft GSC nicht auf und emuliert keinen Suchcrawler.
- Sicherheitsbefunde sind konservative Review-Hinweise und kein Beweis, dass eine Website ausnutzbar ist.
Häufig gestellte Fragen
Wie viele Seiten und Assets prüft Scout Site Audit Free?
Es ruft bis zu 150 exakte Same-Origin-HTML-Seiten ab und prüft anschließend bis zu 100 exakte Same-Origin-HTTPS-Assets nur auf Status. Seiten- und Asset-Coverage werden getrennt berichtet.
Rendert das Audit JavaScript?
Nein. Befunde basieren auf abgerufenem Raw-HTML; JavaScript-gerenderter Inhalt und Links sind ausdrücklich nicht bewertet.
Befolgt es robots.txt?
Ja. Die Seiten-Queue wendet Allow- und Disallow-Regeln für ihre Crawl-Policy an. Crawl-delay wird nicht berücksichtigt, was im Scope-Hinweis genannt wird.
Kann ich Audits über die Zeit vergleichen?
Ja. Exportiere einen begrenzten lokalen JSON-Snapshot und importiere ihn nach einem weiteren Lauf. Verschiebungen in der Coverage können den Vergleich beeinflussen.