Redirect Path Builder — nginx, Apache, Vercel, Netlify

Why a redirect builder

When you migrate URLs (slug rename, domain change, content reorganization), you write redirect rules. The syntax is different for every host — and forgetting one detail breaks SEO and user bookmarks.

This tool lets you author redirect rules once and emit the right syntax for whichever stack you ship on. It’s also the fastest way to compare formats when you’re considering a host migration.

A pragmatic redirect checklist

When migrating URLs, hit all of these:

• 301 the old URLs to their new destinations (preserve SEO authority).
• Update internal links — don’t rely on redirects forever; redirects compound and slow down.
• Update sitemap.xml to list only the new URLs.
• Resubmit the new sitemap in Google Search Console.
• Audit your redirects after a week — fix any 404s for old URLs you forgot.
• Avoid redirect chains — A → B → C is two extra hops. Redirect A directly to C.

Use cases

• Slug rename: redirect /blog/old-post-title to /blog/new-post-title.
• Domain migration: bulk-redirect old domain paths to new domain paths.
• Information architecture rework: collapse /products/foo and /store/foo into one canonical URL.
• Affiliate/short links: redirect /r/xyz to a long affiliate URL with a 302 (temporary so the destination URL can change).