On this page
Broken links can prevent readers and crawlers from reaching intended content. Fix important navigation, purchase and source links, but do not assume that every 404 causes a site-wide ranking penalty. A deliberately removed URL and an accidental broken link need different treatment.
Identify what actually failed
A broken destination might return a not-found response, a server failure, an access restriction or the wrong content. A page can also return a successful status while showing an error. Record the URL, visible result and response before choosing a remedy.
Google’s HTTP-status guidance explains how responses affect processing. A successful response does not guarantee indexing, and a persistent not-found response has a different meaning from a temporary server failure.
Prioritize the reader’s important paths
Start with links that lead to a product, application, contact action, essential instructions or evidence for a claim. Also inspect navigation and links to important articles. A broken reference can make the article less useful even when the rest of the page loads.
Use the page’s actual role and traffic to set priority. Avoid an arbitrary rule that a certain number of broken links automatically lowers all rankings.
Collect a link-review record
- The page containing the link.
- The destination and visible anchor text.
- The observed response and date.
- The intended reader task.
- The proposed replacement, removal or redirect.
- The owner and verification result.
A diagnostic report is a lead for review. Confirm failures in context because access challenges, temporary incidents and redirects can affect a tool’s result.
Choose the appropriate repair
The page moved to a genuine replacement
Update internal links to the current destination. Where the move is permanent, use the site’s authorized redirect configuration to point the old URL to the equivalent new page. Google’s redirect guidance distinguishes permanent and temporary moves.
Verify the final destination, avoid loops and check relevant tracking parameters. A redirect is not a guarantee that every ranking will remain unchanged.
The content was removed without an equivalent
Remove or revise links that promise the missing information. Let the URL communicate that the resource no longer exists through the appropriate response. Do not send every unrelated removed page to the homepage.
An external source no longer supports the claim
Find a current primary source that supports the actual statement. If the evidence is unavailable, revise or remove the claim. Replacing the URL with an unrelated successful page does not fix the factual problem.
The failure is temporary
Investigate the host, application or access issue. Record the incident and recheck after the appropriate repair. Avoid changing every destination based on one transient outage.
Original example: a renamed pricing guide
Suppose a current product page replaces an older pricing resource. The team confirms whether the new page answers the same question, updates internal references and checks an appropriate redirect for the old location.
If the old article described a discontinued product, the team should not imply that the current plan provides its former features. It reviews the surrounding copy along with the URL. This fictional example shows why a working link and an accurate promise need to be checked together.
Use Search Console with its limits
URL Inspection helps compare indexed information with a live test. Inspect the exact affected URL and distinguish an old report from the current response.
The Links report shows a sample of known links over time. It is not a real-time inventory of every broken destination. Use it alongside the actual source-page review.
Do not treat routine broken-link maintenance as a reason to disavow unfamiliar backlinks. That is a separate advanced decision with its own evidence requirements.
Review the content in BrandWell
In RankWell, review the article’s sources, product references and next steps. Fix the text when a destination or product has changed. Confirm the configured publication path and inspect the live page afterward.
AIMEE can help organize approved review work through configured tools. Its output is not proof that a link works; verify the public destination and important action.
Prevent repeat failures
Include link checks in publication and migration reviews. Keep a map of changed URLs, check shared navigation and confirm that important media still loads. Revisit sources when the underlying guidance or product changes.
After repair, verify the reader’s path on mobile and record the outcome. Monitor relevant visits and actions over a comparable period rather than claiming that fixing a link alone caused a ranking or revenue improvement.
Reviewed and updated October 2, 2026.
Written by
