SEO Migration Guide

How to Migrate a Website Without Losing SEO

A website migration can change the technology underneath your site without erasing the search value you have already built. The key is to treat URLs, content, links, metadata, crawlability, and measurement as part of the migration—not as cleanup after launch.

By Randa Vandenack Schilling · Founder of PeachSites and creator of Panderr · September 13, 2026

Moving a website can feel risky when search traffic matters to the business. Pages may already rank for valuable searches. Other websites may link to them. Google may have years of history associated with their URLs. The site may contain hundreds of internal links, images, articles, service pages, metadata, and conversion paths.

That does not mean the website has to stay trapped on its current platform or with its current provider. It means the migration needs a plan.

1. Inventory the site before you change it

Start with the existing website, not the new design. Record the URLs you want to protect and identify the pages that currently matter to search and customers. Include service pages, location pages, articles, FAQs, important PDFs, images with direct traffic, and any unusual URLs that still receive visits or links.

Save current page titles, descriptions, canonical tags, robots directives, structured data, headings, internal links, and sitemap URLs. Record analytics and Search Console baselines so you have something meaningful to compare after launch.

This is one reason Panderr treats migration as an analysis problem before it becomes a design problem. You cannot intentionally preserve what you have not identified.

2. Decide which URLs can stay exactly the same

If the domain and content structure do not need to change, preserving established URL paths can remove unnecessary migration complexity. A page at /pool-maintenance/ does not need a new address simply because the hosting platform changes.

Keeping useful URLs is especially valuable when those URLs already have backlinks, rankings, bookmarks, citations, or marketing materials pointing to them.

When a URL must change, document the old URL and its best new destination before launch.

3. Build an old-to-new URL map

A migration map should give every important existing URL an intentional outcome. Some remain unchanged. Some move to a new equivalent. Some are consolidated into a stronger page. Content that is genuinely obsolete may be removed.

Avoid treating the homepage as a universal destination for removed URLs. If an old page has a clear replacement, redirect it there. If there is no meaningful replacement, returning a legitimate not-found response can be more accurate than sending every obsolete address to the homepage.

4. Use permanent redirects when URLs change

For pages that permanently move, use server-side permanent redirects such as 301 or 308 redirects. Keep redirect paths direct whenever possible: old URL → final new URL, rather than old URL → temporary URL → another URL → final destination.

Redirects protect users as well as search engines. Someone following an old backlink, saved bookmark, directory listing, email campaign, or social post should still reach the right content.

5. Preserve the content that earned the visibility

A URL is only one signal. If a page ranks because it thoroughly answers a searcher's question, replacing it with a thin paragraph during a redesign can change how search engines evaluate it.

Preserve useful headings, explanatory copy, FAQs, images, supporting links, location context, product or service details, and other material that makes an important page valuable. Improve weak content deliberately, but do not erase strong content simply to make a new layout look cleaner.

This is where separating Preserve, Improve, and Redesign becomes useful. Migration determines how the website moves. Redesign determines how much you intentionally change along the way.

6. Check every canonical URL

A canonical tag should reinforce the URL you actually want indexed. During migrations, it is surprisingly easy for a new page to retain a canonical pointing to the old domain, a staging address, a generated preview URL, or another version of the page.

After the site is generated and again after it is live, inspect the rendered HTML. Important indexable pages should generally have self-referencing canonicals using their final public URLs unless you have a specific reason to canonicalize elsewhere.

7. Update internal links to the final URLs

Do not rely on redirects to fix your own navigation. Menus, buttons, article links, breadcrumbs, footer links, image links, and contextual internal links should point directly to the final destination.

This makes crawling more efficient and gives search engines a consistent picture of the site's preferred structure. It also prevents unnecessary redirect hops for visitors.

8. Carry forward page-level SEO details

Review titles, meta descriptions, heading structure, structured data, image alt text, social metadata, and indexing directives on the migrated pages. These do not all directly determine rankings, but together they affect how pages are understood, presented, shared, and crawled.

A redesign is also an opportunity to correct duplicated titles, vague headings, outdated descriptions, malformed schema, and other weaknesses—but make those improvements intentionally rather than allowing metadata to disappear during transfer.

9. Generate a clean XML sitemap

Your production sitemap should contain the canonical URLs you want search engines to discover and index. Do not fill it with staging URLs, redirected URLs, administrative pages, duplicate variants, or pages intentionally marked noindex.

After launch, verify the sitemap at its public URL and submit or confirm it in Google Search Console.

10. Check robots.txt and noindex before launch

Staging environments are often intentionally hidden from search engines. That is good practice until a staging rule follows the site into production.

Check robots.txt, page-level robots meta tags, and response headers on the live domain. Confirm that the pages you want in search can actually be crawled and indexed.

11. Preserve analytics and Search Console access

Keep measurement intact through the transition. Confirm that your analytics tag loads on the new site, conversions still fire, and Search Console verification remains valid.

Immediately after launch, inspect a sample of high-value URLs in Search Console. Confirm Google's selected canonical, crawlability, indexing status, and the final URL after redirects. Request indexing for important new or substantially changed pages when appropriate.

12. Test the live site, not just the preview

A preview can tell you whether a design looks right. It cannot prove that production DNS, HTTPS, redirects, canonical URLs, sitemap routes, robots rules, forms, analytics, and external integrations all behave correctly.

Once the domain is live, crawl and inspect the production version again. Test old URLs. Check mobile navigation. Submit forms. Open downloads. Verify images. Follow internal links. Inspect source HTML. Confirm that www and non-www behavior is intentional.

13. Expect monitoring, not instant certainty

Search engines need time to recrawl changed URLs and process migration signals. Some fluctuation after a substantial migration can occur even when the technical work is sound.

Watch indexed pages, crawl errors, organic landing pages, clicks, impressions, conversions, and important rankings over the following days and weeks. Investigate patterns rather than reacting to a single day's movement.

What can actually cause SEO loss during a migration?

The biggest risks are usually avoidable: deleting useful pages without replacements, changing established URLs without redirects, accidentally blocking crawling, carrying staging canonicals into production, stripping valuable content, breaking internal links, losing assets, publishing duplicate versions, or failing to notice errors after launch.

In other words, the danger is not the act of changing providers. It is losing the information and signals that connected the old website to its audience.

A practical SEO migration checklist

1. Crawl and inventory the current website.
2. Save baseline analytics and Search Console data.
3. Preserve valuable URLs whenever practical.
4. Map every changed important URL to an intentional destination.
5. Implement direct permanent redirects.
6. Preserve or deliberately improve valuable content.
7. Set correct production canonicals.
8. Update internal links to final URLs.
9. Review titles, descriptions, headings, schema, and robots directives.
10. Create a sitemap containing canonical production URLs.
11. Verify robots.txt and remove accidental noindex rules.
12. Confirm analytics and conversion tracking.
13. Test HTTPS, DNS, redirects, forms, images, downloads, and navigation on production.
14. Verify the sitemap and key URLs in Search Console.
15. Monitor indexing, traffic, errors, and conversions after launch.

What Panderr carries forward—and what to verify

Panderr imports available source page titles and meta descriptions into supported page SEO fields. Studio also provides settings for titles, descriptions, canonical URLs, indexing, and social metadata. These support a careful migration, but they do not replace the checks above.

Before publishing, compare the migrated pages with your source inventory. URL paths can change during import or export, and source canonical tags, indexing directives, and structured data are not all carried forward automatically. Configure any required redirects in your publishing environment and test them on the live site; saving a redirect setting alone does not confirm that a redirect is active. Review final URLs, metadata, internal links, sitemap, robots rules, analytics, and indexability. Panderr does not guarantee rankings or a migration with no SEO loss.

Migration should protect the work you have already built

A business should be able to change technology without treating its website as disposable. That principle is central to Panderr: analyze the site you already have, preserve the parts worth keeping, improve what needs attention, and redesign only when redesign is actually the goal.

For the broader migration process, read Website Migration: The Complete Guide. If you are comparing tools, see What Is a Website Migration Tool?. And if you want hands-on help moving a business website, PeachSites provides managed website migration and web services.