How to Find and Fix Broken Links (2026): Audits, 404s, and Redirect Best Practices

Finding Broken Links

Start with discovery, then move to a full inventory.

• Google Search Console (GSC): In 2026, you’ll typically spot “Not found (404)” signals inside the Pages and Indexing reporting (and sometimes via specific examples under indexing statuses). GSC is separate from Google Analytics—you can link properties, but it’s not an analytics integration that automatically explains traffic impact.
• Site crawlers: Tools like Screaming Frog, Ahrefs Site Audit, and Semrush Site Audit crawl your site like a search engine and produce a comprehensive list of broken internal links, broken outbound links, and redirect hops.

If you’re prioritizing internal fixes, it helps to understand internal linking best practices so you can repair the pages that distribute authority and guide crawlers first.

A practical 2026 workflow

1. Use GSC for discovery: Export affected URLs and patterns (e.g., legacy paths, parameter variants).
2. Run a crawler for a full inventory: Capture every 4xx/5xx, every redirect, and every inlink source.
3. Validate with server logs (optional, powerful): Confirm what Googlebot and users actually hit, and how often.
4. Prevent recurrence: Schedule crawls, add CI/CD link checks for templates/content, and use monitoring (uptime tools, CMS plugins, or automated audits) to catch regressions early.

Fixing Broken Links

Once you’ve identified broken URLs, choose the lowest-risk fix that restores a good destination.

• Internal broken links:
• Update the link to the correct URL if the page moved.
• Replace the link with the closest relevant alternative if the content is gone.
• Remove the link if it no longer serves the user.

• External broken links:
• Replace with a current, trustworthy source.
• Remove if no equivalent exists.

Prioritize fixes based on impact: pages with high traffic, strong internal link prominence (nav, templates), and URLs with valuable backlinks.

Preventing Broken Links

Broken links are often a process problem, not a one-time cleanup.

• Add link checks to publishing workflows (especially for resource pages)
• Standardize URL changes with a redirect map
• Re-crawl after releases and migrations
• Monitor recurring 404 patterns (old campaigns, renamed categories, trailing slash changes)

Implementing Redirects

For permanent moves, 301 redirects remain the standard way to send users and crawlers to the right place while consolidating signals over time.

Modern best practice is less about “diluting SEO value” and more about crawl efficiency, latency, and UX. Keep redirects to a single hop and update internal links to point directly to the final URL.

Mini-example:

• Chain (avoid): /old-page → /interim-page → /final-page
• Best practice: /old-page → /final-page (and update internal links to /final-page)

Quick redirect decision checklist:

• Use 301 when a page has a clear replacement (new URL, consolidated content, renamed product/category).
• Use 410 when content is intentionally removed with no replacement and you want to signal “gone” explicitly.
• Leave as 404 when the URL was never valid, is low-value noise, or is the result of random probing—just ensure it’s not linked internally and your 404 page helps users recover.

Conclusion

Fixing broken links is less about chasing every 404 and more about protecting the paths that matter: internal navigation, crawlable site architecture, and high-value URLs that earned links. Use GSC to spot issues, a crawler to inventory them, and clean redirect practices to keep both users and bots moving efficiently.