Practical Lens 41: Broken internal links break identity graph edges

If key pages are not reachable through working internal links, AI crawlers may not use them as evidence. Important facts can exist on the website and still be invisible in the site graph.

What this lens means

AI systems do not only read isolated pages. They also follow links to understand which pages belong together. Broken or missing internal links can disconnect About, Services, References, Certifications or Contact pages from the company identity graph.

Key terms

Internal link
A link from one page on the website to another page on the same website.
Identity graph edge
A connection that helps crawlers understand that two pages support the same company identity.
Evidence page
A page that contains facts AI systems can use to describe the company, such as services, proof, references or contact details.

Why this happens

  • Pages were moved, renamed or deleted without updating internal links.
  • Navigation, footer or content links point to 404, redirected or blocked pages.
  • Important evidence pages exist in the sitemap but are not connected through live page links.
  • Crawlers discover the homepage but cannot reliably follow links to proof, services or references.

What this usually indicates

  • Disconnected evidence: Important facts exist, but crawlers cannot reach them through normal site paths.
  • Broken identity graph: Pages that should support the same company identity are not linked together.
  • Weak proof discovery: References, certifications or service pages may not be used as supporting evidence.
  • Crawler dead ends: Bots follow links that return 404, redirects, blocks or unrelated pages.

What to verify (evidence-only)

  • Check whether core navigation and footer links return 200 status codes.
  • Verify that About, Services, References, Certifications and Contact pages are reachable through internal links.
  • Compare sitemap URLs with live internal links from the homepage and core pages.
  • Check whether important links work for normal requests and crawler-like user agents.
  • Fix broken links and replace redirect chains with direct links to final URLs.

Terminal check example

Replace example.com with the audited domain. The goal is to see whether core identity and evidence pages are reachable through working links.

curl -s https://example.com/ | grep -oiE 'href="[^"]+' | sed 's/href="//' | grep -iE 'about|services|references|case|certification|contact'
curl -I https://example.com/about
curl -I https://example.com/services
curl -I https://example.com/contact

PowerShell check example

Use this on Windows to inspect homepage links and test whether core linked pages return successful responses.

$html = Invoke-WebRequest -Uri 'https://example.com/'
$html.Links.href | Select-String -Pattern 'about|services|references|case|certification|contact'
Invoke-WebRequest -Uri 'https://example.com/about' -Method Head
Invoke-WebRequest -Uri 'https://example.com/services' -Method Head
Invoke-WebRequest -Uri 'https://example.com/contact' -Method Head

Frequently Asked Questions

Why do broken internal links matter for AI visibility?

Because crawlers use internal links to discover supporting evidence. If key pages are not reachable, they may not be used when AI describes the company.

Can a page be in the sitemap but still weak evidence?

Yes. A sitemap helps discovery, but working internal links show that the page is part of the core site structure.

What is the fastest check?

Start from the homepage and test whether links to About, Services, References, Certifications and Contact pages return successful responses.

← Back to Practical Lens library