Planning a Website Redesign for Next Year? Start Here.

A website redesign is one of the biggest investments a business can make in its digital presence — and one of the easiest to get wrong. Rushed timelines, unclear goals, and last-minute scope changes are the most common reasons redesigns run over budget, miss deadlines, or fail to move the needle on traffic and conversions.

If a redesign is on your roadmap for next year, the work that matters most happens now, months before a single wireframe gets drawn. Here’s how to plan it right, and how a full-board digital marketing strategy keeps all the moving pieces connected instead of siloed.

Redesign or Refresh? Know Which One You Need

Not every website problem calls for a full rebuild. A refresh is cosmetic: new fonts, updated photography, a cleaner color palette, refreshed copy on a handful of pages. Your navigation, site structure, and backend stay largely untouched. A redesign goes deeper — it can touch your information architecture, your user experience, your CMS or hosting, and your entire visual identity at once.

Knowing which one you actually need up front prevents two common mistakes: overspending on a full rebuild when a targeted refresh would solve the problem, or underscoping a redesign as a “quick refresh” and hitting structural issues halfway through.

Comparison: Refresh vs. Redesign

Factor	Refresh	Redesign
Scope	Visual updates, select pages	Structure, UX, CMS, full identity
Navigation & IA	Largely untouched	Often rebuilt
Typical timeline	Weeks	Months
Best when…	Structure still serves your goals	Structure works against your goals

Signs You Actually Need a Redesign

A few warning signs tend to show up together when a site has outgrown its current build:

• Bounce rate has been climbing for months with no clear, isolated cause
• The site still carries design patterns from several years ago and visitors notice
• Mobile experience feels like an afterthought rather than the primary way most visitors arrive
• Load times and Core Web Vitals scores lag behind competitors in the same market
• Content, services, or branding have changed enough that the site no longer reflects the business
• Staff can’t easily update pages without developer help
• Accessibility complaints or barriers have surfaced from customers or staff

Start With Why, Not What

Before talking colors, layouts, or platforms, get specific about the problem you’re solving. “Our site looks dated” is a reason to redesign, but it’s not a strategy. Dig deeper:

• Is the site failing to convert visitors into leads or sales?
• Has your brand or product line changed since the last build?
• Are you losing organic traffic to competitors with better content or technical SEO?
• Is the site hard to update, slow to load, or broken on mobile?
• Are sales, marketing, and customer service using the site the way they need to?

Each of these points to a different set of priorities. A conversion problem calls for a redesign focused on user flows and calls to action. A technical SEO problem calls for a rebuild focused on site structure and page speed. Naming the actual problem keeps the project from turning into a purely cosmetic refresh that leaves the real issues untouched.

Set Measurable Goals Before You Set a Budget

Once you know why you’re redesigning, define what success looks like in numbers.

6–12 Mo. Window to track organic traffic growth post-launch

30–60 Days Critical window for catching post-launch SEO or functionality issues

4 Metrics Traffic, conversions, Core Web Vitals, bounce rate to baseline first

• Organic traffic growth within 6 and 12 months post-launch
• Conversion rate on key pages (contact forms, quote requests, checkout)
• Page load speed and Core Web Vitals scores
• Bounce rate on landing pages
• Time to complete common user tasks (finding a service, requesting a quote, checking pricing)

Baseline these metrics on your current site before the redesign starts. A marketing performance audit is the fastest way to get an accurate “before” snapshot across traffic, rankings, and conversions. If your business depends on customers finding you nearby, baseline your local search visibility too, since redesigns can quietly disrupt local rankings if location pages and schema aren’t carried over carefully.

Research Your Users and Your Competitors

Design decisions made without research tend to reflect internal preferences rather than what actually moves visitors to act. Before wireframes start, build out:

User personas. Identify your primary customer segments and the specific tasks they come to the site to complete. A customer searching urgently has different needs than one comparing options for a project next spring.

Journey maps. Walk through how each persona currently moves through the site, where they get stuck, and where they drop off. Analytics data on exit pages and scroll depth backs this up with evidence instead of assumptions.

Competitive design research. Review how competitors in your market structure their sites, present pricing or services, and handle calls to action. The goal isn’t to copy them — it’s to spot what’s become table stakes in your industry and where there’s room to differentiate.

Protect Your SEO Equity

This is where redesigns most often go wrong. A site can look beautiful and still lose most of its organic traffic within weeks of launch if SEO isn’t part of the planning process from day one, not bolted on at the end.

A full URL inventory. Every indexed page on the current site needs a plan: keep it, merge it, or redirect it. Skipping this step is the single most common cause of post-launch traffic drops.

A 301 redirect map. Every old URL that changes or disappears needs a redirect to its closest equivalent on the new site. Redirect to the homepage as a last resort only — a mismatched redirect target can hurt rankings almost as much as no redirect at all.

A content audit. Identify which existing pages rank well and drive traffic or leads. That content and its underlying SEO signals — headings, internal links, metadata — need to carry over intentionally, not get rewritten from scratch by a designer who’s never seen the analytics.

A revisited site structure. Redesigns are the natural point to fix a messy site architecture, but restructuring without a plan for how link equity flows between old and new pages is a common way to lose rankings even when content quality improves. Design and SEO decisions on a redesign are more connected than most businesses expect — see how website design doubles as an SEO weapon for more on that overlap.

Technical SEO requirements for the new build. Structured data, XML sitemaps, canonical tags, and crawlability should be requirements in the project scope, not an afterthought during QA.

Meet 2026 Accessibility Standards

Accessibility is no longer a nice-to-have layered on at the end of a project. Meeting WCAG 2.2 AA guidelines is now standard practice for most redesigns, and the legal exposure for non-compliant sites has grown substantially — accessibility-related lawsuits have been climbing fast, and older or poorly-built sites are common targets.

Build accessibility requirements into the project scope from the start rather than testing for compliance after launch:

• Color contrast ratios that meet WCAG 2.2 AA thresholds
• Full keyboard navigability, not just mouse and touch
• Descriptive alt text and properly structured headings for screen readers
• Accessible form labels and error messaging
• Captions or transcripts for video content

Build a Realistic Timeline

Most redesign timelines fail because they only account for design and development time, not for the internal review cycles, content production, and QA rounds that surround them.

A Realistic Redesign Timeline

Phase	Duration	Covers
Discovery & research	2–4 weeks	Goals, personas, competitive analysis, IA
Content & copywriting	4–8 weeks	New/updated copy for every page, run in parallel
Design	3–6 weeks	Wireframes, visual design, stakeholder review
Development	6–12 weeks	Build, CMS integration, third-party integrations
QA & pre-launch testing	2–3 weeks	Cross-browser/device, redirects, forms, Core Web Vitals
Launch & monitoring	Ongoing	First 30–60 days critical for catching issues

Padding each phase by 20 to 30 percent is a reasonable rule of thumb. Content delays, in particular, are the most common cause of a redesign slipping its launch date — copy and imagery almost always take longer to finalize than clients expect, especially once subject matter experts and brand-tone review get involved.

Budget for the Full Scope, Not Just Design and Development

Redesign quotes that only cover design and development hours tend to miss real costs that show up later in the project. A complete budget usually accounts for:

• Content strategy, copywriting, and photography or video production
• SEO migration work — redirect mapping, technical audits, structured data
• Accessibility testing and remediation
• Third-party integrations (CRM, booking, payment processing, marketing automation)
• Ongoing hosting, maintenance, and post-launch support after the initial build

Costs vary widely by scope, but treating the initial design and development quote as the full project budget is one of the more common ways redesigns run over. Building a contingency of 15 to 20 percent into the budget covers the content delays and scope adjustments that come up in nearly every project.

Choose the Right Platform for Where You’re Headed, Not Just Where You Are

A redesign is a natural point to reconsider your content management system, but the decision shouldn’t be made on aesthetics alone. Consider:

• How often will non-technical staff need to update content, and how easy does that need to be?
• What integrations does the site need — CRM, booking systems, payment processing, marketing automation?
• What’s your realistic budget for ongoing maintenance and hosting, not just the initial build?
• Does the platform have a track record of strong technical SEO support?

Switching platforms adds complexity and risk to a redesign, particularly around content migration and URL structure. It can be the right call, but it should be a deliberate decision weighed against the added timeline and cost, not a default.

Test With Real Users Before You Launch

Analytics and QA checklists catch broken links and technical errors, but they don’t catch confusion. Before launch, put the new site in front of a small group of real users — ideally people who match your actual personas rather than internal staff who already know where everything is — and watch them try to complete key tasks: requesting a quote, finding pricing, booking a service.

This step surfaces navigation and clarity problems that are cheap to fix before launch and expensive to fix after. It’s also the point where assumptions made during the design phase either hold up or need a quick correction, before they’re locked into a live site.

Assign Clear Ownership Internally

Redesigns stall when no one on the client side is empowered to make final decisions. Before the project starts, designate:

• One point of contact for day-to-day communication with the design or development team
• A final decision-maker for design and content approval, so feedback doesn’t loop indefinitely between multiple stakeholders
• Someone responsible for gathering and delivering content (copy, images, testimonials, product data) on schedule

Content delivery, more than any other factor, determines whether a redesign hits its launch date.

Plan for What Happens After Launch

Launch day isn’t the finish line. Build a plan for the weeks immediately after, including:

• Monitoring rankings and organic traffic daily for the first two to four weeks
• Watching for crawl errors or broken redirects in Google Search Console
• Testing forms, checkout flows, and any lead-generation tools under real traffic
• A rollback or hotfix plan in case something breaks that wasn’t caught in QA

A redesign should be treated as the start of a new phase for the site, not a one-time event. Ongoing website maintenance in the first quarter after launch catches issues early and lets you capitalize on what’s working, rather than letting a fresh build slowly drift back into disrepair.

Common Mistakes to Avoid

A quick recap of where redesigns most often go wrong, worth revisiting once a project plan is drafted:

Common Mistakes Recap

Mistake	Why It Hurts	Fix
Skipping goals	Redesign becomes aesthetics-only	Define measurable outcomes up front
Treating SEO as an afterthought	Lost redirects, dropped rankings	Build redirect maps and technical SEO into scope
Underestimating content timelines	Slips the launch date	Start copy and photography early, pad the schedule
Ignoring accessibility until QA	Costly rework, legal exposure	Build WCAG 2.2 AA into scope from day one
No internal decision-maker	Feedback loops indefinitely	Designate one final approver
Skipping user testing	Confusion ships live	Test key tasks with real users pre-launch
Budgeting design and development only	Real costs surface mid-project	Budget content, SEO, and post-launch support upfront

For a look at what this looks like in practice, Techna’s redesign case studies — including the SportsCarePT and Magic Cat Company redesigns and the Core Web Vitals-driven traffic gains for O’Connor Property Tax — show how planning translates into results, and website design done with strategy in mind from the start.