Website Relaunch Without Losing Rankings

Website relaunch without ranking loss: The complete guide

A website relaunch is one of the riskiest undertakings in digital marketing. Done correctly, it can take your online presence to the next level. Done incorrectly, and you could lose rankings you've built up over years in just a few days. This guide will 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 the past three years. The experience gained from these projects – both successes and lessons learned – is incorporated 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 (purely visual) redesign, a relaunch typically includes changes to structure, technology, content, and design.

Types of relaunches

Important:The more things change, the higher the SEO risk. Therefore, plan more time for SEO security.

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.
• Despite optimization, the loading times are unacceptable.
• 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 was completely redesigned.
• Competitors have significantly better websites.
• The conversion rate stagnates despite optimization.
• Regulatory requirements (e.g., accessibility) necessitate fundamental changes.

Content reasons:

• The site 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're unsure whether a relaunch is the right path, we at GoldenWing offer a free initial consultation. A targeted approach is often worthwhile.Web design optimizationmore than a complete relaunch.

The relaunch checklist: Before, During, After

BEFORE the relaunch (3–6 months prior)

1. SEO audit of the existing website

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

• 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 based on traffic and rankings.
• Capture all incoming backlinks (Ahrefs, Majestic)
• Measure the current Core Web Vitals (Our guide will help)
• Check the current indexing (Google Search Console → Pages)

2. Create URL mapping

URL mapping is themost important documentYour relaunch. It maps each old URL to a new URL.

Rules for URL mapping:

• Every old URL with traffic or backlinks needs a 301 redirect.
• Pages with no traffic and no backlinks can be removed with a 410 (Gone) error.
• Avoid redirect chains (A → B → C, instead go directly A → C)
• Don't redirect everything to the homepage – Google interprets this as a soft 404 error.
• Test redirect mappings before going live

3. Content inventory and evaluation

Create a complete inventory list of all contents:

• Which pages are performing well? (Keep + optimize)
• Which pages have no traffic? (Consolidate or remove them)
• What 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)
• Identical server configuration as Production

DURING the relaunch (go-live)

1. Go-Live Checklist

• [ ] All 301 redirects are active and tested
• [ ] robots.txt updated (noindex removed from staging)
• [ ] XML sitemap updated and submitted to Search Console
• [ ] Canonical tags correct on all pages
• [ ] hreflang tags correctly (for multilingual pages)
• [ ] 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 a 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 migration

• Set TTL to 300 seconds (5 minutes) beforehand.
• Perform DNS change
• Monitor propagation (may take up to 48 hours)
• Run 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)
• Test 301 redirects on a sample basis
• Analyze server logs for 404 errors
• Monitor Core Web Vitals
• Verify conversion tracking
• Retest all forms

2. Short term (weeks 2–4)

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

3. Medium term (months 2-3)

• Detailed traffic comparison (month by month, year by year)
• Conversion rate analysis
• Ranking trends for top keywords
• Analyze Core Web Vitals Field Data
• Evaluate the content performance of the new pages

SEO during relaunch: 301 redirects and URL mapping

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

How to properly implement 301 redirects

A 301 redirect tells search engines: "This page has permanently moved." Google transfers the majority 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 should be replaced with 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 is on Home:Google interprets this as a soft 404.
5. Keep permanently:Leave 301 redirects active for at least 1 year, ideally permanently.

Optimize URL structure

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

Previous (typical problems):

• /index.php?page=services&id=42
• /2024/03/15/blog-post-title/
• /services/web-design/responsive-web-design-for-small-businesses/

Afterwards (optimized):

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

Best practices for URLs:

• Brief and descriptive (3–5 words)
• Lowercase letters 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 Toolhelps you check the technical SEO quality of your new website.

Content Migration: More Than Copy-Paste

Content migration is one of the most complex 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

Capture 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: Perform migration

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

Common migration errors

1. Change title tags:If a title tag ranks well, don't change it without a good reason.
2. Shorten content:Less content = fewer ranking signals
3. Internal links were forgotten:Old URLs in content links lead to redirect chains.
4. Do not migrate images:Alt tags and filenames are lost.
5. Structured Data forgotten:Schema markup must be adapted to new URLs.

Design relaunch vs. technical relaunch

Pure design relaunch

What's changing:Colors, typography, layout, images, animations

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

SEO risk:Low if the page structure and URLs remain identical

Typical problems:

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

Technical relaunch

What's changing:CMS, programming language, server, database

What should remain the same:URLs (where possible), content, page structure

SEO risk:Medium to High

Typical problems:

• URL structure changes due to 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 focus onmodern web design technologiessuch as Next.js and Payload CMS, which offer excellent SEO features and performance out of the box.

10 common relaunch mistakes

Based on over 3 years of experience at GoldenWing, we have repeatedly seen the following mistakes – and learned how 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 is being 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 and automatically test all redirects before go-live.

4. Internal links not updated

Consequence:Thousands of internal links lead via redirects – poor user experience and wasted crawl budget.

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

5. Content is migrated "on the side".

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

Solution:Content migration as a separate 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:Minimum 1 week of testing on staging with a checklist.

7. Go-live on Friday

Consequence:Problems are only discovered on Monday, leaving the area unmonitored for 3 days.

Solution:Go-live 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 to Search Console immediately after going live.

10. Performance ignored

Consequence:The new website is slower than the old one – Core Web Vitals are deteriorating.

Solution:Define the 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 for 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.

How much does a website relaunch cost?

Costs depend heavily on scope, complexity, and requirements. Here are realistic guidelines for the Austrian market.

Cost overview

What influences the costs?

For a detailed cost estimate, please also read our guide.How much does a professional website cost?.

Success measurement 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. 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 problems and their prioritization

SEO checklist for the relaunch

Finally, here's a compact checklist that you should work through during 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 correctly (multilingual)
• Schema markup implemented
• Core Web Vitals optimized
• Mobile display tested

Go-Live:

• DNS migration performed
• robots.txt updated (staging disallow removed)
• Sitemap submitted to Search Console
• all redirects are active
• Tracking codes verified
• SSL active, HTTP → HTTPS redirect

Post-launch:

• Check Search Console daily
• Fixing 404 errors
• Tracking rankings
• Monitor indexing progress
• Measuring performance
• Verify conversion tracking

Use ourSEO 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, including full URL mapping and 301 redirects, traffic loss should be less than 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'll see stabilization within 2–4 weeks and a recovery to pre-relaunch levels within 6–8 weeks. If the relaunch includes content optimization, rankings can even improve. The first 48 hours are critical – this is when it's 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 to Google Search Console as soon as the relaunch is live. If you're changing domains, use the "Change of Address" tool in Search Console. Google also recommends reporting URL changes via the URL Inspection API to speed up reindexing.

Can I change the URL structure during the relaunch?

Yes, that's actually one of the most common reasons for a relaunch. However, every URL change poses an SEO risk that must be mitigated with a 301 redirect. Only change the URL structure if there's a clear benefit (better readability, a more logical hierarchy, locale prefixes). Never change URLs "just because that's what everyone does."

What to do if rankings plummet after the relaunch?

Stay calm and proceed systematically: (1) Check Search Console for crawl errors – are there any 404 errors? (2) Check redirects – are they all working correctly? (3) Check canonical tags – are they pointing to the correct URL? (4) Compare content – has the content of the 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 usfor an emergency analysis.

Should I handle the relaunch internally or hire an agency?

That depends on your internal resources. For a simple design relaunch with just a few pages, an internal team might suffice. For a complete relaunch involving URL changes, content migration, and SEO optimization, we recommend collaborating with an experienced agency. At GoldenWing, we guide you through the entire process – from the initial planning stages to the final implementation.SEO analysis about the web designuntil the technical implementation.Contact usfor a free initial consultation.

Stakeholder management during a website relaunch

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

Identify 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 groups, conversion goals, and content requirements.
• IT/Technology:Responsible for hosting, integrations and technical implementation
• Customer service:Knows the most frequently asked user questions and pain points
• External partners: Agency, freelancer, hosting provider

The RACI matrix for relaunch projects

For each project phase, clearly define whoResponsible (responsible), Accountable(accountable),Consulted(to question) andInformed(to inform) is.

Example of content migration:

• Responsible: Marketing Team
• Accountable: Project Manager
• Consulted: SEO agency, sales
• Informed: Management, IT

Create a communication plan

Establish regular communication rhythms:

• Weekly status meeting(30 minutes) with the core team
• Bi-weekly reportto the management
• Milestone Reviewsat critical points (design approval, content freeze, go-live decision)
• Escalation pathfor blockers and conflicts

Typical conflicts and their solutions

Conflict 1: Design vs. SEO

The marketing department 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 sufficient indexable text.

Conflict 2: Feature Creep

New requests keep arising during the project.Solution:Maintain a feature backlog and prioritize accordingly.MoSCoW principle(Must, Should, Could, Won't). Everything that is not a "Must" will come in Phase 2 after the launch.

Conflict 3: Timeline pressure

Management is setting 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 theinternal trainingEmployees who work with the website daily (content maintenance, form processing, analytics) need to be familiar with the new system. Plan for at least...2-3 training daysand create internal documentation.

Performance optimization: Use the relaunch as a speed boost

A relaunch is the perfect opportunity to...To fundamentally improve website speedStudies show that improving loading time by just one second increases the conversion rate by7%can increase.

Hosting upgrade as a foundation

The relaunch is the ideal time to switch hosting providers. For Austrian websites, we recommend:

• Shared hosting (5-15 euros/month):Only for small business websites with low traffic
• Managed WordPress Hosting (25-80 Euro/month):Ideal for most SME websites
• VPS/Dedicated (from 50 Euros/month):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 audience.

Image optimization during the relaunch

Taking pictures takes an average amount of time50-65% of the side weightout. During the relaunch, you should:

• Convert all images to WebP/AVIF-- Savings of 25-50% compared to JPEG
• Responsive ImagesImplement with srcset -- different sizes for different screens
• Lazy Loadingfor all images below the visible area
• Image compressionautomate with tools like Sharp, Squoosh, or TinyPNG
• Define maximum width:No images wider than 1920px; 800-1200px is sufficient for most elements.

Critical CSS and code splitting

ImplementCritical CSSThe CSS code for the visible area is loaded inline in the HTML, the rest asynchronously. This improves theLargest Contentful Paint (LCP)significant.

For JavaScript, useCode Splitting:

• Only load the code that is needed on the current page.
• Use dynamic imports for components below the fold.
• Eliminate unused JavaScript (tree shaking)

Caching strategy

When relaunching, configure a well-thought-out caching strategy:

• Browser caching:Static assets (CSS, JS, images) with long cache durations (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

Define performance budget

Establish binding performance budgets before the relaunch:

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

Integrate performance tests into yourCI/CD pipeline, so that new deployments do not exceed the budgets.

Domain change during relaunch: Special features and risks

A relaunch combined with a domain change is theriskiest optiona website relaunch. Google itself states that a domain change can lead to a temporary loss of ranking.10-30% over 3-6 monthscan lead to this.

When a domain change makes sense

• Rebranding:The company is changing its name or repositioning 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 switch)

• Completely crawl and document all existing URLs of the old domain.
• Create redirect mapping: Each old URL must be assigned to a new URL.
• Set up and verify Google Search Console for the new domain
• Analyze backlink profile and identify important link providers

Step 2: Technical Implementation

• 301 redirectsSet it up at the server level (not via JavaScript or meta-refresh)
• Canonical TagsSet correctly on the new domain
• Hreflang tagsUpdate if multilingual versions exist
• Internal linksOn the new page, everyone must point to the new domain.

Step 3: Inform Google

• Request an address change in the Google Search Console (under "Settings" > "Address Change")
• Submit a new sitemap under the new domain
• The old domain mustat least 6 monthscontinue delivering the 301 redirects -- ideally12 months or longer

Step 4: External Signal Management

• Contact theTop 20 Link Providersand request that the links be updated
• Update allSocial media profiles, Google Business Profile and industry directories
• AdaptEmail signatures, business cards and printed materials to

Common mistakes when changing domains

• Shut down old domain too early:The redirects must remain active for at least 12 months.
• Chain redirects:The old domain redirects to an intermediate page, which then redirects again -- a maximum of one redirect per URL.
• Ignore HTTP vs. HTTPS:All four variants (http://old, https://old, http://new, https://new) must redirect correctly.
• Forgot 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 the go-live.first 90 days after the relaunchare crucial for long-term success. A structured monitoring program helps you to identify and resolve problems early on.

Week 1: Daily monitoring

In the first week after launch, you shoulddailyCheck the following points:

• Crawl errorIn Google Search Console: 404 errors, server errors, redirect loops
• Indexing status:Will the new pages be indexed? Will old pages be deindexed?
• Core Web Vitals:Do the performance figures hold up under real-world conditions?
• Conversion tracking:Are all forms, checkout processes, and tracking codes working correctly?
• Server logs:Unusual access patterns, high error rates, bot activity

Weeks 2-4: Weekly monitoring

• Organic TrafficCompared to the previous month and year (Google Analytics)
• Keyword rankingsfor the top 50 keywords (Sistrix, Ahrefs or SEMrush)
• Impressions and clicksin the Google Search Console
• Bounce rate and dwell timeon the most important landing pages
• Indexed pages:The number should approach the target number.

Months 2-3: Bi-weekly monitoring

• Backlink profile:Will links be transferred to the new URLs?
• Crawl budget:How efficiently does Google crawl your new website?
• Conversion ratecompared to pre-relaunch values
• Page speed trends:Do the scores worsen due to new content?
• A/B testsfor critical landing pages

Typical ranking trend after a relaunch

Expect the following course of events in a well-executed relaunch:

• Week 1-2:Slight ranking decline of 5-15% (normal, Google evaluates the new structure)
• Weeks 3-6:Stabilization; initial rankings return to pre-relaunch levels.
• Month 2-3:Rankings reach or exceed previous levels
• Months 4-6:A clear upward trend is due to improved technology and content.

Warning signal: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

Create a before launchRollback planFor the worst-case scenario:

• Backup of the old websiteincluding database and files
• DNS configurationDocument it so you can switch back quickly.
• Communication planfor stakeholders in case of serious problems
• Escalation levelsDefine: At what traffic decline will the rollback be triggered?

In practice, it turns out that with careful planning, a rollback is possible.in less than 5% of casesnecessary. Nevertheless, it should be possible at any time.

Relaunch communication: How to properly inform customers and partners

A website relaunch doesn't just 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

According to aBitkom studyBy 2025, 34% of all website relaunches in the DACH region will fail not due to technical problems, but due to inadequate communication. Customers can no longer find familiar functions, partner companies can no longer access shared resources, and internal staff are not adequately trained.

The consequences can be serious:

• Support requests are increasingby an average of 180% in the first two weeks after a poorly communicated relaunch
• Conversion rate is decreasingtemporarily by up to 25% if regular customers cannot find their usual workflows.
• B2B partnerships are suffering, if API endpoints, product feeds or partner portals are changed without prior notice
• Brand perception suffers, if 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, you inform your key stakeholders about the upcoming relaunch. For the Austrian market, a [method/approach] is recommended.personal addresswith key customers and partners:

• Key accounts and A-customersPersonal call or meeting with the responsible account manager
• B2B partners and suppliersFormal letter with detailed information about changes that affect them
• Existing customers (B2C)Newsletter announcement with a hint of upcoming improvements
• Internal staffKick-off meeting with training plan and FAQ document
• Press and trade mediaPrepare a press release, but only send it shortly before going live.

Phase 2: Go-Live Communication (Launch Day)

On the day of the relaunch, communication shouldproactive and multi-channel take place:

• Email Blastto all registered users with the most important changes
• Social media postson all relevant channels (LinkedIn is particularly important for the DACH B2B sector)
• Banner on the new websiteincluding information about changes and a link to a help section
• Internal Slack/Teams messageto all employees with support contact details

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

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

• Collectactive feedbackvia surveys, support tickets and social media monitoring
• PublishFAQ Updatesbased on the most frequently asked questions
• Send aFollow-up emailwith tips on new features and functions
• CreateVideo tutorials or Guided Toursfor complex areas such as customer portals or online shops

Special communication for technical stakeholders

If your website relaunch involves technical interfaces, development teams at partner companies require special attention. According to a [source/source], in the DACH region [number]...Survey by the Association of the Internet IndustryOn average, 3.7 external systems are used in conjunction 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 when old interfaces will still work

Preparing for crisis scenarios

Even with the best planning, problems can arise on launch day. Prepare a contingency plan for every realistic scenario.pre-packaged communicationThis saves valuable time in an emergency and prevents rash statements under pressure.

Create templates for:

• Planned maintenance windows and their extension
• Unexpected outages and their expected repair time
• Data migration problems affecting customers
• Functional limitations during the transition phase

Relaunch testing: Quality assurance before go-live

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

The testing pyramid for website relaunches

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

Stage 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 accessibility (Tools: Screaming Frog, Sitebulb)
• 301 Redirect Validation— Test each individual redirect from the redirect map
• SSL certificate— Verify correct installation and validity
• robots.txt and Sitemap— Check for correctness and completeness
• Canonical Tags— Ensure that no duplicate content issues arise
• hreflang tags— Especially important for multilingual DACH websites (de-AT, de-DE, de-CH)

Stage 2: Functional Tests

Here, all interactive elements of the website are checked:

• Forms— Contact forms, newsletter subscriptions, login areas
• E-commerce features— Shopping cart, checkout, payment processing, order confirmations
• Search function— Test internal search for relevance and completeness
• Filters and sorting— Especially in 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 ofStatCounter dataFor Austria, the currently relevant browser market shares are shown:

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

Test your website at least in theTop 4 browsersand on the most common device types (desktop, tablet, smartphone). You should pay particular 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)
• Text display— Webfonts loaded correctly and are readable
• Image display— Responsive images in correct resolution

Stage 4: Performance Testing

Performance testing is crucial because Google uses Core Web Vitals as a ranking factor. Use the following tools and benchmarks:

• Google PageSpeed Insights— Target value: at least 90/100 for desktop and 75/100 for mobile
• WebPageTest— Detailed waterfall analysis of sideload behavior
• Lighthouse CI— Automated performance checks in the CI/CD pipeline
• Load tests— Simulate expected traffic spikes with tools like k6 or Apache JMeter

For Austrian websites, a load test with at least the following is recommended:3 times the expected peak trafficTake into account seasonal peaks such as Christmas shopping, Black Friday, or industry-specific peak periods.

SEO-specific relaunch tests

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

• Indexability— Ensure that the staging environment is set to `noindex` and the production environment allows `index`.
• Structured Data— Validate all Schema.org markups with the Google Rich Results Test
• Metadata— Check title tags and meta descriptions on all pages
• Image alt text— Check that all images have meaningful alt attributes.
• Internal linking— Analyze the link depth and ensure that no important pages are orphaned.
• Page speed comparison— Compare the loading times of the new page with the old one and document any improvements or deteriorations.

Staging environment and pre-live checklist

One production-like staging environmentis indispensable for professional relaunch testing. According to aWKO surveyHowever, only 41% of SMEs have 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.
• The Google Analytics / Matomo tracking code is correctly integrated.
• Cookie banner and privacy policy have been updated to comply with GDPR.
• The contact details in the legal notice are correct (mandatory information according to Austrian law).
• A backup of the old website has been created and stored externally.
• The rollback plan is documented and known to all parties involved.
• DNS TTL was set to a low value 48 hours before the relaunch.

Automated testing for sustainable quality

Modern relaunch projects rely onautomated test suites, which ensure quality not only before go-live, but also continuously. Tools such asCypress,Playwright or Seleniumenable the creation of end-to-end tests that run automatically with every deployment.

The combination of automated tests andVisual Regression TestingTools such asPercy or ChromaticWe create screenshots of all important pages with every build and compare them pixel-perfectly with the previous version. This allows us to immediately detect unintentional layout changes—a huge 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 proper planning, complete URL mapping, clean 301 redirects, and structured post-launch monitoring, your relaunch will not only succeed without ranking loss, but will even improve your SEO performance.

The most important takeaways:

1. Plan for 3–6 months lead timefor SEO protection
2. The URL mapping is your most important document.– invest the necessary time
3. 301 redirects are mandatoryfor each URL with traffic or backlinks
4. Post-Go-Live Monitoringis at least as important as the preparation
5. Use the relaunch as an opportunityfor 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 initial analysis to the successful go-live – and beyond.Contact usfor your relaunch project.

Planning a website relaunch? Our Web Design Agency in Vienna guides you from concept to go-live.