A relaunch doesn't start with colors or animations. It starts with the question of which business task the new website should fulfill better. Clarifying that task before design avoids later loops and decisions made by taste.
1. What should work better after the relaunch?
“Looking more modern” is too vague. A reliable goal describes a behavior: prospects should find a suitable service faster, request appointments, compare products, or gain trust in a complex decision.
2. Who is the most important user journey designed for?
Several audiences are normal. Still, every central page needs a clear priority. A new customer needs different information than an existing customer, an applicant, or a cooperation partner. These paths shouldn't compete for attention in the same navigation.
3. Which offers deserve their own pages?
A single services overview rarely suffices when offers solve different problems. Separate pages create room for benefit, process, prerequisites, frequently asked questions, and a fitting next step. At the same time, more precise entry pages emerge for search engines.
4. Which content can be carried over?
Existing texts and images shouldn't be migrated automatically. Check which content is current, substantiated, and useful for decisions. Outdated service descriptions or arbitrary stock images don't get better through a new layout.
5. Who delivers and decides?
A realistic process names early on who approves texts, sources images, reviews legal content, and provides technical access. Without these responsibilities, development later waits for material that is supposedly “just missing quickly.”
6. Which technology is actually needed?
CMS, shop, forms, newsletter, appointment booking, and analytics should follow from the usage scenario. More systems increase maintenance, privacy effort, and sources of error. The right architecture is the smallest one that reliably supports the planned operation.
7. What must not get lost in the move?
Existing URLs, redirects, metadata, forms, and measurement points belong on a migration list. Especially for an already visible website, an unprepared switch can damage rankings, links, and incoming inquiries.
8. How will success be judged?
Before launch, define a few verifiable signals: qualified inquiries, completed bookings, use of key pages, or technical stability. That way you can improve in a targeted way after publication instead of treating the website as simply finished.
A good relaunch concept doesn't reduce design. It creates the framework in which design can solve a clear task.
Structured preparation doesn't spare you every change. But it makes sure changes come from new insights and not from unresolved foundations.