← All free tools
FUKAMO · FREE TOOLS

Broken Link Checker

Check HTML links and HTTP errors in a sample of internal destinations.

FREE PUBLIC URL CHECK

Broken Link Checker

Check HTML links and HTTP errors in a sample of internal destinations.

Checks the fetched HTML of a public URL.
BEFORE YOU CHECK

Know what you are checking.

A useful link is understandable and leads to the expected content. Link checking goes beyond 404 responses to include empty labels, wrong paths and outdated redirected addresses.

When to use this check

Begin with links needed to complete a task. Booking, instructions or a contact form. Check their content as well as status because a 200 response can still lead to the wrong page.

A practical example

Replace “More here” pointing at a removed article with “How to check canonical URLs” pointing at a current, relevant guide.

A common mistake

A small sample does not prove that every destination works. A server may reject automated requests, requiring manual verification rather than immediate link removal.

Use the result

Review Fukamo’s link inventory and the destinations actually tested in Links and server. Check important fragments in the page and manually investigate rejected automated requests before declaring a link broken.

What to check next
  1. Separate internal, external, anchor and contact links.
  2. Check important destinations and their labels.
  3. Find an appropriate replacement for broken content.
  4. Link directly to the final URL where possible.
  5. Read external sources to confirm that they support the claim.

Understand the result. Make the right change.

How to check page links, fragments and files

A web URL, page fragment, email link and PDF need different checks. A bulk HTTP test cannot establish whether a “Contact” link reaches an existing form.

  • For a fragment, verify the matching id in the current document.
  • For mailto and tel links, check the actual contact details.
  • For a file, check both access and the document the reader receives.
Why a 200 response does not prove a link is useful

A manual can redirect to the manufacturer’s homepage. The server may return 200, but the reader has still lost the promised instructions.

  • Read the final destination of important links.
  • Check for a login screen or error template replacing the expected content.
  • Choose a replacement by meaning, not merely by matching the domain.
How to write descriptive link text

“Download the installation manual (PDF)” explains more than “Click here”. For an image link, also inspect its accessible name.

  • Describe the destination in the link text itself.
  • Identify a PDF or other file when that changes the visitor’s expectation.
  • Fix icon links without a name; accessibility requires an understandable destination.
How to verify repaired links and rejected requests

When your article moves, update internal links to its final URL. Keep the redirect for old bookmarks and external links you cannot edit.

  • After the fix, follow the link from its original page to the right content.
  • Manually investigate an automated 403 before removing a useful source.
  • Record which destinations were tested; an unchecked link is not a confirmed pass.

Google Search Central — crawlable links ↗

Primary reference: developers.google.com ↗

Frequently asked questions

Should I delete an external link that returns 403?

Not without verification. A server may reject an automated client while serving visitors normally. Open the destination in a browser and assess its relevance and redirects. A confirmed 404 differs from bot blocking. Prioritize links that prevent visitors from completing important tasks.

When the task is complete

The corrected link reaches the intended content and has descriptive text. If access cannot be established reliably, retain a review status and its reason rather than inventing a pass.

FUKAMO / PRIVACY

Your privacy, your control.

These choices cover cookies and browser storage. The audit works just as well without optional storage.

Privacy policy ↗Cookies and third parties ↗