A new website can be the best thing to happen to your business, or the fastest way to lose half the organic traffic that took you years to build. The difference isn't in the design: it's in the migration, that unglamorous part that decides whether Google still knows who you are. We've migrated websites for hotels, companies and public bodies — from WordPress to Laravel, from an old domain to a new one, from an old version to a new one — and this is the checklist we use.
Before touching anything
- Complete URL inventory. A crawl of the current site (Screaming Frog or similar), plus the URLs that get traffic according to Analytics and Search Console, plus the ones with external links. There are usually far more than the ones in the menu.
- What ranks and why. The 50 pages that bring the most traffic and their keywords. Those pages can't be cheerfully "simplified" in the new design.
- Baseline. Today's traffic, rankings, Core Web Vitals and indexing. Without this you won't know whether the migration went well or badly.
- Redirect map. Every old URL pointing to its new equivalent, one by one. Not everything to the homepage: that's the most common way to lose rankings. If a page disappears with no replacement, make a conscious decision between a 410 and a redirect to the closest thing.
During development
- Keep every URL you can. If the structure works, don't change it for aesthetics. Every URL change is a redirect that dilutes a little authority.
- Migrate the content, not just the design. The copy that ranks has to stay, with its headings and its depth. "Let's make it cleaner" has sunk many a page.
- Metadata and structured data. Titles, descriptions, canonicals, hreflang if the site is multilingual, schema. Everything the old site had, the new one must have, improved.
- Images with the same name or redirected. Images rank too, and they get links too.
- Staging environment locked down. Google mustn't index the site in development: noindex and a password, and remember to remove them at launch (yes, it happens).
- Performance measured before going live. A new website that's slower than the old one is an SEO step backwards, however much prettier it is.
Launch day
- 301 redirects live and tested against the full inventory (a script that walks through every one and checks the response code).
- Remove noindex, check robots.txt and submit the new sitemap in Search Console.
- If the domain changes, use Search Console's change of address tool.
- Analytics, tags and conversions working on the new site. It gets forgotten more often than you'd think.
- Crawl the new site looking for 404s, redirect chains and internal links pointing to old URLs.
The weeks that follow
Watch Search Console daily for the first two weeks: coverage errors, pages not indexed, drops in impressions per page. A temporary 10-20% dip is normal while Google reprocesses; a sustained 50% drop is a redirect or content problem you need to hunt down. Compare against the baseline at 30, 60 and 90 days. And keep the redirects forever, not "for a year": external links don't expire.
What you can't delegate to the designer
A migration is an SEO project with a design layer, not the other way round. That's why at staycreative web development and SEO sit in the same team from day one. If you're about to rebuild your website and you're worried about the traffic you already have, let's talk before the design starts, not after.