Broken link checking

Every link checked, on every page.

Frank follows every link on every page in your sitemap, internal and external, and tells you which are broken, how serious it is, and exactly where each one sits.

  • Set up in 30 seconds
  • Unlimited scans
  • No code required

Updated

Why it matters

A broken link is the first thing clients click.

  1. 01

    First impressions

    A nav link that 404s on launch day undoes weeks of careful design in one click.

  2. 02

    Leftover dev links

    Links to localhost or a staging domain work on your machine, and nowhere else.

  3. 03

    Links go stale

    External pages move. A link that worked when you built the page can be dead by launch.

How it works

What counts as broken.

Frank sorts what it finds by how serious it is, so the fixes that matter come first.

  1. 01Severity

    Major and minor, sorted for you

    Server errors and unreachable links are major issues. Client errors like a 404 are minor. Timeouts after 8 seconds, DNS and SSL failures, redirect loops and links to localhost or private addresses all count as unreachable.

    • Server errors (5xx): major
    • Unreachable links: major
    • Client errors like 404: minor
  2. 02No false alarms

    Built to ignore the noise

    Sites like LinkedIn block automated checkers, so Frank deliberately ignores 403, 429, 451 and 999 responses. Redirects aren't errors either: Frank follows up to five hops and judges where the link finally lands.

    • Each link checked once per page
    • Shown with its URL, text and status code
    • Highlighted on a screenshot of the page

Frequently asked questions about broken link checking

  • Every link on the page (every <a href>), internal and external. Anchor links, email, phone and SMS links, and links back to the same page are skipped.

  • A button doesn't point anywhere, so there's nothing to follow. Instead, Frank's accessibility check flags buttons and links that have no readable name.

  • Some sites, LinkedIn included, return 403, 429, 451 or 999 to block automated checkers even when the link works. Frank deliberately ignores those codes so you don't chase false alarms.

  • No. Frank follows up to five redirects and judges the final destination. A redirect loop counts as unreachable.

  • The link URL, its text, the status code and its position highlighted on a screenshot of the page. If the same link appears more than once on a page, it's checked and reported once.

Explore Frank

See what else Frank does for you.

  1. 01

    Accessibility checks

    Frank flags missing alt text and common accessibility issues on every page, from skipped heading levels to unlabelled form fields.

    Feature
  2. 02

    Figma design QA

    Map your Figma pages to your live site once, then review every page side by side with its approved design.

    Feature
  3. 03

    For Framer

    Automated QA for Framer sites: check every page and CMS page on your staging or preview URL before you publish to your domain.

    Solution
  4. 04

    For Webflow

    Automated QA for Webflow sites: check every page and CMS template on your webflow.io staging site before you connect the domain.

    Solution
  5. 05

    For WordPress

    Automated QA for WordPress sites: check every page on your staging site for lorem ipsum, broken links and accessibility before launch.

    Solution
  6. 06

    For agencies

    Consistent, automated QA across every project and every team member, with a scored record of every scan.

    Solution
  7. 07

    For freelancers

    A second pair of eyes for solo designers and developers: automated checks on every page, so you can hand over with confidence.

    Solution
  8. 08

    Frank vs BugHerd

    BugHerd collects visual feedback from clients and teams. Frank runs automated QA checks on every page. Here's how they compare.

    Comparison
  9. 09

    Frank vs Pixelay

    Pixelay overlays a Figma design on a live page inside Figma. Frank reviews every page against its design and runs automated QA checks too.

    Comparison
  10. 10

    Frank vs Sitepager

    Sitepager tracks what changes on a site between updates. Frank checks a build before launch and lines it up with the Figma design. Here's how they compare.

    Comparison
  11. 11

    Frank vs manual QA

    Manual QA is slow, inconsistent and easy to skip. Frank automates the repetitive half, so your team keeps the judgement calls.

    Comparison
  12. 12

    Lorem ipsum checker

    Frank checks every block of visible text on every page for Latin filler, in any word order, and flags it before your client sees it.

    Feature
  13. 13

    QA reports & scores

    Every page gets a score out of 100 and a red, amber or green status, with issues highlighted on a screenshot, every scan kept, and reports you can share with clients by link.

    Feature
  14. 14

    Team markers

    Pin issues straight onto a scanned page, comment, @mention a teammate and filter by priority, so nothing gets lost between review and fix.

    Feature

More on pre-launch QA

All articles

Launch without the 404s.

Run your first scan in minutes. Every plan includes unlimited projects and unlimited scans.

  • Set up in 30 seconds
  • Unlimited scans
  • No code required