Highlight links in place
Working links, redirects, broken responses, timeouts, and network errors get clear colored outlines and status badges.
See the problem in context
A focused link check without leaving the page
Click the toolbar icon and CheckLinks starts checking the current page. The page itself becomes the report, so you can see what needs attention and where it appears.
Filter and jump to a result
Use the summary filters, then select a result to scroll to its first matching link on the page.
Export a useful handoff
Download the URL, status, category, status text, and redirect destination as a CSV for follow-up.
Choose the right tool
CheckLinks vs. a full-site crawler
CheckLinks is intentionally a fast page-level checker. A crawler is the better choice when you need a site-wide inventory or ongoing monitoring.
| Need | CheckLinks | Full-site crawler |
|---|---|---|
| Best for | Reviewing the page in front of you before or after a change | Auditing many pages or an entire site |
| Where results appear | On the webpage and in a draggable browser panel | In a separate crawl report or dashboard |
| Setup | Click the extension icon on the current page | Configure a starting URL, scope, crawl rules, and sometimes authentication |
| Coverage | Links already present on one open page | Linked pages discovered across the configured crawl |
| Monitoring | Manual scans when you need them | Often supports scheduled, historical, and team reporting |
| Use both when | A crawler finds the broad pattern, while CheckLinks helps an editor or QA reviewer inspect and fix a specific page in context. | |
One-page workflow
Scan, inspect, fix, and recheck
- Open the page you want to review and click the CheckLinks toolbar icon. Scanning starts automatically.
- Start with Broken, then review Redirect and Other results such as timeouts.
- Click a result to jump to the first matching link, make the change in your editor or CMS, and reload the page.
- Run CheckLinks again to confirm the fix. Export the CSV if another person needs the results.
Developers who want to inspect or install the source can follow the developer-mode instructions on GitHub.
Practical guides
Use CheckLinks in a real publishing workflow
These guides focus on the decisions around a link check, not generic search advice.
How to check links before publishing a webpage
A short pre-publish pass for staging pages, redirects, broken responses, and handoff.
Broken-link QA after a website migration
Use representative pages and a URL map without confusing a page check for a complete migration audit.
Broken-link checking for documentation and content teams
Turn each article or documentation page into a small, repeatable QA unit.
What the colors mean
| Category | Typical result | What to do next |
|---|---|---|
| OK | 2xx response | No HTTP problem found; still confirm the destination content is correct. |
| Redirect | The request ended at another URL | Decide whether the page should link directly to the final destination. |
| Broken | 4xx or 5xx response | Correct, replace, or intentionally remove the link. |
| Other | Timeout, blocked request, network error, or skipped link | Retry and investigate in context before calling the link broken. |
CheckLinks FAQ
Does CheckLinks crawl an entire website?
No. It checks links on the page currently open in Chrome. Use a full-site crawler when you need broad discovery, scheduled monitoring, or complete inventory coverage.
Can a timeout or blocked result still work when clicked?
Yes. A site may require login cookies, block automated requests, rate-limit traffic, or respond differently to a browser-based check. Retry and verify ambiguous results manually.
Does CheckLinks collect browsing data?
No. CheckLinks has no account, analytics, or tracking. It does not send scan results to a service operated by the developer.
Where can I find troubleshooting and known limitations?
See the CheckLinks support and known-limitations page for restricted pages, skipped links, authenticated sites, timeouts, and reporting an issue.
Built and maintained by Mark Lee
I’m a solo developer sharing CheckLinks for free. The code is open source, and practical bug reports are welcome.
Check the page before someone else finds the broken link
Install CheckLinks from the Chrome Web Store, open the page you are reviewing, and run a focused link check in place.
Install CheckLinks on Chrome