One page, not a whole site. For the whole site, start with the sitemap.
The page and each link are requested from our server, with an agent identified as EinscubeBot. Nothing is stored.
The page’s links will appear here grouped by status: broken ones first.
Summary
- Links
- —
- Internal
- —
- External
- —
- Checked
- —
Results
Next step
Shall we fix it for you?
Send us this result and we reply within one business day with what we would fix first, how much work it is and what you can leave as it is.
Opens the form with the diagnosis already written. You can edit it before sending.
How to use it
01
Paste the URL
Of one specific page: a blog post, a product page, the home. All its links are read, internal and external.
02
Wait for the check
Every link is actually requested, three at a time. Broken ones come first; redirects next; fine ones folded at the end.
03
Fix and repeat
A 404 gets fixed or removed; a redirect gets updated to its final destination; a 403 gets checked by hand before touching it.
What a broken link costs
Wasted crawl
Google gives each site a crawl budget. Every link to a 404 is a request that leads nowhere, and on large sites that means fewer useful pages crawled.
Lost signal
An internal link passes authority to its destination. If the destination does not exist, that signal evaporates; if it redirects, it arrives late and sometimes diminished.
A page that looks abandoned
For a visitor, a broken link is proof that nobody reviews the site. It is the kind of detail that decides whether they trust a contact form.
A broken link should never reach production
Links break without anyone touching them: a page gets renamed, a product is withdrawn, an external site shuts down. Reviewing them by hand every so often is the usual way to find out late.
On the sites we maintain, the check is part of the build: every internal link is verified against the generated pages and, if one points at a page that does not exist, the deployment does not go out. External ones are reviewed on a schedule and the alert arrives before a customer finds it. This tool is the pocket version of that review.
Frequently asked questions
Why does a link that works show up as 403?
Because the destination server rejects requests that do not come from a browser. Many sites — and almost every large platform — filter by user agent or IP reputation, and our request identifies itself as a bot on purpose. A 403 here does not mean the link is broken: open it in your browser and, if it loads, leave it alone. That is why it gets its own group rather than sitting among the broken ones.
Is a 301 a broken link?
No: the page exists, just at another address. But it is worth updating the link to the final destination for two reasons: every hop is a round trip paid by whoever clicks, and Google passes less signal through each link. It is the typical clean-up after a migration, when half the site still links to the old URLs.
Does it check the whole site?
One page at a time. Crawling an entire site from here would mean hundreds of requests per visit and would turn the tool into a crawler, which it is not. For a site-wide view, start with the sitemap checker: it tells you which URLs are declared and which respond; then review the pages that matter one by one.
What about nofollow links?
They are checked the same and flagged. Nofollow tells Google not to pass signal or follow the link, but for a visitor it is a link like any other: if it is broken, it is broken. It usually shows up in comments, sponsored links and inherited footers.
Do broken external links hurt SEO?
Less than internal ones, but it is not free. An external link to a 404 is a bad experience for whoever clicks and a sign of an unmaintained page. If the linked site disappeared, point to its copy on Internet Archive or remove the link; if it only changed URL, update it.
How many links does it check?
Up to a hundred per page, three at a time. If the page has more, internal ones are checked first, since those are the ones you can fix, then external ones in the order they appear. The summary says how many there were in total and how many were checked.
Is anything I check stored?
No. The page and each link are requested from our server on Cloudflare because a browser cannot read other domains; the analysis happens in your browser and we log neither the URL nor the results. Responses are cached for ten minutes, so repeating the check does not request the same thing again.
Broken links that come back every month?
Fixing them one at a time is patching. What we do is make them unpublishable: a check on every build for internal ones and a scheduled review with alerts for external ones.
We reply within one business dayBogotá · UTC−5