How Long Does a Website Redesign Take? A Practical Timeline

Most small-to-medium website redesigns take between six and twelve weeks. A focused landing page can move faster. A large website, ecommerce store or project with extensive content and integrations can take several months.

The timeline is rarely controlled by design alone. Content decisions, stakeholder feedback, technical discovery and migration work usually have the biggest effect.

This guide breaks down a realistic website redesign timeline so you can plan internal time as well as agency time.

Website redesign timeline at a glance

A typical professional redesign might follow this pattern:

• discovery and scope: 1–2 weeks
• structure and content planning: 1–3 weeks
• visual design: 2–4 weeks
• development: 3–6 weeks
• content entry and migration: 1–3 weeks
• testing and launch: 1–2 weeks

Several stages can overlap. Copy can develop while early visual concepts are reviewed, and technical setup can begin before every page is final. Overlapping work should be deliberate rather than rushed.

Stage 1: discovery and scope

Discovery turns a vague request for a “new website” into a project that can be planned and priced.

The team should establish:

• business goals and priority audiences
• current website strengths and problems
• required pages and functionality
• content ownership
• SEO and migration requirements
• technical constraints
• approval responsibilities

Skipping discovery appears to save time but often creates rework. A week spent making good decisions can prevent a month of redesigning the wrong thing.

Stage 2: sitemap and content planning

The sitemap determines what pages exist and how they relate. Content planning defines what each page needs to communicate.

This stage is often underestimated. Businesses may have several services described in overlapping ways, old pages still attracting traffic, or important customer questions that are not answered anywhere.

An effective plan combines user needs with search demand. It avoids creating pages simply to fill a navigation menu.

If organic visibility matters, existing URLs, backlinks and ranking pages should be reviewed before anything is removed. Read our guide to website navigation best practices for a practical structure.

Stage 3: wireframes and visual design

Wireframes establish hierarchy without getting distracted by polish. They show where the value proposition, proof, services, calls to action and supporting content belong.

Visual design then applies the brand through typography, colour, imagery, spacing and interaction.

Most projects move efficiently when one or two representative pages are approved first. Designing the homepage and a core service page creates a system that can be extended across the rest of the site.

Feedback should be consolidated. Six separate messages from different stakeholders usually create more delay than one considered response.

Stage 4: development

Development turns approved designs into a responsive, accessible and maintainable website.

The work normally includes:

• reusable page components
• mobile and desktop layouts
• content management
• forms and integrations
• performance optimisation
• metadata and structured content
• accessibility behaviour
• analytics and consent tools

Development time depends on the number of unique layouts and behaviours, not just page count. A small site with complex animation can take longer than a larger editorial site built from consistent templates.

Stage 5: content entry and migration

Content is where otherwise healthy timelines often slow down.

Writing, approving, sourcing images and moving material from an old site requires internal knowledge. Decide who owns each page early and set review dates before development is finished.

Migration should also include redirects where URLs change. Publishing a beautiful new site while sending established search pages to errors is an avoidable loss.

Stage 6: testing and launch

Testing should cover more than whether pages load.

Check:

• common mobile and desktop sizes
• current browsers
• keyboard navigation and focus states
• forms and confirmation messages
• links and redirects
• page titles and descriptions
• analytics events
• image sizes and performance
• spelling, contact details and legal pages

Launch should have a clear checklist, named owners and a rollback plan for anything technically sensitive.

What makes a redesign take longer?

Late content

Placeholder copy hides layout problems and delays meaningful review. Start content work with the sitemap.

Unclear decision-making

Projects stall when nobody knows who has final approval. One accountable owner should consolidate feedback.

Changing scope

New calculators, customer portals and integrations can reshape the whole build. Useful ideas should be assessed, but not silently added to the original deadline.

Hidden technical issues

Legacy platforms, poor data quality, undocumented integrations and complicated domains can add work. Technical discovery reduces the risk.

Trying to perfect every detail before testing

Real pages reveal more than isolated mock-ups. Agree the system, build representative pages and refine from evidence.

How to keep the project moving

1. Prepare brand assets, analytics access and existing content before kickoff.

2. Nominate one decision-maker.

3. Approve the sitemap before visual design.

4. Review work on scheduled dates.

5. Give specific feedback tied to user or business goals.

6. Separate launch essentials from later improvements.

7. Freeze major scope changes before final testing.

Fast does not have to mean careless. It means removing waiting, ambiguity and repeated decisions.

Frequently asked questions

Can a website be redesigned in four weeks?

Yes, for a small, focused site when content is ready, decisions are quick and functionality is limited. Compressing a larger project usually means reducing scope rather than simply working faster.

How long does an ecommerce redesign take?

Allow roughly three to six months for a substantial store, depending on catalogue size, migration, integrations, theme customisation and testing. Complex international or custom-commerce requirements can take longer.

Should the old website stay live during the redesign?

Usually yes. The new site should be built and tested separately, then launched when content, redirects and integrations are ready.

Build a timeline you can trust

TIZZLE uses a staged process to keep strategy, content, design and development connected. See how we turn a rough idea into a finished website, explore our website design service, or start a project.