Ulric
Book a call

Eugene, Oregon · one person, whole builds

Insights

Moving an agent's website to a new domain without losing a lead

Moving an agent's website to a new domain without losing a lead

On the night of November 10, 2026, Lauren Rose Homes moved its website to a new domain to match the name. A move like that worries an agent for good reason. The old address is on business cards, yard signs, years of emails and every search result that sends her buyers. If the move goes wrong, the phone goes quiet and nobody says why. This is how I moved it, and the part of the job that is still open.

Move the name, not the site

The safest site move is one where nothing moves. Lauren's site stayed on the same server, with the same databases and the same build. Before the night, I pointed the new domain at that same site and tested it in place, so both names reached the same pages and the old one was still in charge.

The switch itself was a single small file. When the file exists, every request to the old name is redirected to the same page on the new one, with the path and any search terms kept, so an old link to a particular home or a saved search still lands where it should. Deleting the file turns the redirects off at once. I wanted an undo that took seconds and moved no data, because the worst time to discover a problem is after you have copied a database somewhere new.

Three panels. Before the flip: both names live with the old one in charge, one server, one set of databases, one build, the new domain tested in place, 118 tables counted. The flip: a flag file appears, the old name redirects to the new one with path and query kept, temporary redirects first, 118 tables counted again with no row lost. The undo: delete the flag file, redirects stop at once, the old name answers again, no data to move back.
Nothing was copied. One small file decided which name answered.

I counted every table in the database before the flip and again after it: 118 tables both times, with no row lost. It is a dull check and it is the one I would least like to skip.

What else knows your old name

The redirect is one line of configuration. The list of things that remember the old name is long, and most of it is invisible until it breaks.

  • Sign-ins. Browser cookies belong to a domain, so everyone, Lauren included, signed in again on the new one.
  • The spam check and the sign-in buttons. The challenge that keeps bots off her forms and the "sign in with" callbacks each have a list of allowed hostnames. Both needed the new name added before the flip, or every form would have failed politely.
  • The site's own assistant. Rosie answers buyers' questions from a knowledge base, and 11 of its entries carried links to the old domain. They were rewritten so the assistant does not send people through a redirect.
  • The edge. The new domain needed the same Cloudflare settings as the old one, rule for rule.
  • The back office. Lauren's office was meant to live on its own subdomain of the new name, but the certificate for it never issued. Rather than wait, I moved the office to a path on the main domain, where the certificate already worked.
  • Measurement. A Search Console property covering the whole new domain, and analytics for it, so the first days of traffic were counted from the start.

Why the redirects are still temporary

Google's guide to site moves with URL changes recommends permanent redirects, and it is clear that they do not cost a site its standing. It also says to keep them in place for "generally at least 1 year", and to expect rankings to wobble for a while as Google recrawls. Google updated that guide on June 17, 2026, according to its documentation change log, to say the Change of Address tool should be used for every variant of a domain, with and without www.

Lauren's old domain still answers with temporary redirects today. That is deliberate. A temporary redirect tells search engines the move might not stick, which is exactly true for the first few days of a rebrand: if something had gone wrong, I could delete the flag file and the old domain would carry on as if nothing had happened. Once the new name has run cleanly, the redirects become permanent.

There is a second reason the redirects carry the path and the query string as well as the domain. Lauren's listing pages and saved searches are shared by text message and email, and buyers come back to them weeks later. A redirect that dropped everyone on the new home page would technically work and would still lose the buyer who wanted one particular house. So the old name, with and without www, sends every request to the same address on the new one: the same listing, the same filters, the same page of results. A check of the home page alone proves almost nothing about a site whose value sits three clicks deep, so the deep pages are the ones I test.

The order matters, because Google's Change of Address help page asks for a 301 redirect from the old home page to the new one, and the tool itself checks a few pages for 301s before it will accept the move. Submitting it now would only fail. So the list waits on that one switch.

Two columns. Done on the night, November 10 and 11: temporary redirects with path and query kept, spam check and sign-in callbacks moved, links inside the site's assistant rewritten, edge settings matched, Search Console and analytics set up, back office moved to a path. Still to do, after clean days on the new name: switch the redirects to permanent, Google's Change of Address tool, Bing's site move tool, business profile, listing portals and social links, webhooks that call the old name, the mailbox rename.
Google's Change of Address tool looks for permanent redirects, so it waits for them.

The list that is still open

I would rather publish this with the list visible than pretend a domain move finishes in a night. Still to do:

  1. Switch the redirects to permanent.
  2. Submit Google's Change of Address for each variant of the old domain, and Bing's site move.
  3. Update her Google Business Profile, her listing portal profiles and her Instagram link.
  4. Repoint any webhooks that still call the old name.
  5. Rename the mailbox to match the new domain.

None of these is hard. Each one, missed, quietly leaks a little of what the old name had earned, and that is why they are written down.

If you are changing your name

  • Keep the site where it is. Point the new name at it first and test it before you switch anything.
  • Make the switch a single thing you can undo in seconds, and count your data on both sides of it.
  • Find everything with your old hostname in it: form protection, sign-in buttons, chat answers, email templates, webhooks.
  • Start with temporary redirects, then go permanent once the new name has run cleanly, and keep the redirects for at least a year.
  • Do the search engine paperwork after the permanent redirects, not before.

The site behind all this is the Lauren Rose Homes case study, and the edge caching that came next is covered in edge caching a site on shared hosting. For now, a request to the old domain still comes back as a 302, landing on the same page under the new name with every search term intact.

Common questions

Should I use a 301 or a 302 when I change domains?

Google recommends permanent (301) redirects for a site move. I start with temporary redirects for a few days so the move can be undone, then switch to permanent.

How long should I keep the old domain redirecting?

Google's site move guide says generally at least a year. Keep the old domain registered for longer than that.

When should I use Google's Change of Address tool?

After the permanent redirects are in place, since the tool checks for 301s. Google now asks for it to be submitted for every variant of the old domain.

Will my clients have to sign in again?

Yes. Sign-ins are tied to the domain, so everyone signs in again once on the new name.

Related

← All insights