Practical guide
Generate Redirect Rules for Vercel, Netlify and Apache
By MultiZest · Updated
How to use this tool
- Choose Vercel JSON, Netlify or Apache root .htaccess syntax.
- Choose a permanent or temporary status and enter one source/destination pair per line.
- Generate the rules, merge them with existing host configuration and test each redirect in staging before deployment.
Worked example
The line /old-guide /new-guide with status 301 becomes a permanent redirect. Adding /new-guide /old-guide creates a cycle, which this tool rejects.
Select status intentionally
301 and 308 describe permanent moves; 302 and 307 are temporary. The 307 and 308 statuses preserve the request method. For ordinary page moves, test the actual host response and final destination.
Permanent redirects can be cached. Check mappings before publishing and avoid sending unrelated old pages to a single homepage. Keep useful content available at the most appropriate new URL.
Supported configuration scope
This generator handles literal paths, not wildcards, captures or arbitrary regular expressions. Apache output assumes mod_rewrite in the site-root .htaccess file. Vercel output is an object to merge into vercel.json, not a replacement for your other settings.
Cycle checks cover relative mappings entered in this batch. Existing server rules, cross-domain loops, query behavior and destination availability are not checked. Absolute destinations must be HTTP or HTTPS URLs with special characters percent-encoded.
Map each old page to a relevant replacement
If an article moves, redirect it to the new version of that article. Sending every retired page to the homepage can frustrate someone who followed a specific reference. Review each old path and choose a destination that answers the same task whenever a useful replacement exists.
Use a permanent status for a settled move and a temporary status for a temporary change. Consider method-preserving statuses when the route receives requests other than ordinary page visits. The correct choice depends on the application and host behavior, so test a representative request rather than relying only on the generated text.
Review the full deployment configuration
Merge the generated output with the host’s existing settings instead of overwriting unrelated headers or routing rules. Check for a chain or loop involving rules already deployed; the tool can only inspect the mappings supplied in this batch. Confirm that destination pages actually exist and return the intended response.
After deployment, visit the old address and inspect the redirect status and final destination. Update internal links, canonicals and sitemap entries to use the final URL. Keep the mapping list as a record of the move so future changes do not accidentally reintroduce a retired path.
Questions and troubleshooting
Does generating rules change my website?
No. You must merge the output into your host configuration, test it and deploy it yourself.
Can this tool check whether the target page exists?
No. It validates the supplied mappings locally and does not request destination pages.
Is a redirect file ready to replace my whole host configuration?
No. Merge the relevant rules into the existing configuration and test the complete routing behavior. The generator does not inspect unrelated deployed rules or destination availability.
Continue with a related tool
Use this free robots.txt tester and syntax checker to validate your file, test Googlebot crawl access, and find matching Allow or Disallow rules.
Robots & Sitemap Generator →Create robots.txt rules and an XML sitemap from your URLs. Configure crawler groups, download the files, and validate your rules before publishing.
URL Encoder & Decoder →Encode special characters for URL query strings or decode percent-encoded URLs.
Sources and further reading
Found an error or an unclear instruction? Report it. Read our editorial policy and privacy policy.