AI Search
Capabilities
Methods
Capabilities
Technologies
Capabilities
Tools
Capabilities
Capabilities
Technologies
Capabilities
Engagement Models
Capabilities
Frameworks
Capabilities
Technologies
Capabilities
Technologies
Capabilities
Technologies
Capabilities
Technologies
Capabilities
Search Solutions
For Commerce
Silk Design System
AI Product Discovery
For other industries
Case studies
Scaling Core Apps For Delivery Hero, Local Delivery & Q-Commerce Giant
How Vinted Expanded its Global Marketplace with On-Demand Team Extension
Other projects
Learn more
Join Netguru
Blog
Overcoming Integration Challenges in Super App Development
Building Data Foundations: The Key to Scalable Enterprise AI
Newsletters and originals
Most website redesigns fail not on aesthetics but on execution risk: traffic drops, broken redirects, and blown timelines that could have been avoided with a proper migration plan. For a CTO or VP Engineering, the real decision isn’t whether the new design looks better; it’s whether the team can replatform, restructure information architecture, and cut over DNS without losing a quarter’s worth of organic rankings.
This guide breaks down the decision, the process, and the safeguards that keep a redesign from becoming a traffic incident. Beyond redirects and rankings, it’s also worth auditing subtle UX design choices that quietly shape how users engage with the redesigned site.
Most website redesign projects lose organic traffic and revenue in the first 90 days after launch, not because the new design is weaker, but because nobody mapped 301 redirects or checked Core Web Vitals before cutover (Shopify Blog). That is the real decision on the table.
It should be grounded in a broader web strategy playbook rather than treated as a one-off design refresh.
In our work with enterprise clients including the Cardano Foundation, a design-to-code rebuild built around this process drove 20% growth in engaged sessions. The migration discipline mattered more than the visual refresh itself. This matters even more when modernizing legacy ecommerce platforms, where migration discipline directly determines whether the rebuild protects existing revenue.
Three calls to make before you start:
Quick win: pull your current sitemap and Search Console URL list today, before any design work starts.
A website redesign rebuilds a site’s information architecture, visual design, and front-end code together, not a theme swap or a copy refresh. It changes how users navigate, how content is structured, and frequently which CMS renders it.
Three layers move at once: information architecture (how pages, content, and navigation groups are organized), the design system (typography, components, brand), and the platform itself, increasingly a headless CMS such as Contentful, Storyblok, or Webflow rather than a traditional WordPress install with a template layered on top.
That platform shift matters for performance and marketing agility, not just aesthetics. According to web.dev’s Core Web Vitals guidance, a good Interaction to Next Paint score is 200ms or under, a bar most five-year-old sites miss well before any visual work starts.
In our own project audits, information architecture rework, not visual design, consumes most of the engineering timeline once a redesign moves from Figma into build. That’s the part teams underestimate, and it’s the part that determines whether SEO holds.
A website redesign, a website refresh, and a replatform get treated as interchangeable projects, and that confusion is what blows budgets and timelines. Each moves a different layer of the site, and picking the wrong one is the single biggest scoping mistake we see on new engagements.
A refresh touches visual design only, typography, imagery, color, maybe a component library update, while the information architecture and CMS stay put. A replatform swaps the underlying CMS or tech stack (WordPress to a headless CMS like Storyblok or Contentful, for instance) without necessarily changing the front-end design at all.
A full redesign changes architecture, design, and code together, which is why it carries the most SEO and UX risk.
Going headless (Storyblok, Contentful, or a Webflow hybrid) is usually the right call when marketing needs to ship landing pages without an engineering ticket, or when the same content feeds a website, an app, and a partner portal. It is the wrong call if your team has no appetite for managing an API layer and a separate front end.
Our rule in Netguru engagements: if the audit shows the IA still works and users aren’t getting lost, don’t redesign: refresh or replatform instead, and save the full rebuild for when navigation and conversion paths are genuinely broken.
A website redesign is worth the disruption when two or more of these signals show up together, not when one metric dips for a week. Track them across desktop and mobile, since visitors on different devices often hit different thresholds first.
Core Web Vitals fail on real user data. If field data shows INP past 200ms, LCP past 2.5 seconds, or CLS above 0.1 on your core templates, per web.dev’s Core Web Vitals thresholds, copy edits and plugin fixes won’t move the number. Rebuilding the front end is usually the fix.
Information architecture no longer matches how users actually behave. Nielsen Norman Group’s redesign research consistently finds navigation and findability failures behind most usability breakdowns in redesign audits. If your IA still mirrors a product line from three years ago, users are working around the site instead of through it.
Bounce rate on key landing pages sits above 60% while session duration keeps falling. Pair that with a conversion rate that’s dropped 20% or more year over year even as GA4 shows traffic holding steady. That split is a UX problem, not an SEO one, and no amount of new content fixes it.
Mobile conversion trails desktop by a wide margin, often 30% or more, despite mobile visitors making up over half of total traffic. That gap points to responsive designs that were patched together rather than built for touch from the start.
Marketing can’t ship a landing page or campaign without an engineering ticket. That’s a CMS ceiling, not a workflow gap, and it’s usually the trigger for a headless CMS move.
Accessibility gaps under WCAG 2.2, keyboard traps, missing focus states, unlabeled forms, carry legal exposure beyond design taste. Ensure every core template passes an automated and manual audit before you scope the rebuild.
A stale visual system next to your closest competitor is real, but it’s the weakest signal alone. Pair it with one of the above before committing to a comprehensive website design overhaul, since a redesign website project touches far more than the surface layer.
A website redesign moves through nine stages: audit, goals and KPIs, information architecture, UX/UI design, build, migration, SEO preservation, launch, and measurement. Treat each stage as a gate, not a checklist item, skipping migration or SEO preservation to save two weeks is how a redesign loses the organic traffic it started with.
Before committing to these nine stages, make sure the signals it’s time for a redesign are actually present rather than assumed.
1. Audit. Crawl the existing site, pull real-user Core Web Vitals data, and export the full URL inventory. This becomes the baseline every later decision gets measured against, including the redirect map in step six. If the redesign involves a domain change or platform switch, planning a website migration properly at this stage prevents costly rework later.
2. Goals and KPIs. Set targets in GA4 before anyone touches design, engaged sessions, conversion rate, assisted revenue, so the redesign has a scoreboard, not just a launch date. In GA4’s benchmarking reports, benchmarking data is only available when the selected date range is less than 60 days; if the date range includes the current date or covers a period of 60 days or more, no benchmarking data is shown
3. Information architecture. Rebuild navigation and content groupings before opening a design tool. Information architecture decided after the visual design is locked is the most common rework we see on rescue projects, it should drive the design, not follow it.
4. UX/UI design. This is where Figma and a documented design system earn their keep: components, states, and WCAG 2.2 accessibility patterns defined once and reused across every template instead of redrawn per page. On the Cardano Foundation redesign, a tight Figma-to-code handoff and a shared design system got the site from prototype to launch fast, with a 20% lift in engaged sessions afterward, largely from cutting the drift between what was designed and what actually shipped.
5. Build. Development happens against the new information architecture and design system, on a headless or traditional CMS depending on how much editorial independence marketing needs day-to-day.
6. Migration. Every old URL gets mapped to its 301 destination and tested on a staging environment before DNS cutover. In our own pre-launch crawls, staging audits routinely catch broken canonicals, incorrect redirect targets, and unmapped legacy URLs that never made it into the original migration plan, the kind of gap that shows up as a traffic cliff two weeks after go-live if nobody catches it first.
7. SEO preservation. Canonical tags, XML sitemaps, and structured data get re-verified against the new templates, not copied from the old ones and assumed to still be correct.
8. Launch. DNS cutover happens in a low-traffic window, with real-user INP staying under 200 milliseconds on core templates monitored from hour one, per web.dev’s Core Web Vitals guidance.
9. Measure. GA4 benchmarking against the pre-launch baseline, then A/B testing to tune what the redesign actually changed, starts once traffic stabilizes, usually one to two weeks post-launch.
Most redesigns lose organic traffic in the first 90 days after launch, and the cause is almost always an incomplete 301 redirect mapping, not the new design itself. Skip the mapping and Googlebot rediscovers your site as if it were new, which resets the authority signals your old URLs had built up.
Build the redirect map before a single line of the new front end ships. Crawl the live site, export every indexed URL from Google Search Console and your XML sitemap, and pair each one to its exact destination on the new information architecture. One-to-one 301s preserve link equity; 302s or catch-all redirects to the homepage do not, and Google’s site-migration guidance treats them very differently for reindexing speed.
On a recent migration, our QA pass on the redirect map caught Polpharma API worked with Netguru: How Polpharma leveraged Webflow for rapid deployment, scalability, and easy maintenance. before launch, the kind of gap that only surfaces once you crawl the staging environment the same way Googlebot will crawl production.
Run that crawl against a full staging environment, not a local build. Check canonical tags resolve to the new domain, confirm robots.txt isn’t blocking the new site by accident (a common last-minute error), and validate structured data survives the template change.
Instrument GA4 before cutover, not after. Set up the new site’s GA4 property against the same conversion events and audiences as the old one, so day-one traffic drops show up as real anomalies rather than tagging gaps.
On our Cardano Foundation engagement, we shipped design-to-code migration through this same staging-and-redirect discipline and grew engaged sessions 20% post-launch, evidence that SEO-safe migration and a stronger user experience aren’t a tradeoff. Watch GA4 daily for the first two weeks; a redirect mapping gap usually shows up as an organic-traffic cliff within 72 hours, and it’s far cheaper to fix on day three than to diagnose three months later.
Core Web Vitals thresholds and WCAG 2.2 accessibility criteria need to sit inside the build’s acceptance tests, not a pre-launch audit bolted on afterward. Treat both as constraints from sprint one, because retrofitting either after launch costs more engineering time than designing against them from the start.
INP (Interaction to Next Paint) replaced First Input Delay as the responsiveness metric in Core Web Vitals, and it is the one most redesigns get wrong because heavy client-side hydration on a new front end tanks it. According to web.dev’s Core Web Vitals thresholds, a good INP score sits at or below 200 milliseconds, LCP needs to land under 2.5 seconds, and CLS should stay below 0.1, all measured at the 75th percentile of real user sessions rather than lab data.
WCAG 2.2, formalized by the W3C, adds success criteria many redesigns still miss: focus-not-obscured, dragging alternatives, and a 24-by-24 pixel minimum target size for interactive elements. An overlay widget bolted onto a legacy site will not satisfy these. They need to be built into the component library and design system before development starts, not patched in after QA flags them.
On the Cardano Foundation engagement, our team rebuilt the design-to-code pipeline against WCAG 2.2 and Core Web Vitals budgets from the first sprint rather than auditing after the fact. Engaged sessions grew 20% post-launch, evidence that accessibility and performance work compound rather than compete for the same engineering time.
Bake both into your design system’s component specs, and QA against them on every staging deploy, not just before launch.
AI-assisted design and content workflows compress the path from concept to shipped page in a 2026 website redesign, reducing manual handoffs between design and code. Teams draft component variants in Figma using plugins like Diagram or Builder.io, generate content-model schemas for a headless CMS, and let editors polish AI-drafted copy instead of writing every field from scratch.
A design system is what makes this work rather than produce inconsistent output. When token libraries, spacing rules, and component states are documented before generation starts, AI suggestions inherit brand and visual constraints automatically. Without that system, teams spend more time correcting drift than they saved generating it.
Tool choice matters, but guardrails matter more.
Any redesign vendor using AI copy tools should run generated content through three checks before it reaches visitors: a fact-check pass against source material, a brand-voice review against your style guide, and a mobile readability scan, since AI drafts often produce paragraphs too dense for small screens. Skipping these steps is how comprehensive redesigns ship inconsistent, unverified copy at scale.
On the Cardano Foundation engagement, our design-to-code workflow, built on a shared design system feeding directly into headless CMS templates, lifted engaged sessions by 20% after launch. We attribute this to fewer translation errors between design intent and shipped markup.
The practical question for a CTO evaluating a redesign vendor is simple. Does their design process output a design system your engineering team can consume programmatically, or a folder of static designs someone has to rebuild by hand? That one answer predicts most of the build-phase friction ahead, and it’s a key signal of whether a redesign website project will stay on schedule.
A mid-market website redesign typically runs $25,000-$120,000 and takes 8-16 weeks; a full replatform onto a headless CMS with custom integrations pushes both figures higher, often into the $150,000+ and 20+ week range. Scope, not headline price, is what actually moves these numbers.
Three variables decide where a project lands: page count and content migration volume, the number of third-party integrations (CRM, PIM, marketing automation), and whether the CMS itself changes.
Replatforming to a headless CMS such as Contentful or Storyblok adds cost because content models, API contracts, and preview environments have to be built from scratch, not just re-skinned. We generally see 30-40% of a replatform budget go to migration and integration work rather than visual design.
WordPress-to-headless moves cost more up front than staying on a traditional CMS, but teams report lower long-term maintenance overhead once the content layer is decoupled from presentation.
For Webflow specifically, pricing follows a different logic: plan tiers, apps, and hosting stack differently than a custom build. Our Webflow pricing breakdown covers that in detail if Webflow is on your shortlist.
Treat any quote below these ranges as a signal to ask what SEO preservation and cross-browser QA actually include, since those two line items are where budgets and timelines quietly slip.
Most website redesigns lose organic traffic because 301 redirect mapping gets treated as a launch-week checklist item instead of a pre-launch output planned alongside information architecture.
Working with Harmonya, Netguru caught redirect mapping errors, 404s, redirect chains, and orphaned canonical tags during a staging crawl, issues that would have silently reset rankings within days of DNS cutover had they shipped. That is the pattern behind most traffic drops: not a bad redesign, an unverified migration.
Four mistakes account for most of the post-launch damage we see on audits:
According to Google Search Central’s site-move documentation, Google typically needs several weeks to recrawl and reprocess migrated URLs, longer when redirect chains or unmapped pages force it to rediscover content from scratch. Plan the QA window around that reality, not around launch day.
B2B website redesigns answer a different question than B2C ones: not “will this visitor buy today” but “will this visitor remember us in month four of a nine-month sales cycle.” That changes what the redesign has to optimize for.
Information architecture carries more weight here than almost any other decision. A B2B site typically routes a single buying committee, IT, finance, procurement, end users, through different content paths before anyone talks to sales. Gated content (whitepapers, ROI calculators, case studies) needs its own IA layer, separate from top-of-funnel marketing pages, or you end up hiding bottom-funnel assets behind the same navigation logic built for awareness traffic.
GA4 event tracking has to reflect that reality too. Attribution set up around last-click sessions undercounts every B2B redesign, because the buyer who converts in month four rarely converts on the visit where they downloaded the case study.
We set up GA4 to track micro-conversions, whitepaper downloads, pricing page returns, demo requests, as separate funnel stages, not one blended “lead” event, so post-launch reporting doesn’t quietly erase the assisted conversions that justified the IA changes in the first place. On the Cardano Foundation redesign, restructuring the information architecture around technical documentation and grant pathways, rather than a generic marketing funnel, lifted engaged sessions 20% (Netguru – Rapid Website Redesign for a 24% Increase in Traffic).
DIY works when the redesign is a template swap on a low-traffic marketing site; hire an agency when the redesign touches information architecture, headless CMS migration, or WCAG 2.2 compliance across more than a few hundred URLs. The line is complexity, not budget, especially when managing digital infrastructure.
Builders like Webflow suit teams that want visual control without a full engineering build, and pair well with A/B testing tools for iterating on conversion pages post-launch. Contentful and Storyblok fit better once content operations span multiple brands, locales, or product lines and marketing needs to publish without waiting on a developer for every change.
Netguru works across all three, choosing the CMS based on the client’s content model and team structure rather than defaulting to one platform.
Before you scope either path, run this checklist:
For the full build-stage version of this list, see our web development checklist.
Whether you’re weighing a full replatform or a lighter website redesign, the outcome hinges on who has mapped the migration before, not just who draws the mockups. Our team took Cardano Foundation’s design-to-code rebuild live and saw a 20% increase in engaged sessions, with redirect mapping and Core Web Vitals audits built into the plan from day one, not bolted on after launch.
That played out at SummaSoft by Aurea: SummaSoft now has a radically improved design and new features to support remote and hybrid work, enabling companies to keep teams connected and engaged. shows the same principle at enterprise scale: prioritizing user journeys and self service flows does more for retention than a visual refresh alone.
Technical decisions matter too: modern frontend architecture choices, from rendering strategy to component frameworks, can determine how resilient the new build is to future redesigns.
If you’re scoping a website redesign, a site rebuild, or new design services altogether, our Experience & Design team, running our own Silk design system, can help you improve your product’s UX.
Kacper is a seasoned growth specialist with expertise in technical SEO, Python-based automation, and data-driven digital marketing.
Karina Graj
Mary Achinger
Mary Achinger
Mary Achinger
Mary Achinger
At Netguru we specialize in designing, building, shipping and scaling beautiful, usable products with blazing-fast efficiency.
Let’s talk business
©2026 Netguru S.A. All rights reserved.
