FallbackRedirect

301 (permanent), 302 (temporary), and 307 (temporary, keep the original HTTP method). Use 301 after a real move so search engines transfer equity.

Import a CSV of old path → new destination on the Migration tab. FallbackRedirect also creates 301s when you rename a published permalink. Review the 404s tab for anything the import missed.

source,target,status_code,match_type — status and match type are optional. Example: /old-about/,/about/,301,exact . You can paste full URLs; the plugin stores the path. Maximum 1,000 data rows and 512 KB per import.

No. /wp-admin , wp-login.php , wp-cron.php , and xmlrpc.php are blocked as sources.

Patterns are validated before save, compiled with PCRE match and depth limits, and skipped if they fail or do not compile. Keep them short. Capture groups ( $1 ) can be reused in the destination. In a wildcard, each * is a capture too ( $1 , $2 , and so on). A dollar sign that is not a capture, such as $100 , is kept as written. Patterns may start with ^ and may contain # . Relative destinations stay on this site, including when WordPress is installed in a subdirectory.

The requested path, hit count, first and last seen time, last referrer, a hashed IP, and a status (open, ignored, or redirected). Raw IPs and browser user agents are not stored. Retention and a unique-URL cap are configurable.

Only if you enable Delete data on uninstall. By default, uninstall removes settings and the cleanup cron; tables stay so a mistaken delete does not wipe a migration map.

Yes. Network-activating sets up every site. New sites created while the plugin is network-active are set up automatically. Uninstall and network deactivation also walk all sites.

By default the plugin uses REMOTE_ADDR when hashing IPs for 404 logs. If your host sits behind Cloudflare or another proxy that overwrites client IP headers, enable Trust proxy IP headers in Settings. Do not enable it on a publicly reachable origin that does not sanitize X-Forwarded-For.