Why redirects matter during a site revamp
The redirect map: what it is and how to build it
A redirect map is a spreadsheet with two columns: Old URL and New URL. Every URL that will change in the redesign has an entry mapping the old address to the new equivalent.
Step 1: Crawl your current site Use Screaming Frog to crawl your existing site before the redesign begins. Export all 200-status URLs. This is your starting list.
Step 2: Identify high-priority URLs Sort by inbound links (Screaming Frog shows this from your Google Search Console integration) and by organic traffic (from Google Analytics). URLs with significant backlinks or organic traffic must have redirects losing them is the most costly scenario.
Step 3: Map old URLs to new URLs For each old URL, identify the best equivalent on the new site. Categories: exact match (same content, new URL), closest match (similar content on a differently structured new site), or category (page being consolidated redirect to the parent category).
Step 4: Implement before launch All redirects must be live on the new site before the old site is taken down or the new site goes live. Test every redirect in the redirect map before launch using a redirect checker tool.
Ready to take the next step?
Let Perceptra scope the right approach for your business.
Book a Free Strategy Session ?The four types of redirects and when to use each
301 (Permanent redirect): The standard for SEO. Use when content has permanently moved to a new URL. Passes approximately 90 99% of link equity to the new URL. This is what you use for site revamps.
302 (Temporary redirect): Use when content will return to the original URL A/B testing, temporary maintenance pages. Does not pass link equity as reliably as 301. Never use 302 for permanent URL changes.
307 (Temporary redirect, method-preserved): Technical HTTP standard for temporary redirects. Not commonly needed for SEO purposes.
410 (Gone): For content that is permanently deleted with no relevant replacement. Tells Google the page is gone intentionally and to remove it from the index. Use instead of 404 when you are certain the content will never return.
The redirect mistakes that cause traffic loss
Mistake 1: Redirect chains A ? B ? C ? D. Each hop in a redirect chain loses a small amount of link equity. More importantly, chains slow page loading and can cause crawl issues. Fix chains by updating redirects to point directly to the final destination: A ? D.
Mistake 2: Redirecting everything to the homepage A common lazy migration strategy. If you are moving 200 specific product pages and you redirect all of them to the homepage, Google treats those pages as gone (because the content did not follow them). Redirect each page to its most relevant equivalent.
Mistake 3: Forgetting to update internal links After implementing redirects, update internal links in navigation, content, and sitemaps to point directly to the new URLs. Leaving internal links pointing to redirected URLs creates unnecessary redirect hops for Googlebot.
Mistake 4: Not testing before launch A redirect in your .htaccess or redirect table that works in staging may not work in production due to server configuration differences. Test every redirect after live deployment using a batch redirect checker.
Post-revamp monitoring
After launch: check Google Search Console daily for the first two weeks. Watch for:
- A spike in 404 errors (missed redirects)
- A drop in indexed pages (indexation issues)
- A drop in keyword rankings (legitimate if temporary; investigate if sustained)
Most post-revamp traffic dips recover within 4 8 weeks if redirects were implemented correctly. Sustained drops indicate missed redirects or indexation problems.
Frequently asked questions
How long should we leave 301 redirects in place? At minimum 1 2 years. Ideally, permanently. Removing a 301 redirect before all search engine records have updated creates a 404 error for users who click old bookmarks or search results.
Do redirects slow down our site? A single 301 redirect adds approximately 50 200ms to load time. Multiple redirect chains can add 0.5 1.5 seconds to LCP. Keep redirects to a single hop where possible.
Can we use JavaScript redirects for SEO purposes? No. JavaScript redirects are not reliably followed by Googlebot and do not pass link equity as reliably as server-side 301 redirects. Use server-side redirects for all SEO-relevant URL changes.