Will I drop off Google if I switch?
Not for good, if the move is done carefully. What hurts is old pages vanishing: if a customer or Google follows an old link and lands on "page not found," that page's place in search goes with it.
Google's own site move guide says to expect "temporary fluctuation in site ranking during the move," and that for a medium sized site it "can take a few weeks or more" for Google to show the new addresses in place of the old ones. It also says 301 and other permanent redirects don't cause a loss in PageRank. So a dip for a few weeks is normal; a cliff that doesn't recover usually means redirects were missed.
A 301 redirect is a forwarding address for a web page. When someone, or Google, asks for the old page, the server answers "this moved for good, it's over here now" and sends them on.
Google's redirects page recommends a permanent server side redirect whenever you change a page's address, because it's the redirect Google is most likely to read correctly. A temporary redirect (302) tells Google to keep showing the old address, the opposite of what you want in a move.
Here's ours. Our site lives at mesavalleymarketing.com without the "www," but people type the www and some links will always point there, so we redirect one to the other. On October 6, 2026, https://www.mesavalleymarketing.com/ came back 301 to https://mesavalleymarketing.com/, and https://www.mesavalleymarketing.com/services came back 301 to https://mesavalleymarketing.com/services. The second check matters most: the redirect keeps the page path, so a deep link lands on that same page.
Our services page also used to end in ".html". Today https://mesavalleymarketing.com/services.html comes back with a 308, the other permanent redirect code, pointing to /services. Google treats 301 and 308 the same way: moved for good.
What do I need from my old designer before I leave?
Ask for these while you're still on good terms, and get them in writing:
- Your domain. Find out which registrar it's at and whose name is on it. If it isn't in your name, that's the first thing to fix. ICANN's FAQ on transferring your domain name explains the transfer code (also called an Auth Code or EPP code) you'll need to move it, and warns that a registrar can block a transfer within 60 days of a new registration, and for 60 days after the owner's name, organization or email changes. ICANN suggests finishing the transfer before you change your contact details.
- Logins. Hosting, the website admin, Google Search Console, Google Analytics and your Google Business Profile. You should be an owner on each one, not a guest.
- A copy of the site. Text, photos, and any forms or files customers use.
- The list of page addresses. The sitemap (often at yoursite.com/sitemap.xml) is the easiest place to start.
How do I build the redirect map?
Repeat that for every page. Make a two column list: each old address on the left, its one new home on the right.
- Pages that still exist get matched to their new version. "/plumbing.html" might become "/plumbing."
- Pages you're dropping get pointed at the closest page that's left, not all dumped on the home page.
- Don't forget the variants. Google's guide says to redirect both the www and non www versions of your old addresses, even one you don't actively use, and to verify the http and https versions in Search Console.
- Send each old address straight to its final page. Google says to avoid chains of redirects (old page to a middle page to the new page) and, if you can't, to keep them short.