Broken links rarely arrive as one obvious failure. A service page moves, an old campaign remains online, a PDF is renamed, and a customer follows a saved bookmark into a dead end. For a small business, the consequence is practical: someone who was ready to learn more must now work harder to find the right information.
A broken-link audit should recover useful journeys, not simply make every error disappear from a report. This guide explains how to prioritise missing URLs, choose between a redirect and a genuine error response, and verify that repairs help both visitors and search engines.
What a broken link actually tells you
A link is broken when its destination cannot provide the intended resource. That might be a missing page, an unavailable image, an expired download, or a server error. These situations require different decisions. A spelling mistake in a navigation link is a publishing problem. A temporarily failing application is an availability problem. A retired offer may correctly return a missing-page response.
Begin by recording the full URL, the page linking to it, the observed response, and the intended visitor task. Do not assume a Search Console example reflects the current website: reports can contain historical URLs. Test the actual destination before deciding what to change.
For a renamed page with a clear replacement, Google recommends a permanent redirect. When content has been removed without a similar replacement, a genuine 404 or 410 response is appropriate. See Google's crawling error guidance.
Build an inventory from several sources
Use your website's navigation and sitemap as a starting point, then examine the sources that reveal less visible problems. Search Console can show URLs Google encountered. A crawl of internal links can identify mistakes in current content. Server logs, where available, can reveal requested pages that no longer exist. Sales staff may know which old links still appear in proposals.
Include documents, image links, booking links, and important external destinations. A working contact page does not compensate for a broken booking link. Record whether a problem is on your own domain or a third-party service, because the responsible person and available fix will differ.
Keep a simple spreadsheet with columns for source URL, destination URL, response, business importance, proposed action, owner, and verification date. This is more useful than an unfiltered export containing thousands of URLs with no decision attached.
Prioritise journeys before counting errors
Repair links in the primary menu, contact process, product information, and frequently shared pages first. A broken destination in a proposal template may matter more than dozens of obsolete archive pages. Use business relevance alongside traffic evidence rather than treating every missing URL as equally urgent.
An illustrative example is a design company that changes its service URL from a short generic name to a more descriptive address. The old page appears in client emails and has links from other websites. That deserves a targeted redirect and an update to internal links. An expired recruitment page with no equivalent vacancy may simply need a useful 404 page.
Do not invent traffic estimates to justify a decision. If you lack historical data, document the reason for prioritising the URL: prominent placement, a current campaign, an important customer task, or an external link you can verify.
Choose a relevant replacement
Redirect a visitor only when the new destination reasonably fulfils the original purpose. A retired website-maintenance service might have a replacement support page. A deleted article might have a substantially revised guide covering the same question. A download might have a current version at a new address.
Avoid sending every missing URL to the homepage. That often leaves the visitor searching again and hides the distinction between genuinely retired content and moved content. A broad destination is not automatically a useful replacement just because it is available.
Write the redirect plan before implementation. For each old URL, identify one final destination and explain the match. If no relevant page exists, keep the missing response and improve the guidance presented to the visitor. Your website information architecture should make recovery straightforward.
Repair the original links too
A redirect provides continuity, but internal links should point directly to the current page whenever you control them. Update menus, article references, footer links, reusable CMS blocks, and downloadable templates. Otherwise, every visit through an old internal link continues to depend on an unnecessary extra step.
Check content imported during a redesign. Editors sometimes paste absolute links from staging sites or leave references to obsolete WordPress paths. Search stored content for the old domain and old folder names, then review matches before replacing them. A global replacement without context can damage legitimate references.
Use a short publishing rule: when a URL changes, the editor must review its internal references and identify any external links the business owns. This prevents the same issue returning with the next content update.
Keep redirects direct and predictable
An old URL should ideally reach the intended final page in one redirect. A sequence that moves from HTTP to HTTPS, then to another hostname, then to a new path is harder to troubleshoot and adds avoidable work. Check the complete response chain rather than only the last page displayed in your browser.
Test query parameters when they carry meaningful information. A campaign link, search result, or language selection can behave differently from the clean URL. Decide which parameters should be preserved and which are irrelevant. Document that choice with the implementation rather than relying on accidental server behaviour.
Avoid competing redirect rules spread across a CMS plugin, server configuration, and application code. Assign a single owner to the redirect inventory and keep recovery copies before editing live configuration.
Design a helpful missing-page experience
A good 404 page acknowledges the problem and offers a small set of useful paths. Include a link to the homepage, the main services, the blog, and a contact option where appropriate. A search feature can help if the website has enough content and dependable search results.
Keep the layout consistent with the rest of the site. The visitor should recognise the business and understand that the website is still functioning. Avoid blaming the visitor or presenting a large animation that obscures the recovery links.
The server response must still indicate that the page is missing. A friendly error design that returns a successful page response can confuse technical reports. Ask the developer to verify both the visible interface and the HTTP status.
Verify repairs with a repeatable test
After publishing, revisit every repaired URL from the inventory. Confirm the response code, final destination, page heading, and relevant call to action. Test on mobile as well as desktop, because a redirected page may be technically available while its important content is difficult to use on a phone.
Check that the sitemap contains the current canonical destination and that the old URL is no longer used in internal navigation. For an important moved page, use Search Console URL Inspection to review the destination and request a recrawl when appropriate. This requests processing; it does not guarantee a ranking outcome.
Keep evidence of what changed. A compact record of the previous URL, new URL, implementation date, and verified result makes future redesigns safer. The SEO migration checklist provides a broader process for structural changes.
Make maintenance part of publishing
Run a focused link review after a redesign, a domain change, a large content deletion, or a new campaign launch. Between major changes, review critical customer journeys on a regular schedule that fits your team's capacity. The useful measure is whether the most important paths remain dependable.
For external links, verify that the destination is still relevant as well as available. A service may return a successful page while showing different content, a parked domain, or an expired offer. Editors should review meaning, not just response codes.
If your business website has accumulated old URLs and inconsistent navigation, contact Ali Dev Solutions for a focused audit. A considered repair plan preserves useful content, removes dead ends, and gives visitors a clearer next step.