Only WordPress data: 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; AIOSEO Pro still owns that connection.

No. AIOSEO Pro still owns the matching engine and the HTTP response. SleekView only reads the wp_aioseo_redirects table. Disabling SleekView leaves every redirect rule firing exactly as before.

Yes. wp_aioseo_redirects stores the redirect type per row; a Pie or Bar grouped by 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. wp_aioseo_redirects_404 stores a hits column. Group a Bar by url and aggregate Sum on hits to rank 404 paths by traffic. That ranked list is the exact migration cleanup queue an SEO lead wants.

Yes. wp_aioseo_posts is joined to wp_posts on the post id, so a card grouped by post_date with a Count restricted to non-empty description shows whether new posts are getting meta written. Useful for measuring editorial SLA, not just current coverage.

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.

Yes. Any filtered set behind a card exports as CSV with the same columns the audit table would show. Useful for archiving a redirect snapshot before a migration or for handing a top-404 list to a contractor.

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 cards work on free installations. When Pro activates, the redirect, 404 and Search Statistics cards start populating from their respective tables.