Website Relaunch Without Ranking Loss

Website Relaunch Without Ranking Loss: The Complete Guide

A website relaunch is one of the riskiest undertakings in digital marketing. Done right, it can take your online presence to the next level. Done wrong, you lose rankings within days that you spent years building. In this guide, we show you how to plan and execute your relaunch without endangering your hard-earned search engine rankings.

The GoldenWing team, with more than 13 years of experience, supports website relaunches for companies in Austria. The experience from these projects, both successes and lessons learned, feeds into every section of this guide.

What Is a Website Relaunch?

A website relaunch is a fundamental overhaul of an existing website. Unlike a simple redesign (purely visual), a relaunch typically includes changes to structure, technology, content and design.

Types of Relaunches

Important: The more changes, the higher the SEO risk. Plan correspondingly more time for SEO protection.

When Is a Relaunch Necessary?

Not every problem requires a relaunch. Sometimes targeted optimizations are enough. A relaunch makes sense when:

Technical reasons:

• The CMS is outdated and no longer receives security updates
• The website is not responsive / not mobile-optimized
• Load times are unacceptable despite optimization
• The technical infrastructure no longer scales
• A new technology (e.g. Next.js, headless CMS) offers significant advantages

Business reasons:

• The business model has changed (new target group, new products)
• The branding has been completely overhauled
• Competitors have significantly better websites
• The conversion rate is stagnating despite optimization
• Regulatory requirements (e.g. accessibility) require fundamental changes

Content reasons:

• The page structure has grown chaotically over the years
• There are hundreds of orphaned pages without traffic
• The content strategy has fundamentally changed
• Duplicate content is a systemic problem

If you are unsure whether a relaunch is the right path, GoldenWing offers a free initial consultation. Often, a targeted web design optimization pays off more than a complete relaunch.

The Relaunch Checklist: Before, During, After

BEFORE the relaunch (3-6 months ahead)

1. SEO audit of the existing website

Before you change anything, you need to know the current state:

• Crawl the entire website (Screaming Frog, Sitebulb)
• Export all URLs with page type, title and meta description
• Document all rankings (Google Search Console, Ahrefs, SEMrush)
• Identify the top pages by traffic and rankings
• Capture all incoming backlinks (Ahrefs, Majestic)
• Measure the current Core Web Vitals (our guide helps)
• Check the current indexing (Google Search Console → Pages)

2. Create the URL mapping

The URL mapping is the most important document of your relaunch. It assigns every old URL to a new URL.

Rules for URL mapping:

• Every old URL with traffic or backlinks needs a 301 redirect
• Pages without traffic and without backlinks can be removed with 410 (Gone)
• Avoid redirect chains (A → B → C, redirect directly A → C instead)
• Don't redirect everything to the homepage: Google advises against it and often treats such redirects as soft 404s
• Test the redirect mappings before go-live

3. Content inventory and assessment

Create a complete inventory list of all content:

• Which pages perform well? (Keep + optimize)
• Which pages have no traffic? (Consolidate or remove)
• Which content is missing? (Plan new pages)
• Which content is outdated? (Update)

4. Define technical requirements

• CMS selection (WordPress, Payload CMS, headless)
• Hosting requirements (performance, scalability)
• SSL/TLS certificate
• CDN integration
• Internationalization (hreflang, locale routing)

5. Set up a staging environment

The new website is ALWAYS developed in a staging environment:

• Staging domain with noindex, nofollow (robots.txt + meta tag)
• HTTP authentication (password protection)
• Server configuration identical to production

DURING the relaunch (go-live)

1. Go-live checklist

• [ ] All 301 redirects active and tested
• [ ] robots.txt updated (noindex from staging removed)
• [ ] XML sitemap updated and submitted in Search Console
• [ ] Canonical tags correct on all pages
• [ ] hreflang tags correct (for multilingual sites)
• [ ] SSL certificate active, HTTP → HTTPS redirect
• [ ] Google Analytics / Tag Manager verified
• [ ] Search Console property verified for new URLs
• [ ] All forms tested
• [ ] 404 page configured correctly
• [ ] Internal links updated (no links to old URLs)
• [ ] Images optimized (alt tags, compression)
• [ ] Core Web Vitals in the green
• [ ] Schema markup implemented and validated
• [ ] Mobile display tested

2. Choose the timing

• Never launch on a Friday (no support over the weekend)
• Never before holidays or seasonal peaks
• Ideally Tuesday or Wednesday morning
• Make sure the team is available (developers, SEO, content)

3. DNS switch

• Set the TTL to 300 seconds (5 minutes) beforehand
• Make the DNS change
• Monitor propagation (can take up to 48 hours)
• Run the old and new servers in parallel

AFTER the relaunch (4-8 weeks)

1. Immediate monitoring (days 1-7)

• Check Google Search Console daily (crawl errors, indexing)
• Spot-check the 301 redirects
• Analyze server logs for 404 errors
• Monitor Core Web Vitals
• Verify conversion tracking
• Test all forms again

2. Short term (weeks 2-4)

• Track rankings daily and compare them with pre-relaunch
• Compare organic traffic weekly
• Fix new 404 errors in Search Console
• Monitor the indexing status (how many pages are indexed?)
• Check backlink profiles (do backlinks go to 404s?)

3. Medium term (months 2-3)

• Detailed traffic comparison (month over month, year over year)
• Conversion rate analysis
• Ranking development for top keywords
• Analyze Core Web Vitals field data
• Evaluate the content performance of the new pages

SEO During the Relaunch: 301 Redirects and URL Mapping

This section deserves special attention, because this is where most mistakes happen.

Implementing 301 Redirects Correctly

A 301 redirect tells search engines: “This page has moved permanently.” Google uses a 301 redirect as a signal that the target URL should be the canonical version.

Implementation methods:

Example .htaccess:

RewriteEngine On

RewriteRule ^leistungen/web-design/$ /de/leistungen/webdesign [R=301,L]

RewriteRule ^blog/seo-tipps-2024/$ /de/blog/seo-tipps-guide [R=301,L]

Important rules:

1. 1:1 redirects: Every old URL to the most relevant new URL
2. No chains: A → C, not A → B → C
3. No loops: A → B → A is fatal
4. Not everything to home: Google advises against it and often treats such redirects as soft 404s
5. Keep them permanently: Keep 301 redirects active for at least 1 year, ideally permanently

Optimizing the URL Structure

A relaunch is the perfect opportunity to improve the URL structure:

Before (typical problems):

• /index.php?page=services&id=42
• /2024/03/15/blog-post-titel/
• /leistungen/web-design/responsive-web-design-für-kleine-unternehmen/

After (optimized):

• /de/leistungen/webdesign
• /de/blog/seo-tipps-guide
• /de/leistungen/webdesign/responsive

Best practices for URLs:

• Short and descriptive (3-5 words)
• Lowercase only
• Hyphens as separators (no underscores)
• No date in blog URLs (prevents the “outdated effect”)
• Locale prefix for multilingual sites (/de/, /en/)
• No parameters or session IDs

Our SEO Checker tool helps you check the technical SEO quality of your new website.

Content Migration: More Than Copy-Paste

Content migration is one of the most labor-intensive parts of a relaunch, and one of the most underestimated.

Content Migration Strategy

Step 1: Categorize content

Divide your existing content into four categories:

Step 2: Content inventory with metrics

Record for each page:

• URL
• Page type (blog, service, landing page)
• Organic traffic (last 12 months)
• Top keywords and rankings
• Backlinks (number + quality)
• Conversion data (leads, sales)
• Content quality (rating 1-5)
• Action (Keep / Optimize / Merge / Kill)

Step 3: Carry out the migration

• Don't just copy texts: use every page as an optimization opportunity
• Rewrite meta titles and descriptions (but keep the keywords)
• Adapt internal linking to the new URL structure
• Optimize images (new formats: WebP, AVIF)
• Update or add schema markup
• Close content gaps (add missing sections)

Common Migration Mistakes

1. Changing title tags: If a title tag ranks well, don't change it without a reason
2. Cutting content: Less content = fewer ranking signals
3. Forgetting internal links: Old URLs in content links lead to redirect chains
4. Not migrating images: Alt tags and file names get lost
5. Forgetting structured data: Schema markup must be adapted to the new URLs

Design Relaunch vs. Technical Relaunch

Pure Design Relaunch

What changes: Colors, typography, layout, images, animations

What stays the same: URLs, page structure, CMS, content

SEO risk: Low, if the page structure and URLs stay identical

Typical problems:

• New templates load more slowly (larger images, more JavaScript)
• Content is restructured (H1 hierarchy changed)
• Internal linking changes because of the new menu design
• Mobile display differs

Technical Relaunch

What changes: CMS, programming language, server, database

What should stay the same: URLs (as far as possible), content, page structure

SEO risk: Medium to high

Typical problems:

• URL structure changes because of the new CMS
• Redirects are not implemented correctly
• Rendering differences (server-side vs. client-side)
• Missing SEO features in the new CMS (canonical, hreflang, schema)
• Performance differences (better or worse hosting)

At GoldenWing, we rely on modern web design technologies like Next.js and Payload CMS, which offer excellent SEO features and performance out of the box.

10 Common Relaunch Mistakes

From the experience of the GoldenWing team, with more than 13 years of practice, we have seen the following mistakes again and again and learned to avoid them:

1. No URL mapping created

Consequence: Hundreds of 404 errors, massive ranking losses within days.

Solution: Complete URL mapping as the first document in the relaunch project.

2. Staging environment gets indexed

Consequence: Google indexes the staging version, creating duplicate content.

Solution: robots.txt Disallow + noindex meta tag + HTTP auth on staging.

3. 301 redirects are missing or faulty

Consequence: Link equity is lost, backlinks lead nowhere.

Solution: Implement all redirects before go-live and test them automatically.

4. Internal links not updated

Consequence: Thousands of internal links go through redirects, causing a poor user experience and wasted crawl budget.

Solution: Update all internal links to the new URLs, don't rely on redirects.

5. Content is migrated “on the side”

Consequence: Content is forgotten, shortened or given new (worse) titles.

Solution: Treat content migration as its own workstream with a dedicated team.

6. No pre-launch testing

Consequence: Broken forms, missing tracking codes, performance problems, all discovered only after go-live.

Solution: A minimum of 1 week of testing on staging with a checklist.

7. Go-live on a Friday

Consequence: Problems are only discovered on Monday, 3 days unmonitored.

Solution: Go-live on Tuesday/Wednesday with full team support.

8. No post-launch monitoring

Consequence: Crawl errors and ranking losses are detected too late.

Solution: Daily monitoring for 4-8 weeks after go-live.

9. XML sitemap not updated

Consequence: Google tries to crawl old URLs and finds 404 errors.

Solution: Submit the new sitemap in Search Console immediately after go-live.

10. Performance ignored

Consequence: The new website is slower than the old one, and Core Web Vitals get worse.

Solution: Define a performance budget before the relaunch, optimize Core Web Vitals.

Timeline for a Website Relaunch

Typical Timeline (Complete Relaunch)

Total duration: 16-32 weeks for a complete relaunch

Tip: Always plan a sufficient buffer. Relaunches almost always take longer than planned. At GoldenWing, we work with agile sprints to react flexibly to changes.

What Does a Website Relaunch Cost?

The costs depend heavily on scope, complexity and requirements. Here are realistic benchmarks for the Austrian market.

Cost Overview

What Influences the Costs?

For a detailed cost estimate, also read our guide What Does a Professional Website Cost?.

Measuring Success After the Relaunch

The Most Important KPIs

SEO KPIs (weeks 1-12):

Business KPIs (months 1-6):

Reporting Template

Create a weekly relaunch report with:

1. Traffic comparison: Current week vs. the same week before the relaunch
2. Ranking tracker: Top 50 keywords with position changes
3. Crawl status: New errors, indexing progress
4. Conversion data: Leads, inquiries, sales
5. Action items: Open problems and their prioritization

SEO Checklist for the Relaunch

To close, a compact checklist that you should work through for every relaunch:

Pre-launch:

• Full crawl of the old website
• URL mapping with all old and new URLs
• Backlink profile documented
• Ranking baseline for top keywords
• Content inventory with performance data
• Staging with noindex + robots.txt Disallow
• 301 redirects implemented and tested
• XML sitemap prepared
• Canonical tags correct
• hreflang tags correct (multilingual)
• Schema markup implemented
• Core Web Vitals optimized
• Mobile display tested

Go-live:

• DNS switch carried out
• robots.txt updated (staging Disallow removed)
• Sitemap submitted in Search Console
• All redirects active
• Tracking codes verified
• SSL active, HTTP → HTTPS redirect

Post-launch:

• Check Search Console daily
• Fix 404 errors
• Track rankings
• Monitor indexing progress
• Measure performance
• Verify conversion tracking

Use our SEO Checker to check the technical SEO quality of your new website after the relaunch.

Frequently Asked Questions (FAQ)

How much traffic will I lose in a relaunch?

With a carefully planned relaunch with complete URL mapping and 301 redirects, fluctuations are usually smaller and fade faster. Google points out that visibility can fluctuate temporarily during a move and that it can take a few weeks or more on medium-sized sites for the new URLs to replace the old ones. Without SEO planning, you risk significant and longer-lasting losses, and recovery is then not guaranteed.

How long does it take for rankings to recover after a relaunch?

With a well-planned relaunch, you will see stabilization after a few weeks. For medium-sized sites, Google says it can take a few weeks or more for the new URLs to replace the old ones. If the relaunch comes with content optimizations, rankings can even become better than before. Check right after go-live that the redirects are served correctly.

Do I have to inform Google about the relaunch?

Not directly, but indirectly: submit the new XML sitemap in Google Search Console as soon as the relaunch is live. If you change the domain, use the “Change of Address” tool in Search Console. You can test individual URLs after go-live with the URL Inspection Tool in Search Console.

Can I change the URL structure during the relaunch?

Yes, that is actually one of the most common reasons for a relaunch. However, every URL change is an SEO risk that must be secured with a 301 redirect. Only change the URL structure if there is a clear benefit (better readability, more logical hierarchy, locale prefixes). Never change URLs “because that's just how it's done.”

What should I do if rankings collapse after the relaunch?

Stay calm and proceed systematically: (1) Check Search Console for crawl errors: are there 404s? (2) Check the redirects: do they all work correctly? (3) Check canonical tags: do they point to the right URL? (4) Compare content: has the content of the top pages changed? (5) Measure load times: has the website become slower? Common causes are missing or incorrect redirects. Contact us for an emergency analysis.

Should I carry out the relaunch in-house or hire an agency?

That depends on your internal resources. For a pure design relaunch with few pages, an internal team may be enough. For a complete relaunch with URL changes, content migration and SEO protection, we recommend working with an experienced agency. At GoldenWing, we support the entire process, from SEO analysis through web design to technical implementation. Contact us for a no-obligation initial conversation.

Stakeholder Management in a Website Relaunch

A website relaunch is not just a technical project: it affects numerous departments and interest groups. Poor stakeholder management is the most common reason for failed relaunch projects, even ahead of technical errors.

Identifying the Key Stakeholders

In a typical relaunch project for an Austrian SME, the following stakeholders are involved:

• Management: Decides on budget, timeline and strategic direction
• Marketing/Sales: Defines target groups, conversion goals and content requirements
• IT/Technology: Responsible for hosting, integrations and technical implementation
• Customer service: Knows the most common user questions and pain points
• External partners: Agency, freelancers, hosting provider

The RACI Matrix for Relaunch Projects

For each project phase, clearly define who is Responsible, Accountable, Consulted and Informed.

Example for content migration:

• Responsible: Marketing team
• Accountable: Project manager
• Consulted: SEO agency, sales
• Informed: Management, IT

Creating a Communication Plan

Establish fixed communication rhythms:

• Weekly status meeting (30 minutes) with the core team
• Biweekly report to management
• Milestone reviews at critical points (design approval, content freeze, go-live decision)
• Escalation path for blockers and conflicts

Typical Conflicts and How to Resolve Them

Conflict 1: Design vs. SEO

Marketing wants a minimalist design with little text, while the SEO agency demands extensive text content. Solution: Design content areas with accordions or tabs: visually clean, but with enough indexable text.

Conflict 2: Feature creep

New wishes keep coming in during the project. Solution: Keep a feature backlog and prioritize using the MoSCoW principle (Must, Should, Could, Won't). Everything that is not a “Must” goes into phase 2 after the launch.

Conflict 3: Timeline pressure

Management sets an unrealistic deadline. Solution: Use the critical path to show which tasks can run in parallel and where dependencies exist. Offer alternatives: e.g. a “soft launch” with reduced functionality on the desired date.

Change Management After the Relaunch

Don't forget internal training. Employees who work with the website every day (content maintenance, form processing, analytics) need to know the new system. Plan at least 2-3 training days and create internal documentation.

Performance Optimization: Using the Relaunch as a Speed Boost

A relaunch is the perfect opportunity to fundamentally improve website speed. According to a Deloitte study commissioned by Google, a mobile load time just 0.1 seconds faster led to 21.6% more users reaching the form on lead generation websites.

Hosting Upgrade as the Foundation

The relaunch is the ideal time for a hosting change. For Austrian websites, we recommend:

• Shared hosting (price depends on provider): Only for small company sites with little traffic
• Managed WordPress hosting (price depends on provider): Optimal for most SME websites
• VPS/dedicated (price depends on provider): For shops and high-traffic websites
• Edge hosting/Vercel/Netlify: For modern JAMstack and Next.js projects

Important: Choose a hosting location in the DACH region (e.g. Frankfurt or Vienna) to minimize latency for your target group.

Image Optimization During the Relaunch

According to the HTTP Archive Web Almanac 2024, median pages load about 0.9 MB (mobile) to 1 MB (desktop) of images out of a total weight of 2.3 to 2.7 MB. During the relaunch, you should:

• Convert all images to WebP/AVIF: according to Google, WebP images are 25 to 34% smaller than comparable JPEG images
• Implement responsive images with srcset: different sizes for different screens
• Lazy loading for all images below the visible area
• Automate image compression with tools like Sharp, Squoosh or TinyPNG
• Define a maximum width: No images wider than 1920px, 800-1200px is enough for most elements

Critical CSS and Code Splitting

Implement critical CSS: the CSS for the visible area is loaded inline in the HTML, the rest asynchronously. This significantly improves the Largest Contentful Paint (LCP).

For JavaScript, use code splitting:

• Load only the code needed on the current page
• Use dynamic imports for components below the fold
• Eliminate unused JavaScript (tree shaking)

Caching Strategy

Configure a well-thought-out caching strategy during the relaunch:

• Browser caching: Static assets (CSS, JS, images) with long cache times (1 year) and content hashing for cache busting
• Server caching: Page caching for dynamic content (e.g. Redis or Varnish)
• CDN: Cloudflare or Fastly for global delivery of static content

Defining a Performance Budget

Set binding performance budgets before the relaunch:

• Total weight of the homepage: Maximum 1.5 MB (ideally under 1 MB)
• LCP: Under 2.5 seconds
• Total Blocking Time: Under 200 milliseconds
• Number of HTTP requests: Maximum 50 on the homepage

Integrate performance tests into your CI/CD pipeline so that new deployments don't exceed the budgets.

Domain Change During a Relaunch: Particularities and Risks

A relaunch with a simultaneous domain change is the riskiest variant of a website relaunch. Google points out that visibility can fluctuate temporarily during a move. Google does not give a percentage.

When a Domain Change Makes Sense

• Rebranding: The company changes its name or repositions itself
• Internationalization: Switching from a .at domain to a .com domain
• Domain consolidation: Several domains are merged into one
• Problematic domain history: The current domain has a negative SEO history (e.g. due to penalties)

The Correct Procedure

Step 1: Preparation (4-6 weeks before the change)

• Fully crawl and document all existing URLs of the old domain
• Create a redirect mapping: every old URL must be assigned to a new URL
• Set up and verify Google Search Console for the new domain
• Analyze the backlink profile and identify important linking sites

Step 2: Technical implementation

• Set up 301 redirects at server level (not via JavaScript or meta refresh)
• Set canonical tags correctly on the new domain
• Update hreflang tags if multilingual versions exist
• Internal links on the new site must all point to the new domain

Step 3: Inform Google

• Request the change of address in Google Search Console (under “Settings” > “Change of address”)
• Submit the new sitemap under the new domain
• The old domain must keep serving the 301 redirects for at least 12 months, ideally permanently

Step 4: External signal management

• Contact the top 20 linking sites and ask them to update their links
• Update all social media profiles, Google Business Profile and industry directories
• Adapt email signatures, business cards and printed materials

Common Mistakes in a Domain Change

• Shutting down the old domain too early: The redirects must stay active for at least 12 months
• Chain redirects: The old domain forwards to an intermediate page, which then redirects again, so use a maximum of one redirect per URL
• Ignoring HTTP vs. HTTPS: All four variants (http://old, https://old, http://new, https://new) must redirect correctly
• Forgetting parameter URLs: URLs with parameters (e.g. ?page=2) must also be redirected

Relaunch Monitoring: The First 90 Days After Launch

The work doesn't end with go-live. The first 90 days after the relaunch are decisive for long-term success. A structured monitoring program helps you detect and fix problems early.

Week 1: Daily Monitoring

In the first week after launch, you should check the following points daily:

• Crawl errors in Google Search Console: 404 errors, server errors, redirect loops
• Indexing status: Are the new pages being indexed? Are old pages being deindexed?
• Core Web Vitals: Are the performance values right under real conditions?
• Conversion tracking: Do all forms, checkout processes and tracking codes work?
• Server logs: Unusual access patterns, high error rates, bot activity

Weeks 2-4: Weekly Monitoring

• Organic traffic compared with the previous month and the previous year (Google Analytics)
• Keyword rankings for the top 50 keywords (Sistrix, Ahrefs or SEMrush)
• Impressions and clicks in Google Search Console
• Bounce rate and time on site on the most important landing pages
• Indexed pages: The number should approach the target figure

Months 2-3: Biweekly Monitoring

• Backlink profile: Are links being transferred to the new URLs?
• Crawl budget: How efficiently does Google crawl your new website?
• Conversion rate compared with pre-relaunch values
• Page speed trends: Are the values getting worse because of new content?
• Start A/B tests for critical landing pages

Typical Ranking Development After a Relaunch

As a rough rule of thumb from practice, not a guarantee, because Google gives no fixed duration:

• Weeks 1-2: Temporary ranking fluctuations (to be expected during a move, according to Google)
• Weeks 3-6: Stabilization, first rankings return to the pre-relaunch level
• Months 2-3: Rankings reach or exceed the old level
• Months 4-6: Clear upward trend thanks to improved technology and content

Warning sign: If no upward trend is visible after 4 weeks, there is probably a technical problem (faulty redirects, crawling blockers, canonical errors).

Have an Emergency Plan Ready

Before launch, create a rollback plan for the worst case:

• Backup of the old website including database and files
• Document the DNS configuration so you can switch back quickly
• Communication plan for stakeholders in case of serious problems
• Define escalation levels: At what traffic drop is the rollback triggered?

In practice, with careful planning a rollback is rarely necessary. Still, it should be possible at all times.

Relaunch Communication: Informing Customers and Partners Properly

A website relaunch doesn't only affect your internal teams: it has a direct impact on customers, business partners, suppliers and other stakeholders. A well-thought-out communication strategy ensures that everyone involved is informed, trust is maintained and the relaunch is perceived as a positive signal.

Why Relaunch Communication Is So Important

Relaunches fail not only because of technical problems, but also because of poor communication. Customers can no longer find familiar functions, partner companies can no longer access shared resources, and internal employees are not sufficiently trained.

The consequences can be serious:

• Support requests can rise, especially in the first two weeks after a poorly communicated relaunch
• The conversion rate can drop temporarily when regular customers can't find their familiar workflows
• B2B partnerships suffer when API endpoints, product feeds or partner portals are changed without warning
• Brand perception suffers when the relaunch is seen as chaotic

The Communication Plan: Phases and Target Groups

Effective relaunch communication is divided into three phases, each addressing different target groups.

Phase 1: Pre-announcement (4-6 weeks before go-live)

In this phase, you inform your most important stakeholders about the upcoming relaunch. For the Austrian market, a personal approach is recommended for key customers and partners:

• Key accounts and A customers: Personal call or meeting by the responsible account manager
• B2B partners and suppliers: Formal letter with detailed information on the changes that affect them
• Existing customers (B2C): Newsletter announcement pointing to upcoming improvements
• Internal employees: Kick-off meeting with a training plan and FAQ document
• Press and trade media: Prepare a press release, but send it only shortly before go-live

Phase 2: Go-live communication (day of the launch)

On the day of the relaunch, communication should be proactive and multichannel:

• Email blast to all registered users with the most important changes
• Social media posts on all relevant channels (LinkedIn is particularly important for DACH B2B)
• Banner on the new website pointing to changes and linking to a help area
• Internal Slack/Teams message to all employees with support contact details

Phase 3: Follow-up (2-4 weeks after go-live)

Follow-up is often neglected, but it is crucial for long-term success:

• Actively collect feedback through surveys, support tickets and social media monitoring
• Publish FAQ updates based on the most frequent questions
• Send a follow-up email with tips on new features and functions
• Create video tutorials or guided tours for complex areas like customer portals or online shops

Special Communication for Technical Stakeholders

If your website relaunch affects technical interfaces, developer teams at partner companies need special attention. A typical SME website is often connected to several external systems, such as payment providers, CRM or newsletter tools.

Inform technical stakeholders about:

• API changes: New endpoints, changed authentication, versioning
• Feed formats: Updated product feeds, price lists, catalog data
• SSO integration: Changes to single sign-on configurations
• Webhook URLs: New callback addresses for payment providers, CRM systems etc.
• Deprecation timeline: Clear deadlines for how long old interfaces will keep working

Preparing Crisis Scenarios

Even with the best planning, problems can occur on launch day. Prepare ready-made communication for every realistic scenario. This saves valuable time in an emergency and prevents ill-considered statements under pressure.

Create templates for:

• Planned maintenance windows and their extension
• Unexpected outages and their expected time to resolution
• Data migration problems that affect customers
• Functional limitations during the transition phase

Relaunch Testing: Quality Assurance Before Go-Live

Quality assurance is the last and at the same time most critical phase before go-live. An insufficiently tested relaunch can not only cost rankings but also lastingly damage the trust of your users. Systematic testing reduces these risks to a manageable level.

The Test Pyramid for Website Relaunches

Professional relaunch testing follows a structured pyramid that ranges from basic technical tests to comprehensive user acceptance tests:

Level 1: Basic technical tests

These tests ensure that the basic functionality of the website is guaranteed:

• Broken link check: Check all internal and external links for reachability (tools: Screaming Frog, Sitebulb)
• 301 redirect validation: Test every single redirect from the redirect map
• SSL certificate: Verify correct installation and validity
• robots.txt and sitemap: Check for correctness and completeness
• Canonical tags: Make sure no duplicate content problems arise
• hreflang tags: Especially important for multilingual DACH websites (de-AT, de-DE, de-CH)

Level 2: Functional tests

Here, all interactive elements of the website are checked:

• Forms: Contact forms, newsletter signups, login areas
• E-commerce functions: Cart, checkout, payment processing, order confirmations
• Search function: Test internal search for relevance and completeness
• Filters and sorting: Especially for product catalogs and directories
• User accounts: Registration, login, password reset, profile changes
• Download functions: PDFs, catalogs, price lists

Level 3: Cross-browser and cross-device testing

An analysis of StatCounter data for Austria shows these browser market shares for September 2026 (all platforms):

• Chrome: 46.8%
• Safari: 21.7%
• Firefox: 9.6%
• Edge: 12.3%
• Samsung Internet: 3.9%

Test your website in at least the top 4 browsers and on the most common device types (desktop, tablet, smartphone). Pay special attention to:

• Layout consistency: No overlapping elements or cut-off content
• Touch interactions: Buttons and links must be easy to use on touchscreens (minimum size 44 × 44 pixels)
• Font rendering: Web fonts loaded correctly and legible
• Image display: Responsive images in the correct resolution

Level 4: Performance testing

Performance tests are crucial because, according to Google, good Core Web Vitals align with what its ranking systems seek to reward. Use the following tools and benchmarks:

• Google PageSpeed Insights: Target value: Core Web Vitals in the “good” range (LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1)
• WebPageTest: Detailed waterfall analysis of page loading behavior
• Lighthouse CI: Automated performance checks in the CI/CD pipeline
• Load tests: Simulate expected traffic peaks with tools like k6 or Apache JMeter

For Austrian websites, we recommend a load test with a clear safety margin above the expected peak traffic. Take seasonal peaks into account, such as the Christmas season, Black Friday or industry-specific high periods.

SEO-Specific Relaunch Tests

In addition to the general tests, there are SEO-specific checks that must be carried out before go-live:

• Indexability: Make sure the staging environment is set to noindex and the production environment allows index
• Structured data: Validate all Schema.org markup with the Google Rich Results Test
• Meta data: Check title tags and meta descriptions on all pages
• Image alt texts: Check whether all images have meaningful alt attributes
• Internal linking: Analyze link depth and make sure no important pages are orphaned
• Page speed comparison: Compare the load times of the new site with the old one and document improvements or deteriorations

Staging Environment and Pre-Live Checklist

A production-like staging environment is indispensable for professional relaunch testing. Without a dedicated staging environment, you take on an avoidable risk.

Your pre-live checklist should include at least these points:

• All 301 redirects are implemented and tested
• Google Search Console is verified for the new domain/URL structure
• Google Analytics / Matomo tracking code is integrated correctly
• Cookie banner and privacy policy are updated in compliance with GDPR
• Contact details in the legal notice are correct (mandatory information under Austrian law)
• A backup of the old website has been created and stored externally
• The rollback plan is documented and known to everyone involved
• DNS TTL was set to a low value 48 hours before the relaunch

Automated Testing for Sustainable Quality

Modern relaunch projects rely on automated test suites that ensure quality not only before go-live but permanently. Tools like Cypress, Playwright or Selenium make it possible to create end-to-end tests that run automatically with every deployment.

The combination of automated tests and visual regression testing is particularly effective. Tools like Percy or Chromatic take screenshots of all important pages with every build and compare them pixel by pixel with the previous version. This way, unintended layout changes are detected immediately, an enormous advantage for websites with hundreds of subpages.

Conclusion: Relaunch as an Opportunity, Not a Risk

A website relaunch doesn't have to be a nightmare. With the right planning, complete URL mapping, clean 301 redirects and structured post-launch monitoring, your relaunch succeed with a much lower ranking risk and can even improve your SEO performance.

The key takeaways:

1. Plan 3-6 months of lead time for SEO protection
2. The URL mapping is your most important document: invest the necessary time
3. 301 redirects are mandatory for every URL with traffic or backlinks
4. Monitoring after go-live is at least as important as the preparation
5. Use the relaunch as an opportunity for better content and better technology

The GoldenWing team brings more than 13 years of experience with website relaunches in Austria and the DACH region. We support you from the first analysis to a successful go-live, and beyond. Contact us for your relaunch project.

Are you planning a website relaunch? Our web design agency in Vienna supports you from concept to go-live.