CF7 Redirection (the Redirection for Contact Form 7 plugin) lives in the CF7 form editor as an extra panel where the operator picks an external URL, an internal page or a thank-you template to send the user to once the form submits. The redirect rules sit inside each form's CF7 settings; the submissions themselves still live wherever the install persists them, usually Flamingo or Advanced CF7.

SleekView joins both halves. It reads the submissions, reads the redirect rule configured on each wpcf7_contact_form post and renders one grid with form, sender email, destination URL and submitted_at as columns. Sort by redirect_url to see every form pointing at the same thank-you page. Filter to redirect_url empty for the missing-redirect audit. Filter to destinations matching a retired URL pattern to find stale rules before they keep sending traffic to dead pages.

The grid sits read-only against the redirect rules themselves (those still live in the CF7 form post) and read-write against the submission columns. The plugin keeps owning the redirect logic on submit, SleekView makes the catalog auditable.

CF7 Redirection lives inside each form's settings, which is the right place for an operator setting up a single form. It is the wrong place for an agency or in-house team auditing every form on the install at once. Stale destinations are common: a thank-you page gets retired, a campaign URL changes, a download moves to a new path, and the redirect rule on an old form quietly keeps pointing at the wrong place.

SleekView turns the per-form setting into a grid column. The destination view shows which URLs actually get traffic. The missing-redirect view shows which forms still use the default response.

The plugin keeps owning the redirect logic on submit, the grid makes the catalog auditable.