Start with the decision, not the metric.
A broken link sends a reader to an unavailable or unsuitable destination. Repair work should consider the linking page, destination status, intended task, and whether a relevant replacement exists. A genuine 404 response can be correct for removed content; the problem is often the live link still promising that content.
Broken navigation interrupts a journey, especially when it appears in menus, purchase flows, or widely reused templates. External failures also weaken an article's supporting references. Prioritize links by how people encounter them and what they need next, rather than trying to make every historical URL return a successful response.
A safe link-repair workflow separates detection from replacement. Establish which failures are confirmed, how a relevant destination is chosen, and which edits require review. Work from actual rendered links and retain a reversible change log, especially when a shared template or a batch operation could affect many pages at once.
Turn the idea into a repeatable workflow.
- Collect failing destinations with their source pages, link text, and response status. Distinguish a confirmed missing page from a temporary server error, a blocked automated request, a timeout, or a destination that requires authentication.
- For internal links, establish what happened to the content. Correct a typo, update the source link to the final preferred page, or restore accidentally removed content when appropriate. Use a relevant redirect only when a meaningful replacement actually exists.
- For external references, find the original publisher's current destination and verify that it supports the statement. If no reliable replacement exists, revise the claim or remove the reference rather than linking to an unrelated page merely to eliminate an error.
- Re-test the repaired source pages and shared templates. Keep a helpful error page with navigation while returning the correct error status for missing content. Review new failures after content removals, imports, navigation changes, and domain migrations.
On an illustrative staging site, collect a typo, a moved service URL, and a deleted product with no equivalent. Approve the obvious typo correction, map the service to its intended replacement, and revise the product reference manually. Re-crawl changed pages before applying the same rules to a larger batch.
Make the next step specific.
Choose one commercially important page or a small, related group of URLs. Record its current state, the user need, the proposed change and the person responsible. Separate evidence from assumptions so you can tell whether the work solved the original problem.
Use the Gavek planning workspace to turn these checks into assigned priorities. The free website snapshot can help inspect initial HTML signals; it does not replace a site-wide crawl, a live ranking data source or an index coverage review in Search Console.
Avoid the work that creates more work.
- Redirecting all missing pages to an unrelated homepage.
- Treating every automated request failure as proof a link is dead.
- Fixing a destination while leaving the old URL in shared navigation.
Measure useful progress.
Keep the comparison period, location, device and data source consistent. Search results and AI answers vary; a single observation is a diagnostic clue, not proof of long-term growth or causation. Connect visibility changes to relevant enquiries, qualified leads or sales wherever reliable first-party data is available.
Questions worth asking.
Are all 404 pages harmful mistakes?
No. A removed page without an equivalent replacement should return an appropriate not-found response. Investigate valuable missing content and the links that lead people there; do not hide every genuine removal behind a generic redirect.
Should I replace a broken external link automatically?
Only after checking relevance and accuracy. The new destination must still support the surrounding content. A technically working URL is not a good reference if its topic, ownership, or evidence has changed.
Go to the source.
These independent guides are grounded in primary documentation. Platform behavior and search systems can change; consult the linked documentation when implementing a change.
- developers.google.com · › crawling › docs › troubleshooting › http-status-codes
- developers.google.com · › search › docs › crawling-indexing › 301-redirects
- developers.google.com · › search › docs › crawling-indexing › links-crawlable
Editorial guidance from Gavek. No ranking guarantees, customer-result claims or endorsement by the referenced platforms.