言語

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.

Built by Patrick Stox

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.

Feedback
Report a bug

Found something broken in Link Analyzer? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
 
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">
4 extractable URLs
  • 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
  1. Enter one public page URL and choose Analyze page.
  2. Review structural findings before checking network status; they come directly from the page source.
  3. Inspect each extracted URL, resource type, and source location.
  4. Choose Check HTTP status only when you also need live response evidence for the extracted destinations.
 
 
 
       
     
     
 
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.
 
 
Next stepContent Gap Analyzer — look up the exact spec and expected values.

People also explore
ToolSEO Opportunity FinderToolHeading Structure CheckerToolImage SEO CheckerArticleAlt TextArticleThe HTML lang AttributeArticleRanking in Google Images
 
 
 
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.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
       
ツールについて
ページのリンクとリンク先リソースを調べ、ソース位置、アンカーテキストの検出事項、任意の一括HTTPステータス確認を表示します。
公開URLを取得してリンクを分類し、内部・外部、画像やスクリプトなどのリソース、アンカーテキスト、取得状態を確認します。
機能
  • リンクとリンク先リソースの一覧
  • ソース位置とアンカーテキストの確認
  • 空・一般的・重複アンカーの検出
  • 任意の一括HTTPステータス確認
仕組み
HTMLからリンクとリソースを抽出し、絶対URLへ解決してソース位置、リンク種別、アンカーテキストを記録します。空、一般的、重複、nofollow、壊れた内部リンク、リダイレクトを分け、必要ならURLをバッチで確認します。
制限事項
  • 解析は取得時点のHTMLと、任意で実行した制限付きHTTP確認に限られます。認証、JavaScriptが生成するリンク、ネットワーク一時障害、リンク先の内容品質を推測しません。
  • アンカーテキストの検出事項は文脈の手掛かりであり、アクセシビリティ適合やSEO成果を保証しません。
よくある質問
リンク先へリクエストを送りますか？
初期解析はページのHTMLを取得します。任意の一括ステータス確認を実行した場合だけ、選択したリンクへ制限付きリクエストを送ります。
一般的なアンカーテキストは常に問題ですか？
いいえ。文脈やリンクの目的によっては適切です。検出事項を読み、移動先を説明する文言が必要か確認してください。
JavaScriptで生成されるリンクを確認できますか？
取得したHTMLに含まれないリンクは確認できません。必要ならレンダリング後のHTMLを別途確認してください。