Crawl Export Comparator
Free, no signup. Compare two crawl exports without forcing unlike vendor issue taxonomies into fake equivalence. Shared page evidence is normalized; unmapped columns and incomplete crawl coverage remain visible.
Runs entirely in your browser — nothing you paste is uploaded or stored. Both files stay in your browser. Files over 15 MiB and rows beyond the 100,000-row comparison cap are rejected or reported as truncated. 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 output-shape example
5 changed URLs · 2 added · 2 removed · 1 field-changed
/products/:number — 1 added, 1 removed; verify whether product IDs changed or the crawl scopes differed.
https://example.com/ — meta description and word count changed.
This illustrates the report structure. It is not a live observation or a claim that every difference is a defect.
Changes by path template
Changed URLs
| State | URL | Template | Changed evidence |
|---|
How to use it
- Export page-level CSV or TSV files from the before and after crawls.
- Use comparable crawl scope, robots, rendering, authentication, and limits.
- Load both files and review the detected vendor, mapped fields, ignored columns, invalid URLs, duplicates, and caps.
- Triage inventory changes by path template, then inspect field changes per URL.
- Export the normalized change list and verify important regressions in the source crawlers or on the live pages.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
How it works
The browser parses quoted CSV or TSV, detects known vendor headers, normalizes public HTTP(S) URLs, and keeps the last row when an export contains duplicate URLs. Only fields present in both exports are compared. Numeric evidence is compared numerically; canonicals and content types receive bounded normalization. The path-template rollup replaces only numeric IDs, UUIDs, and long hexadecimal segments.
What the results mean
- Added — the normalized URL appears only in the after export.
- Removed — it appears only in the before export.
- Changed — at least one mutually mapped evidence field differs.
- Ignored column — the source data is preserved in the original file but is not given cross-vendor meaning here.
Limitations
Different crawl configurations are the largest confounder. This tool does not reproduce rendering modes, authentication, robots behavior, custom extraction, vendor scoring, crawl scheduling, or site completeness. It does not infer that two differently named vendor checks mean the same thing. Template grouping is path-shape grouping, not a learned CMS template classification. The report is triage evidence, not proof of a regression.
Frequently asked questions
Which crawl exports can I compare?
The tool recognizes common page-export headers from Screaming Frog, Sitebulb, Scout Site Audit Free, and generic CSV or TSV files. It needs a URL column and compares only fields recognized in both files.
Are vendor issue names treated as equivalent?
No. Vendor-specific issue taxonomies can have different definitions and thresholds. The comparator normalizes shared page evidence such as status, indexability, title, canonical, H1, word count, depth, and inlinks. Issue labels are compared as literal sorted text only when both files provide them.
Does an added or removed URL prove a crawlability change?
No. A URL can appear or disappear because of crawl scope, limits, authentication, robots rules, settings, or a real site change. Confirm comparable crawl configurations before treating inventory differences as regressions.
Are the exports uploaded?
No. Parsing, normalization, comparison, filtering, and CSV export happen in your browser. The selected files are not sent to this site.
How are path templates created?
The grouping replaces numeric IDs, UUIDs, and long hexadecimal tokens in path segments. It is a deterministic triage aid, not a CMS-aware template detector.
Feature requests for Crawl Export Comparator
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.
Sobre a ferramenta
Grátis, sem cadastro. Compare dois rastreamento exports sem forcing unlike vendor problema taxonomies em fake equivalence. Shared página evidência é normalized; unmapped columns e incompleto rastreamento coverage permanecem visible.
Normalize e compare dois Screaming Frog, Sitebulb, Scout, ou generic rastreamento exports locally por URL, campo, e caminho template.
Recursos
- O ferramenta recognizes comum page-export cabeçalhos de Screaming Frog, Sitebulb, Scout Site Auditar Gratuito, e generic CSV ou TSV files. Isso precisa um URL column e compares somente campos recognized em both files.
- O navegador parses quoted CSV ou TSV, detects known vendor cabeçalhos, normalizes público HTTP(S) URLs, e keeps o last linha quando um exportar contains duplicate URLs. Somente campos present em both exports são comparado. Numeric evidência é comparado numerically; canonicals e conteúdo tipos receive limitado normalization. O path-template rollup replaces somente numeric IDs, UUIDs, e long hexadecimal segments.
- Adicionado — o normalized URL aparece somente em o depois exportar. Removido — isso aparece somente em o antes exportar. Changed — em least um mutually mapeado evidência campo differs. Ignored column — o origem dados é preserved em o original file but é não given cross-vendor meaning here.
- Mostrar todas alterações adicionado URLs removido URLs campo alterações
Como funciona
O navegador parses quoted CSV ou TSV, detects known vendor cabeçalhos, normalizes público HTTP(S) URLs, e keeps o last linha quando um exportar contains duplicate URLs. Somente campos present em both exports são comparado. Numeric evidência é comparado numerically; canonicals e conteúdo tipos receive limitado normalization. O path-template rollup replaces somente numeric IDs, UUIDs, e long hexadecimal segments.
Limitações
- Different rastreamento configurações são o largest confounder. Este ferramenta faz não reproduce rendering modes, autenticação, robots comportamento, custom extraction, vendor scoring, rastreamento scheduling, ou site completude. Isso faz não infer que dois differently nomeadas vendor verificações mean o mesmo thing. Template grouping é path-shape grouping, não um learned CMS template classification. O relatório é triage evidência, não prova de um regression.
- Não. Um URL pode aparecer ou disappear porque de rastreamento escopo, limites, autenticação, robots rules, settings, ou um real site alteração. Confirm comparável rastreamento configurações antes treating inventory differences como regressions.
Perguntas frequentes
Que rastreamento exports pode I compare?
O ferramenta recognizes comum page-export cabeçalhos de Screaming Frog, Sitebulb, Scout Site Auditar Gratuito, e generic CSV ou TSV files. Isso precisa um URL column e compares somente campos recognized em both files.
São vendor problema names treated como equivalente?
Não. Vendor-specific problema taxonomies pode têm different definitions e thresholds. O comparator normalizes shared página evidência such como status, indexability, título, canonical, H1, word count, depth, e inlinks. Problema labels são comparado como literal sorted texto somente quando both files fornecer them.
Faz um adicionado ou removido URL prove um crawlability alteração?
Não. Um URL pode aparecer ou disappear porque de rastreamento escopo, limites, autenticação, robots rules, settings, ou um real site alteração. Confirm comparável rastreamento configurações antes treating inventory differences como regressions.
São o exports uploaded?
Não. Parsing, normalization, comparação, filtering, e CSV exportar acontecer em seu navegador. O selecionado files são não sent para este site.
Como são caminho templates created?
O grouping replaces numeric IDs, UUIDs, e long hexadecimal tokens em caminho segments. Isso é um determinístico triage aid, não um CMS-aware template detector.