Website operations
A Small Business Website Migration Checklist
Move a business website without losing important pages, contact routes, or the context people and search engines use.
A website move is rarely just a design project. The old site may contain URLs linked from search results, business profiles, email signatures, customer bookmarks, and paid campaigns. It may also contain a form that quietly sends valuable inquiries to one person’s inbox. A good migration plan accounts for those connections before the new homepage goes live.
This checklist is for a small business moving to a new builder, host, or domain. It is a planning guide, not a promise that search traffic will stay unchanged. Google’s site move documentation notes that visibility can fluctuate while a move is processed.
1. Make an inventory of what exists
Export a list of current URLs, including service pages, articles, contact pages, and files people download. Add the page title, business purpose, and whether it still receives inquiries or useful visits. Search Console, the current CMS, and your own navigation can each reveal pages the others miss.
Also write down the non-page pieces: domain registrar, DNS access, email service, forms, booking tools, analytics, privacy notices, and who owns each login. A new visual design will not compensate for a lost mailbox or a form that stops sending messages.
2. Decide where every important URL goes
For each old URL, choose the closest relevant new page. Do not send every retired article to the homepage merely because it is easy. If a service is discontinued, a useful replacement page or clear explanation may be better. Keep a spreadsheet with old URL, new URL, content owner, redirect status, and test result.
Google recommends creating a URL mapping before implementing redirects, then updating internal links and the new sitemap. Its migration guidance also recommends keeping permanent redirects for as long as possible, generally at least a year. A move between builders is an occasion to simplify duplicate or outdated pages, but preserve useful paths that customers already rely on.
3. Rebuild the important tasks, not just the appearance
Test the journey from a service page to a completed inquiry. Check form recipients, confirmation messages, phone links, booking calendars, and any payment or checkout flow. Assign a person to verify every critical path on a phone and desktop.
Create a small acceptance list: a visitor can understand the offer, reach the right service page, submit a request, and receive a clear next step. The new site should also contain accurate business details and a working route for privacy or correction requests where relevant.
4. Prepare the technical switch
Before changing DNS or publishing the new site, confirm the preferred domain, SSL certificate, canonical URLs, redirect rules, robots settings, and sitemap. Make sure a staging site’s noindex setting is not copied onto the production site. The Google Search developer guide recommends checking how Google sees important pages with its URL inspection tools.
Do not schedule the cutover at a time when nobody can fix a broken form or domain setting. Keep a copy of the old content and a clear rollback plan. If a contractor is doing the move, agree in advance who controls the domain and who will maintain redirects afterward.
5. Test immediately after launch
Open the new homepage, every key service page, the contact route, and a sample of old URLs. Confirm old URLs reach the intended new page. Check for loops, chains, missing images, mobile layout issues, and forms that appear successful but send nothing.
Update links you control: navigation, business profiles, social profiles, email signatures, and advertising destinations. Submit the new sitemap through Search Console and monitor indexing and errors. A sitemap helps discovery but does not guarantee crawling or indexing.
6. Monitor the weeks after launch
Keep a short daily check for the first week, then review at a sensible interval. Look at inquiries, broken links, form delivery, key page traffic, and Search Console issues. Compare the same business outcome before and after the move; a ranking chart alone will not tell you whether customers can reach the company.
If something drops, start with specific pages and tasks. Did an old URL lose its redirect? Is the replacement page missing important information? Did a form recipient change? Fix observed problems rather than making broad changes to the whole site at once.
The goal is continuity for people as well as for search systems. Our homepage content guide can help you rewrite the new entrance page, while the builder test plan helps evaluate the platform before migration.