How do I redirect an old website to a new one?

Why Redirecting Your Old Site Is a Strategic SEO Migration, Not Just a Technical Task

Moving a website to a new domain or platform is far more than setting up redirects—it’s a high-stakes SEO migration where accumulated value can vanish if not handled with strategy. Poorly managed migrations trigger a domain reset, erasing years of search traffic and ranking potential. The V&D case illustrates this starkly: their 2015 migration resulted in a complete loss of organic visibility, and despite renewed SEO efforts, it took three years to recover to prior levels. This isn’t just theoretical—it’s a real-world consequence of treating migration as a technical checkbox rather than a preservation effort.

Conversely, a well-executed migration doesn’t just avoid loss—it can drive growth. The SRO case demonstrates this upside: after their April 2019 migration, they achieved more than ten #1 organic rankings, a 34% increase in conversions, and a 20% rise in general traffic. These outcomes stem from treating migration as a holistic process that safeguards technical SEO, internal linking, structured data, and emerging visibility in AI-powered search experiences like Google AI Overviews. Simply redirecting URLs ignores the deeper work needed to maintain entity signals, crawl budget efficiency, and content integrity during transition.

For businesses launching with AI Business Sites, this strategic approach is embedded in the 7-day build process. While the platform handles technical execution—including permanent server-side redirects and structured data preservation—the migration mindset begins long before launch. Early SEO involvement maps legacy URLs, protects high-value landing pages, and plans redirect implementation in a staged environment for at least two weeks of testing. Go-live is scheduled Monday or Tuesday to ensure team availability for post-launch monitoring, recognizing that ranking fluctuations are normal as search engines recrawl and reindex the site. The goal isn’t just to move pages—it’s to ensure the new site inherits and builds upon the old one’s authority, so traffic doesn’t just return—it improves.

Google's official guidance makes it clear: when changing URLs, permanent server-side redirects (301 or 308) are the recommended approach to ensure both users and search engines reach the correct page. These redirects tell Google the new location should be treated as the canonical version, preserving SEO value and avoiding confusion. Temporary redirects like 302, 303, or 307, by contrast, signal that the move is short-lived, causing Google to keep the original URL indexed and potentially splitting ranking signals between old and new pages.

The interpretability hierarchy Google uses for redirects places server-side methods at the top, followed by meta refresh tags (with zero-second delays treated as permanent), then JavaScript-based redirects, which carry the lowest chance of correct processing. This means that even if a redirect technically works for users, Google may not interpret it as intended unless it's implemented at the server level. For businesses launching a new site—especially during a domain or CMS change—relying on anything less than a permanent server-side redirect risks incomplete indexing and lingering visibility of outdated URLs.

It's also normal for old URLs to appear in search results temporarily after a migration, as Google processes the canonical shift. The search engine treats these as alternate names that gradually fade as users and crawlers adjust to the new structure. During this settlement period, ranking fluctuations are expected, particularly on larger or more complex sites, and should not be mistaken for migration failure. Properly implemented 301/308 redirects, combined with time for recrawling and reindexing, provide the most reliable path to preserving search visibility and traffic. AI Business Sites follows this standard during site launches, ensuring all legacy URLs are permanently redirected server-side to maintain SEO continuity from day one.

A website move is surgery on a live digital asset, and the cut happens before launch.

Success starts with SEO at the table before development begins. Early involvement lets the team identify risks, map legacy URLs to new destinations, review site architecture, and protect important organic landing pages before changes reach production early SEO involvement guidance. Mapping requirements early and involving development from the start is a core process-based best practice SEO migration best practices.

Planning means a real redirect map, not an afterthought. Google states permanent server-side redirects are the best way to ensure Google Search and people are directed to the correct page Google redirect guidance. Server-side redirects have the highest chance of correct interpretation, ahead of meta refresh and JavaScript redirects redirect hierarchy. A badly managed migration can result in a domain reset where accumulated search traffic and ranking potential are lost migration risk warning.

A pre-launch checklist keeps the move controlled.

• Involve SEO before development begins to map legacy URLs and protect high-value landing pages
• Test in a staging environment for at least two weeks to prove redirects and functionality
• Avoid simultaneous front-end and back-end migrations to isolate issues
• Schedule go-live on Monday or Tuesday for developer availability
• Manage crawl budget to prioritize indexing of important pages

Staging time matters. Testing the website for at least 2 weeks in the staging-environment and only going live when everything is proven to work well, and the redirect-plan has been properly implemented, is recommended staging testing guidance. Do not migrate front-end and back-end at the same time. If something goes wrong, the cause is easier to trace migration sequencing advice.

Timing reduces risk. Schedule a go-live on a Monday or Tuesday, so that developers are available in the following days to solve any problems go-live timing recommendation. Google recommends allowing time for search engines to recrawl, reindex, and process a migrated website, with ranking fluctuations being normal during settlement post-migration settlement guidance.

Crawl budget is part of the plan. Migration that ignores crawl budget risks a loss of search traffic on conversion pages crawl budget warning. Google assigns a crawl budget to every website, requiring careful management on large sites to ensure important pages are prioritized crawl budget definition.

Redirects alone are insufficient. In 2026, protecting organic visibility means preserving technical SEO fundamentals, internal linking, content quality, structured data, entity signals, analytics, and visibility across AI-powered search experiences beyond redirects framework. It’s only an SEO migration if the accumulated SEO value is considered and it is consciously moved SEO migration definition.

The contrast is clear in case studies. V&D’s 2015 migration resulted in a domain reset and recovery took until 2018, three years despite renewed SEO efforts V&D case study. SRO’s successful April 2019 migration yielded more than ten #1 organic positions, 34% more conversions, and 20% increased general traffic SRO case study.

For clients in Building Your Website > Getting Started, AI Business Sites applies this process-based discipline during site launches, with planning, staging, and timing built around preserving existing equity while moving to a new 85+ page foundation.

When launching a new website, redirecting an old domain properly is critical to preserving search rankings and traffic. A poorly executed migration can trigger a domain reset, as seen in cases where recovery took three years despite renewed SEO efforts according to industry research. AI Business Sites eliminates these risks by handling the entire redirect process during the 7-day build, so clients avoid technical complexity and potential traffic loss.

Our team begins by mapping legacy URLs to new destinations before development starts, aligning with best practices that emphasize early SEO involvement to identify risks and protect important pages per SEO migration guidelines. We implement permanent server-side 301/308 redirects for all legacy pages, which Google explicitly recommends as the most reliable method for ensuring search engines and users reach the correct content per official guidance. This approach minimizes the chance of misinterpretation compared to JavaScript or meta refresh alternatives.

Before go-live, we test the redirect plan in a staging environment for at least two weeks to verify functionality and proper implementation as advised by migration experts. Go-live is scheduled on a Monday or Tuesday to ensure team availability for post-launch monitoring, and we manage crawl budget to prioritize indexing of key pages. Throughout the process, clients retain full ownership of their domain and data, while we manage the technical heavy lifting—including redirect strategy, staging tests, and post-launch oversight—so they can focus on running their business without facing DIY migration risks.