SleekView for All in One SEO Pro
All in One SEO Pro writes redirects to wp_aioseo_redirects, 404s to wp_aioseo_redirects_404, and SEO meta to wp_aioseo_posts. SleekView reads each table and renders them as sortable, filterable grids you can audit from one place.
♾️ Lifetime License available
Four admin tabs collapse into one queryable surface
All in One SEO Pro is one of the more complete SEO suites in the WordPress ecosystem. It writes to a clean set of dedicated tables: wp_aioseo_redirects for redirect rules, wp_aioseo_redirects_404 for unredirected 404 logs, wp_aioseo_posts for the SEO meta on every post, and a Search Statistics dataset when the Search Console connection is active. Each feature sits behind its own admin tab.
That tabbed model is fine for spot edits. It does not work for the recurring questions every SEO lead asks: what is the redirect set actually doing, where is the 404 traffic going, how is meta coverage trending across post types. Today the answers mean switching between four admin screens and reconstructing the picture in a notebook.
SleekView reads each AIOSEO Pro table and renders the records as real grids. The redirect grid carries source, destination, status code, enabled flag, hits, and last access. The 404 grid carries the path, hits, and first-seen timestamp. The meta grid carries title, description, focus keyword, and post_type. Saved filters do the rest: a view filtered to status code equals 302 in wp_aioseo_redirects is the legacy-302 audit, a view sorted by hits descending in wp_aioseo_redirects_404 is the migration cleanup queue, and a view filtered to description IS NULL in wp_aioseo_posts is the coverage gap.
Workflow
From four tabs to one set of grids
Read every AIOSEO Pro table
Map the columns per surface
Save the audit views
Drill into the record
Sample columns
A typical AIOSEO Pro redirect table view
wp_aioseo_redirects, wp_aioseo_redirects_404, wp_aioseo_posts
| Source | Destination | Code | Enabled | Hits | Last access |
|---|---|---|---|---|---|
| /old-pricing | /pricing | 301 | Yes | 4,812 | 2026-05-15 09:42 |
| /blog/launch-2019 | /blog | 302 | Yes | 1,204 | 2026-05-14 11:18 |
| /shop/old-sku-1842 | /shop | 301 | Yes | 318 | 2026-05-15 06:11 |
| /legacy/api-docs | — | 410 | Yes | 47 | 2026-05-15 10:02 |
| /old-campaign-2024 | /campaigns | 301 | No | 0 | 2025-12-04 08:11 |
Comparison
Default AIOSEO Pro admin vs SleekView
Default AIOSEO Pro
- Redirects, 404 logs, SEO meta, and Search Statistics live in four separate tabs
- No saved filter for legacy 302s across the redirect set
- Top unredirected 404s by hits are paginated, not a queryable feed
- Coverage by post type stays invisible at the post-list level
- No way to share a read-only audit snapshot across tabs
SleekView
- One row per record across wp_aioseo_redirects, _404, and _posts
- Filter by status code, enabled flag, hits, post_type, or missing description
- Saved view for legacy 302s and another for top unredirected 404s
- Spot dead-weight rules where hits equals zero across a quarter
- Click through to the underlying redirect, 404, or post in WP admin
Features
What SleekView gives you for All in One SEO Pro
Cross-feature observability
Redirects, 404s, and SEO meta sit in one set of grids. SEO leads see AIOSEO Pro as a system, not as four separate paginated screens.
Filters span surfaces
Filter to a single post_type or to a status code in one grid; carry the same scope across the others. Same wp_aioseo_ rows, three audit angles.
404 cleanup queue
A saved view of wp_aioseo_redirects_404 sorted by hits descending is the migration cleanup queue. Promote the top entries to redirects and watch the queue shrink.
Audience
Who uses SleekView for All in One SEO Pro
SEO leads
Active rule count, status code mix, top 404s by hits, and coverage by post type all live in one set of grids. The quarterly review stops being a tab-hopping exercise.
Migration teams
The unredirected-404 grid sorted by hits is the migration cleanup queue. Promote the top entries to redirects in AIOSEO Pro and watch the grid shrink sprint by sprint.
Editorial leads
The wp_aioseo_posts grid filtered to description IS NULL grouped by post_type is the meta coverage gap. Custom post types are the usual offenders.
The bigger picture
Why a multi-feature SEO suite earns a unified grid
AIOSEO Pro is one of the more capable SEO suites on WordPress, and the team behind it has built dedicated tables for each major feature: redirects, 404 logs, SEO meta, and Search Statistics. That schema is exactly why a grid layer can exist. The constraint is the admin itself, which treats those four products as four tabs and never gives the SEO lead a unified picture.
SleekView reads from all four AIOSEO Pro datasets and renders the grids a quarterly review actually needs: a redirect rule grid, a 404 cleanup queue, and a meta coverage audit. AIOSEO Pro still owns the head tags, the redirect engine, and the Search Console connection. The grid owns the story.
Questions
Common questions about SleekView for All in One SEO Pro
No. AIOSEO Pro owns the matching engine and the HTTP response. SleekView reads the wp_aioseo_redirects table and renders it as a grid. Disabling SleekView leaves every redirect rule firing exactly as before.
From WordPress data only: wp_aioseo_redirects (rules), wp_aioseo_redirects_404 (unredirected 404 logs), wp_aioseo_posts (SEO meta per post), and the Search Statistics tables when AIOSEO's Search Console connection is active. SleekView never calls Search Console directly.
Yes. wp_aioseo_redirects_404 stores a hits column. Sort the grid by hits descending and the top entries are the 404 paths carrying traffic. That ranked list is the exact migration cleanup queue an SEO lead wants.
Yes. wp_aioseo_redirects stores the redirect type per row; a filter on type shows the 301 vs 302 vs 307 vs 410 mix. Useful for spotting legacy 302s on a publication that has been moving content around for years.
Yes, when AIOSEO's Search Console connection is active. SleekView can join Search Statistics rows to wp_aioseo_posts and surface impressions or clicks alongside SEO meta. Useful for finding pages with high impressions but missing meta descriptions, a classic rewrite candidate.
The redirect rules, 404 logs, and Search Statistics features come with AIOSEO Pro. wp_aioseo_posts (SEO meta) is populated by free as well, so the meta coverage grid works on free installations. When Pro activates, the redirect, 404, and Search Statistics grids start populating from their respective tables.
Yes. AIOSEO Pro writes per-site tables on multisite, and SleekView respects that scope. Each subsite has its own set of grids, and a network roll-up can aggregate across blogs when one SEO team monitors a network.
Yes. Any filtered view exports to CSV with the same columns the audit table shows. Useful for archiving a redirect snapshot before a migration, handing a top-404 list to a contractor, or sharing a coverage gap with an external editor.
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