Managing redirects at scale is the part of a site migration that usually gets handed to whoever has time, and then breaks quietly: a config file grows past a platform limit, an editor adds a rule that creates a loop, or a chain of three hops appears after the second redesign. This article treats redirects as a small production system with its own data model, validation, runtime, failure modes and tests. If you need the SEO process side (URL inventory, mapping, launch-day checks), start with our website migration checklist for keeping your SEO ; here we focus on the engineering behind it.
Why a list in a config file stops working
Most frameworks let you declare redirects in configuration, and for a few dozen rules that is the right answer. The problems show up as the list grows.
Platform limits. The Next.js docs warn that redirects may have a limit on platforms, and on Vercel there is a limit of 1,024 redirects ; for 1,000+ they recommend a custom solution.…