My website has been running for more than 15 years, and over time I've added, removed, and reorganized many pages. I now have more than 1,000 old URLs that need to redirect to relevant destinations. The site is mostly static PHP and HTML running on Linux with Apache. What's the most efficient way to manage this many permanent redirects without hurting server performance or Core Web Vitals?
3 Answers
An Apache RewriteMap is a good fit for a large collection of one-to-one redirects. Store the old and new paths in a text map and have Apache look up the destination. Make sure unmatched URLs are allowed to continue normally—don’t use a fallback that sends every unknown path to the homepage, since that can turn genuine 404s into incorrect redirects. Generate the map from one source file if possible, and collapse redirect chains so old URLs go directly to their final destinations. The redirects themselves aren’t rendered as pages, so they don’t directly add a Core Web Vitals measurement.
Before keeping all 1,000 entries forever, check the access logs and search data to see which old URLs still receive meaningful traffic. Some may only be requested by crawlers and can be removed so they return a normal 404 or 410. Be careful when pruning, though—keep redirects for URLs with backlinks, bookmarks, or useful referral traffic.
For a list this large, keep the redirects in the main Apache virtual-host configuration rather than .htaccess. Apache avoids the repeated directory-level configuration checks, and the performance difference is preferable for a busy site. If several URLs follow the same pattern, combine them into a few RewriteRule directives instead of maintaining hundreds of individual rules.
It’s also worth testing the whole list after each change. A simple script using curl can detect redirect loops, chains, bad destinations, and typos before they become a problem.