Simple 301 Redirects stores every rule as a serialized option row in wp_options under keys like 301_redirects and wildcard_301_redirects. The default plugin settings screen shows those rules as one long form with paired source and target fields, which works fine for a few dozen entries but turns into a scroll fest once a site has hundreds of legacy redirects collected over years of editorial work.

SleekView Kanban points at a thin custom table that mirrors the Simple 301 Redirects option rows, then groups every rule by a status-like column you choose. Use a category column to slice between Active, Wildcard, Review, and Retired lanes. Each card shows the source URL pattern, the target URL, whether the rule uses a wildcard, and the date it was last touched so an editor can decide which rules deserve keeping and which can retire safely.

Dragging a card between columns writes the new state back to the mirror table, and SleekView serializes the change into the Simple 301 Redirects option rows the plugin actually reads. The plugin keeps serving 301s from its existing storage, the option row stays in sync with the board, and the editorial queue for redirect cleanup lives in one obvious place instead of buried inside a long settings form.

Simple 301 Redirects is excellent at doing one thing well, which is mapping a source URL to a target with a 301 response. The plugin storage is intentionally minimal, which keeps the plugin fast and reliable. The trade off is the admin experience.

Every rule lives in one long settings form, and that form is the only built-in tool for editing rules. On a small site with twenty redirects, the form is fine. On a large site with hundreds of rules collected over a decade of editorial work, the form turns into a maze.

Editors scroll, search the page with the browser find tool, and edit pairs of text fields in place, with no obvious way to mark which rules they have reviewed. SleekView Kanban fixes this by treating the rules as a board. Every rule is a card, every category is a column, and dragging a card writes the new state back to the option row.

The plugin keeps serving 301s from its existing storage, and the cleanup queue lives in one obvious place across the admin.