Launched this week
Broken Link Checker is a native app built for Liferay DXP that automatically scans pages, navigation menus, web content, fragments, ADTs, and templates to detect broken, invalid, and inaccessible links. It pinpoints the exact source of every issue, helping teams quickly resolve errors, improve SEO, enhance user experience, and maintain a reliable, high-performing digital platform.
Does it catch redirects or only true 404s, and how often does the scan run in the background?
@kenan784649
Yes, the plugin handles redirects separately from broken links. It follows redirect responses (such as 301 and 302) and checks the final destination. If the final URL returns a 200 OK response, the link is treated as valid and is not reported as broken. Only links that ultimately result in client or server errors (such as 404, 410, or 5xx responses) are flagged.
The scan does not run continuously in the background. It is executed on demand when initiated by the user, so there is no periodic background scanning or additional load on the system unless a scan is started.
One thing that would make this even more useful is adding a scheduled scan with email alerts so admins get notified right away when a new broken link appears, instead of having to run checks manually.
@rdvantemizzx9u
That's a great suggestion and definitely a valuable enhancement.
The current version of the plugin performs on-demand scans initiated by an administrator and reports the findings within Liferay. We intentionally kept the initial implementation focused on manual scanning to minimize background resource usage and give administrators full control over when scans are executed.
Super useful for our Liferay setup, finally caught a bunch of dead menu links we'd been ignoring for months. The detail showing exactly which fragment or template holds the broken URL saved me a ton of digging.
@zlemmld5
Thanks so much! 😊 We're really happy to hear it helped. Knowing exactly where a broken link lives was one of the biggest pain points we wanted to solve, so it's great to hear it saved you from digging through fragments and templates. Really appreciate you sharing your experience!
finally a tool that actually points to where the broken link lives instead of just saying "page not found". the scan across web content and fragments saved me a solid afternoon of clicking through structure pages.
@turgay76925
Thanks for the kind words! That was exactly the problem we wanted to solve. It's one thing to know a link is broken, but finding where it's actually used can take a lot of time. We're glad the scanner helped you skip all that manual searching. Thanks for sharing your experience!
Does this handle redirects and 404s differently, or does it flag any non-200 response the same way?
@grkem154790
The Broken Link Checker treats redirects and broken links differently.
200 OK – The link is considered valid.
3xx Redirects (301, 302, etc.) – The plugin follows the redirect chain and validates the final destination. If the final URL returns 200 OK, the link is considered valid and is not flagged as broken.
4xx/5xx Responses (404, 403, 500, etc.) – These are treated as broken or inaccessible links and are flagged for review.
In short, the plugin does not flag every non-200 response the same way. It distinguishes between redirects that successfully resolve and genuine broken or inaccessible links.