Broken links interrupt a reader at the exact moment they want to continue. They can point to deleted pages, mistyped URLs, moved files or external sites that have changed. A repeatable audit helps you fix the highest-impact problems first instead of relying on occasional manual clicks.
Start with a complete inventory
Begin with a list of published URLs from your sitemap or content management system. Crawl internal links where possible, then inspect reported errors rather than assuming every warning is a real broken link. Temporary server errors and blocked tools can create false positives, so verify a sample directly.
Keep a record of the change and verify the live destination after publishing. This simple second check catches mistakes introduced during editing.
Prioritise internal links
Start with links on high-traffic pages, navigation, conversion flows and evergreen guides. An internal link to a removed article is usually within your control; update it to the closest relevant destination or restore the original page if it still serves a purpose. Do not redirect every deleted URL to the homepage because the destination may not answer the visitor's intent.
Keep a record of the change and verify the live destination after publishing. This simple second check catches mistakes introduced during editing.
Fix the underlying cause
Correct the source link where possible. If a page has moved permanently and a true replacement exists, configure a relevant redirect and update internal links to point directly to the new URL. Avoid redirect chains and loops, and do not redirect unrelated content just to make an error report look clean.
Keep a record of the change and verify the live destination after publishing. This simple second check catches mistakes introduced during editing.
Check redirects carefully
Check external links manually before removing them. A temporary outage is different from a permanently retired resource. Keep a brief record of the affected URL, the fix and the date, then rerun the check after deployment. Add broken-link review to a monthly maintenance routine.
Keep a record of the change and verify the live destination after publishing. This simple second check catches mistakes introduced during editing.
A practical example
For example, if a guide links to a retired feature page, first determine whether the feature moved or disappeared. Update the guide to the replacement if one exists; otherwise explain the current alternative. That is more useful than sending every old URL to the homepage.
Write down the intended outcome before making a change, then test a representative case from start to finish. If the task affects other people, ask someone unfamiliar with the workflow to review the result. Fresh eyes often reveal unclear wording, unexpected permissions or interface details that the person who built the page no longer notices.
Common pitfalls to avoid
Do not bulk-remove links based only on one automated report. A crawl may be blocked, a server may briefly fail, or an external resource may be temporarily unavailable. Verify errors, preserve useful references and test fixes after deployment.
Keep a source copy and document any change that is difficult to reverse. When a result matters, use the relevant official documentation and verify the final output independently. Practical guides can help structure the work, but the correct settings may vary by browser, device, platform and local requirements.
Final checklist
- Define the task and check the current source material.
- Use a practical workflow that matches the audience and device.
- Review quality, accessibility, privacy and performance where relevant.
- Test the final result instead of assuming the first output is correct.
- Keep notes on important changes so the process can be repeated.
Frequently Asked Questions
Should every broken URL redirect to the homepage?
No. Redirect only when a relevant replacement exists. Otherwise, a useful not-found page is clearer than sending visitors to an unrelated destination.
How can I check that the result is correct?
Review the finished result in the real context where it will be used, check for errors, and repeat the process with a representative example before relying on it for an important task.
Does this guide replace professional advice?
No. It offers general practical guidance. Follow the relevant platform documentation, organisational policies and professional advice where the task has legal, security or accessibility implications.