Every site migration, URL restructure, or page consolidation leaves old URLs behind — and every old URL that 404s instead of redirecting bleeds traffic, breaks backlinks, and dead-ends the crawlers trying to reach your content. This tool converts a simple list of old→new pairs into deploy-ready rules in the four most common formats.
Why it matters for AI search: the classic case for redirects — preserving link equity and not breaking bookmarks — extends directly to AI systems. Models trained on data mentioning your old URLs, and AI search indexes that stored them, will keep trying those URLs long after you've moved the content. A 301 redirect means those references still resolve to your content and can be cited; a 404 means an AI assistant fetching your old URL comes back empty-handed and cites someone else. During any migration, redirects are how you carry your existing AI visibility over to the new structure.
How this tool works: add your redirect pairs — source path on the left, destination on the right — and toggle each between 301 (permanent) and 302 (temporary). The output panel generates all four formats simultaneously, one per tab: Apache .htaccess (Redirect 301 /old /new), nginx rewrite rules with correctly escaped regex characters, a complete next.config.js redirects() block for Next.js/Vercel, and Cloudflare Pages' _redirects file format. Copy from the tab that matches your hosting, or download the file directly.
Limitations: the generated rules are exact-match, one URL to one URL — pattern/wildcard redirects, query-string handling, and conditional logic (by country, device, or header) are platform-specific enough that no generic generator handles them well; use these rules as your starting scaffold and consult your platform's docs for pattern syntax. The tool also doesn't verify your destination URLs exist or check for redirect chains (A→B→C) — after deploying, spot-check a few old URLs manually and keep chains to a single hop, since both crawlers and users pay for every extra redirect in the chain.