Link Analyzer
Free, no signup. Find crawlable links, images, stylesheets, and scripts on one page. Review structural anchor patterns first, then optionally batch-check the extracted URLs.
Checks run from our server; we fetch the URL you enter and don't keep the results. The page URL and, only when you choose status checks, its extracted public resource URLs are fetched; nothing is stored. 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
Illustrative example — deterministic output for the HTML below
<a href="/pricing">Learn more</a>
<a href="/support">Learn more</a>
<a href="#">Contact us</a>
<img src="/images/product.webp" alt="Product dashboard">- Warning: 1 non-navigational link —
href="#". - Warning: “learn more” points to two different targets.
- Info: 2 generic anchor-text labels.
- Extracted: three links and one image, with source line and resolved URL. HTTP statuses remain unchecked until requested.
How to use it
- Enter one public page URL and choose Analyze page.
- Review structural findings before checking network status; they come directly from the page source.
- Inspect each extracted URL, resource type, and source location.
- Choose Check HTTP status only when you also need live response evidence for the extracted destinations.
+ 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.
Structural findings
Extracted URLs
Rate this tool
What the results mean
Warnings identify concrete ambiguity or non-navigation. Info marks patterns that need human context. A clean structural report means none of the implemented anchor rules fired; it does not prove every link is useful. Status numbers are live network observations, while a missing status or network error is not treated as a pass.
How it works
The page fetch returns raw HTML. A local extractor reads a, img, link, and script elements, resolves eligible relative URLs against the final page URL, and records source line and column. Anchor rules compare labels, targets, and rel values. Optional checks deduplicate public URLs and send batches of at most 25 to the status endpoint.
Features
- Links, images, stylesheets, and scripts in one inventory.
- Generic, empty, conflicting-label, and internal-nofollow findings.
- Source locations for faster template debugging.
- Opt-in, deduplicated status checks for up to 250 extracted items.
Limitations
This is a single-page raw-HTML audit, not a site crawler or rendered-DOM analyzer. It does not score PageRank, judge the editorial quality of a link, discover links created by JavaScript, or prove that a 200 response contains the expected content. Status checks can also be blocked or rate-limited by destination servers. Use Render Gap to compare links added after JavaScript runs →
Frequently asked questions
Does the Link Analyzer crawl my whole website?
No. It extracts links and resources from one page. Optional status checks request only the unique public URLs found on that page, in bounded batches.
What counts as a generic anchor?
Short labels such as “click here,” “read more,” and “learn more” are flagged because they provide little destination context when read alone.
Are internal nofollow links always wrong?
No. They are shown as informational findings for review. Nofollow may be intentional, but routinely using it on ordinary internal navigation can make the linking strategy harder to understand.
Why are some links missing from the report?
The analyzer reads raw HTML and does not execute JavaScript. Links inserted after rendering, links hidden inside application state, and resources beyond the 250-item display cap are not included.
Feature requests for Link Analyzer
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
Analysez une page publique pour inventorier ses liens et ressources, repérer les ancres ambiguës et vérifier facultativement les statuts HTTP par lots.
Fonctionnalités
- Liens, images, feuilles de style et scripts réunis dans un même inventaire.
- Constats sur les ancres génériques, vides, contradictoires et les liens internes en nofollow.
- Emplacements dans la source pour accélérer le débogage des modèles.
- Contrôles de statut dédupliqués et facultatifs pour jusqu’à 250 éléments extraits.
Fonctionnement
La page est récupérée en HTML brut. L’extracteur local lit les éléments a, img, link et script, résout les URL relatives et conserve leur ligne et colonne source. Les règles comparent les libellés, cibles et attributs rel ; les contrôles facultatifs dédupliquent les URL publiques et les envoient par lots bornés.
Limites
- Il s’agit d’un audit HTML d’une seule page, pas d’un crawl de site ni d’une analyse du DOM rendu.
- Les contrôles de statut peuvent être bloqués ou limités par les serveurs de destination.
- Une réponse 200 ne prouve pas que le contenu attendu est présent.
Questions fréquentes
L’Analyseur de liens explore-t-il tout mon site ?
Non. Il extrait les liens et ressources d’une seule page. Les contrôles facultatifs interrogent uniquement les URL publiques uniques trouvées sur cette page.
Qu’est-ce qu’une ancre générique ?
Les libellés comme « cliquez ici », « en savoir plus » ou « learn more » donnent peu de contexte lorsqu’ils sont lus seuls.
Pourquoi certains liens manquent-ils du rapport ?
Le mode d’analyse lit le HTML brut ; les liens ajoutés après l’exécution de JavaScript ou masqués dans l’état d’une application ne sont pas inclus.