What is website relaunch SEO?
Website relaunch SEO is the set of tasks that carries a site's search visibility across a rebuild: mapping old URLs to new ones, preserving the signals Google uses to rank each page, and checking that the new site is crawled and indexed correctly after launch.
A relaunch in German business usage covers almost any big change: a new design on the same CMS, a move from TYPO3 or Joomla to another system, a domain change after a rebrand, or merging several country sites into one. Each of these changes URLs, templates or both, and each change is a chance for Google to lose track of pages that used to rank.
The SEO work is not glamorous. Most of it is spreadsheets, redirect rules and checks on staging. But it decides whether the relaunch brings the traffic curve up or leaves the marketing team explaining a drop in the next quarterly meeting.
We treat website relaunch SEO as part of the build rather than an audit bolted on at the end. The same three developers who map the URLs also write the templates, set up the redirects on the server and sit in Search Console on launch day. That removes the classic handover gap where a consultant's redirect list sits in an inbox while the site goes live without it.
Why do rankings drop after a relaunch without website relaunch SEO?
Rankings usually drop after a relaunch because old URLs return 404 errors, redirects point to the home page instead of matching pages, content that ranked was cut or rewritten, or the new templates lost titles, internal links and structured data.
The common causes, roughly in order of how much damage they do:
- Missing redirects. Pages with rankings and backlinks disappear, and their signals go with them.
- Redirects to the wrong target. Sending every old URL to the home page or a category is treated much like a missing page.
- Content cuts. A design-led relaunch trims long service pages to short blocks, and the queries they ranked for go too.
- Changed internal linking. New navigation drops links to pages that were ranking because they were well linked.
- Lost technical signals. Titles, meta descriptions, canonicals, hreflang and schema not carried into the new templates.
- Staging leaks. A test site indexed by Google competes with the live site or triggers duplicate content.
- Slower pages. Heavier templates and scripts that fail Core Web Vitals on mobile.
Every item on this list is preventable before launch. That is the whole point of website relaunch SEO: do the boring checks early so the launch is uneventful.
When should SEO join a website relaunch project?
Website relaunch SEO should join before the new sitemap and design are signed off, ideally in the first week of the project. Once the navigation and page list are fixed, cutting or merging pages that rank becomes an expensive late change.
The first SEO deliverable is not a redirect map but a list of what must not be lost: the pages that bring organic visits, the pages with external links, and the queries each page ranks for. That list feeds straight into the information architecture. If the design team plans to merge five service pages into one, they can see which of those five bring leads and decide knowingly.
The second deliverable is a set of rules for the new URL structure: short, lowercase, hyphenated, without file endings or parameters, and stable. It is worth deciding early whether German umlauts are written as ae, oe and ue in URLs, whether language versions live in folders or on separate domains, and whether the trailing slash is used consistently. Changing any of these after launch means a second round of redirects.
Relaunch projects that bring SEO in at the end usually still launch, but the redirect map is rushed, content parity is not checked and the first month is spent fixing 404 errors reported by Search Console.
How do you build a URL inventory before a relaunch?
In website relaunch SEO, a URL inventory combines every source of old addresses into one list and marks each URL with its value: traffic, links and rankings. Crawling the live site alone is not enough, because orphaned pages, old campaign URLs and PDFs often do not show up in a crawl.
The sources we merge for a website relaunch SEO inventory:
- A full crawl of the current site, including PDFs and images that rank in image search.
- Every XML sitemap the site has ever submitted, plus old sitemaps still listed in Search Console.
- Search Console's performance report exported by page, covering as much history as Search Console keeps.
- Landing pages from your analytics tool for the same period.
- Backlink target URLs from any backlink tool you have access to.
- Server logs, where the host provides them, to catch URLs bots still request.
- Old redirects already on the server, so chains can be flattened.
After deduplication, each URL gets a status: keep as is, move to a new address, merge into another page, or retire with a 410 or 404 because it has no value. The result is usually a spreadsheet, and it becomes the single source of truth for the rest of the project.
How do you build a 301 redirect map for a website relaunch?
A redirect map pairs every old URL that has value with the single new URL that best replaces it, and the server returns a permanent redirect from one to the other. Google's documentation on site moves recommends server-side permanent redirects such as 301 or 308 and keeping them for at least a year.
Our rules for a clean map:
- One old URL, one new URL: the closest equivalent page, not the home page.
- No chains: if an old redirect already points to a URL that is changing, update it to point straight to the final target.
- Pattern rules only where patterns are clean (for example a whole blog folder), with a tested list of exceptions.
- Parameters handled explicitly, especially for shops with filter and tracking parameters.
- Retired pages without a good equivalent return 410 or 404 rather than a misleading redirect.
- Redirects configured on the server or edge, not only through a CMS plugin that may disappear in the next update.
Before launch, we run every old URL in the map against staging with the new rules in place and check that each returns one 301 to a page that returns 200. For guidance straight from the source, see Google's site move documentation.
Relaunch with a domain change: what changes for SEO?
A domain change adds one more layer to website relaunch SEO: every URL changes, and Google needs to learn that the whole site moved. Search Console's Change of Address tool exists for exactly this and should be used once the redirects are live.
According to Google's site move documentation, the Change of Address tool applies when moving from one domain or subdomain to another, for example from one .de domain to a new brand domain. It is not needed for moving from HTTP to HTTPS, switching between www and non-www, or changing paths on the same domain.
The practical sequence we follow: verify the new domain in Search Console before launch, keep the old domain verified too, launch with all redirects live, run the Change of Address tool from the old property, submit the new sitemap, and leave the old domain registered and redirecting. Letting the old domain expire is one of the most expensive mistakes after a rebrand, because both backlinks and redirects stop working at once.
German companies also often merge country domains, such as a .de, .at and .ch site, into one domain with language folders. That is a domain change for two of the three sites and a restructure for the third, so each needs its own section in the redirect map and its own check of hreflang afterwards.
Moving off TYPO3, Joomla or Jimdo without losing SEO
Each old platform leaves its own URL habits behind, and the redirect map has to handle them. The platform you leave matters more than the one you move to.
Leaving TYPO3
TYPO3 sites often carry years of redirect records, language fallbacks, mounted pages and URLs from older extensions. We export existing redirects, crawl every language tree, and flatten old chains into the new map. The TYPO3 project announced that free community support for v12 LTS ended on 30 April 2026, so many German companies on v12 or older are choosing now between an upgrade and a move; our TYPO3 vs WordPress comparison helps with that decision.
Leaving Joomla
Older Joomla sites can expose the same article under several paths, sometimes with index.php in the URL or numeric IDs, depending on how URL rewriting was configured. We collect all variants from the crawl and logs so each one redirects straight to the new page rather than through a chain.
Leaving Jimdo or another site builder
With a hosted builder you do not keep the old server, so every redirect must live on the new host. As long as the domain moves with you, that works well. We record the builder's URL patterns, blog and shop paths before the switch, because once DNS points elsewhere the old site is hard to crawl.
Leaving a page builder on WordPress
Same CMS, new theme: URLs may not change, but templates, headings and internal links do. The risk here is content and markup loss rather than 404 errors, so the parity check matters most.
Whatever the source, the new platform is chosen for the business, not for the relaunch. See our notes on TYPO3 vs WordPress and the TYPO3 developer page if staying on TYPO3 is an option.
How do you keep hreflang and structured data intact in a relaunch?
Keep them by rebuilding them into the new templates rather than hoping a plugin reproduces them, and by testing every language version and template type on staging before launch.
Hreflang breaks easily during relaunches because URLs change in every language at once. Google's documentation on localised versions says each language version must list itself and all other versions, and if two pages do not point to each other the tags are ignored. So a relaunch that updates the German URLs but forgets the return links on the English or Swiss pages quietly switches hreflang off. We generate hreflang from one mapping table so all versions update together, and add an x-default where there is a sensible fallback page.
Structured data goes the same way. The old site may have Organization, LocalBusiness, Product, Event or FAQ markup buried in a theme file. We list every schema type found in the crawl, rebuild it into the matching templates, and validate a sample of each template type before launch.
Titles, meta descriptions, canonicals, image alt text and Open Graph tags are part of the same parity check. A spreadsheet compares old and new values for the top pages, and differences are reviewed by your marketing team rather than accepted by accident.
Website relaunch SEO for staging: how should it be hidden from Google?
Protect staging with a password and add noindex; do not rely on robots.txt alone. A password-protected staging site cannot be crawled at all, and noindex is a second safety net if protection is ever switched off.
The robots.txt trap catches many relaunch teams. Google's documentation on blocking indexing explains that for noindex to work the page must not be blocked by robots.txt, because a crawler that cannot fetch the page never sees the noindex rule, and the URL can still appear in results. So a staging site with only a robots.txt disallow can still show up in search if someone links to it.
On launch day the reverse matters: noindex and password protection must come off the live site. It sounds obvious, yet a leftover noindex tag or X-Robots-Tag header is a classic cause of a site vanishing a week after relaunch. It is the first item on our launch checklist and we check the response headers, not just the page source.
We also keep staging on a separate subdomain with its own robots rules and never copy staging URLs into sitemaps, canonicals or internal links. A find-and-replace of the staging hostname is part of the go-live script.
Content and internal links: what must survive the redesign
Good website relaunch SEO means pages that rank keep their main content, their headings and roughly the same internal links, even if the design around them changes completely. A relaunch is a design and platform project; it should not be a silent content rewrite.
Designers often want shorter pages, tabs, accordions and fewer navigation links. Some of that is fine. But when a service page that ranked for a dozen queries is cut to a headline and three bullet points, those queries go. We flag every top page whose word count or heading structure drops sharply and let your team decide page by page.
Internal links need the same attention. Pages linked from the main navigation, footer or hub pages on the old site were telling Google they matter. If the new navigation drops them, add links from relevant hubs or related-content blocks so the signal continues.
A relaunch is also the right moment to fix structure deliberately: merge thin pages that compete for the same query, add a hub for a service that was scattered across posts, or build location pages properly. Done on purpose and redirected carefully, these changes improve rankings rather than risk them. Large content restructures are where our SEO website builds from US$300 fit best.
What should you check in Search Console on relaunch day?
On launch day, check that the live site is indexable, that the redirects work, that the new sitemap is submitted and that Google can fetch key pages. Most launch problems show up within hours if you know where to look.
- Response headers and page source of key templates: no noindex, correct canonicals, no staging hostnames.
- The full redirect list run against the live server: one 301 each, final targets returning 200.
- robots.txt on the new site allows crawling of everything that should rank.
- The new XML sitemap submitted in Search Console; the old sitemap kept temporarily so Google revisits old URLs and sees the redirects.
- URL Inspection on a sample of top pages, with a live test to confirm Google renders the content.
- Change of Address submitted if the domain changed.
- Analytics and consent tool firing correctly, so post-launch data is trustworthy.
- Hreflang and structured data spot-checked on live templates.
We stay online through the launch window, which is usually timed for a German weekday morning so that the rest of the working day is available for fixes.
How long does it take rankings to recover after a website relaunch?
For a well-prepared relaunch, most sites see a short dip and a return to normal within weeks; poorly redirected sites can take months or never fully recover. Google's site move documentation says a small to medium site can take a few weeks for most pages to move, and larger sites take longer.
Google also warns that rankings may fluctuate temporarily during a move. That is normal and not a reason to change things in a panic. The time to worry is when a group of pages loses traffic and stays down, or when Search Console shows old URLs as not found rather than redirected.
The speed of recovery depends on things you control: how complete the redirect map is, whether content survived, how fast the new site is, and how quickly Google recrawls. Submitting a new sitemap, keeping the old one available for a while and linking to key pages from the home page all help Google find the new addresses sooner.
What you cannot control is everything else happening in search at the same time, such as core updates or competitors relaunching. That is why website relaunch SEO compares page groups before and after, rather than judging the whole site by one total traffic number.
The 90-day website relaunch SEO monitoring plan
Monitor daily for the first two weeks, then weekly until day 90. The aim is to catch problems while they are small and while the old URLs are still fresh in Google's memory.
Days 1 to 14
Daily checks of 404 errors, redirect errors and indexing reports in Search Console, server logs where available, and organic sessions for the top 50 landing pages. Missing redirects found here are added the same day.
Weeks 3 to 6
Weekly comparison of clicks and impressions by page group against the same weeks before launch. Pages that lost visibility are checked for content, links and indexing, one by one.
Weeks 7 to 13
Core Web Vitals field data starts to reflect the new templates. We check page experience reports, crawl stats and whether old URLs have dropped out of the index in favour of new ones.
Day 90 review
A written summary for your team: what moved, what was fixed, what remains, and whether the redirects, sitemaps and old domain are set up to stay as they are.
If you want ongoing SEO after that, monthly work starts from US$150/mo; many clients simply move to a maintenance plan from US$120/mo after the two free months.
Using the website relaunch to close DSGVO and BFSG gaps
Website relaunch SEO and compliance belong together: a relaunch rebuilds every template anyway, so it is the cheapest moment to fix privacy and accessibility problems that would be expensive to retrofit. Consent handling, fonts, embeds, hosting and accessible markup all live in the templates.
On the privacy side, we build the new site so non-essential cookies and third-party scripts stay off until consent, fonts are served from your own server, maps and video load on click, and hosting sits in the EU under an AVV in your account. Your lawyer or legal-text service supplies the Impressum and privacy notice; we make sure they match what the site actually does. The full list is on our GDPR compliant website page.
On accessibility, the Barrierefreiheitsstärkungsgesetz (BFSG) has applied since 28 June 2025 to many consumer-facing digital services, including e-commerce, as set out in section 38 BFSG. Whether it applies to your company is for your lawyer to confirm, but semantic headings, keyboard navigation, form labels, contrast and alt text cost little in a new build. Details are on our BFSG website requirements guide.
These fixes also help SEO: cleaner markup, fewer third-party scripts and better headings make pages faster and easier to understand for both search engines and AI answer tools.
How much does website relaunch SEO cost in Germany?
With BtechWaleTech, a relaunch of a site up to 100 pages starts at US$150, a large site with 299+ pages at US$300, and a shop at US$750. Redirect mapping, staging protection, launch-day checks and 90 days of monitoring are included in the relaunch quote.
The main cost drivers are the size and age of the site. A 60-page company site with clean URLs needs a short map; a 4,000-URL shop with filter parameters, three languages and ten years of old redirects needs far more mapping and testing. Content migration is the other big variable: exporting structured content from a database is fast, copying text by hand from page builders is slow.
If your design agency builds the site and you only want the SEO side from us, we quote the inventory, map, checks and monitoring separately after seeing the URL count. Quotes from German agencies and freelancers for relaunch SEO vary widely; compare what is included, especially whether redirects are implemented and monitored or just delivered as a spreadsheet. For general budget ranges, see website development cost in Germany.
Running a relaunch with a team in India from Germany
Website relaunch SEO fits remote work well because most of it is planning, building on staging and testing, and only launch day needs everyone online at once. We schedule that for a German morning, which falls in our early afternoon.
Calls happen in English, usually weekly during the build and daily in launch week. Your marketing team reviews the URL inventory and content parity sheet, your German copy comes from your team or your copywriters, and we implement everything else. WhatsApp gets a reply from us seven days a week, which matters in the first weekend after launch.
Quotes are itemised in USD, and invoices come from India in USD or EUR, paid by Wise or bank wire. Nothing is billed before written approval. Domain, hosting, code and Search Console properties stay in your company's accounts throughout; we work with our own user logins that you remove when the project ends.
The first two weeks usually cover: access to Search Console and analytics, the crawl and URL inventory, a workshop on the new structure with your team, the draft redirect rules, and the staging site set up behind a password with noindex. By the end of week two you can see how much of the old site's value is accounted for.
Worked example: a Bielefeld machine builder merges two domains
Say a mid-sized machine builder near Bielefeld runs a German TYPO3 site on a .de domain and a separate English site on a .com domain, both on TYPO3 v11, and wants one bilingual site on a new stack. This is a hypothetical case to show how the website relaunch SEO steps fit together.
The inventory finds around 900 URLs across both domains, including 140 product PDFs and a set of old trade-fair pages with backlinks from industry directories. The team decides to keep product pages, merge the trade-fair pages into one events archive, and retire outdated news posts with 410.
The new site uses one .com domain with /de/ and /en/ folders. The redirect map sends each .de URL to its /de/ equivalent and each old English URL to /en/, with PDFs redirected file by file. Hreflang is generated from one table so both folders reference each other and x-default points to the English version. Staging runs behind a password with noindex throughout.
On launch morning the redirects are tested in full, the Change of Address tool is run for the .de domain, and the new sitemap is submitted. The .de domain stays registered and redirecting. Monitoring shows the expected short fluctuation; the team tracks page groups weekly until day 90 and adds redirects for a handful of old URLs that only appear in the logs.