Enter a page address: we read the page and check every link on it once (up to 60): pages, other sites and images. Free, no account needed.
This checks one page. To walk a whole site level by level, use the broken link finder on a paid plan. Run the full check →
Guide
How to use the broken link checker
What this broken link checker does
Enter the address of one page. The checker reads that page, collects every link on it, up to 60, and requests each one once: other pages of your site, pages on other sites and images. You get the links that fail, the ones that could not be verified, and the ones that redirect. It needs no account and does not walk the rest of your site.
How to read the results
Broken links: the target answered with an error such as 404 Not Found or 410 Gone, or could not be reached. The HTTP column shows the status.
Could not be verified: the target blocked the request, limited the rate or was too slow. These are often fine in a browser; open them yourself before you change anything.
Redirected links: the link works but goes through a redirect first. The table shows where it ends up.
Found on: the page where the link appears, so you know where to edit it.
The summary line counts the broken links, the pages read and the links checked.
What to fix first
Fix broken links in your main navigation, footer and calls to action first: they appear on many pages and lead visitors and crawlers into dead ends. Then fix links inside your content. For a page you moved, link to the new address and add a 301 redirect from the old one. For a page that is gone for good, remove the link or point it to the closest useful page.
Update internal links that redirect so they point straight at the final address. One redirect is harmless, but chains slow down people and crawlers, and a link that redirects to the home page usually means the original page no longer exists.
Common mistakes, with examples
Mixing up http:// and https://, or www and the bare domain, in internal links, so every link goes through a redirect.
Relative links that break when a page moves, such as ../pricing on a page that is now one level deeper.
Images that were deleted from the media library while posts still use them.
Links to files on a staging or local server, such as http://localhost:8000/ or a test subdomain, left in published pages.
Treating every 403 from another site as broken. Many sites refuse automated requests; check those links in a browser.
Fixing links only in the page body and forgetting templates, so the same broken link keeps appearing on new pages.
Why broken links matter for AI search
AI crawlers follow links the same way search crawlers do. A page that links to dead ends wastes their visits and looks less maintained, and a source an assistant tries to open through your link may simply fail. Working links to your own key pages also help crawlers find those pages at all.
Checking a whole site
This free checker reads one page. On a paid plan, the broken link finder in your account walks your site level by level from a start page, 100 pages per run on Pro and more on higher plans, runs in the background and keeps each report so you can compare runs.
Frequently asked questions
How many links does the free checker test?
Up to 60 links on the page you enter, each requested once. Pages, links to other sites and images all count.
Why is a link marked as not verified when it works in my browser?
The other site refused our request, limited the rate or answered too slowly. Many sites block automated requests; if it opens in a browser, it is usually fine.
Does it check links in JavaScript menus?
It reads the links in the page's HTML. Links that appear only after JavaScript runs are not seen, just as most AI crawlers do not see them.
Is a redirect a problem?
One redirect is not an error. Point your own links at the final address anyway, and check redirects that end on the home page: the original page is often gone.