Are any internal links sending visitors to a dead end?
A link that once worked and now 404s is invisible until someone clicks it. Broken internal links waste crawl budget, leak the trust you built, and quietly cost conversions.
Checks a set of internal links from your key pages with a real request. Saved to your account if you are signed in to a paid plan.
How this check works
Shipwork collects the internal links on a set of your key pages and requests each one, reporting any that return 404, 410 or a server error. It reads the links a crawler would follow, from outside your network.
What the broken internal link check tests
The check reads links from the pages discovered in a bounded crawl, deduplicates up to 30 internal URLs and requests up to 25 of them with HEAD. It reports URLs that return 404, 410 or a 5xx response and names the linked page URL. If all checked links respond outside those failure statuses, it reports that the checked sample answered cleanly. A failed request caused by a timeout is inconclusive and is not reported as a dead link.
This is not a full-site link inventory. A clean result covers only the links in the sample from pages the crawl reached. Some servers handle HEAD differently from normal browser requests, so confirm important findings with a direct request before removing or changing a link.
- Internal links found on fetched pages.
- A bounded set of unique destinations, with status checks for 404, 410 and 5xx.
- The dead destination and its reported HTTP status.
- No claim of a broken link when a request times out.
How to read a broken link result
A 404 means the server says the requested page is not found; 410 means it is gone. A 5xx response indicates a server-side error. The finding points to the destination, but you still need to locate the source page and decide whether the destination should exist. A temporary server error may clear on retry, while a removed product may need a redirect or a corrected link.
When a destination moved, update internal links to the new URL rather than relying on an old address to redirect. A redirect can preserve access, but the page should still be relevant to the original link. For permanently removed content without a replacement, remove the link or show an appropriate not-found response.
- Open the destination and source page to confirm the failure.
- Fix the link at its source if the page moved or the URL contains a typo.
- Restore the page or add a relevant redirect when content has a true replacement.
- Do not redirect every deleted URL to the homepage; the destination should match intent.
Fix broken links after site changes
Common causes include product handle changes, deleted collections, migrations, manual typos and links copied from a staging host. Search the site for the exact path shown in the finding. Update navigation, templates, editorial links and product references at the source. If the old URL has meaningful inbound traffic or a valid replacement, create a direct redirect and then update internal references so visitors do not need the extra hop.
For example, if a product moved from /products/blue-shirt-old to /products/blue-shirt, link to the current path in the product description and navigation. Add a redirect for legitimate old links, but keep the final URL in your own pages and sitemap.
- Check source pages and templates for the outdated href.
- Update the href to the live destination and verify it returns successfully.
- Use the redirect generator when an old URL needs a replacement rule.
- Use outbound link check for external destinations.
When a broken link check is useful
Run it after renaming pages, deleting products, migrating a domain or changing navigation. It is useful for catching obvious internal dead ends in the discovered sample, especially on key landing pages. If you need a complete map of links across a large site, use a deeper crawl with a larger page budget; this free check deliberately limits requests.
Broken links affect visitors directly and can waste crawler time, but one finding does not establish a broad ranking problem. Fix links that matter to navigation and content first, then check the relevant page response and rerun.
- Outbound links: dead external sources.
- Link graph: internal paths and site structure.
- Deep crawl: broader coverage when you need more than a bounded sample.
Questions
Why do broken internal links matter?
How are links broken?
Is this a full site crawl?
How do I find broken internal links on my website?
Do broken links hurt SEO?
Why does a broken link checker show a link that works in my browser?
Does the broken link checker crawl my whole site?
Should I redirect a broken internal link?
Keep reading
What this reads
- Reads public pages from outside your network, the way a crawler does.
- No signup, and nothing is stored on the free checks.
- One of 83 checks across discovery, content, markup, trust and catalogue data.
Cool, just ran an audit and got some insights! Let’s see if I can fix them :)
Whoah! this site is crazy, nothing to roast at all
cool as heck, tried it on my blog and the insights it gave are helpful and not bluff.