Linkbruno Reviews and Details

Social recommendations and mentions

• Your redirects file should be append-only. Deleting a redirect is a breaking change.

  We think about this a lot at linkbruno.com, because the most common source of broken inbound links isn't a site disappearing. It's a site that moved, and then forgot where it used to live. - Source: dev.to / about 21 hours ago

• Every URL in your error messages is a promise: a 10-point checklist for links baked into software

  If you'd rather not build all of this yourself, checking links continuously, including the ones that live outside your current pages, is the problem we focus on at linkbruno.com. - Source: dev.to / about 21 hours ago

• How to find broken #anchor links, the ones every link checker says are fine

  Fragment checks are one of the details we care about at linkbruno.com, because a link that lands in the wrong place wastes the reader's time just as surely as a 404. - Source: dev.to / 2 days ago

• 429, 403, 999: a link checker's FAQ for sites that don't want to talk to you

  All of this logic (per-host limits, retries, classification, caching) is the unglamorous core of a reliable link checker. If you'd rather not build it, a service such as linkbruno.com handles it and reports broken links separately from ones it couldn't verify. If you do build your own, the buckets above are the thing to copy. - Source: dev.to / 3 days ago

• Markdown links in a monorepo: 7 things I'd do differently after the third big folder move

  The fix is mostly cultural, with a little tooling: one style, a fast local check that blocks merges, a slower external check that doesn't, and a habit of leaving signposts. For the published side of your docs (the site your users actually read), a crawler such as linkbruno.com can watch for broken links after deploy, which catches the cases a repo-level script can't see, like a redirect removed on the hosting side. - Source: dev.to / 3 days ago

• Case study (hypothetical): moving from Windows to Linux hosting broke 1,900 links, all because of capital letters

  After the changes, the team re-crawls the site and confirms internal broken links are back to near zero. They keep watching the 404 log for a few weeks for external links they didn't know about, and set up a scheduled crawl with linkbruno.com so new breakage shows up within days instead of via customer emails. - Source: dev.to / 4 days ago

• Quick tip: your link checker probably skips mailto: and tel: links. Check them yourself in 40 lines

  This is a static check: it looks at the HTML, not at whether mail actually arrives. It complements regular link checking rather than replacing it. For the HTTP side, a crawler like linkbruno.com scans your pages for broken links on a schedule, and a script like this covers the contact links that don't have a status code to check. - Source: dev.to / 4 days ago

• Your link checker's timeout is lying to you: a local benchmark of false positives

  If you'd rather not tune this yourself, linkbruno.com separates timeouts from hard errors and re-checks uncertain results before reporting them. But the experiment above is worth running once either way, just to see how much a single setting changes the story. - Source: dev.to / 5 days ago

• Your static site generator can catch broken links at build time. Here's how in 6 popular ones

  A monitoring service that crawls your live site and reports broken outbound links over time. That's what linkbruno.com does, and it also catches problems that appear on the live site without a deploy. - Source: dev.to / 5 days ago

• Should your docs link to GitHub's main branch or to a permalink? Both options rot.

  Run a link checker (your own script, or a crawler like linkbruno.com for a published docs site) to catch the 404s. Line drift needs a human or a smarter script, because no status code reports it. - Source: dev.to / 6 days ago

• The anatomy of a URL, and which part of it broke your link

  Automated checkers do the same walk at scale. A simple script with new URL() catches missing schemes and localhost links, and a crawler such as linkbruno.com checks the rest against live responses. - Source: dev.to / 6 days ago

• HEAD vs GET for link checking: HEAD is faster, and it lies more than you'd think

  If you'd rather not maintain the retry logic, user agents and edge cases yourself, a hosted checker like linkbruno.com handles the crawl. The method choice still matters to understand, because it explains most of the "this link works for me!" disputes you'll have with a report. - Source: dev.to / 7 days ago

• '0 broken links found' is a myth: 7 places link checkers don't look

  Close it: match frequency to importance. Check critical pages (pricing, signup, top docs) daily, the rest weekly. A scheduled crawler such as linkbruno.com handles the "run it repeatedly" part, and the cadence decision is still yours. - Source: dev.to / 7 days ago

• Redirect chains: why 3 hops is 2 too many (and a script that finds them)

  Chains come back with every migration. A crawler that follows links and reports redirecting internal links will catch new ones early. Running a regular crawl with linkbruno.com, or the script above in CI, turns "we'll clean up redirects someday" into a list you can actually close. The worst version of a chain, the one that loops back on itself, gets its own post next: how to find redirect loops before users hit... - Source: dev.to / 7 days ago

• ERR_TOO_MANY_REDIRECTS: the 6 configs that cause redirect loops and how to find them

  Pipe those through a hop tracer and flag anything that repeats or exceeds 5 hops. A link checker like linkbruno.com will report redirect loops it meets during a crawl, but the variant list is what catches the ones no internal page links to. - Source: dev.to / 7 days ago

• Soft 404s: your 'page not found' returns 200, and your link checker thinks it's fine

  Status-code checks miss soft 404s, so a decent link-checking setup adds at least one of: a not-found fingerprint, a keyword scan, or redirect-to-home detection. Watch for loops too, since some catch-all rules bounce missing pages around before landing on /. The previous post on redirect loops has the tracing commands. linkbruno.com and similar crawlers are most useful when the site returns honest status codes in... - Source: dev.to / 7 days ago

• LinkedIn returns 999, Cloudflare returns 403: why your link checker reports links that aren't broken

  A hosted crawler like linkbruno.com is useful mostly because someone else has already done this classification tuning. Whatever you use, check that its report separates "dead" from "couldn't verify". - Source: dev.to / 7 days ago

• Should a broken link fail your CI build? Block internal links, warn on external ones

  The same policy works with any tool. In a small repo, even a short script that resolves relative Markdown links against the file tree is enough for the PR job. Check links in Markdown docs with a 60-line Python script has one you can drop in. For a live website rather than a docs repo, a browser test like the one in How to find broken links with Playwright fits better, and a scheduled crawl with something like... - Source: dev.to / 7 days ago