Before we rebuilt our site on Next.js, our site was based in WordPress, and there weren't a lot of ideal decisions made prior to my coming on board related to URL site structure, much of which was based in SEO understandings at the time (i.e. have as much as possible at the top level, like site.com/my-blog-post, site.com/my-page, etc). Exacerbated by WordPress plugins that allowed endless redirects, we now lug around a pretty hefty amount of redirects, close to 1,000, as we've restructured content over the years to better accomodate.

It's a pretty big issue. Thousands upon thousands of historical inbound links would immediately break if we dumped most of these, and the way Google is handling SEO and 404s and authority at the moment, it would be really bad. So I'm not interested in the "just don't have that many redirects", because we're already working on that piece. I'm trying to figure out how to performantly handle this many redirects of varying kinds in the meantime.

Has anyone effectively managed to handle an astronomical amount of redirects? Edge Config seems fully out of the question, with the 64kb limit, and next.config redirects has a limit of 1024. Just looking for more options to figure these sorts of things out.