SleekView reads wp_redirection_items for the rules, wp_redirection_logs for matched redirect hits with their http_code and timestamp, and wp_redirection_404 for unmatched URLs. Rule groups in wp_redirection_groups join in for label resolution. No schema changes, no replication, no plugin patches.

No. SleekView is strictly read-only against Redirection's tables. Rule edits, regex matching, redirect ordering, group permissions, CSV imports, and the actual HTTP response continue to live inside the Redirection admin. The dashboard rebuilds its read-out the next time a card is opened.

Yes. Cards accept a filter on group_id from wp_redirection_items, so a multisite or multi-brand setup can pin a dashboard per group. Useful when one site section is migrated and the team wants its 404 KPI in isolation rather than mixed with the rest of the estate.

It will be close but not identical. Redirection logs only requests that reach WordPress. Search Console reports what Googlebot encountered, which may include cached responses, CDN-edge 404s, or paths blocked before WordPress. Use the SleekView KPI to drive same-day cleanup and Search Console for the crawler's view.

Redirection prunes wp_redirection_404 on a schedule or on demand. SleekView reads whatever is there at query time, so once a row is deleted it stops counting in the KPI. To keep a longer history, raise Redirection's log retention or archive snapshots into a secondary table that SleekView can also read.

Yes. SleekView views appear in the WordPress admin menu like any other custom post type list. Pin the chart view, scope it per role, and the SEO team sees the 404 KPI on login instead of digging through Tools then Redirection then the 404 tab.

No. The Redirection log is still where the team inspects an individual hit and confirms the rule that matched. SleekView Charts is the read-out across thousands of hits. Per-row drill-down stays in Redirection, aggregated reporting moves to SleekView.

The tables stay in the database unless the plugin is uninstalled with its uninstall hook. SleekView will keep reading the historical rows until they are removed. If Redirection is uninstalled cleanly, the tables are dropped and the cards will return empty until a new redirect plugin populates equivalent data sources.