Broken Links: How to Find Them and Decide What to Fix

A broken link sends someone to a page or file that is missing, unavailable or reached through an outdated address. On a small-business website, that might be a service page linked from the menu, a booking button, a PDF price list or an external resource. The visible error is only part of the problem: the real question is whether the link interrupts a useful customer task or points search engines towards a dead end. You do not need to repair every 404 indiscriminately. Some URLs were intentionally removed, some failures are temporary, and some old pages have a relevant replacement. Start by finding links across your own site and checking important external links, then judge each issue by its audience, purpose and likely consequence. A measured approach helps avoid irrelevant redirects and wasted effort. This guide explains practical ways to detect broken links, prioritise them, choose an appropriate fix and check that the repair works. It also covers simple habits that reduce repeat problems, whether you manage WordPress yourself or work with a developer.

Content

What counts as a broken link

What counts as a broken link?

A broken link is one that fails to take someone to the information or action they reasonably expect. The failure may be obvious, such as a browser showing “404 – Not Found”, or less obvious: the link loads a page, but that page is unrelated, incomplete or no longer supports the task the visitor came to do.

Common causes include a mistyped URL, a page moved without its old address being updated, a deleted file, or a link to another website that has changed or shut down. Links can also fail because a server is temporarily unavailable, a domain has expired, or a destination blocks access. An internal link can be broken even when the rest of your website works; an external link can fail for reasons outside your control.

A link that returns an error is not always a permanently broken link. For example, a server error or a temporary network problem may stop a page loading for a short time. A 404 means the server could not find a page at that address, while a 410 indicates that content has been removed. These responses help describe what happened, but they do not tell you by themselves whether the link should be repaired. Check the destination and the context before deciding.

A removed page and a broken link are related, but they are not the same thing. A page may have been deliberately taken down because it is outdated, duplicated or no longer relevant. If no current page serves the same purpose, leaving it removed may be reasonable. The broken link is the remaining route on your site that still points to it. If the page has moved, the old address is stale; if it has been retired, the link may need to be removed or replaced rather than the page restored.

Also check links that appear to work but lead visitors astray. A button labelled “Book an appointment” that opens a general homepage, for instance, has not delivered the intended destination, even if that page loads successfully. Likewise, a link to a document may open the wrong version, or an in-page link may fail to take the reader to the section named in the text. Whether you call these broken links or poor link destinations, they create a practical problem worth reviewing.

The visitor’s intended task should guide your assessment. Someone following a link to contact details, a service description, a booking step or an essential form may be blocked from taking an important next step. A link to an old background article may be less urgent, particularly if it is rarely used and has no useful replacement. Consider the link label, where it appears and what a visitor would expect to do next. That context helps distinguish a minor outdated reference from a failure that could interrupt a customer journey.

Find broken links

Use several checks to find broken links

No single check will reveal every broken link. A site crawler can scan your website and flag links that lead to errors, redirect chains or destinations it cannot reach. Run a crawl of the public site and review both internal links, such as links between your own pages, and external links to other websites. If your site has areas behind a login, a crawler may not reach them without suitable access, so check those pages separately. Crawler results are clues to investigate, not proof that a visitor sees the same failure: an error may be temporary, or the crawler may be blocked.

Start with the report’s source page and the URL it links to. Open both in a browser and follow the link as a visitor would. Check whether the destination loads, whether it redirects somewhere relevant, and whether the intended content is available. A page that loads successfully but shows an error message, missing content or an unrelated destination can still create a broken experience. For important pages, test the full journey—for example, moving from a service page to a booking or enquiry step—rather than checking only whether the first page opens. If a result changes between attempts, note when you tested it and check again later before treating it as a persistent problem.

Google Search Console can add context, but it is not a complete broken-link scanner. Check its Page indexing report for URLs Google reports as not found or otherwise unavailable, and use URL Inspection to review a particular page’s reported status. These reports concern Google’s ability to access or index URLs; they may not identify every broken link on your site, and they do not replace following links from their source pages. The Links report can help you understand which pages receive internal or external links, but it is not a list of links that currently fail. Treat Search Console findings as leads, then verify the URL in a browser and, where useful, compare it with your crawler’s source-page report.

Build in a simple way for staff and customers to report problems. A staff member might notice a faulty link while updating a page; a customer may encounter one while trying to download a form or find contact details. Ask them to provide the page they were on, the link or button they selected, what they expected to happen, what appeared instead, and roughly when it happened. A screenshot can help, but avoid requesting sensitive personal information. Reproduce the steps yourself, ideally in a private browser window if sign-in or saved browser data might affect the result.

Keep a shared record with the source page, destination URL, how the issue was found, the observed response, the date checked and whether it still occurs. This makes it easier to compare crawler scans with real visitor reports, spot repeated failures and avoid investigating the same link twice. When a report cannot be reproduced, retain the details and check again rather than assuming either that the customer was mistaken or that the fault remains. A short, repeatable checking routine gives you evidence to work from before deciding what action, if any, is appropriate.

Prioritise by impact

Rank broken links by likely customer impact

A list of broken links is a starting point, not a repair queue. Rank each issue by how much it could disrupt a visitor or an important business task. A practical review considers five factors: the importance of the page, where the link appears, what the visitor is trying to do, how much relevant traffic the page receives, and whether the failure is likely to be temporary. You do not need a precise score; consistent notes make it easier to choose what to investigate first.

Start with the page’s role. A link from a main service page, contact page, pricing information or a key landing page usually deserves more attention than a link buried in an old article. Consider whether the destination supports a task such as understanding a service, making an enquiry, finding opening hours or downloading a necessary document. If the broken destination blocks that task, raise its priority even if the referring page is not among the site’s most visited pages.

Next, look at placement and intent. A prominent button or menu link is more likely to be noticed and used than a reference in a long page’s final paragraph. Ask what a reasonable visitor expects after clicking: a relevant service page, a booking or enquiry step, a policy, or further reading? The closer the link is to a decision or action, the more consequential a failure may be. Check the surrounding text as well; a link labelled “Contact us” leading nowhere is more confusing than a clearly dated reference to an unavailable past event.

Use available traffic information as context, not as the only test. Where analytics or Search Console data is available, check whether the referring page receives visits or search visibility. A frequently visited page can send more people towards a broken destination, so its link may warrant faster attention. But low traffic does not automatically make an issue unimportant: a specialist service page may receive fewer visits while serving visitors with strong intent. Similarly, consider whether the broken URL appears on several important pages, rather than treating every occurrence as an isolated error.

Before scheduling a repair, check whether the failure is temporary. A destination may be unavailable because of a short-lived server, network or third-party service problem. Retest it later, ideally in a browser, and compare results from more than one check if possible. Note when and where you tested it. If it works again, investigate whether the interruption is recurring; if it remains unavailable, treat it as a persistent issue and decide what the link should do instead. Avoid changing a URL based on a single failed check when the destination may simply be having a temporary problem.

For a simple working list, record the referring page, broken destination, link placement, likely visitor task, available traffic context, last test date and next action. Then group issues into urgent, investigate soon and lower priority. Hypothetical: a 404 on a core service page linked from the main menu deserves attention before an old resource-page link with no visits. The first issue is prominent and may interrupt a visitor researching a service; the second may still need review, but is less likely to affect a current customer journey. Reassess priorities when the page’s role, traffic or destination status changes.

Choose the right fix

Match the repair to the visitor’s next step

Before changing anything, open the broken link from the page where it appears and identify what a visitor would reasonably expect to find. Check the surrounding text, the link label and the page’s purpose. A link labelled “Book a consultation” should lead to a working booking route; a link to an old announcement may no longer need a replacement. The right fix depends on whether the destination still exists, whether its content remains useful and whether another page genuinely serves the same need.

Correct the URL when the intended destination is still available and the link simply points to the wrong address. This is usually the most direct repair: update the link on your site, then test it. Check for common causes such as a typing error, an outdated URL after a page was moved, or a link that uses the wrong version of a web address. If several pages contain the same incorrect link, search your site for other instances and update them too.

Restore the page when it was removed by mistake or its information is still needed and can be kept accurate. This can be appropriate for an important service, product or resource page that has a clear role in your site. Review the content before restoring it: outdated details, expired offers or obsolete instructions should not be republished as though they were current. If you cannot maintain the page or its purpose has ended, another option may be more suitable.

Use a redirect only when there is a close, useful replacement. For example, if a page has moved to a new address, redirect the old address to the new one. If a product or service page has been retired, a current page covering the same need may be a reasonable destination. Avoid sending unrelated old URLs to the home page or to a broad category simply to avoid a 404. That can leave visitors unsure whether they have reached the right information. Where possible, update links on your own site as well, rather than relying on a redirect indefinitely.

Remove the link when there is no suitable replacement and visitors no longer need it. This may mean editing a sentence, deleting an outdated call to action or removing a reference from navigation. Read the surrounding content after the change to make sure it still makes sense and does not leave a misleading instruction. If the destination is an external website that has disappeared, consider whether a trustworthy alternative exists; otherwise, remove or rewrite the reference rather than pointing readers to an unrelated page.

A 404 is not automatically a fault that must be concealed. Leave an intentional 404 when a page has been deliberately removed, has no relevant replacement and should not return. Make sure your site’s error page helps visitors recover—for instance, by offering a route back to useful content—and remove links on your site that still send people to the retired address. Keep the 404 response for that URL rather than redirecting it somewhere unrelated. This makes the outcome clearer for both visitors and systems that interpret the page status.

When a choice is uncertain, record the URL, the page linking to it, the reason for the decision and any follow-up needed. That gives whoever maintains the site a clear basis for revisiting the issue if the content or customer journey changes.

Verify repairs and prevent repeats

Test the repair from the visitor’s point of view

After changing a link or setting up a redirect, open the original link as a visitor would. Check it from the page where it appears, rather than testing only the new address in isolation. Confirm that the destination loads, shows the expected content and works without an error or an unexpected detour. If it redirects, check that the final URL is the intended replacement and that the browser does not show a redirect loop or pass through several unnecessary addresses.

A redirect is useful when a page has moved and there is a genuinely close replacement. It should take visitors to that replacement, not simply to the home page or a broadly related page. If the redirect is not relevant, visitors may struggle to complete their task. Where the original page has been restored or the link can be corrected, test that route too; a redirect is not automatically the best fix for every broken URL.

Then recheck the journey around the link. Follow the route from the page a visitor is likely to start on, through the repaired link and on to the next useful step. For a service enquiry, for example, check that the relevant service information opens and that the enquiry link or form is still available. For a product or booking journey, test the relevant next step without submitting a real order or booking. Check on a phone as well as a computer if the page is important to mobile visitors.

Build checks into publishing and maintenance

Many broken links follow routine changes: a page is renamed, a product or resource is removed, or a URL is copied incorrectly. Reduce avoidable errors by checking links before publishing, especially links in menus, prominent buttons and pages that guide visitors towards an enquiry or purchase. Open the links in the finished page, not just in the content editor, and confirm that they point to the intended address.

When changing a page address, decide what should happen to the old URL before the change goes live. Update links on your own website to use the new address, and add a redirect from the old one when visitors or search engines may still use it and there is a suitable replacement. Keep a record of important redirects and review it when pages are changed again. Avoid creating a redirect simply to hide an error if the destination does not meet the visitor’s original need.

Include link checks in regular website maintenance. A site crawl can help identify links that need review, while browser testing confirms what a visitor actually sees. Pay particular attention to key pages and journeys, and investigate reports from customers or staff promptly. Automated checks can flag possible problems, but they may not establish whether a replacement is relevant or whether a failure is temporary. Use judgement before removing a link or changing a destination.

After a repair, check the affected page again and, where appropriate, run another crawl to catch related internal links that still use the old address. Keep the original URL, final destination and reason for the change in your maintenance notes. This makes later reviews clearer and helps prevent a quick fix from becoming a new source of confusing redirects.

Conclusion

Conclusion

Broken links are worth fixing when they interrupt an important visitor task or weaken a useful page—not simply because a report lists them. Find issues with a site crawl, browser checks, Search Console and feedback from customers or staff. Then check where each link appears, what visitors are trying to do, whether the destination still exists and whether the failure is temporary. This gives you a practical basis for deciding what to address first.

For high-priority links, correct the URL, restore the missing page or redirect to a genuinely relevant replacement. Remove links that no longer serve a purpose; leave a 404 in place when there is no suitable destination rather than sending visitors to an unrelated page. After making changes, test the link and any redirect, then revisit key journeys such as reaching a service page or submitting an enquiry. Add link checks to routine publishing and maintenance so errors are easier to catch early. A short, prioritised list of repairs is more useful than treating every reported error as equally urgent.

Explore related information: Booking Website Design & Development; Web Design Sunshine Coast.

Let’s talk websites.

DIGITALON’s in-house team in Wurtulla on the Sunshine Coast designs, builds and supports WordPress and eCommerce websites for businesses across Australia. Tell us what you want your website to do, and we’ll help you work out the next step.

How may we assist you?

Contact

Or, call us now