SEO Website Migration: A Checklist for a Safe Relaunch

A website relaunch changes much more than the design. When URLs, navigation, page templates or the CMS change, search visibility needs to make the move too. The most damaging SEO migration mistakes happen when pages, signals and measurement are treated as separate jobs. A reliable SEO website migration answers three practical questions: where each existing page goes, what should intentionally end, and how the new site will be checked after launch.

This guide is for businesses redesigning a website, changing CMS platforms or reorganising their information architecture. It does not replace a project-specific audit, but it gives the team a useful order of work before, during and after launch.

Start an SEO website migration with a clear baseline

Before a design is approved, create a record of the website that exists today. Teams often copy over the pages visible in the menu but overlook useful guides, campaign pages, PDFs, older service pages or URLs that earn valuable links. Those are the omissions that become expensive after the new site goes live.

Build a working inventory from the XML sitemap, Google Search Console, analytics, a crawl export, the CMS and previous campaign lists. For each important URL, capture the planned destination, page type, organic clicks and impressions, significant inbound links and a decision about its future.

Decision	When it fits	What to do in the migration
Move	The content and its search intent still matter.	Build an equivalent new page and redirect the old URL directly.
Improve	The topic matters, but the page is weak or out of date.	Create a stronger destination page and redirect to it where the intent matches.
Consolidate	Several URLs answer the same user question.	Expand one destination and point the older URLs to it.
Retire	There is no useful replacement and no remaining user value.	Return a correct 404 or 410 response rather than redirecting everything to the homepage.

This is where a website content audit pays off. It separates pages with real business value from material that has simply accumulated over time. Google also recommends collecting the old URLs and assigning them to relevant new destinations before a site move with URL changes.

Treat URL mapping as the core migration document

The URL map is the document that connects the old website to the new one. Prepare it before launch, not when the first 404 reports arrive. Avoid blanket rules such as sending every retired page to the homepage. Someone looking for a specific guide or product page expects a relevant answer, and Google may interpret unrelated redirects as soft 404s.

A useful URL map usually includes:

• the old URL, including relevant trailing-slash variants
• the new destination or a deliberate 404 / 410 decision
• the redirect type and technical owner
• the reason for the decision
• test status before and after launch
• notes about campaigns, backlinks or especially valuable rankings

Several older URLs can lead to one page when that page genuinely consolidates the topic. The reverse assumption is less safe: keeping the same slug in a new system does not guarantee the same search intent, navigation context or language structure.

Check redirects, canonicals and internal links together

For a permanent move, server-side permanent redirects are normally the right choice. Google recommends HTTP permanent redirects such as 301 and 308 for site moves, and advises avoiding redirect chains. In practice, an old URL should go straight to its final destination, not through an interim page, tracking variant or legacy HTTPS/WWW rule.

Redirects are only one part of the signal set. The new page should use a self-referencing canonical URL, and navigation, breadcrumbs, sitemaps and contextual links should point to the new address directly. Google explains that redirects are also canonical signals, but they do not make a consistent internal link structure optional.

Check these details as one workstream:

• HTTP/HTTPS and www/non-www variants resolve to the preferred domain.
• Canonicals do not point to staging or legacy URLs.
• Internal links go straight to current destinations.
• Language alternatives and document links have been updated.
• Ads, social profiles and other high-value external links use the new landing pages.

For a more complex restructuring, combine this work with a technical SEO review. It provides a broader view of status codes, load behavior and duplicate pages that can be indexed.

Keep staging out of search and release the live site correctly

A test environment should not appear in search results. Access protection or clear indexing rules can prevent that during development. The launch is the point where temporary barriers become risky: rules that made sense on staging must not remain on public pages.

robots.txt and noindex have different jobs. Google explains that preventing crawling with robots.txt does not reliably prevent a URL from appearing in search, while noindex is the appropriate directive for an accessible page that should stay out of the index. Its robots meta tag documentation also makes clear that a crawler has to access a page in order to read that instruction.

Before release, test the homepage, core service pages, high-value guides, contact journeys and language versions. Do not stop at a 200 status code: verify metadata, canonicals, sitemap output, forms and consent-based tracking in the live configuration.

Preserve search intent, not just old copy

A relaunch is a good moment to remove outdated wording and improve how people move through the site. The risk comes when a page with stable visibility disappears without a suitable replacement. You do not need to preserve every sentence. You do need to preserve the questions, evidence and decisions that made the URL useful in search.

Review Search Console queries before rewriting pages with organic traffic. Which phrases bring qualified visitors? What problem is the page solving? Does the new page still meet that need? A service page can become much clearer while retaining the important subjects, examples and paths to related content.

For businesses reshaping their offer, web design and conception connects content structure with user guidance. When there is a large content base, a relaunch should also reduce accidental keyword overlap: one strong destination page with useful supporting content is usually more effective than several pages with nearly identical labels.

Page signals and technical quality that are easy to lose

A template that looks finished is not necessarily a page that is ready to migrate. CMS and template changes frequently drop small but valuable elements: individual page titles and meta descriptions, one clear H1, structured data, image alt text, downloadable resources or correct language annotations. Review these items across representative page types, not only on the homepage.

Previous titles and descriptions do not need to be copied word for word. They often contain valuable clues about topics and queries that a replacement page must still address. For pages with organic traffic, compare the historic snippets with Search Console data before rewriting titles, introductions and headings. That prevents an otherwise good relaunch from quietly removing established keyword relevance.

Thin replacement pages can cause a similar problem. A URL with only a heading and a few generic lines is not an equivalent replacement for a page that previously helped users. If a complete page cannot be published yet, delaying it or redirecting to a genuinely relevant alternative is often the better decision.

Secure delivery also belongs in the acceptance process. Every address variant should resolve to the preferred HTTPS version, with a valid certificate, no mixed-content warnings and working resources. Web hosting and WordPress hosting should therefore be part of relaunch planning, not an afterthought on launch day. Check mobile loading and layout as well: a page may be indexable but still lose visitors if it is slow to orient users or the form feels unresponsive.

SEO website migration checklist for launch and the weeks after

Use the following items as an acceptance plan. Assign them to content, development, hosting and marketing; a checkmark without a tested URL has little value.

Before launch

1. The URL inventory and URL map are complete, credible and approved.
2. Every important new page has a relevant title, description, canonical URL and internal links.
3. Permanent redirects have been tested in a production-like environment.
4. Staging is not publicly indexable, and live pages have a clear release plan.
5. The XML sitemap includes only canonical, indexable destination URLs.
6. Page titles, meta descriptions, H1s, structured data, alt text and language annotations are checked for key page types.
7. HTTPS, certificates, domain-variant redirects and external resources cause no security warnings.
8. Analytics, consent and conversion events work in realistic consent states.
9. Mobile layouts, forms, downloads, the 404 page and key loading paths have been tested.

On launch day and afterwards

1. Sample important old URLs: status code, final redirect destination and destination content should all match the URL map.
2. Sample new URLs: 200 status, canonical, robots directive and internal links should be correct.
3. Submit the new sitemap in Search Console and verify the important site properties.
4. Watch Search Console for indexing and crawling errors, soft 404s and server issues.
5. Compare organic entry pages, search queries, campaign URLs and conversion tracking with the pre-launch baseline.
6. For an affected page, inspect the snippet, index status, destination content, internal links and measurement separately instead of reacting only to overall traffic.
7. Keep redirects for as long as users, backlinks and search engines need them. Google gives at least one year as a rule of thumb for domain or URL moves.

Larger moves can bring temporary ranking fluctuations while Google crawls and processes the new URLs. That does not mean the structure should be rebuilt after two days. Act on clear faults instead: wrongly mapped URLs, accidental noindex directives, unavailable destinations or growing server errors.

A relaunch finishes after the migration, not at launch

An SEO website migration is successful when the handovers are controlled: old URLs reach relevant new pages, staging becomes an indexable public site, and the previous data baseline becomes active monitoring. URL mapping, suitable redirects, clear canonicals, deliberate indexation and a candid post-launch review protect visibility better than last-minute cosmetic changes.

Planning this work early as part of search engine optimization and website conception gives a relaunch room to achieve its real goal: a better website without needlessly losing the value of existing content and access paths.