Broken Links Finder

Find links on a public page and check their HTTP responses.

What Is a Broken Links Finder?

A broken links finder checks links associated with a webpage or website and helps identify destinations that cannot be reached. You begin with a web address and examine the links or errors reported by the checker. A missing destination may return a 404 or 410 response, while other failures need further investigation. The results help website owners locate outdated URLs, repair navigation, and make useful content easier to reach.

Broken Links Finder

Find links on a public page and check their HTTP responses.

Broken Links Finder thumbnail

Check links on a webpage

Finds links on one page. Checks up to 20 unique HTTP(S) destinations per scan with real status requests. 404 and 410 are marked broken; 403, 429, timeouts and other uncertain responses need manual review. Anchors and other non-web schemes are skipped. Some servers block automated requests.

Rate this tool 4.5 out of 5 from 2 ratings

Find Dead URLs, Understand the Errors, and Repair Your Links

Broken links often appear after a page is renamed, a product is discontinued, an external article disappears, or a WordPress permalink changes. The link may still look normal in a menu or paragraph, but the destination no longer provides what a visitor expects. Checking links is therefore both a maintenance task and a usability check.

Start with the URL of a public page you want to inspect. Review the results for unavailable destinations and investigate where each link appears before editing anything. A link to your own missing page usually needs a different fix from a link to another website. Also remember that a temporary server failure or a website blocking automated requests does not necessarily mean the content has been deleted. The guide below explains how to make that distinction.

Read Full GuideShow Less

What Makes a Link Broken?

A hyperlink has a source, such as a blog post containing the link, and a destination, which is the address it opens. A link is genuinely broken when its destination cannot provide the intended resource. Common examples include a misspelled path, a deleted product page, or an old article URL that was never redirected.

Internal links point to pages on your own website. External links point to other domains. Both deserve attention, but the repair options differ. You control your internal destinations and redirects; for external destinations, you generally control only the hyperlink on your page. An inbound backlink is different again: it sits on somebody else’s website and points to yours. Checking links on your own pages does not automatically discover all inbound backlinks.

Choose the Right Page and Check the Coverage

  1. Enter the full address of the public page or website in the tool’s URL field.
  2. Run the available check and review any reported links and error information.
  3. Separate links to your own domain from links to external websites.
  4. Open suspicious destinations independently before deciding they are permanently broken.
  5. Find the source page or template where the link must be corrected.

Do not assume a single-page check covers an entire domain. A website-wide audit requires discovering multiple pages and checking the links found on them. The exact crawl depth, link limits, and handling of scripts depend on the checker being used. If a report does not include the original linking page, use your content search, navigation editor, or a dedicated crawler to locate it.

How to Interpret Common HTTP Status Codes

Result What it generally means Recommended response
200 OK The server successfully returned the requested resource. No broken-link fix is normally needed; confirm the page is the intended one.
301 or 308 The address permanently redirects to another URL. Check the final destination and update an internal link to its preferred URL when practical.
302 or 307 The address redirects temporarily. Check whether the temporary move is intentional before changing the link.
404 Not Found The requested resource was not found. Correct a typo, locate a replacement, or remove the obsolete link.
410 Gone The resource is no longer available and is likely permanently removed. Replace or remove links to it; redirect only if there is a genuinely relevant replacement.
403 or 429 Access is refused or too many requests were made. Check in a normal browser; automated access may be restricted.
500, 502, or 503 The destination has a server-side problem. Retry later and investigate persistent failures before editing links.
Timeout or DNS error A connection or name-resolution problem prevented a response. Retry and verify the hostname, network, and destination availability.

Important: a redirect is not automatically a broken link, and a response code alone cannot prove that a page contains the content a visitor wanted. A website may even show a “not found” message while incorrectly returning 200; this is sometimes called a soft 404.

Trace a Missing Destination Back to Its Source

Imagine an article at https://example.com/guides/launch/ links to https://example.com/resources/old-checklist/. The second address now returns 404, but the checklist has moved to /resources/launch-checklist/. The most useful repair is to update the hyperlink in the guide to the correct destination.

If several articles link to the old checklist, repair each internal reference. If the old address also receives bookmarks or links from outside your site, consider a permanent redirect to the equivalent checklist. The source page matters because a report of a missing URL, without its referring page, does not tell an editor where the visible error originates.

Fix Internal Links With the Smallest Accurate Change

First determine whether the destination still exists under a different address. A spelling error can be fixed directly in the hyperlink. A renamed article can be linked to at its new URL. A permanently moved page may also need a 301 or 308 redirect so old bookmarks and external links continue to reach the replacement.

Do not redirect every missing address to the homepage. That often sends visitors to content unrelated to their original request. If there is no comparable replacement and the page was deliberately retired, remove the obsolete internal link and allow an appropriate 404 or 410 response. For Apache-based sites, the Htaccess Redirect Generator can help with certain redirect configurations; test changes before applying them to a live server.

For WordPress, also review menus, widgets, reusable blocks, and page templates. A single broken navigation link may appear across many pages. Following a migration, compare your site structure against the URLs listed in your XML sitemap, while remembering that a sitemap is not a complete inventory of every hyperlink.

Repair Dead External References Without Losing Context

When an outside source disappears, look for the original publisher’s updated page, a newer edition of the same document, or another authoritative source that supports the sentence. Replace the hyperlink only when the new destination genuinely matches the claim. If a reference is no longer necessary, remove the link; if the evidence is essential and cannot be recovered, revise the statement itself.

A failed automated check is not enough reason to delete a valuable external citation. Some publishers block crawlers while serving normal visitors. Open the URL yourself, check its final destination, and repeat the test before making an editorial decision.

Why a Link Checker Can Report a False Alarm

Websites can respond differently according to user agent, location, authentication, request frequency, or bot-protection rules. A 403 or 429 response may reflect access restrictions rather than a missing article. A slow response can become a timeout during a short automated check, and a temporary 5xx error may disappear after the destination recovers.

Other problems may not show up in a basic check. Links added only after JavaScript runs can escape a crawler that reads initial HTML. A fragment such as #pricing may point to a missing section even when the page itself returns 200. Login-only content, forms, and restricted dashboards may also be inaccessible to public checkers. Treat results as evidence to investigate, not as an unquestionable deletion list.

Build Broken-Link Checks Into Website Maintenance

Check key navigation and heavily visited landing pages after publishing a redesign, changing permalinks, or migrating domains. Review old content links periodically, especially articles that cite third-party studies or product pages. For large sites, use a crawl that records the source URL, target URL, and response so fixes can be assigned and checked again.

A Website Links Count Checker can provide context about the internal and external links on a page, while a Backlink Checker addresses a different question: links from other sites pointing toward your website. After repairs, recheck affected pages and use Google Search Console to investigate crawl or indexing reports. Search Console is not a complete inventory of outbound links.

Does Every 404 Error Need a Redirect?

No. A 404 can be the correct response for an address that never existed or a page with no suitable successor. The priority is to stop sending visitors through broken internal links and to restore genuinely useful destinations where possible. Use permanent redirects for meaningful page moves, not to hide every missing URL. A clear custom 404 page can help visitors recover, but it should still return the proper 404 status code.