Development

Website Relaunch in Days, Not Months: How It Really Works

11 June 2026Zensations

A relaunch rarely fails due to technology. It fails due to unclear goals, missing content, and too many rounds of approval.

Decide What to Remove First

Most websites carry content that no one reads. An analysis of page views quickly reveals which twenty percent of pages generate almost all traffic. Everything else is consolidated, updated, or removed.

Making this decision before the project starts significantly shortens implementation, as fewer pages need to be designed, written, and reviewed.

Content Before Design

If texts are created only at the end, the entire timeline shifts. Therefore, work with finalised content for the ten most important pages before the layout is finalised. Language models assist with drafting, while expert review remains with the team.

A Proven Process

Here is a realistic timeline:

Day 1 to 3: Goals, Structure, and Content Inventory
Day 4 to 8: Designing Core Templates
Day 9 to 15: Implementation, Content, and Redirects
Day 16 to 20: Tests for Speed, Accessibility, and Forms

Do Not Forget Redirects

Every old address needs a target. Missing redirects cost rankings and lead to error pages in newsletters and advertisements. Create the list early and test it automatically before launch.

Our case studies demonstrate how we implement projects of this kind.

Speed comes from decisions, not from more people on the project.

Why are clear goal definitions so crucial for relaunch success?

Clear goals define the benchmark for success and guide all decisions. Without them, the project team gets bogged down, features are arbitrarily added, and focus is lost. A clear goal like "increase online enquiries by 20% within six months" enables measurable results and a targeted implementation guided by key performance indicators.

A typical scenario: a company simply wants "a more modern website". What does that specifically mean? More traffic? Higher conversion rates? Better usability for a specific target audience? If these questions remain unanswered, the project quickly becomes a bottomless pit. Every stakeholder has a different idea of "modern", and the result is often a compromise that satisfies no one. At Zensations, we start every project with a workshop where we collectively define concrete, measurable goals. For example: a real estate agent from Vienna wanted to increase their online visibility. Instead of just "more modern", we defined the goal as: "increase leads for new build projects in Vienna by 15% within three months of launch through an improved content strategy and mobile performance". This clear goal influenced the choice of technologies, content prioritisation, and design.

What types of goals are relevant for a website relaunch?

Goals can be divided into three main categories: Marketing Goals, Usage Goals, and Technical Goals. Marketing goals include lead generation, sales increases, or brand awareness. Usage goals focus on user experience, such as improved dwell time or lower bounce rates. Technical goals concern performance, scalability, or accessibility. A successful strategy considers all three areas.

It is crucial to quantify these goals to measure their success later. An example of a marketing goal would be "increase newsletter sign-ups by 25%". A usage goal could be "reduce clicks to the contact form from five to three". Technically, one might define: "improve Largest Contentful Paint (LCP) to under 2.5 seconds on mobile devices". This specificity helps to define the project scope and set priorities. A Salzburg tourism association wanted to boost its booking numbers. Instead of focusing solely on design, we identified the goal of optimising the mobile booking process to increase the conversion rate from 1.5% to 2.2%. This required a deep analysis of existing user data and a targeted redesign of critical steps.

Checklist: Define Goals for Your Relaunch

What should the website achieve after the relaunch (business benefit)?
Which key performance indicators (KPIs) will be used to measure success?
Who is the primary target audience and what are their needs?
Which problems of the old website should be solved?
Are there technical requirements (e.g. integration with CRM system)?
Is there an upper limit for budget and timeframe?
Who is responsible for the final approval of the goals?

Content Inventory: How Content Can Truly Shorten the Timeline

A content inventory is more than just a list of old pages. It is a strategic clean-up and realignment. Many companies carry old, irrelevant, or outdated content for years, which only bloats the project. By consistently reducing to core content that offers genuine user value and serves business goals, the time spent on design, copywriting, and quality assurance can be drastically cut. A clear focus on the top 20% of content that generates 80% of traffic is often key here.

Imagine your current website has 500 pages. Re-evaluating, designing, and populating every single page for a relaunch is an enormous effort. The content inventory begins with data-driven analysis: Which pages are actually visited? Where does the traffic come from? Which pages convert best? An industrial machinery manufacturer from Upper Austria had over 1,000 product pages, many for long-discontinued models. Through a detailed analysis of Google Analytics data, we found that only about 150 pages generated relevant traffic and enquiries. The rest was either archived, consolidated, or deleted. This reduced the project scope by over 80% and allowed a focus on the truly important content. This significantly cut both the project duration and costs.

What steps does an efficient content inventory involve?

An efficient content inventory includes six steps: identification of all existing content, analysis of its performance (traffic, conversions), evaluation of its relevance and currency, decision-making (keep, revise, archive, delete), definition of the new information architecture, and finally, content creation or migration. An early decision on content prevents subsequent revisions and delays.

The first step is to create a complete list of all URLs, documents, and media assets. Tools like Screaming Frog or sitemap generators are useful here. This is followed by an analysis of performance data: How many page views did each page have in the last 12 months? What is its bounce rate? How long do users stay on this page? Then, you evaluate each page for relevance to your goals, currency, quality, and redundancy. Has a page had no visitors for two years but causes maintenance effort? Get rid of it. Is the content outdated or incorrect? Update it. Are there three pages covering the same topic? Consolidate them. A craft business from Vorarlberg discovered during its inventory that many pages contained duplicate information or referred to outdated offers. By systematically cleaning up, they were able to reduce their website from over 120 to 45 pages, which significantly improved clarity for users and maintainability for the team. This accelerated the entire relaunch process considerably.

Table: Content Decision Matrix

Criterion	Action	Description
High Traffic, High Relevance	Keep & Optimise	Important pages to be kept current or improved.
Low Traffic, High Relevance	Revise & Increase Visibility	Valuable content that is not being found. SEO optimisation.
High Traffic, Low Relevance	Review & Potentially Redirect/Delete	Often outdated news that still has links. Redirect to relevant pages.
Low Traffic, Low Relevance	Delete & Redirect	Content without value. Definitely set up redirects.

Why are Redirects so Important and How Do You Plan Them Effectively?

Redirects are the invisible backbone of a relaunch. They ensure that old links do not lead to dead ends and that users and search engines always find the desired content. Without correct redirects, valuable SEO rankings are lost, existing bookmarks become unusable, and customers land on error pages. Carefully planned redirect management protects your traffic and the user experience you have built up over years.

Imagine you have invested a lot of effort into your search engine ranking over the years. Every old URL has accumulated a certain "link power". If these URLs lead to dead ends (404 errors) after the relaunch, this link power is lost. This can lead to a massive drop in search engine visibility. Moreover, it is frustrating for users who access your website via old bookmarks, emails, or social media posts and then see an error page. A Salzburg hotel neglected this in a previous relaunch. The result was a 30% drop in direct bookings via the website in the first two months after launch. At Zensations, for every relaunch project, we create a comprehensive redirect list, which begins during the content inventory and is continuously maintained. We use automated tools to crawl old URLs and map them to the new ones.

What types of redirects are there and when are they used?

The most common redirect is the 301 redirect ("Moved Permanently"). It signals to search engines that a page has permanently moved and that link power should be transferred to the new page. A 302 redirect ("Found") is used for temporary redirects when content is only moved temporarily. For relaunches, the 301 redirect is the standard choice to avoid SEO disadvantages.

A 301 redirect is crucial for transferring "link juice" from the old to the new URL. This means the authority and ranking of the old page are passed on to the new page as much as possible. Using a 302 redirect for a relaunch is incorrect in most cases and can lead search engines to continue viewing the old URL as the primary one. For example: a Graz online shop restructured its product categories during a relaunch. All URLs of the old categories were redirected via 301 redirects to the corresponding new categories. As a result, the shop retained its good rankings for important category keywords and did not lose valuable traffic from Google. Detailed mapping of old to new URLs is essential and should not be done only at the end of the project, but already during the structure planning.

Checklist: Successfully Manage Redirects

Create a complete list of all old URLs.
Create a mapping from each old URL to its new target URL (1:1 or 1:n).
Use 301 redirects for permanent moves.
Implement redirects server-side (Apache .htaccess, Nginx).
Test all redirects before and after launch automatically.
Monitor Google Search Console for 404 errors after launch.
Remember internal links: update them to the new URLs.

Content-First Approach: How Content Drives Design

The content-first approach reverses the traditional order, prioritising content before design. Instead of filling empty layouts with placeholder text, designers work with real content. This avoids later adjustments and compromises that often "break" the design or impair readability. Real content allows designers to create layouts that present text optimally and convey the message effectively, rather than just looking good.

Often, a relaunch begins with a web designer creating beautiful layouts filled with "Lorem ipsum". When the actual texts are delivered, they rarely fit into the designated areas. Sections are too long, too short, images are missing, or are superfluous. This leads to costly adjustment loops that blow the timeline and increase costs. With a content-first approach, the most important content for the core pages (e.g. homepage, about us, services, contact) is created first and approved by the client. These texts then form the basis for the design. A Carinthian service provider, who needed a new website, provided us with the finalised texts for its three main services and the homepage. Our UI/UX team could then develop precise design modules that perfectly showcased the content. The result was a website whose design optimally supported the content and required no subsequent adjustments. This shortened the design phase by almost 25%.

What role do language models play in content creation and optimisation?

Language models like ChatGPT can provide valuable support in a content-first approach. They help create drafts, revise existing texts, get straight to the point, or adapt them for specific target audiences. They significantly speed up the process by providing the first version or variations of texts, which are then reviewed and finalised by the expert team. The expert knowledge remains irreplaceable.

AI-powered tools can accelerate initial text creation manifold. For example, a language model can generate a draft for an "About Us" page within minutes, based on key company information. Or it can break down a long, complex text into several shorter, more digestible sections. The internal team thus saves time on the rough draft and can focus on refining, ensuring factual accuracy, and maintaining brand tone. At Zensations, we use internal prompt systems to ensure the consistency and quality of our texts before they are reviewed and refined by human editors. This allows us to produce high-quality content faster and more efficiently, which in turn saves our clients time and budget. You can find more about this in our article on Prompt Systems Instead of Prompt Collections.

Advantages of the Content-First Approach

Efficiency: Reduces rework and saves time in design and development phases.
Focus: Ensures the website serves business goals and user needs.
Quality: Enables tailored designs that optimally present content.
Clarity: Avoids misunderstandings between content creators and designers.
Search Engine Optimisation: Content can be SEO-optimised from the outset.

Accessibility from the Start: Not Just a Duty, But a Mark of Quality

Accessibility is not a luxury but a necessity and is increasingly becoming a legal obligation, especially with the European Accessibility Act. When accessibility is integrated into the relaunch process from the outset, costly rework is avoided, and the website is opened to a wider audience. An accessible website is easier for all users to operate and improves overall quality and user-friendliness. It is a mark of quality that pays off.

Many companies view accessibility as an additional item on the checklist, ticked off only at the very end of the project. This is a mistake. If barriers are only discovered after design and development are complete, changes are often complex and expensive. An incorrect colour contrast, a missing keyboard navigation, or insufficient alt text for images can impair the entire structure. The WCAG (Web Content Accessibility Guidelines) are the international standard. In Austria, there are also specific requirements that apply to public bodies and, from June 2025, also to many private companies. A large financial institution from Vienna integrated accessibility from the beginning into its relaunch. Every design element and interaction was checked for conformity before implementation. The result was not only a legally compliant website but also one that was measurably more intuitive and user-friendly for all target groups. This also translates into better SEO performance. Learn more about its importance in our article Accessibility as a Quality Driver.

What core aspects of accessibility should be considered in a relaunch?

At its core, it is about the WCAG principles: perceivability, operability, understandability, and robustness. Practically, this means: sufficient colour contrasts, keyboard navigation for all elements, descriptive alt text for images, clear heading structures, subtitles for videos, and a semantically correct HTML structure. These aspects must be considered during the design and content creation process.

Some common mistakes can be easily avoided if considered early. For example: poor colour contrasts make text unreadable for people with visual impairments. Navigation that only works with a mouse excludes keyboard users. Missing alternative texts for images are a barrier for screen readers. A Vorarlberg industrial company ensured during its relaunch that all form fields were correctly labelled and error messages were clear and understandable. In addition, the font size was dynamically and scalably implemented. These measures ensured that the website was optimally usable even for users with limited eyesight and that the submission of enquiries significantly increased. Comprehensive tests with various assistive technologies and diverse user groups are essential to guarantee true accessibility. Preparing a WCAG audit is a good first step here.

Checklist: Accessibility in the Relaunch

Are the WCAG guidelines (currently 2.1 or 2.2) being followed?
Are colour contrasts sufficient and visually checked?
Is the entire website operable via keyboard?
Do all images have descriptive alt text?
Is the heading structure semantically correct and logical?
Are there subtitles or transcripts for audio/video content?
Are forms clearly labelled and error messages understandable?
Have tests been conducted with screen readers or other assistive technologies?
Is an Accessibility Statement available?

Agile Project Management: How Flexibility Accelerates the Relaunch

An agile approach to website relaunch allows for flexibility and quick adaptation to new insights or changed requirements. Instead of a rigid waterfall model that delivers results only after months, agile teams work in short iterations (sprints). Each sprint delivers a functional, albeit incomplete, partial result. This reduces risks, improves communication, and ensures that the project goal is continuously kept in sight.

Traditional relaunches often follow a linear plan: requirements phase, design phase, development phase, testing phase. Changes in later phases lead to significant delays and cost explosions. Agile project management, such as Scrum, divides the process into two-week sprints. At the end of each sprint, there is a "deliverable increment", i.e. a piece of functional website. This allows the customer to provide early feedback, leading to continuous optimisation. A telecommunications provider from Austria used agile methods for its last relaunch. Instead of developing in silence for months, prototypes and partial functionalities were presented every two weeks. Direct customer feedback made it possible to react quickly to changed market conditions and continuously improve the product, instead of having a rigid product at the end that no longer met current requirements. This led to a 20% faster time-to-market and higher customer satisfaction.

Which agile practices are particularly useful for a relaunch?

For a relaunch, practices such as defining a Minimum Viable Product (MVP), working in sprints, regular stand-ups, and retrospectives are particularly useful. The MVP ensures that core functionalities go live quickly. Sprints maintain focus. Stand-ups promote communication, and retrospectives enable continuous learning and process improvements. Transparency is crucial here.

The concept of a Minimum Viable Product (MVP) is particularly valuable: instead of trying to build the perfect website in one go, one identifies the absolutely necessary functions for an initial launch. This enables a faster go-live and collects valuable user feedback that can be incorporated into later iterations. A Vienna-based start-up wanted to launch a new platform. Instead of implementing all planned features immediately, they started with an MVP that covered the core functionality. After three months, the MVP went live, and the team could prioritise the next development steps through user feedback and data analysis. The remaining features were added in subsequent sprints. This reduced the initial risk and enabled market-driven development. At Zensations, we also apply agile methods in the development of Website Implementation with AI to remain flexible and responsive even in complex projects.

Agile Methods in Relaunch: Advantages at a Glance

Early Value Creation: Initial results are visible and usable quickly.
Lower Risk: Problems are identified and resolved early.
High Adaptability: Changes can be flexibly integrated.
Better Quality: Continuous feedback leads to a more mature product.
Transparency: The customer is closely involved in the process and informed at all times.

Technology Stack: How the Right Choice Secures the Future

The selection of the technology stack influences not only implementation but also long-term maintenance, scalability, and performance of your website. A well-founded decision between content management systems, frameworks, and hosting solutions is crucial. It must meet current requirements while also considering future growth and technological developments, so you do not have to plan the next relaunch soon.

A relaunch is also always an opportunity to reduce technical debt and opt for modern, future-proof solutions. The decision for a CMS, a frontend framework, or a hosting strategy should be well considered. An outdated technology stack can lead to security vulnerabilities, performance issues, and high maintenance costs. A medium-sized company from Styria operated its website on a proprietary CMS that was no longer being developed. Every adjustment was expensive and time-consuming. For the relaunch, we opted for a modern, headless CMS in combination with a powerful frontend framework. This not only enabled significantly faster development and better performance but also the connection to other systems such as a mobile app or displays in the salesroom. The decision between a headless CMS and a traditional system is often a strategic one. You can find more about this in our Headless CMS Decision Aid.

When is a Headless CMS useful for a relaunch?

A headless CMS separates content management (backend) from output (frontend). It is useful when content needs to be delivered not only on the website but also on other channels (apps, IoT devices, voice assistants). It offers maximum flexibility for developers and enables highly performant and individualised user experiences. For complex digital strategies with multiple touchpoints, it is often the best choice.

The advantage of a headless CMS lies in its flexibility. You can manage content centrally once and then deliver it via an API to any number of "heads". This is ideal for omnichannel strategies. A Tyrolean tourism company wanted to use its content not only on the website but also in an app, on digital information terminals, and in various marketing campaigns. A headless CMS made it possible to manage all content centrally and keep it up-to-date across all channels automatically. This saved enormous editorial time and ensured consistency of the brand message. Moreover, websites built with a headless CMS are often extremely fast and offer high scalability, which positively impacts Core Web Vitals and thus SEO.

Criteria for Selecting the Technology Stack

Requirements: What functions must the website fulfil?
Scalability: How many users and how much content are expected in the future?
Security: Are regular updates and patches guaranteed?
Performance: How fast should the website load?
Developer Community: Are there sufficient resources and support?
Costs: Licensing fees, development costs, maintenance effort.
Integrability: Connection to existing systems (CRM, ERP, marketing automation).
Editor Experience: How easy is content management for the editorial team?

Frequently Asked Questions

Is fast the same as poor quality?

No. Speed comes from clear scope, not from less care.

What is the most common reason for delays?

Missing content and unclear approvals on the client side.

When is a complete rebuild worthwhile?

When technology, structure, and design are simultaneously outdated.

Your Next Step

Would you like to implement this topic for your company? We will examine your initial situation, identify the three most effective measures, and inform you of the effort and timeframe. Email us at office@zensations.at or start with the free GEO-Check.