Changing URLs during a rebrand, platform migration, or site redesign is one of the fastest ways to lose organic traffic if you get the technical details wrong. This guide walks you through exactly how to redirect old URLs for SEO, step by step, so your search rankings, backlinks, and user experience survive the transition intact.
Key Takeaways
Always use a 301 redirect to send users and search engines from each old URL to the closest relevant new page, not to the homepage or a generic landing page.
Update internal links pointing to legacy URLs, submit an updated sitemap in Google Search Console, and monitor rankings for at least 4–12 weeks after any URL change.
Careless JavaScript redirects, redirect chains, and mass-redirecting deleted pages to the homepage can hurt SEO, waste crawl budget, and create a poor user experience.
During site migrations, rebrands, or moves to a new domain or new website, a detailed redirect map is a non-negotiable technical SEO task that must happen before launch.
Canonical tags complement redirects but do not replace them. Some deleted pages with no honest replacement are better served by a clean 404 or 410 status.
Nonofo Joel helps founders and marketing leads plan and QA complex redirect projects so they don’t burn a year of organic growth on preventable mistakes.
Why Redirecting Old URLs Matters for SEO in 2026
Changing URLs in 2026, whether for a rebrand, a platform move, or a full redesign, still causes major drops in Google Search visibility when redirects are mishandled.
Older URLs often have strong backlinks and high search rankings built up over years. Those pages accumulate behavioral signals, link equity, and trust that Google uses to determine search rankings. 301 redirects pass nearly all SEO value to new URLs, preserving that accumulated authority. Without proper redirects, you’re telling search engines that your content simply vanished, and redirecting old URLs prevents broken links and 404 errors that frustrate users and crawlers alike.
Consider two common scenarios. Moving from HTTP to HTTPS changes every URL on your site. Moving a service page from /services/web-design to /branding/web-design-services on a new website changes the path entirely. In both cases, a permanent redirect from the old URL to the new location ensures search engines understand where the correct content now lives.
AI-powered search tools like ChatGPT, Google AI Mode, and Perplexity largely consume Google’s index. Broken redirect logic doesn’t just reduce blue-link visibility; it can also reduce how often your content surfaces in AI-driven answers. The rest of this article is a practical, step-by-step guide aimed at marketers and founders, not just developers.
When You Must Redirect Old URLs (and When You Shouldn’t)
Not every URL change calls for a redirect. This section helps you decide when a 301 is the right move versus when a 404, 410, or canonical tag serves you better.
Scenarios that should trigger redirects:
Moving to a new domain
Launching a new site or CMS
Changing URLs for category cleanups
Consolidating similar pages or thin blog posts into one page
Merging acquired microsites
When a page has a clear, honest replacement, redirect to the closest relevant page, not the homepage. For example, if a product line is renamed or a city office is relocated, send traffic from the old address to the new page that best matches intent.
Pages with no links, no traffic, and no real replacement are often better served with a 404 or 410 status. Thin, outdated URLs and expired campaign pages fall into this category. Redirecting everything to the homepage is a common anti-pattern. Google may treat these as soft 404s, which weakens topical relevance and confuses users who expect correct content at the redirect target.
Step 1 – Audit Legacy URLs Before You Change Anything
Every redirect project starts with a complete list of legacy URLs, not guesswork. This step happens weeks before launch, not after traffic has dropped.
How to build your inventory:
Crawl the old site with tools like Screaming Frog or a site audit tool to capture every URL, including ones no longer linked internally.
Pull server logs and CMS exports to catch outdated URLs that crawlers still visit.
Export performance data from Google Analytics (organic sessions and conversions per URL) and impressions and clicks from Google Search Console for the last 6–12 months.
Identify high value URLs: pages with strong backlinks, top pages that consistently drive leads, and URLs ranking on the first page for target queries. These get priority in the redirect plan.
Check alternate versions too. HTTP vs HTTPS, www vs non-www, trailing-slash variants. All of them must resolve cleanly before and after URL changes so you don’t end up with duplicate content issues.
Step 2 – Build a Redirect Map from Old URLs to New Pages
The redirect map is a spreadsheet (old URL → new URL → notes) that becomes the single source of truth for devs, marketers, and stakeholders during the migration. Mapping old URLs to new ones is crucial during migrations and should be completed before any changes go live.
How to structure it:
Group old URLs by template or section: blog posts, service pages, product pages.
Match each one URL to the closest relevant new page on the new website or new domain based on the same question the user was trying to answer.
Apply equivalence rules: same or very similar topic, similar search intent, same language or region when alternate versions exist.
Common mapping tactics include merging 3–4 thin guides into one strong evergreen guide and redirecting all legacy URLs to that consolidated asset. This preserves search value while improving keyword relevance on the destination page.
Your map should also track special cases: URLs that should return a 404 or 410, URLs handled primarily with canonical tags, and important pages whose URLs should not change at all.
Choosing the Right Redirect Type (301, 302, 307, 308, JS)
Not all redirect rules are equal. The HTTP status code tells search engines whether a move is permanent or temporary, which directly influences how they index and rank pages.
Redirect Type | Signal | Best For |
|---|---|---|
301 | Moved permanently | Domain moves, page merges, permanent URL changes |
308 | Permanently moved (preserves method) | Same as 301 when HTTP method matters |
302 | Temporary redirect | A/B tests, seasonal content, maintenance windows |
307 | Temporarily unavailable (preserves method) | Short-term routing when POST must stay POST |
JS / Meta Refresh | Weak, last resort | Only when server access is impossible |
A 301 redirect indicates a permanent URL change. Use 301 redirects for permanent URL changes and page merges. 301 redirects pass nearly all SEO value to the new URL, making them the default choice for retiring old URLs, migrating domains, and consolidating content.
A 302 redirect indicates a temporary URL change. 302 redirects keep the old URL indexed by search engines, so they should only be used for temporary redirects where the original URL is expected to return.
JavaScript redirects and meta refresh are last-resort options. Overuse of JavaScript redirects can hurt SEO because Google must render the page before detecting the redirect, making them slower and less reliable. Mixing redirect types inconsistently across the same legacy URLs can delay canonical decisions and create ranking volatility.
How Redirects Interact with Google Search and Canonical Tags
Redirects influence how search engines index and rank pages, but they don’t work in isolation. Google tracks both old and new URLs after a redirect, re-evaluates which should be canonical, and may briefly continue to show the old URL in search results even after a 301.
Canonical tags should be updated on the new page to point to itself, reinforcing the redirect decision. They are a complement, not a replacement. If a new page still carries a canonical tag pointing back to the original URL, or if a noindex directive blocks the new page, Google may continue using the old URL as canonical, or fail to index the new page at all.
Common migration hangovers include incorrect canonical tags, XML sitemaps still listing old URLs, and noindex tags accidentally left on new pages. These redirect signals conflict with each other and confuse search engines.
Use Google Search Console’s URL Inspection tool to confirm Google’s selected canonical, verify that the redirect is recognized, and request reindexing of critical new URLs. This is the fastest way to catch SEO issues before they compound.
Implementing 301 Redirects on Common Platforms
This section covers concrete implementation patterns across common server setups. The goal is giving your developer clear direction, not writing server configuration files from scratch.
Apache: Use the htaccess file or virtual host configuration with mod_rewrite or mod_alias to redirect individual legacy URLs and path patterns. A simple Redirect 301 /old-slug /new-slug handles one page. Pattern-based RewriteRule directives handle bulk path changes.
Nginx: Use map directives and server blocks to define old-to-new pairs. Ensure HTTP to HTTPS and www to non-www (or vice versa) are handled in a single hop. Nginx’s return 301 is efficient for large-scale redirect rules.
WordPress and CMS platforms: Redirects may be created via plugins like Redirection or at the host and CDN level. Having multiple overlapping redirect systems without clear ownership is risky. Decide who owns the rules and document it.
Front-end frameworks (React, Next.js): Avoid JavaScript redirects implemented client-side for SEO-critical moves. Prefer server-side routes or framework-level redirects (e.g., next.config.js) that send proper 301s. Redirects can cause ranking drops if misconfigured at the framework level.
Updating Internal Linking, Sitemaps, and Navigation
Redirects are a safety net, not a permanent crutch. Update internal links to point directly to the final URL to avoid unnecessary hops.
What to update:
Bulk-update internal links within CMS content: posts, landing pages, navigation menus, footers. Every internal link pointing to a legacy URL that now redirects should be changed to the new page directly.
Regenerate XML sitemaps to include only current canonical URLs. XML sitemaps should contain only canonical URLs post-redirection. Submit the updated sitemap in Google Search Console and monitor coverage reports.
Use the migration as a chance to reinforce new hub pages or topic clusters by linking from legacy-equivalent content and updating breadcrumbs.
Relying on internal links that still go through one or two redirects wastes crawl budget on large sites. In aggregate, this can slow pages and hurt SEO and UX. Redirects help preserve link equity during migrations, but they work best as a bridge while you clean up all the links internally.
Common Redirect Mistakes That Hurt SEO
Many SEO issues come not from using redirects, but from using them carelessly across different tools and teams over time.
Key mistakes to avoid:
Redirect chains (A → B → C): Redirect chains dilute SEO value and slow page loading. Each hop leaks authority and adds latency. Collapse chains so every old URL points straight to the final URL in a single step.
Redirect loops (A → B → A): These create too many redirects errors and block both users and crawlers entirely.
Mass redirecting to the homepage: Redirecting unrelated pages to the homepage can create soft 404 errors. Google sees the mismatch and may devalue both the redirect and the homepage.
Leaving temporary 302s in place for permanent changes: This delays canonical decisions and fails to transfer authority.
Excessive redirects across the site: Excessive redirects waste crawl budget and delay indexing.
JavaScript redirects, interstitials, and complex client-side routing can delay rendering and indexing. They should not be the primary tool for managing redirects on SEO-critical legacy URLs.
Build a simple redirect hygiene habit: log new redirect rules, sunset unneeded ones after Google has fully adopted the new URLs, and reconcile rules across CMS, CDN, and server configurations. Regularly audit redirects to prevent technical debt.
Redirect Strategy for New Domains, Rebrands, and Migrations
When you’re rebuilding on a new domain or restructuring an entire site, almost every URL changes. Redirects can cause ranking drops if misconfigured, so a structured approach is essential.
Three-phase approach:
Pre-migration: Audit legacy URLs. Build the redirect map. Benchmark search rankings for top pages. Map old URLs to new ones before a migration begins.
Launch: Activate 301s. Test key flows on the new site. Submit new sitemaps. Verify the old site’s redirect rules are live and correct.
Post-migration: Monitor organic traffic. Fix missed legacy URLs. Reclaim broken links from external sites still pointing to the old site.
When moving to a new domain, use site-wide redirects that preserve paths: oldsite.com/product-a → newsite.com/product-a. This is far better than blunt forwarding everything to the new homepage, which destroys page level relevance.
Check Search Console data for both properties (old and new domain), set address change where appropriate, and watch for crawl errors for several months. Involve SEO, dev, and content stakeholders early so URL naming, topic clusters, and redirect decisions support brand positioning alongside raw rankings.
Handling Deleted Pages, Legacy URLs, and Alternate Versions Over Time
Redirect work doesn’t end at launch. Websites accumulate deleted pages, outdated sections, and legacy URLs that need a clear long-term policy.
Framework for deleted pages:
Situation | Recommended Action |
|---|---|
Strong, honest replacement exists | 301 to the new equivalent page |
Business offer is gone, no comparable alternative | Return 410 (Gone) |
Low-value, unlinked page | Normal 404 is fine |
Legacy URLs that still have backlinks or type-in traffic years later should continue to 301 to the best current equivalent, even if the immediate successor page has itself been retired.
Manage alternate versions of URLs (trailing slash vs none, uppercase vs lowercase, tracking parameters) via canonicalization plus a single preferred redirect pattern. This prevents duplicate content and ensures one URL carries all the ranking power.
Schedule quarterly audits to find and clean up redirect chains created by multiple generations of URL changes, especially on sites older than five years. Monitor performance after implementing redirects to catch degradation early.
Monitoring Redirect Impact with Google Search Console and Analytics
Implementing redirects is only half the work. Confirming they are working and not silently hurting SEO performance is the measurement layer that too many teams skip.
What to monitor:
Use Google Search Console’s Performance report to compare rankings and clicks for key queries before and after the redirect rollout. Focus on the top 50–100 legacy URLs. Monitoring redirects using tools like Google Search Console can catch issues early.
Watch Coverage and Page indexing reports for spikes in 404s, soft 404s, and “Redirect error” issues. These often point to gaps in the redirect map.
Set up annotations in Google Analytics on launch day to track organic traffic changes. Use landing page reports to verify that traffic previously landing on legacy URLs is now landing on the correct new pages.
Allow a 4–12 week observation window post-migration before making drastic changes. If specific pages are losing performance significantly, check that the redirect type, redirect target, and internal linking are all correct before concluding something else is wrong.
How Nonofo Joel Supports Redirect-Heavy SEO Projects
If you’re a founder or marketing lead planning a migration, rebrand, or major restructure, Nonofo Joel works as a strategic partner to reduce the risk of losing organic growth.
That support includes auditing legacy URLs, shaping a redirect map aligned with brand positioning and topic clusters, defining governance so redirects don’t sprawl over time, and QA across staging and production environments.
Post-launch, ongoing monitoring via Search Console and analytics tools catches missed old links and emerging SEO issues before they compound.
Subscribe to the newsletter for in-depth technical SEO and AEO guides, or get in touch for a redirect and migration consultation before you push a new site live.
FAQ: Redirecting Old URLs for SEO
How long should I keep 301 redirects from old URLs?
For significant pages and domain migrations, keep 301 redirects in place for years, not weeks. External links and user bookmarks can persist indefinitely, and removing redirects too early reintroduces broken links.
For low-value or temporary URLs, you can consider retiring redirects after Google has clearly adopted the new page as canonical and no longer crawls the legacy URL frequently. Always run a crawl and check Search Console before removing any long-standing redirects to avoid reintroducing 404s that could hurt SEO.
Do too many redirects on a single page hurt SEO?
A single direct 301 from an old URL to a new URL is fine. The problem is multiple hops. A chain like A → B → C → D slows pages, wastes crawl budget, and weakens the transfer of authority to the final URL. Redirect chains dilute SEO value and slow page loading at every step.
Periodically rewrite old redirect rules so every legacy URL points straight to the current destination in one step. Users also experience slower loads and higher bounce rates when chains are long, which can indirectly send negative performance signals.
Are JavaScript redirects ever OK for SEO?
JavaScript redirects are acceptable for non-critical flows like geo prompts, login gates, or A/B testing. They should not be the primary method for moving legacy URLs that you expect to rank in Google Search. Because Google must render the page to see a JS redirect, they are slower and less reliable than server-side 301s for URL changes and migrations. Always prefer HTTP-level redirects for SEO-important moves.
Should I change my URLs just to improve keywords?
Changing URLs purely to insert more keywords is usually not worth the SEO risk, especially for legacy URLs that already rank and have backlinks. If URLs are extremely messy or non-descriptive (e.g., /page?id=12345), a one-time cleanup with a careful redirect plan can pay off. But frequent renaming is harmful. Focus on content quality, internal linking, and on-page optimization before resorting to keyword-driven URL changes.
What if I can’t implement redirects on my old site or server?
If you’ve completely lost access to the old site or server, you cannot set proper 301s from those old URLs. In that case, focus on what you can control: update external links where possible, strengthen internal linking and sitemap signals on the new site, and use canonical tags correctly. You may have to accept some loss of SEO value and prioritize building new authority rather than perfectly salvaging every one of the old links.