Change domains without losing what you’ve already earned.

Rebranding, consolidating sites, or moving off a domain you no longer control — every one of those means every existing URL needs a correctly mapped 301 redirect, or the rankings, backlinks and bookmarks that URL earned disappear with it.

THE PROBLEM

Why do domain changes tank rankings so often?

A domain change isn’t one URL moving — it’s every URL on the site moving at once, each one needing to land somewhere specific on the new domain. Google treats a missing or wrong redirect as a dead end, not a minor inconvenience, and every ranking, backlink and bit of trust that old URL had built up simply doesn’t transfer if the path isn’t mapped correctly.

WHAT USUALLY GOES WRONG

  • Every old URL redirected to the new homepage instead of its actual equivalent page
  • Older or less obvious URLs simply forgotten, since they weren't in the main navigation
  • Redirects implemented as client-side JavaScript or meta-refresh instead of a proper server-level 301
  • Redirect chains — old URL to interim URL to final URL — that dilute the SEO value at every hop
  • Google never told about the change through Search Console's change-of-address tool
  • The old domain left to expire, breaking every redirect the moment it lapses

SIGNS YOU NEED THIS

When to plan a redirect map, not just switch DNS

Any of these means the domain change needs an SEO-aware plan, not just a technical switch.

Rebranding to a new domain name

The business name, domain, or both are changing, and the existing site already ranks for terms worth keeping.

Consolidating multiple sites into one

Merging two or more domains into a single site means mapping every URL from every source domain individually.

Leaving a domain you no longer control

A former agency, a former partner, or an expiring domain you can't renew — the migration needs to happen before that access disappears.

Restructuring URLs at the same time

If the site's folder structure or slugs are also changing, the redirect map needs to account for both changes at once, not just the domain.

SCOPE

What I deliver

  • A full crawl of every URL on the old domain, indexed or not
  • A one-to-one redirect map from every old URL to its correct new destination
  • 301 redirects implemented at the server level, not client-side JavaScript
  • Google Search Console change-of-address handling and sitemap resubmission
  • Redirect chains and loops checked and flattened before launch
  • Post-launch ranking and traffic monitoring for the first few weeks

TECHNOLOGY I USE

  • WordPress
  • Screaming Frog
  • Google Search Console
  • .htaccess / Nginx
  • Redirection plugin
  • Google Analytics
Two domain nodes connected by a labeled 301 redirect path

PROCESS

How a domain migration runs

  1. Crawl the old domain completely

    Every URL gets captured, including ones no longer linked in navigation but still holding rankings or backlinks.

  2. Build the one-to-one redirect map

    Each old URL is matched to its specific new destination — never a blanket redirect to the homepage.

  3. Implement redirects at the server level

    Proper 301s in .htaccess or Nginx config (or a redirect plugin where that's the right fit), not JavaScript or meta-refresh.

  4. Check for chains and loops

    Every redirect gets tested end to end, flattening any old-to-interim-to-final chains into a single direct hop.

  5. Launch on the new domain

    DNS, SSL and the redirect rules go live together, timed to minimize any gap where URLs might resolve incorrectly.

  6. File the change-of-address with Google

    Search Console's dedicated tool tells Google directly that this is a site move, not two unrelated domains.

  7. Resubmit sitemaps and verify indexing

    The new domain's sitemap gets submitted and checked, confirming Google is crawling and indexing it as expected.

  8. Monitor rankings and traffic afterward

    The first few weeks get watched specifically for any URL that isn't transferring cleanly, so it can be caught and fixed early.

BENEFITS

What you get out of it

A domain change is a one-shot event — there’s rarely a clean way to undo a botched migration after Google has already re-crawled it. Getting the redirect map right the first time is the entire job.

Nothing gets missed

A full crawl, not a list built from memory of what the old site's important pages were.

Rankings transfer, not just traffic

A one-to-one map preserves the specific relevance each URL had, not just a working redirect.

Someone is watching after launch

The weeks right after a migration are when problems actually surface. That's covered, not left to you to notice.

RELEVANT WORK

Projects built this way

Each of these is written up as a full case study — the problem, the approach, the stack and the outcome.

Allex

A rebuild where existing search visibility had to carry over intact, not restart from zero on the new structure.

  • WordPress
  • SEO
  • Migration

FAQ

Questions I get asked

What people ask before committing to a domain change.

Will I lose my Google rankings when I change domains?

Not if every URL is redirected correctly with a proper 301 and Google is told about the change through Search Console. Most ranking loss in a domain migration comes from missing redirects, incorrect redirect targets, or using the wrong redirect type — not from the domain change itself.

What's the difference between this and your general Migration service?

The general Migration service covers moving hosts, servers or platforms where the domain usually stays the same. This one is specifically for when the domain itself is changing, which brings its own SEO-specific requirements: a complete redirect map, a Search Console change-of-address, and backlink considerations that a same-domain host move doesn't need.

How long does Google take to fully transfer rankings to the new domain?

Google generally recognizes the migration within days to a few weeks once redirects and the change-of-address are in place, though full ranking stabilization on the new domain can take longer, particularly for competitive terms. This timeline is set by Google's own re-crawling schedule, not by the technical work itself.

Do I need to redirect every single URL, even old blog posts?

Yes, ideally. Any URL with backlinks, direct traffic, or search rankings loses that value if it 404s instead of redirecting, even if it looks unimportant now. The redirect map is built from a full crawl specifically so nothing gets missed by assuming a page doesn't matter.

Can I just redirect the whole old domain to the new homepage?

That's the single most common way a domain migration destroys rankings. A blanket redirect to the homepage tells Google every old page is now the homepage, which it isn't, and it discards the specific relevance each old URL had built up individually.

What if my URL structure is also changing, not just the domain?

That's the normal case, not an edge case — most domain changes come with some restructuring. The redirect map accounts for both at once: old domain and old path both map to their correct new destination, which is exactly why a one-to-one map matters more than a simple domain swap rule.

Should I keep the old domain registered after the migration?

Yes, for at least a year, ideally longer. If the old domain lapses, its redirects stop working the moment it's re-registered by someone else, and any traffic or link value still flowing through it is lost for good.

Available for new projects

NEXT STEP

Tell me both domains, and I’ll map the move.

Based in Bangladesh, working with clients worldwide. Share the old and new domain (or structure) and your timeline — every serious enquiry gets a reply within one working day.

  • Reply within one working day
  • Fixed quote before work starts
  • UK, EU and US hours covered