Choose the right repair for each broken journey instead of sending every missing URL to your homepage.
A broken internal link interrupts a journey on your own website. Someone opens a useful guide, follows a recommendation and lands on a missing page. The best fix depends on what the original destination was supposed to provide. Restoring content, correcting a typo, redirecting a moved page and removing an obsolete reference solve different problems.
This guide shows how to find and fix broken internal links on a website without turning every error into a homepage redirect. Use the free link analyzer to collect source and destination evidence, then verify each important finding. The examples below are hypothetical repair scenarios, not claims about measured ranking improvements or a client's results.
1. Understand what the response tells you
A response code describes what happened when the server was asked for a URL. It does not explain the editorial intention behind that URL. A missing destination, an access restriction and a temporary server failure therefore need different investigations. Google's HTTP status documentation distinguishes missing content from server failures and notes that a successful response does not itself guarantee indexing.
In your action sheet, keep the observed status next to the check time. Record failures without a response separately, because a timeout does not identify a missing page. A crawler can also receive a different response from a browser because of security controls. Before changing content, repeat the important check and open the destination normally. This initial separation helps avoid removing valid links during a brief outage.
2. Find every source that needs an edit
Run an analysis and inspect the broken-link findings. For each destination, collect the source pages and anchors that point to it. If the same old address appears in a navigation component, one template edit may repair many occurrences. If several authors inserted it independently in articles, each content record may need attention.
For example, imagine that /services/window-cleaning was accidentally typed as /services/windows-cleaning in five guides. The correct page already exists and the relationship is still useful. Fixing the five source links is the primary task. You might separately consider a redirect for visitors using the mistaken address, but that does not replace correcting links you control. Keep the distinction visible in your task list so a redirect does not hide unfinished editorial work.
3. Choose between correcting and restoring
Correct the destination when the source contains a typo, an outdated slug or an incorrectly constructed relative URL. Check whether a CMS field, imported content or template generated the mistake. If an entire section shares the error, solve the generation problem as well as the current instances. Otherwise the next publication could introduce the same broken path again.
Restore the page when content was removed accidentally and still has a clear purpose. Confirm that the restored version contains the information the anchor promises. An empty page with the old title is not a meaningful repair. Ask the content owner whether the offer, instructions or downloadable resource remains valid. If the business no longer supports it, choosing a truthful replacement or removing the reference is better than reviving misleading information solely to make a status report green.
4. Redirect only when a suitable replacement exists
A permanent redirect is appropriate when a page has genuinely moved or equivalent content has been consolidated. Google explains permanent and temporary behavior in its redirect guidance. Match the implementation to the actual move. The replacement should satisfy the original visitor intent, not simply be the nearest page with a successful response.
Suppose an old installation tutorial has been replaced with a revised tutorial for the same product. Map the old address to that new guide, then update your current internal references to link directly to it. If an unrelated product was discontinued with no substitute, sending visitors to the homepage can be confusing. Use the redirect chain cleanup workflow when a sequence of historical moves already sits between the original URL and its replacement.
5. Remove references that no longer help
Sometimes the correct repair is an editorial change. An expired event registration page may have no equivalent destination. Remove the registration link or rewrite the sentence to explain that the event has ended. If the historical page remains useful as an archive, link to that archive with wording that makes its purpose clear.
Do not delete surrounding useful information merely because one citation is unavailable. Review the paragraph and decide whether the statement still stands, needs an updated source or should be removed. For internal links, coordinate with whoever owns the destination content. A link report cannot tell you whether a department plans to republish a resource next week. Recording the reason for removal prevents another editor from restoring the same obsolete call to action during a later content refresh.
6. Separate genuine errors from restricted access
A link to an account area may intentionally require authentication. A crawler seeing an access response does not mean customers cannot use it. Review whether the link is labeled clearly and whether it belongs in the public journey. Never weaken authentication or security rules just to let a public analyzer report success.
Similarly, rate limiting and temporary outages should be assigned to an operational investigation. Note the affected host, approximate time and whether multiple destinations failed together. If the browser works but the crawler does not, check your own server logs or security configuration through authorized access. The tool's crawling approach explains why some requests remain unchecked. Keep those entries pending until you have enough evidence to distinguish a content repair from an infrastructure issue.
7. Verify both the destination and the source
After the edit, open the exact source page and activate the link. Confirm the final address and read the content that loads. Test the relevant mobile layout too: a repaired desktop navigation item may have a separate mobile configuration. If the source was cached, make sure you are checking the published version visitors will receive.
Then run another crawl and compare the affected links against your saved list. A repair is complete when the intended source points to the right working destination and the text still describes it accurately. Keep redirects that serve legitimate old visits even after updating current links. If the report still shows the original failure, check for duplicate content records, another template instance or a deployment cache before assuming the crawler is wrong.
8. Prevent the next batch of broken links
Add link review to the process for renaming, merging or deleting pages. Before changing a URL, search for incoming references and prepare a mapping when a move is appropriate. After publishing, check the destination and its main sources. This small release habit is easier than reconstructing years of undocumented changes.
Maintain a short repair log containing old URL, decision, replacement if any, editor and validation date. Review recurring causes: manual slug entry, copied relative paths, menu duplication or imported articles. A broader internal link audit can identify where navigation and content ownership need improvement. Focus the ongoing process on preventing interrupted tasks, rather than requiring every historical URL to remain a live content page forever.
Frequently asked questions
Should every 404 redirect to the homepage?
No. Choose a redirect when there is a relevant replacement for the old content. If no replacement exists, remove misleading internal references and let the missing URL behave honestly. A generic destination may leave the original visitor's question unanswered.
Why does a link work in my browser but fail in a crawl?
Your browser may have a login session, different network access or different treatment by a security service. The failure may also be temporary. Compare the exact URL and check time, then investigate authorized logs before classifying the destination as missing.
Do I need to change internal links after adding a redirect?
Update links you control to the intended current destination when practical. That keeps source content accurate and avoids an unnecessary intermediate request. The redirect can remain useful for old bookmarks, external references and visitors who still request the previous address.
How should I prioritize hundreds of broken occurrences?
Group them by destination and source template. Start with links that block important visitor tasks and shared components that affect many pages. Review representative examples before applying a bulk fix, then verify both the shared template and individual article links.