Broken Link Checker
Paste a page URL and every link on it gets requested and classified: working, redirected, client error or server error. Then fix the ones that actually cost you crawl budget, equity or users.
Give the checker one full URL, including https://. It passes the request to app.search.co, where search.co's own crawler loads that live page, extracts the links it contains and requests each destination to record the HTTP response. You get a per-link verdict instead of a sitewide guess, which makes it the right tool for spot-checking a template, a high-value article or a page you just migrated.
Running the first page costs nothing and needs no login. To check more pages after that, sign in with a free search.co account.
The guidance below skips the basics and covers what slows link cleanup down: template-level breaks, soft 404s that return a 200, redirect chains, and what to fix first.
What a page-level link check reports.
The scope is the single page you submit, not the whole site. Every anchor the crawler finds in that page's HTML is tested, which covers body copy, navigation, sidebars and footers. Expect the output to group links by outcome so the failures surface first.
- Client errors (4xx): destinations that return 404 Not Found, 410 Gone, 403 Forbidden and similar. A 404 or 410 is a real break; a 403 can mean a bot block on the remote server rather than a dead page.
- Server errors (5xx): destinations that failed on the server side. These are often transient, so recheck before you rewrite anything.
- Redirects and chains: links that do not resolve directly, with the hops between the linked URL and the final one, so you can see a 301 that leads to another 301 that leads to a 200.
- Internal versus external: whether the destination sits on your own host or someone else's, which decides who can fix it.
Reading status codes like an auditor.
A status code is the start of a diagnosis, not the end. The same 404 can be a typo in one article, a deleted product linked from a mega menu, or a URL pattern that changed in a CMS upgrade.
Internal breaks are fully in your control and usually the bigger problem. They waste crawl requests on dead ends, strand any equity that internal links would have passed, and tell users the site is unmaintained. External breaks are someone else's outage or deletion. You cannot fix the destination, but you can update, replace or remove the link.
Redirect chains deserve their own attention. Google follows a limited number of hops for a single fetch and treats a working redirect as a signal toward the final URL, so one 301 is fine. The trouble is accumulation: an HTTP to HTTPS hop, then a non-www to www hop, then an old slug to a new slug. For internal links there is no reason to link to anything other than the final 200 URL.
| Result | Typical cause | Owner and fix |
|---|---|---|
| Internal 404 | Deleted or renamed page, typo in a hardcoded link | You: update the link to the live URL, and add a 301 if the old URL had traffic or backlinks |
| Internal redirect chain | Several site migrations layered on top of each other | You: point the link at the final URL and flatten the redirect rules |
| External 404 or 410 | Source removed the page | You: swap in a current source or remove the link |
| External 403 or 429 | Remote server blocking automated requests | Open it in a browser first; often the link works for people |
| Any 5xx | Remote or origin server failure | Recheck later; act only if it persists across several checks |
Soft 404s, templates and other things a status code hides.
A soft 404 is a page that says "not found" or shows an empty result but returns a 200. A status-code check will mark it as working because, technically, it is. Google's systems may still classify it as a soft 404 and drop it from the index. When a link in the report resolves through a redirect to a homepage or a generic category page, treat that as a likely soft 404 too: redirecting removed content to an unrelated page is a pattern Google has said it may treat the same way.
Links that sit in a header, footer or sidebar appear on every page built from that template. One broken footer link checked on one URL is the same broken link on thousands of URLs. That is why checking one representative page per template is so efficient: the blog post template, the product template, the category template and the homepage cover most of a site's shared markup. For a sitewide crawl of many pages at once, the site audit is the better starting point.
Also watch for links that return 200 for the checker but fail for users, such as URLs behind a login, links that depend on JavaScript to build the destination, and fragment links (#section) pointing at anchors that no longer exist. A status code cannot see a missing anchor id, so spot-check jump links by hand.
A triage order for pages with many problems.
Fix in order of blast radius times value. A broken link in global navigation beats a broken citation in a three-year-old post, even though both are a single 404 in the report.
- First: template links: breaks in navigation, footer or shared components, because they repeat across the site.
- Second: internal links to money pages: links that should reach product, service or lead pages but hit a 404 or a chain.
- Third: internal chains: update hrefs to the final URL so internal links resolve in one request.
- Fourth: external breaks in high-traffic content: replace dead citations with a current source so the page stays credible.
- Last: everything else: batch the long tail into a quarterly cleanup instead of chasing it daily.
If a broken internal URL used to rank or earned links from other sites, do not just update your own links. Restore the page or 301 it to the closest equivalent, then confirm with the backlink checker whether external links still point at the old path.
Mistakes that make link cleanup slower.
Most wasted effort comes from fixing symptoms one page at a time, or from trusting a single check of an unstable remote server.
- Redirecting everything to the homepage: it hides the error from reports but gives users and search engines a mismatched page.
- Fixing the link, not the source: if a CMS shortcode or menu builder generates the bad URL, editing one page leaves the rest broken.
- Treating every 403 as dead: many sites block automated checkers. Confirm in a browser before deleting a valid citation.
- Checking once and moving on: external links decay over time. Recheck evergreen pages on a schedule you set in your own workflow.
Check a site's templates in four passes.
Cover most shared markup without crawling every URL.
List your templates
Pick one live URL for the homepage, a category or service page, a product or detail page, and a blog post.
Run each URL
Submit each page and note any break that appears in navigation or footer links on more than one template.
Fix shared components first
Correct template-level links in the theme or menu settings, then rerun one page to confirm.
Clean up page-specific links
Work through remaining internal 404s and chains, then external breaks on your highest-traffic pages.
Get an expert read on your results
Tools give you the raw numbers. Tell us your site and an SEO.co strategist will email you what they'd prioritise and the next steps they'd recommend.
Broken link checker questions.
Does this check my whole website?
Why does a link work in my browser but show an error here?
Are redirects bad for SEO?
Can it detect soft 404s?
Should I remove or replace broken external links?
How many pages can I check for free?
Migrating or cleaning up a large site?
SEO.co's technical audit maps broken links, redirect chains and soft 404s across every template, then hands your developers a prioritized fix list.