How to find and fix broken links and 404 errors on your website

What counts as a broken link?#

A broken link prevents readers from reaching the destination that the page promises. The common example is a URL returning 404, but the practical problem can also be a missing file, a redirect to unrelated content or a fragment that no longer identifies a section.

Distinguish the problem from the symptom. A server outage needs an availability investigation; a misspelled path needs a content edit. The right repair preserves a useful journey. Removing every flagged link without understanding the destination can erase valid references and hide recurring technical issues.

Find the source page before you choose a fix#

A list of failing URLs tells you what failed but not where to edit. In a whole-site Linky report, use the source page and link text to locate the reference. Open the source page and confirm whether the link appears in the main content, a navigation component, a footer or another shared element.

Search for repeated destinations. If dozens of pages point to the same missing download, decide what should happen to the download before editing the references. If the reference comes from one template, repair that template and check representative pages after publication.

1. Record the source page, anchor text, failing URL and observed response.
2. Open the destination and verify whether the problem persists.
3. Identify who owns the content or server configuration.
4. Choose an appropriate fix and publish it.
5. Test the repaired source link and repeat the relevant scan.

Choose between updating, restoring, redirecting and removing#

Update a source link when it uses a typo, an old path or an outdated document address. Restore content when it was removed accidentally and remains useful. Set up a permanent redirect when content genuinely moved to a relevant replacement and you control the old URL.

Remove or rewrite the reference when the content is intentionally gone and no appropriate replacement exists. Do not force a redirect to unrelated material merely to eliminate a response code. A visitor looking for a specific setup document will not be helped by arriving at a general marketing homepage.

Repair internal links and external references differently#

For an internal destination, you can often coordinate the source edit with a server redirect or CMS change. Check that the replacement address is stable and publicly accessible to the intended audience. Also update links in reusable components and other pages that repeat the old path.

For an external reference, you may only control your own source page. Find an authoritative replacement that supports the same point. If the external service temporarily blocks automated requests, verify the content manually. Do not replace a useful primary source with unrelated material simply because the primary source returned one restricted response.

Handle redirects and fragments as part of the repair#

A repair is incomplete if a source link now takes several unnecessary redirect hops or lands at the top of a long page when it promised a particular section. Check the final URL and any fragment separately. Server responses usually concern the resource; a fragment identifies a location within the document.

When you change a heading ID, preserve an old stable anchor where practical or update references that depend on it. If a document migration also renamed sections, review the URL mapping and fragment mapping together. A successful page load does not prove that the destination section still exists.

Verify the published change and prevent the next failure#

Test the live source page after publishing. Follow the link as an intended visitor, check the destination content and repeat the scan. If a redirect was part of the change, test the old URL independently rather than relying only on the edited source.

Reduce repeat problems by using stable URLs and element IDs, documenting content moves and checking links during publication. Include link audits in migration and template changes. A maintenance routine should be short enough to use consistently and specific enough to catch the links your readers rely on.

• Use stable paths for resources that are referenced repeatedly.
• Keep a redirect map when URLs change.
• Check shared templates after navigation edits.
• Assign an owner to recurring errors.
• Audit important external references on a schedule suited to your site.

Frequently asked questions#

Put this workflow into practice

Read the related Linky documentation for the product controls and limits used in this article. Contact support if a result requires further investigation.