Broken links and dead anchors: find them before launch
Why 404s and missing #section targets hurt users and crawl paths, how to check a page, and what to fix first.
Short answer
Broken links return errors (404, 410, 5xx) or never resolve; dead anchors point to #ids that are missing on the page. Both waste clicks and leave crawlers at dead ends. Check each important page before launch, update internal hrefs to final URLs, and re-test after content moves.
Use the free broken link checker on key pages, and the redirect checker when a single URL needs a hop-by-hop look.
Why broken links hurt
Dead links waste clicks on pricing, docs, and blog posts. For crawlers, broken internal links are dead ends that leave deeper pages harder to discover. Links also rot after redesigns and partner URL changes—quietly, until a launch or client review.
Errors vs anchors vs redirects
- Broken destinations — HTTP 404, 410, or 5xx (or DNS failures).
- Dead anchors —
#idtargets missing from the page HTML. - Redirects — not failures, but update internal hrefs to the final URL when you can.
What to fix first
- 404s and 5xx on internal navigations and CTAs.
- Missing in-page anchors on long docs and pricing FAQs.
- Redirect chains on high-traffic paths (see the redirect guide).
- External partner links that permanently moved—update or remove.
How to check
Before launch, run the broken link checker on home, pricing, docs, and any page you share publicly. Pair with the launch checklist and, for hop-level status codes, the redirects guide. The Shipcheck extension checks the rendered tab when navigation is built only in JavaScript.
Questions
Are redirects counted as broken?
Usually not. A single redirect is fine for users. Prefer updating internal links to the final URL. Long redirect chains are worth fixing first.
What is a dead anchor?
A link to #section-id when that id is missing on the page. Users land at the top instead of the section; in-page navigation fails.
Why do some links show as blocked?
Many sites reject automated bots with 401, 403, or 429 even when browsers work. Confirm those URLs manually; focus on clear 404 and 5xx failures first.
How do I check a whole site?
Run the free broken link checker on each important page. Pro sitemap audit and the Chrome extension crawl help agencies cover more URLs.
Tools for this guide
Broken link checker
Find dead links, redirects, and missing pages on any public page.
Open tool →HTTP status & redirect checker
Follow the redirect chain hop by hop: status codes, Location headers, HTTPS upgrades, and long chains.
Open tool →Free website checker
Paste a public URL for one launch report from server HTML (SEO, headers, AI). Speed and WCAG are Pro in the Chrome extension; free install still helps on localhost and JS-heavy apps.
Open tool →More guides
Cloudflare, CDN, and WAF settings that block AI crawlers
Why ChatGPT and Perplexity still fail when robots.txt allows them: bot fight modes, AI scrapers rules, and how to verify real crawler access.
Read · 8 min →Keyboard focus order: catch tab traps before launch
What focus order means for WCAG, how to test with the keyboard alone, and how Shipcheck Pro’s overlay shows missing focus styles and unreachable controls.
Read · 8 min →Shipcheck fix prompts for Cursor, Claude, and ChatGPT
How free sample prompts differ from Pro’s every-issue prompts, what to paste into Cursor or Claude, and how to keep AI edits minimal and reviewable.
Read · 7 min →