Broken Internal Links
Checks for internal links pointing to 404 or 500 responses.
What this check measures
We extract all same-origin `<a href>` links from each crawled page and HEAD-request them. Any 404 or 500 is reported with the source page.
Why it matters
Broken links waste crawl budget, create dead ends for users, and signal poor maintenance to Google. Too many 404s = deprioritization.
How our audit detects it
Parse all <a href>, filter same-origin, HEAD request each. Collect 404/500 responses.
Typical findings
- error_outlineFooter links to /old-url that 404.
- error_outlineBlog post links to a renamed internal URL.
- error_outlineNav link to a page deleted in a redesign.
How to fix
Fix the link target or 301 redirect the old URL to a relevant current one. Use Screaming Frog or Sitebulb to find all broken links systematically.
Copy-paste fix prompt for your stack
Lovable · Cursor · Bolt · v0 · Replit · Windsurf · Claude Code · Base44
Frequently asked questions
301 or fix the link?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.