Website Migration SEO Checklist: Keep Your Rankings
A before, during and after checklist for website migrations: URL inventory, 301 redirect maps, launch-day checks and the monitoring that catches ranking losses early, plus why agencies miss items.
Short answer: a website migration keeps its SEO when every old URL that matters redirects with a 301 to its closest new equivalent, the content, titles and internal links on key pages survive the move, the new site is crawlable on launch day, and someone watches Search Console closely for the following weeks. Almost every migration disaster traces back to a skipped item below.
First, name your migration type
The risk depends on what changes:
| Migration | What changes | Risk |
|---|---|---|
| HTTP to HTTPS | Protocol only | Low |
| Platform change, same URLs | CMS or builder | Low to medium |
| Redesign with new URL structure | URLs, templates, content | Medium to high |
| Domain change | Every URL | High |
| Several at once (new domain + platform + structure) | Everything | Highest |
If you can, avoid doing everything at once. Changing domain and URL structure and content in the same launch makes it very hard to tell what caused a drop.
Phase 1: Before you build
1. Benchmark current performance. Export 16 months of Search Console data (queries and pages), and record organic sessions and conversions by landing page from your analytics. You need a baseline to compare against.
2. Build a complete URL inventory. Combine three sources, because each misses things:
- A full crawl with a tool such as Screaming Frog or Sitebulb
- Every landing page that received organic traffic in analytics or Search Console
- Every URL with external backlinks, from a backlink tool
The CMS page list alone is not enough. It misses old campaign pages, PDFs, image URLs and pages that were deleted but still have links.
3. Mark your priority pages. Sort the inventory by organic clicks, conversions and referring domains. The top pages get individual attention throughout.
4. Save the old site's on-page data. Titles, meta descriptions, H1s, canonical tags, structured data and internal link counts for priority pages. Crawl tools can export all of this.
Phase 2: The redirect map
This is the single most important deliverable. It is a spreadsheet with two columns, old URL and new URL, covering every URL from the inventory.
Rules:
- One to one where possible. /services/roof-repair should go to /roof-repair, not the homepage.
- Closest relevant page when a page is merged or removed. Redirecting many unrelated pages to the homepage is often treated by Google like a soft 404.
- No chains. Old URL to new URL in one hop. If the site has had earlier migrations, update those older redirects to point straight at the final URL too.
- Permanent redirects (301 or 308).
- Include variants: trailing slash, uppercase, www and non-www, HTTP and HTTPS, and URLs with common parameters.
- Let genuinely dead pages return 404 or 410 if they have no traffic, links or equivalent. Not every URL needs a redirect.
Test the map on staging by running the old URL list through a crawler in list mode and checking that each returns one 301 to the expected destination with a 200 at the end.
Phase 3: Build the new site with SEO intact
- Keep the content on priority pages. Rewriting or cutting the text on your best-ranking pages during a migration is a common cause of losses.
- Carry over titles, meta descriptions and H1s for priority pages unless there is a clear reason to change them.
- Keep internal links pointing to priority pages at least as strong as before, and update them to new URLs directly rather than relying on redirects.
- Carry over structured data, hreflang tags if you have them, and image alt text.
- Set self-referencing canonical tags on the new URLs.
- Block staging from indexing with password protection, and make sure that protection (or any noindex tag or robots.txt block) is removed at launch.
- Check page speed on the new templates. A heavier design can undo ranking gains.
Phase 4: Launch day
Run this in order, ideally at a quiet traffic time:
- Deploy the new site and the redirects together.
- Check robots.txt allows crawling and does not contain a leftover "Disallow: /".
- Confirm no noindex tags on live pages (crawl the site and filter by indexability).
- Crawl the old URL list and confirm every redirect resolves in one hop.
- Spot-check priority pages by hand: content, title, canonical, structured data.
- Submit the new XML sitemap in Search Console. For a domain change, verify the new domain, then use the Change of Address tool from the old property.
- Confirm analytics and conversion tracking fire on the new site.
- Update links you control: Google Business Profile, social profiles, email signatures, ad destinations, directory listings.
Phase 5: After launch
Days 1 to 14: check Search Console every day for crawl errors, 404 spikes and indexing issues. Look at server logs if you have them to see Googlebot hitting old URLs and following redirects.
Weeks 2 to 8: compare clicks and impressions by page against your baseline. Some movement is normal. A priority page that has dropped sharply and stays down needs checking: redirect correct, content intact, internal links present.
Ongoing: keep redirects in place for at least a year per Google's guidance, and preferably indefinitely. Reach out to the sites behind your most valuable backlinks and ask them to update the URL.
Why agencies miss migration checklist items
The query "why do agencies miss key items on their SEO checklist during website migrations" gets asked for a reason. The recurring causes:
- SEO joins at the end. The designers and developers finalize URLs and templates, and SEO is asked to "check it" a week before launch, when changing anything is expensive.
- The inventory comes from the CMS. Pages that exist only as old links or PDFs never make it into the redirect map.
- Content is rewritten for the new design. Copy on high-ranking pages is shortened to fit layouts.
- Staging settings leak to production. The noindex tag or robots block from staging goes live.
- Nobody owns post-launch. The project is marked done at launch, and the 404 spike in week two goes unnoticed.
Prevention is procedural: involve SEO when the sitemap is being planned, make the signed-off redirect map a launch requirement, add "robots and noindex check" to the deploy steps, and assign a named person to monitoring for the first month with a written rollback or fix plan.
Worksheet: inventory, map and check (filled and blank)
Filled example (labelled demonstration, a fictional five-page plumbing site moving builders):
| Old URL | Clicks, last 3 months | New URL | Redirect | Title kept? | Checked after launch |
|---|---|---|---|---|---|
| /plumbing-services.html | High | /services | 301 | Yes | Day 1, day 7 |
| /about-us.html | Low | /about | 301 | Yes | Day 1 |
| /boiler-repair.html | Medium | /services/boiler-repair | 301 | Rewritten, same keyword | Day 1, day 7 |
| /old-offer-2023.html | None | /services | 301 to closest page | n/a | Day 1 |
| /contact.html | Medium | /contact | 301 | Yes | Day 1 |
Blank worksheet:
| Old URL | Clicks, last 3 months | New URL | Redirect | Title kept? | Checked after launch |
|---|---|---|---|---|---|
Prelaunch: canonicals, robots, sitemaps and translations
- Each new page's canonical points to itself on the final domain, not to staging.
- The robots file allows crawling; any staging noindex is removed.
- The new sitemap lists only final URLs that return 200.
- If you have translated pages, keep their language alternates pointing at the new URLs.
Launch ownership and rollback
Write down one named person for launch day, who can undo what, and the trigger for rolling back (for example, key pages returning errors). Keep the old site's files or export until the new one is stable.
Postlaunch Search Console checks with a dated window
Compare a fixed window, such as the 28 days after launch against the 28 days before, using the same pages. Record the dates in your worksheet so the comparison is repeatable. Expect some movement in the first weeks; investigate pages that drop and stay down. Official guidance: Google Search Central's documentation on site moves with URL changes.
Start building your business website. Create your account. Building a site on We.Inc is free for every account, with no card needed. AI building and your own domain start on Starter at $20 a month; see pricing.
Useful next steps: check an existing site with the free website grader, estimate a budget with the website cost calculator, browse business website templates or read how the We.Inc website builder works.
Quick checklist
- [ ] Baseline data exported
- [ ] URL inventory from crawl + analytics + backlinks
- [ ] Priority pages identified
- [ ] Redirect map complete, one hop, permanent, tested on staging
- [ ] Priority page content, titles and internal links preserved
- [ ] Staging blocks removed at launch
- [ ] Sitemap submitted, Change of Address used if the domain changed
- [ ] Analytics verified
- [ ] Daily Search Console checks for two weeks
- [ ] Redirects kept for at least a year
Moving to a new builder
If you are migrating because your current platform is hard to maintain, choose a destination where you control URLs, titles and redirects yourself. We.Inc lets you rebuild pages from a chat description and then adjust them visually or in code, with hosting and SSL included, so you can keep your existing URL structure. Before launch, run the new pages against our on-page SEO checklist and make sure tracking is in place with the analytics setup guide.
Frequently asked questions
How do I compare traffic before and after a migration?
Pick a fixed window, such as 28 days after launch versus 28 days before, and compare the same pages in Search Console. Note the dates so you can repeat the check.
Will I lose rankings when I migrate my website?
Some temporary fluctuation is normal while Google recrawls and processes redirects. Lasting losses almost always come from preventable problems: missing redirects, removed content, blocked crawling, or changed titles and internal links. A careful migration usually recovers within weeks.
Should I use 301 or 302 redirects for a migration?
Use permanent redirects (301 or 308) for pages that have moved for good. Temporary redirects (302 or 307) tell search engines the old URL may come back, which is not what you want in a migration.
How long should I keep redirects after a migration?
Google's guidance is to keep redirects for at least a year, and in practice keep them indefinitely where you can, because old links, bookmarks and emails keep sending visitors to the old URLs.
Do I need the Change of Address tool in Search Console?
Only when you move to a new domain. After redirects are live, use the Change of Address tool in the old domain's Search Console property. It is not used for moving URLs within the same domain or switching from HTTP to HTTPS.
Why do agencies miss items on migration checklists?
Usually because SEO is brought in after the build is finished, the URL inventory comes from the CMS instead of a crawl plus analytics and backlink data, and nobody owns post-launch monitoring. Fix it by making the redirect map a sign-off item before launch and assigning a named person to check Search Console daily for two weeks.
More in Blog
- Small Business Website Cost: What to Budget in 2026
- Social Proof Strategies That Boost Conversions
- Softr Client Portal: Setup, User Groups and Limits
- Notion Softr: Use Notion as a Softr Data Source (2026)
- The Solopreneur's Tech Stack: Every Tool You Actually Need in 2026
- Squarespace AI Website Builder Review: Is Blueprint AI Worth It?
- Squarespace Domain: Buy, Connect, Transfer, Free Year
- Squarespace Favicon: Change It, Size, Format, Fixes
Related guides and tools
Start building
- how to make a website
- AI website builder
- free website builder
- website templates
- website builders by industry
How we research, test and update this page: our editorial policy. We.Inc is our own product.
Product
Who It's For
- For Agencies
- For Freelancers
- For Hosting Providers
- For SaaS Platforms
- For Startups
- For Financial Services
- For Healthcare
Features
Resources
- Blog
- Help Center
- Free Business Tools
- Free UI Components
- Website Templates
- Template Collections
- Website Examples
- Guides
- Comparisons
- Alternatives
- Best Lists
- Reviews
- Pricing Guides
- Use Cases
- Glossary & Guides
- Integrations
- Developers
- Benchmark
- Windows App