SleekView for Safe Redirect Manager
Safe Redirect Manager (10up) writes every redirect to the redirect_rule custom post type with standard postmeta. SleekView reads the same posts and renders the redirect set as a sortable, filterable grid.
♾️ Lifetime License available
A CPT-based redirect set earns a grid, not just a post list
Safe Redirect Manager is 10up's enterprise-leaning redirect plugin. Instead of a custom table or a single option, each rule is stored as a post of type redirect_rule with postmeta keys _redirect_rule_from, _redirect_rule_to, _redirect_rule_status_code, _redirect_rule_from_regex, and _redirect_rule_notes. The schema is friendly to anyone querying through WordPress APIs, which is exactly why it earns a chart-and-table layer.
The default Tools, Safe Redirect Manager screen is the standard WP post list with a few custom columns. That works for spot edits. It does not work for the recurring audits on a multisite or a publication with a thousand-plus rules accumulated across years of cleanups. Which rules are regex, which are 302s that should have been 301s, who created which rule, when were rules added in waves.
SleekView reads the same redirect_rule posts and their postmeta and renders the set as a real grid. Each row carries the source, destination, status code, regex flag, author, and post_date. Saved filters carry the rest: a view filtered to _redirect_rule_from_regex equals 1 is the regex audit, a view sorted by post_date is the migration archaeology, and a view grouped by post_author surfaces whether one SEO lead is doing all the redirect work or whether contributors are also adding rules.
Workflow
From the post list to a redirect grid
Read the redirect_rule posts
Map the columns
Save the audit views
Drill into the rule
Sample columns
A typical Safe Redirect Manager table view
redirect_rule custom post type joined to its postmeta keys
| Source | Destination | Code | Regex | Author | Created |
|---|---|---|---|---|---|
| /old-pricing | /pricing | 301 | No | jane | 2026-04-18 |
| /blog/2019/.* | /blog | 302 | Yes | alex | 2026-03-02 |
| /shop/old-sku-1842 | /shop | 301 | No | jane | 2026-02-11 |
| /legacy/api-docs | — | 410 | No | ops | 2025-11-22 |
| /author/.*/old | /author | 301 | Yes | alex | 2025-09-04 |
Comparison
Default Safe Redirect Manager admin vs SleekView
Default Safe Redirect Manager
- List view is the standard WP post list, not an audit grid
- No saved filter for regex rules across an enterprise rule set
- Cannot group by post_author to see who is creating rules
- Status code mix blurs into the default post list
- Migration archaeology by post_date requires re-sorting every time
SleekView
- One row per redirect_rule post with source, destination, code, regex flag, and author
- Filter by status code, regex flag, author, or post_date window
- Saved view for the regex audit and another for legacy 302s
- Spot waves of additions by sorting on post_date
- Click through to the underlying redirect_rule post in WP admin
Features
What SleekView gives you for Safe Redirect Manager
Rule observability
Render the redirect_rule CPT as a real grid. The post list keeps doing its job; the grid handles the audit at scale where the post list runs out of room.
Regex isolation
Filter to _redirect_rule_from_regex equals 1 to audit regex rules separately. Regex is powerful and easy to misconfigure, so the ratio and the authors matter on an enterprise team.
Author accountability
Group by post_author and the grid shows whether one SEO lead is doing all the redirect work or whether contributors are also creating rules. Governance gets a real picture.
Audience
Who uses SleekView for Safe Redirect Manager
Publishers and large editorial sites
Sort by post_date and the grid becomes the migration archaeology. Which wave of cleanups added which rules, useful when the editorial archive grows past five years.
Multisite ops
Per-site rule grids on a network of brands tell governance whether one site is doing all the redirect work and another is letting URLs rot quietly.
Enterprise SEO leads
The regex-flag filter surfaces governance risk. Regex rules added by contributors with limited review are the most common source of accidental site-wide intercepts.
The bigger picture
Why a CPT-based redirect plugin earns a chart-and-table layer
Safe Redirect Manager is the go-to choice on 10up-built sites because its schema (one post per rule, standard postmeta) is friendly to every other WordPress tool. That friendliness is exactly what lets a grid layer exist: SleekView reads the redirect_rule posts and their postmeta the same way any well-behaved plugin would. The benefit shows up at scale.
On a publication with five years of cleanups and four authors of redirect rules, the default post list is not where governance happens. A regex filter, an author group, a status code sort, and a post_date timeline give the SEO lead, the multisite ops team, and the migration contractors a shared view of the same redirect set. The matcher stays in Safe Redirect Manager; the grid makes the post list legible.
Questions
Common questions about SleekView for Safe Redirect Manager
No. Safe Redirect Manager's matcher runs on the front-end request and is unchanged. SleekView reads the underlying posts. Disabling SleekView leaves every redirect rule firing exactly as before, including the wp_options-cached redirect array the plugin builds.
From every redirect_rule custom post and its postmeta keys (_redirect_rule_from, _redirect_rule_to, _redirect_rule_status_code, _redirect_rule_from_regex, _redirect_rule_notes), plus wp_posts columns like post_status, post_author, and post_date. No additional logger is required.
Yes. _redirect_rule_from_regex is a 1/0 postmeta value, so a filter on that key is one click. Governance teams use this filter to plan a regex review, especially when contributors have limited review on the rules they create.
Yes. post_author is a standard wp_posts column, so a group by author counts rules per WordPress user. On an enterprise editorial team, that surfaces whether one SEO lead is doing all the redirect work or whether contributors are also creating rules.
Yes. post_date is the column to sort or filter on. A view restricted to post_date within the last 30 days is the wave of recent additions; a view sorted by post_date ascending is the migration archaeology of the entire set.
Yes. SleekView reads each site's own redirect_rule posts, so a per-site grid works as expected. For a network roll-up, SleekView can aggregate counts across the network's posts tables and surface per-site KPIs, which is what enterprise governance asks for.
No. SleekView paginates the grid the same way the post list does, so a site with three thousand redirect_rule posts queries the same as a site with thirty. Postmeta joins are indexed by Safe Redirect Manager's standard schema.
Yes. Any filtered view exports to CSV with source, destination, status code, regex flag, author, and post_date columns. Useful for archiving a redirect snapshot before a migration or for handing a portable inventory to a contractor.
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