REDESIGN AND LAUNCH
How to find and fix broken links on a business website
Broken links interrupt a customer's task. Review them by destination and purpose so the fix preserves the intended journey, rather than simply making an error disappear.
Collect the affected links
Check the main menu, service buttons, footer, downloads and links inside articles. Use a crawler if appropriate, then review its findings manually. Record the source page, link text, destination and observed result. A link that opens the wrong service may be broken in practice even if the server returns a successful response.
Identify the cause
Look for a typo, a renamed page, a deleted file, a changed external URL or a missing anchor. Links may also differ by case or trailing slash on some platforms. Ask the developer to confirm the actual deployed path instead of repeatedly guessing variants.
Choose the right correction
Update an internal link to the correct final address. Restore useful missing content when appropriate. If an old public address has a relevant replacement, consider a documented redirect. If the content is intentionally gone, provide a useful missing-page response rather than redirecting visitors somewhere unrelated.
Make the missing page useful
MDN describes 404 as the response for a resource the server cannot find. A branded error page can explain the situation and link to the main services or homepage, but the developer should also check the response status. Friendly wording alone does not establish correct HTTP behaviour.
Retest from the source
Return to the original page and click the corrected link. Confirm the destination and any anchor position. For a download, open the actual file and check that it is the intended version. Record the fix and its verification date.
Prioritise links that block enquiries, then important content and supporting resources. Keep an external-link review in your maintenance plan because providers can change their destinations. A clean report today is not a permanent guarantee; it is evidence of the current checked state.
Sources and further detail
Technical references checked on 8 October 2026. Provider features can change.
Practical guidance with illustrative examples. Read our editorial standards or send a correction.