SleekView Charts for Broken Link Checker
Broken Link Checker fills wp_blc_links and wp_blc_instances with every URL it scans. SleekView Charts reads the same rows and renders them as Number, Pie, Bar and Area cards so SEO leads see the shape of the rot, not just the latest scan page.
♾️ Lifetime License available
Broken Link Checker already scans the site. The pile-up needs a picture.
Broken Link Checker stores every link it finds in wp_blc_links (with columns like url, http_code, broken, redirect_count, last_check, log) and every place that link appears in wp_blc_instances (post id, container type, container field). After a few weeks on a mid-size site, those tables hold tens of thousands of rows, and the default Tools, Broken Links screen is a paginated list of the latest fifty.
A list is fine for a one-by-one fix. It is not fine for a quarterly link-health review or a migration sign-off. SleekView Charts reads the same tables and pivots them: a Number card for total broken links right now, a Pie for the http_code split, a Bar for which container type (post body, comment, custom field) holds the most rot, an Area for broken-found-per-day so leads can see whether the rot is steady or spiking.
The plugin still does the crawling, the retry logic and the dismiss workflow. SleekView only surfaces what is already in the database, so editorial standups can argue about a real KPI instead of guessing how bad the link inventory looks this month.
Workflow
Turn Broken Link Checker tables into a dashboard
Read the link and instance tables
Compose the chart cards
Save and scope the dashboard
Share or export
Sample dashboard
Charts you can build from Broken Link Checker data
Currently broken links
Count
Broken links by HTTP code
Count
group by http_code
Broken links by container
Count
group by container_type
New broken links per day
Count
group by first_failure
Comparison
Default Broken Link Checker reporting vs SleekView Charts
Default Broken Link Checker results screen
- Tools, Broken Links is a paginated list, not a KPI surface
- No native split by HTTP code or container type as a visual
- No time series of newly broken links to brief a quarterly review
- Dismissed and warned states stay invisible at any aggregate level
- No way to share a read-only link-health snapshot outside WP admin
SleekView Charts
- KPI card for current broken-link count across the site
- Pie split by http_code so SEO leads see why links break, not just that they do
- Bar of broken links per container type for editorial vs comment rot
- Area trend of newly broken links per day for cadence reviews
- Filters carry between the chart view and the audit table
Features
What SleekView Charts gives you for Broken Link Checker
Dashboard, not just a results page
Render the blc tables as Number, Pie, Bar and Area cards so SEO leads see the shape of link rot, not another paginated results screen.
Filters span table and chart
Filter to 404s only or to a single container type in the chart view and the audit table stays in sync. Same rows, two ways of reading them.
Share a read-only snapshot
Send the migration lead a URL of the link-health dashboard or export the filtered set to CSV. Quarterly reviews get a number, not a vibe.
Audience
Who builds Broken Link Checker charts dashboards with SleekView
SEO leads
Watch total broken links by week, split by http_code and container, then argue about resourcing with a real KPI instead of a screenshot of the latest scan.
Migration teams
After a launch, the broken-per-day Area card tells you whether new rules are catching the legacy URLs or whether the rot is still climbing.
Editorial leads
The container-type bar separates editorial rot from comment rot, so the cleanup ticket lands on the right desk instead of the SEO lead's queue.
The bigger picture
Why link rot needs a dashboard, not just a results page
Broken Link Checker is excellent at finding broken links, but the default Tools screen treats every result as an individual ticket. That works on a brochure site with twenty links. On a mid-size publication with twenty thousand outbound URLs, the list view never gives anyone the shape of the problem: how bad is it this quarter, is it getting worse, which container is bleeding, are the failures 404s or upstream timeouts.
SleekView Charts pivots the same wp_blc_links and wp_blc_instances rows into a Number KPI, a code split, a container split and a daily trend. Editorial leads suddenly have a number to chase. SEO leads have a chart to put on the slide.
The crawler keeps doing its job, the dismiss workflow stays in the plugin, but the inventory finally tells its own story.
Questions
Common questions about SleekView Charts for Broken Link Checker
Only WordPress data: the wp_blc_links table (url, http_code, broken, redirect_count, last_check, first_failure, log) and the wp_blc_instances table (container_type, container_id, container_field, link_text), plus any custom columns the plugin adds in your version. SleekView does not re-crawl. If a link is not in the table, it does not appear in the chart.
No. SleekView never makes outbound HTTP requests to verify links. It only surfaces what Broken Link Checker has already written to wp_blc_links and wp_blc_instances. Crawling, retry logic, schedule and dismiss workflow stay in the plugin.
Yes. Group a Pie or Bar card by http_code and the chart shows 404 vs 410 vs 500 vs timeout vs DNS failure. Useful for separating links that genuinely disappeared from upstream servers that are flaking. Different splits drive different actions, and the split makes that obvious.
Yes. Group an Area or Line card by first_failure (or last_check, depending on the angle you want) with a Count aggregation, and the chart shows new broken links per day, week or month. Migration sign-offs use the trend to confirm that the post-launch rot stops climbing.
Yes. The dismissed and warned flags are columns on wp_blc_links, so a Pie split by status or a filter on broken vs warned vs dismissed surfaces the full triage state. Useful for spotting links that have been silently warned for months without anyone acting on them.
Yes. wp_blc_instances stores the container_id and container_type for every link instance, so a filter on container_type = post (or page, or a custom post type) narrows every card. Editorial cleanups for a documentation knowledge base, for example, can run against a docs-only dashboard.
Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show, so the SEO lead can share a quarterly link-rot briefing with an external editor or archive a snapshot before a clean-up sprint.
The cloud version stores results in WPMU DEV's servers rather than wp_blc_links, so the local-table dashboard only applies to the classic, self-hosted scanner. Sites running the cloud variant should keep that variant's own dashboard. SleekView Charts reads what is in WordPress; it does not call WPMU DEV's API.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout