Broken External Links
What Is This Issue?
Broken External Links is a final-tier technical or quality signal that commonly goes unresolved because it sits outside the core on-page and speed audit categories. Search engines process these signals continuously, and leaving them unaddressed creates a ceiling on ranking improvement even after higher-priority issues are fixed.
The underlying cause is usually that link audits focus on external broken links while internal link quality — nofollow misuse, empty anchor text, and redirect chains — is rarely included in regular QA cycles. This means fixing one instance rarely provides durable relief — the fix must be applied at the template, CMS configuration, or infrastructure level to prevent recurrence.
Internal link quality directly affects PageRank distribution, crawl efficiency, and anchor text relevance signals — broken or nofollowed internal links silently drain authority from target pages. Related issues to address in the same session: [Broken Page (404)](/seo-knowledge/issues/broken-page-url), [Too Many Links on Page](/seo-knowledge/issues/too-many-links).
Why This Matters
Outbound links to 404 pages reduce user experience and can signal low content maintenance quality to quality evaluators.
Step-by-Step Fix (Beginner Friendly)
- 1. Identify all affected URLs by running a full audit crawl filtered to this check type — group results by template, page type, and CMS section.
- 2. Fix at the source: update the template, CMS plugin setting, or server/CDN configuration rather than patching individual pages.
- 3. For CMS-managed sites: add a field validation rule or publishing pre-flight check so editors cannot publish new content with this issue.
- 4. Handle edge cases: test the fix on paginated pages, archive pages, localised URL variants, and AMP versions if applicable.
- 5. Deploy to staging first and verify using the relevant validation tool (Rich Results Test, Lighthouse, Search Console URL Inspection, or a dedicated link checker).
- 6. After production deployment, run a re-crawl on the same URL group and confirm the check passes for all previously failing URLs.
- 7. Cross-check related issues in this cluster — resolving [Broken Page (404)](/seo-knowledge/issues/broken-page-url), [Too Many Links on Page](/seo-knowledge/issues/too-many-links) at the same time amplifies the total fix value.
Code Example (Problem)
Current Problematic Implementation
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>SEO Issue Example</title>
</head>
<body>
<a href="/services/old-page">Learn more</a>
<!-- /services/old-page returns 404 — broken internal link -->
<a href="/blog/">rel="nofollow"</a>
<!-- Internal link with nofollow — PageRank not passed to own content -->
</body>
</html>Code Example (Solution)
Copy-Paste Ready Fix
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>SEO Fix Example</title>
</head>
<body>
<!-- Updated internal link to live URL -->
<a href="/services/technical-seo-audit">Learn more about technical SEO audits</a>
<!-- Internal links should NOT use rel="nofollow" -->
<a href="/blog/">SEO Blog</a>
<!-- Remove nofollow from internal navigation to allow PageRank flow -->
</body>
</html>Before vs After
Before
- Search engines and AI systems receive weaker technical signals for this page.
- The page can lose ranking potential and clarity in SERP presentation.
- Validation tools report this issue as unresolved.
After
- The page outputs a valid, machine-readable implementation for this check.
- Ranking and crawl interpretation signals become clearer and more reliable.
- Re-crawl and validation tools confirm the issue is fixed.
How to Verify (DevTools + Tools)
- Open the page in Chrome and press F12 to open DevTools.
- Use the Elements tab to confirm the expected HTML/meta/schema output is present.
- Use View Source to check server-rendered output (not only client-rendered DOM).
- 1. Re-run the audit crawler on affected URLs — confirm zero failures for this check across all previously flagged pages.
- 2. Open Chrome DevTools → Lighthouse on a representative URL and confirm no remaining diagnostics for this issue type.
- 3. Use Google Search Console URL Inspection → View Crawled Page to verify the fix is visible in the rendered DOM, not just View Source.
- 4. Validate in the appropriate specialist tool: Rich Results Test for schema, PageSpeed Insights for performance, or a hreflang checker for international issues.
- 5. Publish a fresh page using the same template and confirm it passes this check without manual intervention — proving the fix is durable.
When to Ignore
- Ignore only if the affected page is intentionally excluded from organic search (noindex with explicit editorial intent) and this is documented in the page settings.
- Ignore temporarily during an active migration where a replacement URL and redirect are scheduled within 30 days and tracked in a migration plan.
Common Mistakes
- Fixing the specific audited URL without updating the source template — the issue reappears on the next content publish.
- Validating only in View Source and missing rendered-DOM issues, or validating only in the browser and missing server-side template problems.
- Applying the fix to desktop templates but overlooking AMP, mobile, or PWA-specific templates that render the same content independently.
- Closing the issue in the project tracker before running a second audit pass to confirm zero recurrence across all page variants.
Related Issues
Glossary Terms
External Links
Links from your website to other websites — when used well, they add credibility by citing authoritative sources.
References
Free Audit
Check if your website has this issue
Run a free SEO and AI readiness audit on your website. Get a prioritised list of issues like this one — with step-by-step fix guides.