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 elevate your online presence to the next level. Done wrong, you lose rankings within days that took years to build. In this guide, we show you how to plan and execute your relaunch without jeopardizing your hard-earned search engine rankings.

At GoldenWing, we have supported numerous website relaunches for companies in Austria over more than 3 years. The experiences from these projects -- successes and lessons learned -- flow 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 involves changes to structure, technology, content, and design.

Types of Relaunches

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

When Is a Relaunch Necessary?

Not every problem requires a relaunch. Sometimes targeted optimizations are sufficient. 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
• Loading 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 audience, new products)
• The branding has been completely overhauled
• Competitors have significantly better websites
• The conversion rate stagnates 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 with no traffic
• The content strategy has fundamentally changed
• Duplicate content is a systemic problem

If you are unsure whether a relaunch is the right path, we offer a free initial consultation at GoldenWing. Often a targeted web design optimization is more worthwhile 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, meta description
• Document all rankings (Google Search Console, Ahrefs, SEMrush)
• Identify the top pages by traffic and rankings
• Record all incoming backlinks (Ahrefs, Majestic)
• Measure current Core Web Vitals (our guide helps)
• Check current indexing status (Google Search Console -> Pages)

2. Create URL Mapping

URL mapping is the most important document of your relaunch. It assigns each 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, instead directly A -> C)
• Do not redirect everything to the homepage -- Google treats this as a soft 404
• Test redirect mappings before go-live

3. Content Inventory and Evaluation

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 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)
• Identical server configuration as 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 to 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 correctly configured
• [ ] Internal links updated (no links to old URLs)
• [ ] Images optimized (alt tags, compression)
• [ ] Core Web Vitals in the green zone
• [ ] Schema markup implemented and validated
• [ ] Mobile display tested

2. Choose the Right Time

• Never launch on Friday (no support on weekends)
• Never before holidays or seasonal peaks
• Ideally Tuesday or Wednesday morning
• Ensure team availability (developers, SEO, content)

3. DNS Transition

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

AFTER the Relaunch (4-8 weeks)

1. Immediate Monitoring (Day 1-7)

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

2. Short-term (Week 2-4)

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

3. Medium-term (Month 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 content performance of 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 permanently moved." Google transfers most of the link equity (ranking power) to the new URL.

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: Each 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 treats this as a soft 404
5. Keep permanently: Keep 301 redirects active for at least 1 year, ideally permanently

Optimizing 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-title/
• /leistungen/web-design/responsive-web-design-for-small-businesses/

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 pages (/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

For each page, record:

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

Step 3: Execute migration

• Do not simply copy texts -- use each page as an optimization opportunity
• Rewrite meta titles and descriptions (but keep keywords)
• Update internal linking to 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, do not change it without 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 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 page structure and URLs remain identical

Typical problems:

• New templates load slower (larger images, more JavaScript)
• Content gets restructured (H1 hierarchy changed)
• Internal linking changes through 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 due to new CMS
• Redirects are not correctly implemented
• 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 use 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 over 3 years of experience at GoldenWing, we have seen the following mistakes repeatedly -- 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, duplicate content arises.

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

3. 301 Redirects Missing or Incorrect

Consequence: Link equity is lost, backlinks lead nowhere.

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

4. Internal Links Not Updated

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

Solution: Update all internal links to new URLs, do not rely on redirects.

5. Content Is Migrated "On the Side"

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

Solution: Content migration as a standalone workstream with a dedicated team.

6. No Pre-Launch Testing

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

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

7. Go-Live on Friday

Consequence: Problems are discovered only 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 recognized too late.

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

9. XML Sitemap Not Updated

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

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

10. Performance Ignored

Consequence: The new website is slower than the old one -- Core Web Vitals deteriorate.

Solution: Define 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 buffer of 20-30%. Relaunches almost always take longer than planned. At GoldenWing, we work with agile sprints to be able to react flexibly to changes.

What Does a Website Relaunch Cost?

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 How Much Does a Professional Website Cost?.

Measuring Success After the Relaunch

The Most Important KPIs

SEO KPIs (Week 1-12):

Business KPIs (Month 1-6):

Reporting Template

Create a weekly relaunch report with:

1. Traffic comparison: Current week vs. same week before 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 issues and their prioritization

SEO Checklist for the Relaunch

To conclude, a compact checklist to work through with every relaunch:

Pre-Launch:

• Complete 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 transition completed
• robots.txt updated (staging disallow removed)
• Sitemap submitted to 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 during a relaunch?

With a carefully planned relaunch with complete URL mapping and 301 redirects, traffic loss should be under 10% and recover within 4-8 weeks. Without SEO planning, 30-70% of organic traffic can be lost. Recovery then takes 6-12 months -- if it happens at all.

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

With a well-planned relaunch, you will see stabilization within 2-4 weeks and recovery to pre-relaunch levels within 6-8 weeks. If the relaunch includes content optimizations, rankings can even improve beyond the previous level. The first 48 hours are critical -- this is when it is determined whether Google processes the redirects correctly.

Do I need 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 are changing domains, use the "Change of Address" tool in Search Console. Google also recommends reporting URL changes via the URL Inspection API to accelerate re-indexing.

Can I change the URL structure during the relaunch?

Yes, this 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 advantage (better readability, more logical hierarchy, locale prefixes). Never change URLs "just because."

What to do if rankings drop after the relaunch?

Stay calm and proceed systematically: (1) Check Search Console for crawl errors -- are there 404s? (2) Verify redirects -- are they all working correctly? (3) Check canonical tags -- do they point to the right URL? (4) Compare content -- has the content of top pages changed? (5) Measure loading times -- has the website become slower? In 80% of cases, the problem lies with missing or incorrect redirects. Contact us for an emergency analysis.

Should I do the relaunch internally or hire an agency?

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

Stakeholder Management During 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 more so than technical errors.

Identifying the Most Important 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 audiences, 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, freelancer, hosting provider

The RACI Matrix for Relaunch Projects

Clearly define for each project phase 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
• Bi-weekly report to management
• Milestone reviews at critical points (design approval, content freeze, go-live decision)
• Escalation path for blockers and conflicts

Typical Conflicts and Their Resolution

Conflict 1: Design vs. SEO

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

Conflict 2: Feature Creep

New requests keep coming during the project. Solution: Maintain a feature backlog and prioritize according to the MoSCoW principle (Must, Should, Could, Won't). Everything that is not "Must" goes into Phase 2 after launch.

Conflict 3: Timeline Pressure

Management sets an unrealistic deadline. Solution: Show the critical path to demonstrate which tasks can run in parallel and where dependencies exist. Offer alternatives: e.g., a "soft launch" with reduced functionality at the desired date.

Change Management After the Relaunch

Do not forget internal training. Employees who work with the website daily (content management, form processing, analytics) must 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. Studies show that improving loading time by just one second can increase the conversion rate by 7%.

Hosting Upgrade as the Foundation

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

• Shared Hosting (5-15 euros/month): Only for small business sites with little traffic
• Managed WordPress Hosting (25-80 euros/month): Optimal for most SME websites
• VPS/Dedicated (from 50 euros/month): For stores 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 audience.

Image Optimization During the Relaunch

Images account for an average of 50-65% of page weight. During the relaunch, you should:

• Convert all images to WebP/AVIF -- savings of 25-50% compared to JPEG
• 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 max width: No images over 1920px wide; for most elements 800-1200px is sufficient

Critical CSS and Code Splitting

Implement Critical CSS: The CSS code 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 homepage weight: 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 new deployments do not exceed the budgets.

Domain Change During the Relaunch: Specifics and Risks

A relaunch with a simultaneous domain change is the riskiest variant of a website relaunch. Google itself states that a domain change can lead to a temporary ranking loss of 10-30% over 3-6 months.

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: Multiple domains are merged into one
• Problematic domain history: The current domain has a negative SEO history (e.g., through penalties)

The Correct Procedure

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

• Completely crawl and document all existing URLs of the old domain
• Create 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 link sources

Step 2: Technical Implementation

• Set up 301 redirects at the 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 address change in Google Search Console (under "Settings" > "Change of Address")
• Submit new sitemap under the new domain
• The old domain must continue to serve the 301 redirects for at least 6 months -- ideally 12 months or longer

Step 4: External Signal Management

• Contact the top 20 link sources and request link updates
• Update all social media profiles, Google Business Profile, and business directories
• Update email signatures, business cards, and print materials

Common Mistakes During Domain Changes

• Shutting down the old domain too early: Redirects must remain active for at least 12 months
• Chain redirects: Old domain redirects to an intermediate page which then redirects again -- maximum 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 does not end with go-live. The first 90 days after the relaunch are crucial for long-term success. A structured monitoring program helps you identify 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 new pages being indexed? Are old pages being deindexed?
• Core Web Vitals: Are performance values correct under real conditions?
• Conversion tracking: Are all forms, checkout processes, and tracking codes working?
• Server logs: Unusual access patterns, high error rates, bot activity

Week 2-4: Weekly Monitoring

• Organic traffic compared to the previous month and 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 number

Month 2-3: Bi-Weekly Monitoring

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

Typical Ranking Trajectory After a Relaunch

Expect the following trajectory with a well-executed relaunch:

• Week 1-2: Slight ranking decline of 5-15% (normal, Google evaluates the new structure)
• Week 3-6: Stabilization, first rankings return to pre-relaunch level
• Month 2-3: Rankings reach or exceed the old level
• Month 4-6: Clear upward trend through improved technology and content

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

Have an Emergency Plan Ready

Create a rollback plan for the worst case before launch:

• Backup of the old website including database and files
• DNS configuration documented for quick rollback
• Communication plan for stakeholders in case of severe problems
• Escalation levels defined: At what traffic decline is the rollback triggered?

In practice: With careful planning, a rollback is necessary in fewer than 5% of cases. Nevertheless, it should be possible at any time.

Relaunch Communication: Properly Informing Customers and Partners

A website relaunch does not only affect your internal teams -- it has direct implications for customers, business partners, suppliers, and other stakeholders. A well-thought-out communication strategy ensures that all parties are informed, trust is maintained, and the relaunch is perceived as a positive signal.

Why Relaunch Communication Is So Important

According to a Bitkom study from 2025, 34% of all website relaunches in the DACH region fail not due to technical problems but due to 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 severe:

• Support requests increase by an average of 180% in the first two weeks after a poorly communicated relaunch
• Conversion rate drops temporarily by up to 25% when returning customers cannot find their usual workflows
• B2B partnerships suffer when API endpoints, product feeds, or partner portals are changed without warning
• Brand perception suffers when the relaunch is perceived 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, inform your most important stakeholders about the upcoming relaunch. For the Austrian market, personal outreach to key customers and partners is recommended:

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

Phase 2: Go-Live Communication (Day of launch)

On the day of the relaunch, communication should be proactive and multi-channel:

• 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 highlighting changes with a link to a help section
• Internal Slack/Teams message to all employees with support contact details

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

Follow-up care is frequently neglected but is crucial for long-term success:

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

Special Communication for Technical Stakeholders

If your website relaunch affects technical interfaces, developer teams at partner companies require special attention. In the DACH region, according to a survey by the Association of the Internet Industry, an average of 3.7 external systems work with a typical SME website.

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 still function

Prepare Crisis Scenarios

Even with the best planning, problems can occur on launch day. Prepare pre-written communication for every realistic scenario. This saves valuable time in emergencies and prevents thoughtless statements under pressure.

Create templates for:

• Planned maintenance windows and their extension
• Unexpected outages and their estimated resolution time
• Data migration issues that affect customers
• Feature limitations during the transition period

Relaunch Testing: Quality Assurance Before Go-Live

Quality assurance is the final and simultaneously most critical phase before go-live. An insufficiently tested relaunch can not only cost rankings but also permanently damage your users' trust. Systematic testing minimizes these risks to a manageable level.

The Test Pyramid for Website Relaunches

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

Level 1: Basic Technical Tests

These tests ensure 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 -- Ensure no duplicate content issues 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 tested:

• Forms -- Contact forms, newsletter sign-ups, login areas
• E-commerce functions -- Shopping 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 the currently relevant browser market shares:

• Chrome: 48.3%
• Safari: 27.1%
• Firefox: 8.2%
• Edge: 9.7%
• Samsung Internet: 3.4%

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

• Layout consistency -- No overlapping elements or clipped content
• Touch interactions -- Buttons and links must be easily operable on touchscreens (minimum size 44 x 44 pixels)
• Font rendering -- Web fonts correctly loaded and readable
• Image display -- Responsive images in correct resolution

Level 4: Performance Testing

Performance tests are crucial since Google uses Core Web Vitals as a ranking factor. Use the following tools and benchmarks:

• Google PageSpeed Insights -- Target: at least 90/100 for desktop and 75/100 for mobile
• WebPageTest -- Detailed waterfall analysis of page load 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, a load test with at least 3 times the expected peak traffic is recommended. Consider seasonal peaks such as Christmas season, Black Friday, or industry-specific high phases.

SEO-Specific Relaunch Tests

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

• Indexability -- Ensure the staging environment has `noindex` and the production environment allows `index`
• Structured data -- Validate all Schema.org markups with Google Rich Results Test
• Meta data -- Check title tags and meta descriptions on all pages
• Image alt texts -- Verify all images have meaningful alt attributes
• Internal linking -- Analyze link depth and ensure no important pages are orphaned
• Page speed comparison -- Compare loading 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. In the DACH region, however, according to a WKO survey, only 41% of SMEs work with a dedicated staging environment -- a risk factor you should definitely avoid.

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 correctly integrated
• Cookie banner and privacy policy are updated to GDPR compliance
• Contact details in the legal notice are correct (mandatory information under Austrian law)
• Backup of the old website is created and stored externally
• Rollback plan is documented and known to all parties
• 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 also permanently. Tools like Cypress, Playwright, or Selenium enable the creation of end-to-end tests that run automatically with every deployment.

Particularly effective is the combination of automated tests and visual regression testing. Tools like Percy or Chromatic create screenshots of all important pages with every build and compare them pixel-by-pixel with the previous version. This immediately detects unintended layout changes -- an enormous advantage for websites with hundreds of subpages.

Conclusion: Relaunch as an Opportunity, Not a Risk

A website relaunch does not have to be a nightmare. With the right planning, a complete URL mapping, clean 301 redirects, and structured post-launch monitoring, your relaunch will not only succeed without ranking loss but even improve your SEO performance.

The key takeaways:

1. Plan 3-6 months lead time for SEO safeguarding
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 preparation
5. Use the relaunch as an opportunity for better content and better technology

At GoldenWing, we have over 3 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.