Internal Link Cluster Visualizer
Free, no signup. Turn a crawl export, page inventory, or a bounded raw-HTML crawl into a navigable link map. See observed internal authority, root reachability, and explainable missing-link opportunities.
Use the explicit “Export graph for Cluster Visualizer” download in Scout Site Audit Free. The JSON is read locally and is never embedded in a URL or stored in this browser.
Accepted columns and pipe format
Edge CSV: Source,Destination, source,target, or a Screaming Frog All Outlinks export. Optional Source Entities and Target Entities columns accept semicolon-separated names. Quoted values and extra columns are accepted. A headerless two-column CSV also works.
Page inventory: one row per page as URL | title | comma-separated terms | comma-separated linked URLs | optional entities. This format can represent a page with no links, so orphan checks are possible.
Runs entirely in your browser — nothing you paste is uploaded or stored. Supplied graph and entity columns are analyzed in this browser. This mode never crawls, calls an AI model or knowledge graph, or writes links. 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.
Scope: up to 150 fetched same-host pages and 1,000 discovered URLs, raw HTML only, one request at a time and at most 0.5 request starts per second, with shared URL normalization, robots Allow/Disallow checks, and crawl-trap guards. A root crawl cannot prove a page is an orphan. A sitemap is only the inventory it contains; it is not proof of every site page.
Checks run from our server; we fetch the URL you enter and don't keep the results. Public pages are fetched through the bounded shared crawler. The graph stays in this browser tab unless you export it. 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.
Need detector-based technical findings too? Run the same site through Scout Site Audit Free. Want to compare link structure with semantic structure? Explore the public Semantic Site Map case study.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Graph evidence
Internal-link map
Node size = PageRank. Color = evidence-based segment. Drag or select a node for evidence.
Page evidence
Metrics describe only this graph. PageRank is normalized within this input.
Possible missing links
The published score keeps lexical overlap, segment fit, PageRank and target deficit primary. Shared entity evidence can contribute at most 10% of topical strength. Every row is review/export only and means only that the source→target edge was not observed in this analyzed graph.
| Entity evidence | Graph evidence and reasons |
|---|
Need page-level technical findings for this crawl? Run Scout Site Audit Free on the same root.
Want to keep exploring without another request? . It keeps the observed edges locally; crawl coverage and raw-HTML limits still apply.
Rate this tool
How to use it
- Use supplied mode for a page inventory or edge export; use crawl mode for a bounded public raw-HTML graph.
- Choose the correct parser or let the tool detect it, then analyze the graph.
- Select the click-depth root and read coverage warnings before metrics.
- Use the map for patterns, the table for exact evidence, and the suggestion table for human link review.
- Export page evidence and suggestions when you need an auditable handoff.
Example result Built-in page-inventory example
The built-in seven-page inventory includes a homepage, four editorial pages, a tool, and an About page. The deterministic analysis reports 7 supplied pages, 7 unique internal links, root click depths, normalized PageRank, and evidence-based segments. The unlinked “Topic cluster strategy” row can be evaluated as an orphan because pipe format explicitly supplies the complete example inventory.
These counts describe the included fixture only; they are not a live site measurement.
What the results mean
- PageRank — relative link equity normalized within this graph.
- Click depth / unreachable — shortest observed path from the selected root, or no observed path.
- Orphan — evaluated only when the supplied inventory can represent pages with no edges.
- Entity evidence — a shared supplied name or bounded local title/heading heuristic, shown separately with provenance.
- Missing-link score — transparent lexical, segment, modest entity-overlap, and graph-deficit factors, not a requirement.
How it works
The parser normalizes up to 250 supplied pages and 3,000 edges, or the bounded crawler collects up to 150 raw-HTML pages from 1,000 discovered URLs. Graph analysis deduplicates edges, calculates iterative normalized PageRank and shortest root paths, groups pages from URL/term evidence, and scores absent observed edges. Entity overlap contributes at most 10% of topical strength; no bulk AI or knowledge-graph request occurs.
Features
- Pipe inventory, generic edge CSV, optional entity columns, and Screaming Frog outlink support.
- Bounded exact-host root or sitemap crawl with robots and trap controls.
- Interactive canvas plus accessible sortable evidence tables.
- Normalized PageRank, click depth, reachability, segment counts, and scoped orphan state.
- Explainable review-only missing-link suggestions and two CSV exports; no link writes.
- Handoff to Semantic Site Map for a public example of semantic clusters, which are deliberately kept distinct from this tool's observed links and lexical/entity clues.
Limitations
Supplied graphs are only as complete as the input. Root crawls cannot discover isolated pages, sitemap crawls cover only the inventory supplied, and raw HTML omits JavaScript links. PageRank is internal to this graph; entity names can be ambiguous; and suggestions do not inspect paragraph context. “Existing-link absence” means absent from this analyzed graph only. Crawl caps, redirects, policies, or trap sampling can make all results partial.
Does this tool crawl my website?
Supplied-graph mode never makes a request. Crawl mode retrieves up to 150 public same-site raw-HTML pages through the bounded shared crawler; it does not render JavaScript or write to the audited site. Results remain in this tab unless you export them.
Can an outlinks export identify orphan pages?
Not by itself. A page with no links may be absent from an outlinks export entirely. Orphans are evaluated only for the pipe-format page inventory, and the selected crawl root is never called an orphan merely because nothing links to it.
Are the segments semantic topic clusters?
No. The segments use visible URL directories first and supplied or derived lexical terms only when a directory is unavailable. They are navigation evidence, not an embedding or search-engine interpretation.
What does PageRank mean in this report?
It is normalized only within the supplied or bounded observed graph. It helps compare nodes in that input and is not Google PageRank or an external authority metric.
Should I add every suggested missing link?
No. Suggestions combine lexical/segment overlap with visible graph deficits. Add a link only when the source passage gives readers a natural reason to visit the target.
Feature requests for Cluster Visualizer
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.
Informazioni sullo strumento
Visualizza gruppi di query e pagine per individuare temi, sovrapposizioni, lacune e opportunità di struttura dei contenuti.
Funzionalità
- Importazione di query o URL con colonne riconosciute.
- Cluster e relazioni visualizzati con filtri leggibili.
- Riepilogo di sovrapposizioni, pagine isolate e temi scoperti.
- Elaborazione locale e export dei risultati sanificati.
Come funziona
Carica dati strutturati o incolla righe, controlla le colonne riconosciute e genera la vista. Esamina gruppi e outlier prima di decidere una struttura editoriale.
Limitazioni
- Un cluster è un’ipotesi basata sui dati forniti, non una tassonomia editoriale definitiva.
- La visualizzazione non prova intento, ranking, conversione o qualità senza revisione del contesto.
Domande frequenti
I cluster sono automaticamente corretti?
No. Sono raggruppamenti da interpretare e validare con intento, pubblico e contenuto reale.
Posso usare solo le query per decidere le pagine?
Usale come evidenza, ma verifica sovrapposizione, intento e copertura prima di creare o unire pagine.
Il file viene caricato?
L’elaborazione del file selezionato avviene localmente nella scheda; condividi solo export sanificati.