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.
À propos de l’outil
Gratuit, sans inscription. Explorez jusqu’à 150 pages HTML de même origine, vérifiez jusqu’à 100 ressources, regroupez les constats SEO du HTML brut et exportez des preuves bornées.
Fonctionnalités
- Exploration par racine ou sitemap avec contrôles robots, protections contre les pièges et prise en charge de l’interruption.
- Jusqu’à 150 pages HTML et 100 contrôles de ressources limités au statut.
- Constats groupés de page, interpages et ressources avec couverture séparée.
- Exports CSV de pages, liens, redirections, ressources et problèmes, plus instantanés bornés imprimables et comparables.
Fonctionnement
Une file protégée explore les pages HTTPS de même origine depuis une racine ou un sitemap borné, vérifie robots, normalise les liens et plafonne les motifs de piège. Chaque réponse brute exploitable devient un enregistrement pour les détecteurs déterministes. Le récapitulatif conserve la couverture d’évaluation et produit des preuves exportables.
Limites
- L’exploration est bornée, limitée au HTML brut et à la même origine exacte ; elle ne prouve pas la couverture complète ni le statut orphelin.
- Les contrôles de ressources n’analysent pas les corps de fichiers ni les ressources tierces.
- Scout ne rend pas JavaScript, ne s’authentifie pas, n’exécute pas de contrôles IA, n’appelle pas GSC et n’imite pas l’index d’un robot de recherche.
Questions fréquentes
Qu’est-ce que le score du site en HTML brut ?
C’est un score d’état technique fondé sur l’impact et l’ampleur des pages concernées par les problèmes évalués dans l’échantillon borné ; ce n’est ni un score Google ni une mesure complète de la qualité du site.
L’audit rend-il le JavaScript ?
Non. Les constats utilisent le HTML brut récupéré ; le contenu et les liens rendus par JavaScript ne sont pas évalués.
Combien de pages et de ressources vérifie-t-il ?
Il récupère jusqu’à 150 pages HTML de même origine exacte et vérifie le statut de jusqu’à 100 ressources HTTPS extraites du HTML brut complet. Les couvertures sont rapportées séparément.
Respecte-t-il robots.txt ?
Oui, le robot applique les règles Allow et Disallow à sa politique d’exploration. Il ne respecte pas crawl-delay, comme indiqué dans la note de périmètre.
Puis-je comparer des audits au fil du temps ?
Oui. Exportez un instantané JSON local borné et importez-le après une autre exécution ; les variations de couverture peuvent affecter la comparaison.