Pretty Links stores every redirect in the wp_prli_links table. Each row carries a slug for the pretty URL, a url for the destination, a redirect_type like 301, 302, or 307, plus an enabled flag, a nofollow flag, and a sponsored flag. Click events land in wp_prli_clicks with timestamps and IP hashes. The plugin's links admin shows everything as a flat sortable table, which is fine for archive lookups but blind to the live audit and curation work the marketing team really needs to do.

SleekView Kanban reads the same wp_prli_links rows you would query with PrliLink. Pick the enabled flag or a derived status column as the group field and every link becomes a card slotted under Enabled, Disabled, Draft, or Trash. Card fronts show the pretty slug, the destination URL, the click count from wp_prli_clicks, the redirect type, and the date created, so the marketing team has every detail right on each card without opening any individual link.

Dragging a card between columns calls the Pretty Links helper for toggling the enabled flag or moving the link to trash, which writes back to wp_prli_links. The plugin's redirect cache refreshes so the storefront pretty URL stops or starts redirecting immediately, the link tracker updates, and any extension listening on the link state filters reacts, exactly as it would after a manual update from the links admin screen.

Sites running Pretty Links accumulate hundreds of redirects over time. Some are top performers driving steady traffic to affiliate partners. Some go broken when a partner changes their URL structure or sunsets a product.

Some belong to campaigns that ended months ago but the redirects are still live and pointing readers somewhere they should not be. The default Pretty Links admin treats them all the same, which means marketing managers spend hours scrolling through long lists trying to identify which redirects need attention versus which are quietly working. The disconnect between what readers actually click and what the team can see shows up in the worst places.

A broken redirect drives readers to a 404 page on the partner site and the affiliate revenue from that pretty URL quietly drops to zero. A discontinued campaign keeps redirecting readers to the wrong page months after the campaign ended. A kanban view that reads and writes the same wp_prli_links rows the storefront reads keeps the team and the redirect inventory honest.

Every drag is a real state change, every column count reflects the real link health, and the cards themselves carry enough context for a new marketing manager to start curating redirects on day one of the job.