FallbackRedirect keeps old URLs working after you rename pages, move a site, or delete content. It stores redirect rules, serves 301 \/ 302 \/ 307 responses on the front end, and logs unique 404s so you can turn the worst broken links into redirects.<\/p>\n\n
Under Settings \u2192 FallbackRedirect you get six tabs:<\/p>\n\n
How SEO protection works:<\/p>\n\n
template_redirect<\/code> before the theme 404 template<\/li>\n- Exact rules are looked up by hash; prefix, wildcard, and regex rules are checked next<\/li>\n
- Changing a published post or page permalink can auto-create a 301 from the old path<\/li>\n
- Looping rules (same source and destination on this site) are rejected<\/li>\n
- Admin, login, and cron paths cannot be used as sources<\/li>\n
- 404s ignore bots, logged-in users, static file extensions,
.php<\/code> probes, and wp-includes \/ plugin \/ theme scans by default<\/li>\n- IP addresses are stored as a salted hash, not in the clear<\/li>\n<\/ul>\n\n\n
\n- Upload the
fallbackredirect<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n- Activate the plugin through the Plugins menu in WordPress.<\/li>\n
- Open Settings \u2192 FallbackRedirect.<\/li>\n
- Add redirects, or wait for 404s to appear and repair them from the 404s tab.<\/li>\n<\/ol>\n\n\n
\nWhich redirect types are supported?<\/h3><\/dt>\n301 (permanent), 302 (temporary), and 307 (temporary, keep the original HTTP method). Use 301 after a real move so search engines transfer equity.<\/p><\/dd>\n
What happens after a site migration?<\/h3><\/dt>\nImport a CSV of old path \u2192 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.<\/p><\/dd>\n
How should the CSV look?<\/h3><\/dt>\nsource,target,status_code,match_type \u2014 status and match type are optional. Example: \/old-about\/,\/about\/,301,exact<\/code>. You can paste full URLs; the plugin stores the path. Maximum 1,000 data rows and 512 KB per import.<\/p><\/dd>\nWill this redirect wp-admin?<\/h3><\/dt>\nNo. \/wp-admin<\/code>, wp-login.php<\/code>, wp-cron.php<\/code>, and xmlrpc.php<\/code> are blocked as sources.<\/p><\/dd>\nAre regex redirects safe?<\/h3><\/dt>\nPatterns 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<\/code>) can be reused in the destination. In a wildcard, each *<\/code> is a capture too ($1<\/code>, $2<\/code>, and so on). A dollar sign that is not a capture, such as $100<\/code>, is kept as written. Patterns may start with ^<\/code> and may contain #<\/code>. Relative destinations stay on this site, including when WordPress is installed in a subdirectory.<\/p><\/dd>\nWhat 404 data is stored?<\/h3><\/dt>\nThe 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.<\/p><\/dd>\n
Does uninstall delete my redirects?<\/h3><\/dt>\nOnly 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.<\/p><\/dd>\n
Does it work on WordPress Multisite?<\/h3><\/dt>\nYes. 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.<\/p><\/dd>\n
Behind a reverse proxy?<\/h3><\/dt>\nBy 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.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n<\/ul>","raw_excerpt":"Redirect manager for 301, 302 and 307 redirections. Monitor and fix 404 errors, log every broken link, and protect your SEO after a migration.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/383826","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=383826"}],"author":[{"embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/alexhedstrom"}],"wp:attachment":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=383826"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=383826"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=383826"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=383826"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=383826"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=383826"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}