Website relaunch checklist: five phases without losing rankings
A relaunch is a handover, not a new build: which addresses, content and measurement points have to move, how a redirect plan is created and which figures really count after going live.
A website relaunch checklist is not a design plan but a handover plan: it records which content, addresses and measurement points move from the old site to the new. Write it only after going live and you pay for the relaunch twice – once in design, once in lost visibility.
The process below is written for small and medium-sized companies in Germany replacing a website grown over years that want to keep their search positions. It covers sequence, ownership and measurement, not design trends. What a relaunch costs is covered in our article on the cost and running cost of a website.
Key takeaways
- The inventory comes before the design: without a complete address list with traffic figures, there is no reliable redirect plan.
- Every old address needs a destination. Unresolved addresses are the main cause of visibility loss after a move.
- Content is carried over, not trimmed: text volume, heading structure and page titles are part of the inventory.
- Technical sign-off means Core Web Vitals, accessibility, mandatory legal pages and analytics – in a staging environment blocked for search engines.
- After going live, a fixed observation window applies: 72 hours, four weeks, three months.
What belongs in a website relaunch checklist?
A reliable checklist organises the relaunch into five phases and names a verifiable result for each. Only that result decides whether the next phase may start.
The advantage of this format: at any point you can say what is finished and what is missing. A list of tips cannot, because it has no sequence.
Each phase also needs a named person inside the company who signs off. In practice the build rarely delays a relaunch; feedback on texts, images and legal details does. Scheduling those approvals in advance shortens the project more than any technical choice.
| Phase | Core task | Result |
|---|---|---|
| 1. Inventory | Export all addresses, traffic figures and queries | Address list with priorities |
| 2. Concept | Define structure, content mapping, target addresses | Redirect plan and site tree |
| 3. Build | Transfer design, content, templates, page titles | Staging with complete content |
| 4. Sign-off | Check technology, law, analytics, redirects | Sign-off record, no open items |
| 5. Go-live and monitoring | Switch over, prompt indexing, track key figures | Report after 72 hours and four weeks |
How do you relaunch without losing rankings?
A relaunch without ranking losses works when the new site fully takes over the inventory of the old one: every address, every page title, every load-bearing section of text. Losses almost never come from new design, but from quietly deleted content.
- Export the address list of the current site with organic traffic per page, sorted by traffic.
- Decide per address: keep, merge or deliberately retire – with a written reason.
- Carry over page titles, descriptions and structured data of the strongest pages unchanged.
- Compare text volume and heading structure of old and new pages before signing off staging.
- Change one thing at a time: do not combine the move with a new address structure.
The second decision is the hardest, because it concerns content nobody in the company owns any more. Demand is the only useful yardstick: a page with steady traffic from search is carried over, even if it does not fit the new design grid. Merging is fine; deleting without a successor suits only pages with no demand and no inbound links.
Google makes the same point in its guide to site moves with URL changes: plan changes one after another, move large sites in sections, and watch traffic on old and new addresses in parallel. How positions arise in the first place is explained in our article on SEO fundamentals in the right order.
How do you build a reliable redirect plan?
A redirect plan is a table mapping every old address to exactly one new address – with no blanket redirect to the home page. It is created during the concept phase, not on the day of the go-live.
Technically, the permanent redirect with status code 301 is the standard case, because it tells users and search engines the new address is final; Google describes the variants in its documentation on redirects and Google Search.
- Every redirect leads to comparable content, not to an unrelated overview page.
- Redirect chains are resolved: one hop, not three.
- The mapping is tested in staging before the switch.
- Redirects stay in place permanently, at least one year beyond the go-live.
- Pages without a successor get a helpful error page with search and entry points.
A typical example: three separate service pages become one page with three sections. All three old addresses then point to the new page, and the dissolved pages' content reappears there in full. If it is missing, the redirect is technically correct and still a loss.
Which Core Web Vitals do you check before going live?
Core Web Vitals are the three metrics Google uses to judge the experienced quality of a page: loading time of the largest element, response time to input, and layout stability. All three are measured in the field, not the lab.
| Metric | What it measures | Good value |
|---|---|---|
| LCP | Loading time of the largest visible element | up to 2.5 seconds |
| INP | Response time to user input | up to 200 milliseconds |
| CLS | Unexpected shifts in the layout | up to 0.1 |
The thresholds and their reasoning are documented by the Chrome team in defining Core Web Vitals thresholds; what counts is the 75th percentile of real page views. For sign-off that means one lab test is not enough: the values need a few weeks of field data after the go-live. Planning design and loading time together avoids rework later, which is why both belong in the redesign of your website.
What do you check legally and technically before going live?
Legal sign-off covers mandatory disclosures, accessibility and consent – three items that regularly get lost in design-driven projects. A relaunch is the cheapest moment to settle them, since templates are rebuilt anyway.
Since 2025 the German Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG) has required accessible use for many digital services; the requirement itself is set out in § 3 BFSG. Who is affected and which exemptions apply to micro-enterprises is covered in our article on the obligation to run an accessible website.
- Impressum (legal notice) and privacy policy reachable, current and linked from every page.
- Consent banner configured so analytics load only after agreement.
- Keyboard operation, contrast and alternative texts checked in all new templates.
- Forms and appointment booking tested, including confirmation emails.
- Staging set to noindex and blocked in robots.txt so no duplicate content appears.
Technical sign-off also includes the analytics setup. If counting pixels, conversion goals and the Search Console connection are only added after the go-live, the data basis is missing in exactly the critical week. The new site therefore takes over the existing measurement unchanged before extra reporting is built.
What does a relaunch mean for your website, and when is it worth it?
A relaunch means your website is rebuilt technically, structurally and in content, not merely redesigned. It is worth it when all three levels reach the end of their life at once: no more security updates, years of legacy in the navigation, content that no longer reflects what you sell.
If only one applies, partial steps are usually cheaper and carry less risk: a new home page, a reworked service page, a technology change without touching addresses. The advantage lies in the risk, not only the budget – leave the address structure untouched and there is nothing to lose. Partial steps also keep each change measurable and reversible.
We say openly when a project does not justify the effort, and we work with fixed prices; packages and typical ranges are listed on our prices and fixed-price packages page. For lasting visibility after the move, the relaunch is not the decisive factor anyway, but continuous SEO support.
How do you measure success after going live?
The success of a relaunch is measured in fixed windows, not by gut feeling. Fluctuations in the first days are normal, as long as they recede by the fourth window.
- First 72 hours: spot-check redirects, fix indexing errors in Search Console, review server-log error pages.
- First two weeks: watch coverage reports, resubmit missing pages, compare forms and goals with the previous period.
- Four weeks: compare positions for your twenty most important queries with the state before the move.
- Three months: assess Core Web Vitals in the field and sharpen the strongest pages' content.
The baseline is created before the move: positions, traffic and form completions of the most important pages are saved as a snapshot. Without it you cannot prove afterwards whether the relaunch helped or hurt.
The comparison period matters: not the previous month, but the same period a year earlier, otherwise seasonal patterns look like a relaunch effect. If an important page is still clearly behind after four weeks, the cause is usually an incomplete redirect or shortened text, not design.
Frequently asked questions about a website relaunch
How long does a website relaunch take?
For a mid-sized company with ten to thirty pages, a relaunch takes eight to twelve weeks in practice, across concept, build and sign-off. The pace is set less by technology than by the approval of texts and images inside the company.
How long do redirects have to stay in place?
Redirects stay active permanently, and at least one year beyond the go-live. Search engines need several visits before the new address fully replaces the old, and bookmarks or directory entries keep pointing to old addresses for years.
What does a website relaunch cost?
The price depends on the number of pages, the volume of content and the integrations, not on design alone. Typical ranges, running costs and cost drivers appear in our article on website costs for companies, so that this process guide can stay on procedure.
Should you change the address structure during a relaunch?
The address structure is only changed when the content gives a reason – a new way of sorting your offering, for instance. Every change creates redirects and therefore risk, so a working structure stays untouched when in doubt.
Your relaunch mit ZeuZ IT
We plan relaunches as a handover: inventory, redirect plan, sign-off record and an observation window after the go-live. If partial steps are cheaper than a full rebuild, we say so before quoting – and work with fixed prices either way.
Send us the address of your current website and the goal of the relaunch – we will reply with an assessment of the handover risk and a fixed price.