LynBro Plugins
/ Links
LynBro Plugins
/ Links
The two plugins most sites use for this hold 3.8 and 3.9 stars between them, and their reviews say why in three words: my database crashed, and false positives every time. This one is built against those two sentences.
Free forever, with no paid tier planned. Scanning runs on your own server, so there is nothing for us to meter.
checks for ten thousand links — an address is stored once, however many pages point at it.
A URL is stored once, however many pages link to it, so ten thousand links on a site are usually eight hundred requests rather than ten thousand. Every pass reads a fixed number of rows with a cursor, so nothing gets slower the deeper it goes, and no work at all happens on a visitor’s page load.
A 404, a 410, and a domain that no longer resolves. A timeout, a certificate problem, a server having a bad day, a site that refuses automated requests — each is reported as exactly that, in a sentence, with the evidence attached. A report you can trust is worth more than a report that is confident.
You find a page that has gone, and the next thing you want is for its old address to lead somewhere. So the redirect rules live here too, one click from the link that sent you looking, and one click from the 404 journal that shows who came asking.
No "Pro" tier, no nag screens. The features other plugins paywall are here from day one.
Amazon, LinkedIn, the academic publishers and anything behind Cloudflare refuse robots while serving people perfectly. Those are reported as blocked, never as broken. Ninety of the usual suspects ship with the plugin, protection layers are recognised from the response itself, and you can add your own.
It is listed on its own, with the address it now points at, so you can tidy it up when you feel like it. Redirect chains are followed by hand, so you are told both that the old address moved and whether the new one works.
A domain that will not resolve has to fail more than once before we believe it, and a link that never answers is reported with how many times we tried rather than promoted to broken behind your back.
Posts, pages, every custom type, comments, category descriptions, widgets and custom menu links — and within them, links, images, embeds, background images, Gutenberg block attributes and the JSON a page builder keeps a whole page in. A checker that reads only the post body reports an Elementor site as having no links at all.
Change an address everywhere it appears, or take the link off and keep the words. Both work in bulk, both work inside a page builder’s data, and both are written down so they can be undone.
301, 302, 307, 308 and 410. Exact addresses or patterns with $1 groups, compiled when you save them so a broken one never reaches a visitor. Each rule counts how often it is actually used, so you can retire the ones that are not.
Every request that ended in a 404, how often, and where it came from — one click from a redirect. Capped so a robot trying random paths cannot fill your database, and trimmed on your schedule. The visitor’s IP address and browser are off by default.
Rules from Redirection and Simple 301 Redirects, and — the part nobody else offers — the links you already went through by hand in Broken Link Checker and marked as fine. They arrive already ignored, so you do not spend that afternoon twice.
The two plugins most sites use for this, and what they are actually rated.
| Feature | Lynbro Links | Broken Link Checker | Redirection |
|---|---|---|---|
| A reason in words for every verdict | â | â | â |
| A 403 from a robot-blocking site is not “broken” | â | â | â |
| Never calls a single timeout broken | â | â | â |
| “Not broken”, remembered for good | â | â | â |
| Each address checked once, not once per page | â | â | â |
| A wall-clock budget on every burst of work | â | â | â |
| Stopping keeps its place | â | â | â |
| Reads page-builder layouts, not just the post body | â | â | â |
| Change an address across the whole site | â | â | â |
| Undo a change it made to your content | â | â | â |
| Redirect rules and a 404 journal | â | â | â |
| Imports the other one’s work | â | â | â |
| Scanning stays on your own server | â | â | â |
| No paid tier at all | â | â | â |
The scan never runs on a visitor’s request. It runs in the background in short bursts, each with a time budget and a memory ceiling that are checked between every page it reads and every address it asks about. On the front end the only work is a redirect lookup against a cached list, plus — if you leave the journal on — one small write when a request ends in a 404.
Because we do not know, and saying so is the point. A timeout, a certificate problem, a 500 or a refusal from a bot filter all happen to links that work perfectly well. Calling those broken is how a link report turns into a list nobody reads. The reason is always spelled out, so you can judge it in a second.
Not here. Amazon answers automated requests with whatever it likes — including a 404 for a product page that opens fine in a browser. We tested exactly that. A refusal, or even a “not found”, from a site on the robot-blocking list is reported as what it is and never as a broken link. If a site of yours behaves that way, add its address in the settings.
Yes. Elementor keeps the whole page in a custom field rather than in the post body, and that field is read — including markup nested inside it. Other builders can be added by naming their field in the settings.
No. It reads your site and checks the addresses your site points at. Crawling other people’s sites is a different product, and not one we are building.
They stop, because nothing is left running. They are still in the database and start working again when you switch it back on. Deleting the plugin removes them for good, so export first if you might want them back.
No, and there will not be one. Everything runs on your server, which costs us nothing per site, so there is nothing honest to charge for. Nothing here is capped, metered or reserved for later.
Nothing. Every table and every setting it made is removed, and none of your data was ever anywhere but your own database in the first place.