This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung
SEO
How do I move a website so that Google and visitors can find the new pages?
A move can mean a lot: new content, a new editorial system, a new domain or a new server. Each of these changes can change addresses, and any old address that leads to the void costs visitors and placement. According to Google’s guides, this article describes how to move and what to watch afterwards.
Change one thing after another
Google advises planning changes one after another, such as changing the domain separately from changing the editorial system and a new design. So you see which change had which effect. Small and medium-sized websites move to Google best at once, large ones can move section by section.
If only the server moves, the addresses remain the same
Switch only the provider and the addresses remain, test the copy first under a provisional address, protected with noindex. About a week before, lower the validity period (TTL) of the DNS record to a few hours, and to move the DNS record to the new server. Fewer retrievals by the Googlebot immediately after the change are normal; You only switch off the old server when no visit arrives there.
For each old address, there is a destination in the list
Collect all old addresses from sitemaps, server logs, web analytics or editorial system, including those from images, videos, JavaScript and CSS files, and set the new destination for each. On the server, permanently forward, with status 301 or 308, any old address directly to its final destination. Redirecting many old addresses to an inappropriate page such as the home page can rank Google as a Soft 404. The forwardings shall remain for as long as possible, usually at least one year.
Internal links and the sitemap
Switch the internal links of the new website to the new addresses and submit the new sitemap to Search Console. Keep the list of old addresses to check after moving. You only need the tool to change the address of Search Console when changing the domain or subdomain. You only use a redirect via JavaScript if a redirect is not possible on the server.
Pages without successors answer with 404 or 410
Content that you delete or merge and for which there is no suitable new page responds with the status 404 or 410. In the Search Console page indexing report, you can see which pages Google has not found; Google recommends fixing the 404 errors that you link to yourself or that are in your sitemap. If a page has moved, redirect it to its new address.
After moving, watch old and new addresses
Expect temporary fluctuations in placement; For medium-sized websites, it may take a few weeks or more to find the new addresses. In the Search Console and in the server logs, watch both sides: the visits of the old addresses decline, the new ones rise, and an unusually high number of errors "not found" shows missing redirects. If the errors suddenly rise, a change to a template may have triggered them.
- Move content, technology, and domain in separate steps.
- Create a table with each old address and its new destination and set up permanent redirects on the server.
- After moving, check each old address from the table and see the page indexing report regularly in the weeks afterwards.
- Before starting, check the redirects with a script that calls up each old address and writes down status and destination.
- Keep the old domain and renew it as long as redirects run through it.




