Many tables are available with AIOSEO free, including the SEO meta data in wp_aioseo_posts. Redirects and 404 logs require AIOSEO PRO to be active, since that is where AIOSEO stores those features. If your site has only free, the SEO meta audit works fully and the redirects features become available the moment PRO activates.

Yes. SleekView lets you promote any 404 row into a new redirect inline, so triage becomes one workflow instead of two. The promoted redirect writes to wp_aioseo_redirects exactly as if it had been created through the AIOSEO UI, including all the match-type and activation defaults you configure.

Yes. Edits go straight to the AIOSEO tables through the same save paths AIOSEO's own UI uses, so the rules behave exactly like ones you create through AIOSEO's screens. Activation, redirect type, source URL, and destination all save back, and AIOSEO's redirect engine picks up the changes immediately on the next request.

Yes, when AIOSEO Search Statistics is connected. SleekView can surface impressions and clicks alongside the matching post or URL, so SEO leads can see ranking pages losing traffic, posts with high impressions but low clicks (a meta description rewrite candidate), and 404s that previously had Search Console traffic. The Search Console connection still runs through AIOSEO.

Yes. SleekView paginates against the AIOSEO tables, so sites with thousands of redirects stay responsive. Queries hit indexed columns and only fetch the visible page, so a 50,000-redirect ruleset performs the same as a 500-redirect one in the grid. Migration teams can audit even the largest redirect sets without timeouts.

Yes. Saved views can be shared by role, so the whole SEO team sees the same triage queue. An SEO lead can build a High-priority 404s view and ship it to junior team members without each person rebuilding the filter. Useful during migration cleanups when consistent views matter for handoff.

AIOSEO supports exact, regex, and pattern-based redirects, and SleekView surfaces match type as a column and filter. Audit how many regex rules exist, find catch-all patterns that may be intercepting more than intended, and bulk-convert match types when refactoring redirect rules. The match type column makes it visible which approach a rule uses without opening it.

Yes. AIOSEO stores schema markup configuration and sitemap inclusion flags as part of the wp_aioseo_posts row for each post. SleekView exposes those as columns and filters, so SEO leads can audit which posts have custom schema attached, find pages incorrectly excluded from the sitemap, and bulk fix sitemap configuration after a site reorganization.