Flux Redirect

After activating the plugin, open Flux Redirect in the WordPress admin menu. Only users with the manage_options capability (typically Administrators) can view or change redirects.

Yes. Administrators can save full HTTP or HTTPS destination URLs. The plugin uses WordPress safe redirect handling and only permits the saved destination host for the active redirect.

Use 301 for permanent moves (most SEO cases). Use 302 for temporary moves. 307 and 308 keep the original request method and are useful when you need stricter temporary or permanent behavior. If you are unsure, 301 is the usual choice for renamed or removed content that has a lasting replacement.

Yes. Enable the Regex source option when adding or editing a redirect. Invalid regular expressions are rejected before saving or redirecting. Use regex only when you need one rule to cover many similar paths.

Yes. Export a CSV with broken_url, redirect_url, status_code, and is_regex columns. Common aliases such as source and target are accepted on import. This is useful when migrating from tools like Redirection, Yoast, or a server redirect export that can be mapped into those columns.

On the Flux Redirect admin screen, use Export Redirects CSV. The download includes configured redirects only (rows that already have a destination URL).

Ignore hides a 404 record from the main list so it does not clutter your queue. Delete removes the record completely. If the same broken path is requested again after a delete, Flux Redirect can rediscover it as a new 404.

Yes. Select the rows you want, choose a bulk action, and click Apply. You can bulk-ignore, bulk-delete, or bulk-create redirects to one shared destination URL and status code.

Browsers and privacy tools do not always send a referrer. Flux Redirect only stores a referrer when the HTTP Referer header is present. An empty value is normal for direct visits, bookmarks, some apps, and privacy-restricted browsers.

When Flux Redirect finds a published post or page slug similar to the broken path, it offers that URL as a suggested destination. Suggestions are optional helpers. Always review them before saving.

Enable notifications in Settings and add one or more recipient addresses. Flux Redirect emails those recipients the first time a new broken path is discovered. Repeat hits on the same path do not send another email.

When enabled, a daily cleanup ignores or deletes open 404 records that have not been hit for the configured number of days. Configured redirects are never removed by auto-expire. This helps keep the table manageable on busy sites.

No. Flux Redirect stores the requested 404 path, a hit count, and the HTTP referrer URL when the browser provides one. It does not store IP addresses, user agents, or personal profiles.

Flux Redirect is designed to stay lightweight. It only evaluates redirect rules and records 404s on front-end requests. Active rules are cached briefly to reduce database lookups.

You can, but overlapping redirect rules can cause confusing results. For the cleanest setup, keep one plugin as the primary redirect manager, or make sure the same source path is not handled in two places.

No. Redirects are handled inside WordPress. That makes the plugin portable across hosts, though very high-traffic sites sometimes still prefer server-level redirects for maximum performance.