SleekView for Simple 301 Redirects
Simple 301 Redirects keeps every rule in the wp_options 301_redirects array. SleekView unpacks that option and renders a thousand-rule site as a sortable, filterable grid instead of a two-column textarea.
♾️ Lifetime License available
An audit grid that survives the textarea form
Simple 301 Redirects is the WordPress directory's deliberately minimal redirect plugin. Every rule (request path, destination URL) is one entry in the 301_redirects option, optionally with a 301_redirects_wildcard flag on a sibling option. The settings screen is a two-column form rendered straight from that array. There is no rules table, no logs, no hit counter, no per-rule status.
On a brochure site with twenty rules, that is exactly the right shape. On a site that quietly grew to twelve hundred rules across five years of migrations and editorial cleanups, the textarea becomes the audit surface, which is the moment the plugin stops scaling for the SEO lead asking how many wildcards exist or which destinations are absorbing most of the rules.
SleekView reads the same option, unpacks it into one row per rule, and renders the inventory as a real grid. Each row carries the source path, the destination, the wildcard flag, and the order in the option array. Saved filters do the rest: a view filtered to wildcard equals 1 surfaces the greedy patterns the team should review carefully, a view grouped by destination shows the homepage catch-alls and over-used hubs, and a view sorted by source alphabetically is the audit a migration contractor wants to take into the next system.
Workflow
From a textarea to a real rule grid
Read the option array
Map the columns
Save the audit views
Drill into the rule
Sample columns
A typical Simple 301 Redirects table view
wp_options 301_redirects array (and 301_redirects_wildcard)
| Source | Destination | Wildcard | Order |
|---|---|---|---|
| /old-pricing | /pricing | No | 1 |
| /blog/2018/* | /blog | Yes | 42 |
| /shop/old-sku-1842 | /shop | No | 118 |
| /legacy/* | / | Yes | 207 |
| /about-us-old | /about | No | 311 |
Comparison
Default Simple 301 Redirects admin vs SleekView
Default Simple 301 Redirects
- Settings screen is a two-column textarea, not a queryable grid
- No filter for wildcard versus exact rules
- Duplicate source paths are silently overwritten, not flagged
- Over-used destinations (homepage catch-alls) are invisible in the form
- No export of the rule set without a copy-paste from the textarea
SleekView
- One row per rule with source, destination, wildcard flag, and order
- Filter by wildcard flag, destination, or source pattern
- Saved view for greedy wildcard rules that deserve a manual review
- Spot duplicate source paths where only the last entry actually fires
- Click through to the settings screen scrolled to the right rule
Features
What SleekView gives you for Simple 301 Redirects
Inventory observability
Confirm what is actually in the rule set without scrolling a textarea. The grid surfaces the inventory at scale, which is the question Simple 301's UI was never built to answer.
Wildcard isolation
Filter the grid to wildcard equals 1 to audit the greedy patterns separately from exact-match rules. Wildcards punch above their weight in a redirect set and deserve a separate review.
Duplicate finder
Group by source path and any group with a count above one is a duplicate the plugin silently kept the last version of. The grouping makes the conflict visible, which the settings screen never has.
Audience
Who uses SleekView for Simple 301 Redirects
SEO leads
Audit how many rules actually exist, how many are wildcards, and where they all point. The cleanup sprint starts with a real grid instead of a textarea scroll.
Migration teams
Before porting off Simple 301, export the grid to CSV. That sheet is the exact shape the next system (Redirection, Safe Redirect Manager, or a server rules file) needs to ingest.
Developers and ops
Find homepage catch-alls and greedy wildcards before they intercept a new legitimate URL. The grid groups destinations in one sort instead of needing a regex pass over the option.
The bigger picture
Why a minimal redirect plugin earns a real grid
Simple 301 Redirects is intentionally minimal, and that is why it stays on so many WordPress sites for so many years. Minimalism scales right up until a site grows past the point where a two-column form is a reasonable interface, which on most marketing sites is somewhere around three hundred rules. By a thousand, the audit work is essentially impossible from the settings screen.
SleekView does not change the plugin, does not add a database table, does not touch the redirect path. It reads the option the plugin already writes and renders it as the sortable, filterable, exportable grid the audit always needed. The plugin stays simple; the audit stops being a textarea exercise.
Questions
Common questions about SleekView for Simple 301 Redirects
No. Simple 301 reads the same 301_redirects option on every front-end request and issues the redirect itself. SleekView reads the option, never writes back through a different path. Disabling SleekView leaves every existing rule firing exactly as before.
 From the 301_redirects option in wp_options (and 301_redirects_wildcard when present). Simple 301 Redirects stores every rule there as a serialized array of request_path => destination pairs. SleekView unpacks it into one row per rule.
 Yes. A column derived from the wildcard flag is a real filterable field, so isolating wildcards is one click. On many older sites the wildcard slice is tiny but is responsible for most of the actual redirect traffic, which is a useful thing to surface.
 Yes, indirectly. Group by source path; any group with a count above one is a duplicate definition. The plugin keeps the last one in array order, so the earlier entries are dead. The grouping makes the silent overwrite visible.
 Yes, as long as the fork stores its rule set in the same option key. Most forks (Simple 301 Redirects with Bulk Uploader and similar) preserve the original option for compatibility. If a fork uses a different option, SleekView can be pointed at that key instead.
 Yes. The option is per-site by default, so each subsite has its own grid. A network-level roll-up can aggregate rule counts across blogs when one SEO team monitors the whole network.
 No. The option is one read from wp_options and the array is parsed in memory. A site with thirteen hundred rules unpacks instantly because the data is already a single option blob.
 Yes. Any filtered view exports to CSV with source, destination, wildcard flag, and order. That sheet is the exact migration artifact the next redirect system needs to ingest.
 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