How do you handle redirects after a domain change?
Redirect path for path rather than pointing the whole old domain at the new homepage, which discards everything. Keep the old domain registered indefinitely on auto-renew, because the redirect only works while you pay for it, and make sure it holds a valid certificate or visitors see a warning first.
Redirect at the URL level, not the domain level
The common shortcut is to point the whole old domain at the new homepage. It is one setting and it takes thirty seconds, and it discards everything.
What is needed instead is a rule that preserves the path:
old-domain.com/services/plumbing -> new-domain.com/services/plumbing
If the URL structure also changed, you need an explicit map, not a pattern. Build it from a crawl of the old site, ordered by traffic, and write real destinations for the pages that mattered.
Keep the old domain registered
This is the part businesses let slip. The redirect only works while the domain is registered and the DNS points somewhere you control.
Set it to auto-renew, keep the registrar account details somewhere the business — not an individual — controls, and treat it as a permanent cost. Letting a former domain expire hands your inbound links and any direct traffic to whoever registers it next, and that has gone badly for businesses before.
Check both the redirect and the certificate
A domain redirect over HTTPS needs a valid certificate on the old domain. Without one the visitor sees a security warning before the redirect ever fires, which is worse than a 404.
Test all four variants explicitly:
for u in http://old.com https://old.com http://www.old.com https://www.old.com; do
echo "$u -> $(curl -sIL -o /dev/null -w '%{http_code} %{url_effective}' $u)"
done
All four should land on the same final HTTPS destination, in as few hops as possible.
Update what you control
Redirects handle links you cannot change. Everything you can change should be changed:
- Google Business Profile and every directory listing
- Social profiles
- Email signatures and templates
- Supplier and partner sites — ask
- Any printed material still in circulation
For a Sugar Land business with local partnerships and association memberships, asking a handful of organisations to update a link is usually a quick win and worth more than any technical adjustment.
Handle Search Console properly
Use the change of address tool, keep both properties verified, and expect a period of instability. Do not remove the old property — its historic data is how you will diagnose anything that goes wrong.
Do not stack a rebuild on top
Changing the domain and redesigning the site in the same release makes every subsequent problem ambiguous. If both must happen, separate them by a month so you can attribute what changed.
What to expect
Some ranking movement is normal and usually settles within a few weeks to a few months. What is not normal is a sustained drop, and the usual cause is a mapping that silently sends most old URLs to the homepage.
Frequently asked questions
Can I just point the old domain at the new homepage?
You can, and it takes thirty seconds, but it discards every old URL's value and sends every visitor to the wrong place. Redirect path-for-path, with an explicit map where the structure also changed.
How long do I need to keep the old domain?
Indefinitely. The redirect only works while the domain is registered and its DNS points somewhere you control. Set auto-renew and keep the registrar account under the business's control, not an individual's.
Why does the certificate matter on the old domain?
An HTTPS redirect needs a valid certificate on the old domain. Without one the visitor gets a security warning before the redirect fires, which is worse than a plain 404.
Should I redesign at the same time?
No. Changing the domain and the site together makes every later problem ambiguous. Separate the two releases by about a month so you can attribute what changed.
How much ranking movement is normal?
Some movement is expected and usually settles within a few weeks to a few months. A sustained drop is not normal, and the usual cause is a mapping that quietly sends most old URLs to the homepage.