Website Migration Checklist for a Small Business

A website migration is a change of addresses. Sometimes the domain changes. Sometimes HTTP becomes HTTPS. Sometimes every path changes because the new site has a cleaner structure. The design can be excellent and the business can still go quiet if the old URLs, the ones already printed and already indexed, lead nowhere useful.

Google's guide to moving a site with URL changes is the document this checklist follows. It says a significant move can bring temporary ranking fluctuation while Google recrawls, that a medium-sized site can take a few weeks or more before new URLs replace old ones in results, and that larger sites take longer. It also says 301 and other permanent redirects do not cause a loss in PageRank. The fear that "redirects throw away SEO" is not what that page says. The fear that a sloppy redirect map throws away customers is justified.

If you are still deciding whether to move, read signs you need a new website before you buy a new coat of paint. If you are buying the project, the line items are in the redesign cost breakdown. The service is website redesign. A first site, rather than a replacement, starts at website development.

Change one thing when you can

Google's best-practice list says to change one major thing at a time when that is possible. A new domain, a new CMS, and a new layout in the same cutover give you three explanations for every lost visit. If you can move the URLs first and change the design after, or the reverse, the next week is easier to debug. Small businesses often cannot split the work that cleanly because the old host is the thing being replaced. When the moves have to travel together, write down what changed so you are not guessing in Search Console a month later.

Time the cutover for a quieter day if your week has one. A Friday night launch with nobody watching the form on Saturday is how a broken redirect lives all weekend. Google also suggests moving during a traffic dip when you have one, so fewer customers meet the rough edge and the server has room for the extra crawl.

Make the map before you make the design

List the URLs that already matter. Google suggests starting with the sitemap, the server log or analytics, Search Console links, and the CMS. Include images and files, not only HTML. A PDF that other sites link to is still a URL.

For each old URL, name the new one. The best match is the page that now answers the same need. Google says not to send many unrelated old URLs to the new homepage. That pattern confuses people and can be treated as a soft 404. If you merged three old service pages into one new page on purpose, those three can point at the merged page. If you deleted a service you no longer sell, a 404 or 410 is an honest answer. Do not redirect it to a page about a different service just to "save the link."

A Dallas firm and a law practice feel this more than a brand-new company does, because the old URLs may already be how clients and referring sites arrive. The city page is how we describe remote work in that market. It is not a CodeHunterz office on a Dallas street, and the redirect map should not invent locations either.

Redirects, canonicals, and the noindex you used in staging

Use a server-side permanent redirect, 301 or 308, from the old URL to the final new URL. Google says it can follow a chain of up to 10 hops and still recommends you avoid chains, ideally no more than three and fewer than five. Point at the destination. Do not point the old page at a temporary URL that points at the new one.

Every new URL should carry a self-referencing canonical once it is the page you want indexed. Update internal links so the new site does not depend on the redirects for its own navigation. Redirects are for the outside world and for bookmarks. Your menus should use the new paths.

Staging sites are often discouraged with noindex or a robots.txt disallow. Google's troubleshooting section names this as a common way to launch a site that will not be indexed. Remove those rules on the URLs you want found. Confirm the live response, not the setting you think the plugin saved. The technical SEO checklist is the tag-by-tag version. The free website audit will fetch one new URL and show the status, the redirect hops, the canonical, and a noindex tag or header if they are on that response. Run it on the homepage and on one old URL you expect to redirect. It will not crawl the whole map. A large map still needs a list and a spot check, or a crawler you run yourself.

Search Console, sitemaps, and what not to file

Verify the properties you actually have, including the www and non-www hostnames and both schemes if they answer. Google says Change of Address is for a move from one domain or subdomain to another. You do not need it when you only switch HTTP to HTTPS, only switch www, or only change paths on the same host.

Submit a sitemap of the new URLs. You can remove the old sitemap once the new one is the list you want crawled. Google notes that Search Console may warn that old sitemap URLs redirect. That warning is expected during a move.

Keep the redirects up for a long time. The documentation says generally at least one year, so that recrawls and links from other sites can be reassigned. Customers do not expire on that anniversary. A redirect that still works in year three is a favor to anyone who saved the old address. Update your own ads, the Google Business Profile website field, and the social profiles so the highest-traffic clicks skip the hop.

Expect the reports to look worse before they look normal. Index coverage on the old host should fall and the new host should rise. Queries should start showing the new URLs. A spike in not-found errors means the map is wrong, not that "SEO is volatile." Open those URLs.

The checks that are not about Google

Call the number on the new page. Submit the form and confirm a named inbox received it. Read the hours against the door and the profile. A migration that preserves rankings and loses the lead path is a failed project. What a small business site needs is the feature list. Next.js and WordPress is the stack conversation if the move is also a platform change. Do that choice before launch week, not during it.

Watch the host. Google says it crawls more heavily after a move because requests to the old URLs are redirected onto the new server in addition to the new crawl. A small site on a small plan can fall over on a day that should have been a celebration. Tell the host if the site is large enough that this is a real risk. Most local sites are not. The ones with thousands of URLs are.

Price the map, not a mood

A redesign quote that says "SEO included" and does not list the redirect map is a quote that skipped the migration. The website cost guide is the public range for the build. It is not an invoice. The CodeHunterz Website plan starts at $6,000 one time after a 20% launch offer (regular starting price $7,500). The written quote names the pages and the redirects. Limited-time launch offer, final quote after free strategy call.

If you are mid-move and the important old URL does not land, run it through the checker and book a call with the result. We would rather fix a hop than explain a ranking chart.