✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Feedback for Broken Link Checker

Broken Link Checker scans every internal and outbound link in WordPress and writes results to a custom table. SleekView Feedback turns those rows into a sortable, upvoteable board so editors vote on which links to fix, flag redirect loops, and request schema or sitemap follow up.

♾️ Lifetime License available

SleekView Feedback board for Broken Link Checker

From broken link scans to a live feedback board

Broken Link Checker writes every scan result to the blc_links table with HTTP status, source post, and last checked timestamp. The admin screens list rows in flat tables, but they leave editors with no shared view of which broken links actually matter, which redirect to a useful target, and which deserve schema or sitemap follow up after the fix.

SleekView Feedback reads blc_links directly. Point it at the scan table or a custom join with wp_posts, map a numeric column to votes, the HTTP status to category, and the fix progress to the status pill. Each broken link becomes one card with URL, source post, vote count, and status the whole team can triage.

Editors stop scrolling through hundreds of red rows. They land on a sorted board, upvote the broken links on pillar pages, flag the loop on a vendor redirect, and request a sitemap update once the canonical lands. The link cleanup roadmap stops being a guess and becomes a votable backlog tied to scan results already in the database.

Workflow

From link scan results to a public board

1

Pick the Broken Link Checker source

Point SleekView at blc_links or a custom join with wp_posts. Filter by HTTP status, source post type, or scan date so the board surfaces only the broken links the editorial team needs to fix during the current sprint.
2

Map vote, status, category

Choose which numeric column counts as upvotes, which carries the fix progress like Open, Redirected, or Resolved, and which holds the HTTP status or source path. SleekView reads these live so the board reflects the latest scan results.
3

Embed the feedback view

Drop the SleekView block on an internal editorial page or use the shortcode. Editors see a sorted feed of broken links with URL, vote count, source post, status pill, and HTTP status pill. The board paginates, filters by status, and runs on phones.
4

Votes write back to BLC

Every upvote increments the score column on the source row. That means Broken Link Checker itself ranks which links the team cares about, so you can sort future scan lists by score, fix high voted links first, and ignore one off 404s from forgotten posts.

Sample board

Sample Broken Link Checker board

A peek at how recent Broken Link Checker scan rows look on a SleekView Feedback board, with redirect requests, schema and sitemap fixes, and outbound 404 flags mixed into one feed.
263 votes
Replace dead vendor link on the pillar pricing guide with new URL
Helena R. Redirect In progress
172 votes
Outbound 404s on the legacy stats post still show as link errors
@editmarco Bug Investigating
138 votes
Add the new resource hub URLs to sitemap.xml after the link swap
Priya N. Sitemap Planned
84 votes
Schema update for replaced links on Recipe and HowTo posts
Tomasz K. Schema New
46 votes
Bulk unlink option for hundreds of old affiliate URLs works smoothly
@linkannika Praise Shipped
13 votes
Auto suggest the Wayback Machine URL when the original returns 404
Lukas W. Idea New

Comparison

BLC admin vs SleekView Feedback

BLC default screens

  • Scan table lists every broken link with no shared way to triage which matters
  • No way for editors to upvote which links to fix first or flag useful redirects
  • Schema and sitemap follow up lives in Slack threads, not next to the link row
  • Status of each link sits in row meta with no shared front end view in admin
  • No public queue to show clients which broken links were fixed this sprint

SleekView Feedback

  • One card per broken link with URL, source post, votes, status pill, and HTTP code
  • Upvote writes back to the score column so scan lists can sort by team priority
  • Filter by HTTP status, post type, or scan date using any column in blc_links
  • Embed on an internal editorial page or behind a login with one shortcode or block
  • Editors stop arguing in Slack and start voting on link fix plans in WordPress

Features

What SleekView Feedback gives you for Broken Link Checker

Link review built in

Each broken link row becomes a votable card. Editors see which links earn fixes, which were ignored, and which moved to Resolved. The board doubles as a living changelog of your link cleanup without anyone keeping a separate planning spreadsheet.

Redirect and schema flags

Add Redirect, Schema, or Sitemap categories and editors flag any broken link with one click. The flag lives next to the source row, so the SEO lead can ship the 301, update JSON-LD, and trigger a sitemap rebuild in one focused sprint.

Upvotes feed back into scans

Because votes write to the source column, you can sort the BLC scan list by score, fix high voted links first, and ignore one off 404s from forgotten posts. Link cleanup work stops being a guess and becomes a real number in the database.

Audience

How editorial teams use the BLC board

Editorial link cleanup

Editors vote on which broken links to fix first based on traffic and pillar status. The board surfaces the worst offenders, the team works through them, and cleanup is visible to managers without a weekly report.

Redirect chain audit

SEO teams use the board to flag broken links that should be 301 redirected. Top voted ones get rules added to the redirect plugin, and the board moves them to Resolved so the audit trail stays visible to the agency lead.

Sitemap and schema follow up

Editors flag links that need sitemap or schema updates once the canonical lands. The SEO lead works through top voted entries in one sprint, and JSON-LD, sitemap, and the 301 ship together without a ticket queue.

The bigger picture

Why a Broken Link Checker board changes the workflow

Broken Link Checker is great at finding broken URLs. It is much worse at telling you which of those links actually matter, which deserve a real 301 redirect, and which need schema or sitemap follow up once a new canonical lands. Most editorial teams end up with hundreds of red rows and no honest signal about which ones earn real Google or reader impact.

Editors miss the broken link on the pillar page until a reader complains, SEO leads ship sprints that fix legacy posts first, and clients lose trust because nobody can show them which links were fixed last sprint. A feedback board changes that pattern. Broken link rows stop being silent admin entries and start being something the team reacts to in public.

Upvotes give you a cheap, honest signal about which links deserve sprint time. Redirect, schema, and sitemap flags give you a backlog sorted by impact, not by whoever opened BLC last. And because everything writes back to the source row, the next time someone opens the scan list it shows the team score next to the URL.

The result is fewer dead links on pillar pages, fewer ignored redirects, and a much shorter loop between a broken link today and a clean redirect tomorrow.

Questions

Common questions about SleekView Feedback for Broken Link Checker

No. SleekView Feedback reads directly from the BLC scan table and the WordPress posts table. You point it at the source, pick the columns for votes, status, category, source, and URL, and the board renders. No ETL, no sync, no duplicated data. Anything BLC scans shows up on the next page load.

 

Yes. SleekView ships with anonymous voting backed by cookies, so any reviewer can upvote broken links without an account. You can also require login if you want the board restricted to editors or SEO leads, and the same view handles both modes with a single toggle.

 

SleekView tracks votes by cookie for anonymous reviewers and by user ID for logged in editors. A second click on the same card removes the vote instead of adding another one, so the count stays honest and the BLC score reflects unique voters, not raw clicks.

 

Yes. The data source supports any WHERE clause and any join. You can filter by HTTP code, by source post type, by scan date, or by any meta key, then save that filtered view as a board for a specific cleanup sprint, vendor, or client retainer.

 

No. Votes only write to a score meta column. BLC scan settings stay exactly as configured. The SEO lead decides which votes get acted on, so the board acts as a prioritised backlog while BLC stays the single source of truth for which URLs are scanned and how often.

 

Yes. Add Sitemap or Redirect categories so editors can flag any broken link with the type of follow up needed. The board surfaces all three workstreams together, so the SEO lead can ship the 301, the schema fix, and the sitemap entry in one focused sprint.

 

Yes. The Feedback view is responsive by default. Cards stack to one column on small screens, the vote button stays thumb sized, and category and HTTP status pills wrap cleanly. Lazy loaded URL previews keep the page light on a slow connection.

 

The card disappears on the next page load because the board reads live scan data, not a cached copy. The votes recorded against the source row stay in meta until you delete them, so if the URL breaks again later the score and history attach to the new scan row.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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