Skip to content
SEO & visibility

New Domain for Your Website: Moving Without Losing Rankings

Changing your domain after a rebrand: redirect every URL, use the Change of Address tool, keep redirects 180 days, keep the old domain, move email and listings.

22 min read DomainwechselWeiterleitungenWebsite-RelaunchSearch Console

In short and in plain language

Some companies get a new name. Then the website often gets a new address too. This is called a domain change.

Each old page should lead to the matching new page. A redirect does this. It sends visitors and Google from the old address to the new one.

Google has a tool for this. It is called Change of Address. You use it to report the move. The redirects should stay for at least 180 days. One year or more is better.

You should keep the old domain for at least one year. Otherwise a stranger can buy it. That person then also gets mail sent to the old addresses.

The email addresses move too. The legal notice shows the new address. Then you check whether Google shows the new pages.

A new company name, a merger or a brand that is meant to carry a different name from January: at some point it becomes clear that the website needs a new address too. In Germany, 91.7 percent (Eurostat) of enterprises with ten or more employees had their own website in 2025, counted without agriculture, forestry, fishing, mining and the financial sector. Each of those addresses carries more than a home page. Google knows every single subpage, customers have bookmarks, directories and partners link to the current domain, and the team's email addresses run on it as well. Moving to a new domain name is therefore not a single click but a process with fixed stages: redirect every URL one to one, report the change of address in Google Search Console, keep the redirects in place long enough, keep paying for the old domain and move email addresses and directory listings along with it. For the redirects, Google names a minimum of 180 days (Search Console Help). This article walks through the process step by step and shows how to tell after the move whether your visibility has come along.

Key points at a glance

  • Every old URL gets a permanent server-side redirect with 301 or 308 straight to its matching page on the new domain, without a detour via the home page and without chains (Google Search Central).
  • The Change of Address tool in Search Console requires you to be an owner of both the old and the new property with the same Google account and to use properties without a path. Each variant with and without “www” is submitted separately.
  • Redirects stay active for at least 180 days, and longer while they still bring visitors from Google Search (Search Console Help). The site move guide generally recommends at least one year (Google Search Central).
  • Keep paying for the old domain for at least one year (Search Console Help). A deleted .de domain can be registered by anyone after a 30-day grace period (DENIC), and email sent to old addresses then ends up with strangers.
  • The new domain needs MX, SPF, DKIM and DMARC before the first message goes out, old mailboxes forward, and the legal notice shows the new email address (Section 5(1) No. 2 DDG). Business Profile and directories move on moving day.
  • Both sitemaps, the Performance report and the server logs show whether Google is picking up the new URLs. For small to medium-sized sites this generally takes a few weeks (Google Search Central).

What a domain change is and what it is not

This article is about changing the domain name: altname.example becomes neuname.example because the company name changes, two businesses merge or a brand is repositioned. The content stays essentially the same; only its address changes. Switching hosting providers while keeping the domain is a different case. All URLs stay the same there, and the work is about data, DNS and mailboxes; our article on switching providers without downtime covers it. Moving from HTTP to HTTPS or between an address with and without “www” is not a domain change in the Search Console sense either. Google explicitly says not to use the Change of Address tool for these cases (Search Console Help).

A domain change often coincides with a relaunch, because a new name tends to bring a new look. Google advises making such changes one after another: first move the site to the new domain, then change the layout (Google Search Central). The reason is troubleshooting. If visibility drops after a combined overhaul, it is hard to tell whether the redirects, the new structure or new copy caused it. If you plan both in one project, at least separate them in time. What can go wrong in a relaunch with changed URLs is collected in our article on relaunch mistakes.

For the move itself, Google recommends keeping the site architecture in the new location so that signals can be passed on to the new site one to one as far as possible (Search Console Help). If you rework content and URL structure at the same time, expect Google to have to relearn and reassess individual pages. For small and medium-sized sites, Google recommends moving all URLs at once rather than section by section (Google Search Central); a period with few visitors is a good time for it. Errors then have less impact, and the server has more headroom for the extra crawling.

Before buying: check the name, variants and history

Before the new domain is registered, three checks pay off. The first concerns the name itself. Company identifiers are protected as commercial designations (Section 5 MarkenG), and so are registered trademarks. A search in the register of the German Patent and Trade Mark Office and in the commercial register shows whether someone already uses the name you want in the same industry. This does not replace legal advice. It does prevent the most expensive case: a name that has to change again after the move, so the whole process has to be repeated.

The second check covers variants. Spellings with and without a hyphen, with an umlaut and in transliteration, and obvious extensions belong in the decision, because customers will type the new address from memory at first. Whether buying extra variants is worthwhile is a judgment call. If you register them, redirect them permanently to the main domain as well. What matters is that every domain is registered to the business itself and not to an agency. Our article Who owns your website? explains why.

The third check concerns the domain's history. If the domain you want was registered before, it may come with baggage. Google advises cleaning up a recently purchased domain and checking in Search Console whether there are manual actions from earlier spam problems or URL removal requests from the previous owner (Google Search Central). That is only possible once the new domain is verified in Search Console, which is one more reason to create the property well before the move. How to choose the property type and verify it with a DNS record is shown in our article on setting up Search Console.

  • Name checked against the trademark register and the commercial register
  • Spelling variants and extensions decided, all domains registered to the business
  • New domain verified in Search Console, manual actions and removal requests checked
  • Moving date set for a period with few visitors
  • One person named as responsible for redirects, Search Console and email

The URL mapping: every address gets its counterpart

The heart of the move is a list that assigns exactly one new URL to every old one. If the structure stays the same and only the domain name changes, a server-side wildcard redirect that appends the path unchanged to the new domain may be enough (Google Search Central). altname.example/leistungen/heizung/ then becomes neuname.example/leistungen/heizung/. As soon as paths change, for example because service pages are renamed or merged, you need a real mapping list, line by line.

Google names several sources for this list: the sitemaps, the server logs and the web analytics with the addresses that bring the most traffic, the links-to-your-site report in Search Console and the content management system, which often exports a complete URL list (Google Search Central). Images, PDF files and videos are often forgotten. They have addresses too, are reached via search or links and have to be migrated like all other content. A price list in PDF form that has been linked in forums for years otherwise leads to nothing but an error page after the move.

Two rules apply to the mapping. First, every redirect points to the matching target. Redirecting a large number of old URLs wholesale to the new home page confuses visitors and can be treated as a soft 404 error (Google Search Central). If an old page no longer has a counterpart, its address on the new site responds with status code 404 or 410 (Google Search Central). Second: no chains. Googlebot follows up to 10 redirects in a row (Google Search Central), but Google recommends redirecting straight to the final destination and, where that is not possible, ideally up to 3 and at most 4 hops (Google Search Central). Chains easily arise in a domain change when the old site already had redirects from an earlier relaunch. Those old rules are rewritten in the mapping to point to the new final destination.

Old URLNew URLStatusNote
altname.example/neuname.example/301Home page to home page
altname.example/leistungen/heizung/neuname.example/leistungen/heizung/301Path unchanged, wildcard rule is enough
altname.example/bad-sanierung.htmlneuname.example/leistungen/bad/301Old relaunch redirect rewritten to point straight to the final target
altname.example/kontakt/sendenneuname.example/kontakt/senden308Form target, receives data via POST
altname.example/preisliste.pdfneuname.example/downloads/preisliste.pdf301File moved along
altname.example/aktion-sommer/neuname.example/aktion-sommer/301, target 410Content dropped, no counterpart

301 or 308: which redirect goes where

For the move, Google recommends server-side permanent redirects. Status codes 301 and 308 mean that a page has permanently moved to a new location (Google Search Central). For search, both work the same way: the redirect target is understood as canonical and appears in the search results. Temporary redirects send the wrong signal for a domain change, because with them the source page stays in the results.

The difference between 301 and 308 shows up with forms and interfaces. Under the HTTP standard, a browser may, for historical reasons, change the request method from POST to GET for the subsequent request after a 301 (RFC 9110). A submitted form then arrives at the target without its content. If that is undesired, the standard names 308 as the alternative (RFC 9110). For pages, 301 remains the usual choice. Form targets, callback addresses of payment services and other endpoints that receive data via POST are redirected with 308, or the new address is entered directly at the sender.

A second property calls for care before switching on: a 301 response is heuristically cacheable (RFC 9110), so browsers may remember the redirect for a while. A wrong rule can be fixed quickly on the server but stays stuck for a while with visitors who have already seen it. That is why every rule gets tested on a staging environment before the switch. Google recommends testing individual URLs with the URL Inspection tool and large numbers with command-line tools or scripts (Google Search Central).

.htaccess of the old domain (example)
RewriteEngine On

# Individual changed paths first, straight to the final target
RewriteCond %{HTTP_HOST} ^(www\.)?altname\.example$ [NC]
RewriteRule ^bad-sanierung\.html$ https://neuname.example/leistungen/bad/ [R=301,L]

# Form target: 308 keeps the POST method
RewriteCond %{HTTP_HOST} ^(www\.)?altname\.example$ [NC]
RewriteRule ^kontakt/senden$ https://neuname.example/kontakt/senden [R=308,L]

# Everything else with the same path to the new domain
RewriteCond %{HTTP_HOST} ^(www\.)?altname\.example$ [NC]
RewriteRule ^(.*)$ https://neuname.example/$1 [R=301,L]

Where the server does not allow redirects, Google names an instant meta refresh redirect as the fallback, which Google Search treats as permanent, and JavaScript redirects only when neither is possible (Google Search Central). With your own server configuration, a domain change should not need to go that far. If the site runs on a system without access to the server configuration, that is exactly a reason to combine the move with a switch to your own web hosting.

Preparing the new domain

Before the first redirect goes live, the new site is fully ready. Every target URL carries a self-referencing canonical tag, hreflang annotations of multilingual pages point to the new addresses, and internal links are switched directly to the new URLs instead of running through redirects (Google Search Central). Add an XML sitemap with the new URLs. If you blocked the new site with robots.txt or noindex during development, decide in advance which blocks come off on moving day. Google explicitly lists content blocked by noindex or robots.txt among the common mistakes in migrations (Google Search Central).

Certificates are needed for both domains. The new domain needs HTTPS anyway. So does the old one, because bookmarks and links point to https://altname.example, and without a valid certificate visitors see a security warning before the redirect can even take effect. Certificates issued on or after March 15, 2026 may be valid for at most 200 days (CA/Browser Forum), and those issued on or after March 15, 2027 for at most 100 days (CA/Browser Forum). While the redirects run, the old domain's certificate is therefore renewed several times, and that should happen automatically. Background is in our article on shorter certificate lifetimes.

In Search Console, both domains are verified in all variants: with and without “www” and, where URL-prefix properties are involved, for HTTP and HTTPS as well (Google Search Central). Settings of the old property are carried over to the new one, such as an uploaded file for disavowing backlinks. Finally, server capacity: after a migration, Google temporarily crawls the new site more heavily than usual, because the crawling of the old site is redirected along with it (Google Search Central). For small sites this is rarely a problem; for large shops, tell the hosting provider in advance.

The Change of Address tool in Search Console

Once the redirects are active, report the move with the Change of Address tool. It tells Google about the change and helps migrate the search results from the old site to the new one. It is used after the site has been moved and the redirect has been set up (Search Console Help). You open it in the settings of the property that belongs to the old domain.

  • You are an owner of both the old and the new property and manage both with the same Google account (Search Console Help).
  • Both properties are at domain level, i.e. without a path such as /shop/. Path-level properties cannot be moved (Search Console Help).
  • The old home page redirects with a 301 to the new home page; Google also recommends 301 redirects for the canonical pages of the old site (Search Console Help).
  • The tool does not move subdomains, not even “www”. A separate change of address is submitted for every variant of the old domain, including unused ones (Search Console Help).

Before submitting, the tool runs checks. If a critical check fails, the problem has to be fixed first; non-critical checks show a warning with recommendations, and the request can still go ahead (Search Console Help). Google then forwards various signals from the old site to the new one and prefers the new site when determining canonical pages. These actions continue for a period of 180 days after the migration starts (Search Console Help). Within 180 days of submitting, the request can also be canceled (Search Console Help), for example if the new name falls through; to do so, the redirects are removed and set in the opposite direction. How to set up the property properly is explained in our article on setting up Search Console.

Two limits matter. Google does not delete the old site from its index, and old URLs can keep appearing as long as they are available and have no counterpart on the new site (Search Console Help). And moves cannot be chained: if you moved A to B, you cannot directly submit the next move from B to C. If you merge several domains, for example after a merger, move them to the shared location one at a time and wait for traffic to stabilize each time (Search Console Help).

The old name in search results

Even when the new URLs have long been indexed, after a domain name change Google will very likely still show the old URLs occasionally, for example when a query suggests that someone trusts the old address more. According to Google this is normal: as users get used to the new name, these alternate names appear less often and eventually disappear without any further action (Google Search Central).

How long redirects and the old domain stay

Google gives two statements on duration that complement each other. The help page for the Change of Address tool asks you to keep the redirects for at least 180 days, and longer if traffic from Google Search still flows through them (Search Console Help). After the 180 days, Google no longer recognizes a relationship between the old and the new site and treats the old one as an independent site, provided it still exists and can be crawled (Search Console Help). The site move guide is more explicit: keep the redirects for as long as possible, generally at least one year (Google Search Central). During that time Google can transfer all signals, including links from other sites to the old URLs.

From a user's point of view, Google says it is ideal to keep the redirects indefinitely (Google Search Central). That matches practice: business cards, brochures, vehicle lettering, QR codes on packaging and links in old forum posts do not disappear after a year. The 180 days are therefore the lower limit for the Search Console process, not the planned shutdown date. Whether a meaningful number of visitors still arrive via the old domain after a year is shown by the server logs, and they are the basis for any later decision.

For the old domain itself, Google recommends continuing to pay for it for at least one year so that third parties cannot buy it and use it for harmful purposes (Search Console Help). For a .de domain, a grace period of 30 days (DENIC) starts automatically after deletion, during which only the last holder or a person they designate can register it again. After that, anyone can register it.

What an abandoned domain takes with it

Whoever registers a domain that has become free can run a website and mailboxes on it. They then receive visitors from old links and the email still sent to old addresses, including password reset messages for accounts that still run on an old address. Before any deletion, switch every login with banks, authorities, suppliers, platforms and tools to the new domain. As a rule, keeping the old domain permanently is the cheaper solution.

Moving email addresses

In a domain change, email is the part that lingers longest, because addresses sit in other people's address books, contracts and systems. The process therefore runs on two tracks: the new domain is fully set up before the first message is sent, and the old domain keeps receiving.

For the new domain, that means MX records, SPF, DKIM and DMARC are in place before the first message goes out. Gmail requires SPF or DKIM from all senders, and anyone sending more than 5,000 messages per day (Gmail Help) to Gmail accounts needs SPF, DKIM and DMARC as well. A new domain has no sending history yet, so clean authentication from day one matters all the more. If the shop, newsletter, contact form and accounting will send under the new domain, they all belong in the SPF record. A hard limit applies there: an SPF check evaluates at most 10 mechanisms and modifiers that trigger DNS lookups, such as include, a, mx and redirect, and ends with an error beyond that (RFC 7208). How the three records work together is described in our article on SPF, DKIM and DMARC.

For the old domain, that means the MX records stay, and incoming messages to old addresses are forwarded to the new mailboxes or collected there. From moving day, replies go out from the new address so that the other side remembers it. Once the old domain sends nothing at all, you can record that in DNS: an SPF record with no permitted senders and a strict DMARC policy make it harder to misuse the old domain for forged senders.

Then there are the places where the address is printed or legally required. The legal notice must contain information that enables fast electronic contact, including the email address (Section 5(1) No. 2 DDG). The privacy policy, withdrawal notice and terms usually name it as well. Our article on the legal notice requirement summarizes what belongs in the legal notice. Signatures, letterheads, invoice templates and automatic emails from shop and forms are switched on the same date.

Directories, profiles and domain-bound services

Google recommends updating as many links as possible at the start of the migration: internal links, links from other websites, profile links on social networks and links in ad campaigns (Google Search Central). For links from other websites, it pays to prioritize by the number of visits each link brings; the old property's Search Console provides the list of linking sites. The site operators are contacted and asked to change their link to the new address.

For businesses with local customers, the Google Business Profile comes first. The website is stored there as its own field with the full URL including https, and depending on the category there are links for orders, reservations or appointments (Google Business Profile Help). All of these links still point to the old domain after the move until someone changes them. How to maintain the profile overall is covered in our article on the Google Business Profile. How the new name appears as the site name in search results is covered in our article on site name and favicon.

Services bound to the domain are easily overlooked: callback addresses of payment services, sign-ins via third-party accounts with stored return addresses, keys for maps or spam protection that only work for specific domains, consent management, security policies in the site's headers and the analytics script. Each of these keeps working at the old location and fails at the new one without it being obvious at first glance. A list that is ticked off item by item during the move test helps catch them.

  • Google Business Profile with website link and links for orders, reservations or appointments
  • Industry directories, listings with chambers and associations, review portals
  • Profiles on social networks, marketplaces and job boards
  • Running ad campaigns with their landing pages
  • Callback addresses and domain-bound keys for payment, map and form services
  • Email signatures, letterheads, invoice and quote templates
  • Printed materials, signs, vehicle lettering and QR codes at the next reprint

After the switch: measuring whether visibility comes along

The first days after the switch show whether the technology works; the following weeks show whether Google follows. For a small to medium-sized site, Google says it generally takes a few weeks for most pages to move, and longer for larger sites (Google Search Central). Fluctuations in visibility during that time are normal and settle down after a while.

In Search Console, submit both sitemaps, the one with the old URLs and the one with the new URLs. At first, none of the pages in the new sitemap is indexed, but many of the old ones are. Over time, the number of indexed pages in the old sitemap drops to zero while the new one rises accordingly (Google Search Central). Warnings about redirects in the old sitemap are expected and can be ignored. In the Performance report, the date range can be extended to the last 16 months (Google Search Central), so the comparison with the previous year remains possible. In addition, a filter on queries containing the old and the new name shows how searches for the business shift; how to separate branded from other queries is covered in our article on branded queries in Search Console.

Outside Search Console, the server logs are the most important source. On the old domain, they show how many requests still run through the redirects and where they come from. On the new one, they show which URLs unexpectedly respond with an error code. Google recommends checking the access and error logs regularly and paying attention to crawling by Googlebot (Google Search Central). Once hardly any visitors from search arrive via the old domain, the condition is met under which the tool's help page considers the 180 days sufficient. As long as visitors still arrive there, the redirects stay.

WhenTaskHow you can tell where things stand
Lead timeCheck the name, register the domain to the business, verify both properties, build the mapping listOwnership of both properties in Search Console
Before the moveTest redirects, certificates for both domains, sitemap and email records on stagingTest list without chains and without error codes
Day 0Activate redirects, submit a change of address for every variant, submit both sitemaps, update the Business ProfileSearch Console notice that the move is in progress
First weeksEvaluate error pages and redirect hits, follow up on links and directoriesServer logs and the page indexing report
Until day 180Change of address in progress, Google transfers the signals (Search Console Help)Indexed pages in the old sitemap fall toward zero
From month 12Keep the redirects, keep paying for the old domain (Search Console Help), shut down only after measuringRequests via the old domain in the server logs

Approaching the domain change with a redirect plan

A domain change affects technology, search, email and communication at once, and many mistakes only surface weeks later. In a website relaunch with a redirect plan, we record all existing addresses of your website, assign a target to each and test the redirects on a preview environment before the switch. After go-live we monitor rankings and step in if an address does not redirect correctly. For the time after that, website care monitors availability and certificates, and the work on visibility under the new name is part of search engine optimization.

This article is based on data from: Search Console Help (Change of Address tool), Google Search Central (Site moves with URL changes; Redirects and Google Search; Debugging drops in Google Search traffic), Google Business Profile Help (Edit your Business Profile), Gmail Help (Email sender guidelines), RFC 9110 (HTTP Semantics), RFC 7208 (Sender Policy Framework), CA/Browser Forum (Baseline Requirements), DENIC (Deleting a .de domain), Eurostat (Websites and functionalities by size class of enterprise, 2025), the German Digital Services Act DDG (Section 5) and the German Trade Mark Act MarkenG (Section 5). It puts the requirements into practical context and does not replace legal advice in individual cases.

Related Articles

SEO & visibility

Set up Search Console: choose and verify your property

Setting up Search Console: domain or URL-prefix property, verification by DNS, file or meta tag, roles for business and agency, sitemap and email alerts.

20 min read
SEO & visibility

Branded or not: separating queries in Search Console

Search Console's filter separates branded from non-branded queries: what it counts, when it is missing, limits, a regex cross-check and year-over-year analysis.

18 min read
SEO & visibility

Checking SEO or GEO offers: questions before hiring

How to check SEO and GEO offers: Google's questions for providers plus checks on reporting, access, contract term and AI texts, without ranking promises.

21 min read