Broken Link Checker scans every URL referenced by the site's posts, pages, and comments, then flags 404s, redirect chains, and unreachable hosts. It writes scan results to wp_blc_links with link metadata, references in wp_blc_instances mapping each broken link to its containing post, filters in wp_blc_filters, and synchronization state in wp_blc_synch. The admin sees a clean dashboard; the visitor still hits the original 404 until someone fixes it.

SleekAI runs as a separate plugin and gives the visitor a chance to recover. On the site's 404 template, the chatbot reads the post archive, the relevant categories, and any redirects map the team has published, then suggests the closest live page in plain language. Broken Link Checker handles the audit; SleekAI handles the recovery in the moment.

Display conditions scope the chatbot to the 404 template and the search-results page, with no chatbot on the rest of the site to avoid noise. Every conversation logs page URL, model name, and token count so the team can see which 404s readers keep hitting, which is a useful signal for what to fix first in the Broken Link Checker queue. Generic chatbots cannot help here because they do not know the site's actual archive.

Broken Link Checker is one of the most useful tools in the WordPress ecosystem for any site with more than a few years of content behind it. Posts rot, external destinations move, internal URLs change after a slug edit, and without a scanner the team would never know. The trade-off is that the scanner reports the problem but does not solve the visitor's immediate experience.

A reader arriving from a five-year-old Reddit link still hits the 404 until someone in the team gets to that backlog item. A chatbot scoped to the 404 page catches that reader in the few seconds before they bounce back to Google. SleekAI is the right shape for this because it actually knows the site.

The bot reads the post archive, the categories, and any redirects map the team has published, then offers a confident suggestion of the closest live page. It does not have to guess like a generic chatbot would. It can say, with grounded data, that the 2021 buying guide moved to the 2024 revision and that the category page for coffee gear has the rest.

Over time, the conversation log doubles as a 404-prioritisation backlog: which URLs do readers actually arrive at, and which of those does the bot still struggle to redirect well. Each one is either a Broken Link Checker fix or a Safe Redirect Manager rule. The combination quietly turns a normally-leaky 404 page into a high-recovery surface.