How Long Does a Website Redesign Take?
A website redesign typically takes between 8 and 16 weeks, depending on the size and complexity of your site. This timeline breaks down into distinct phases: discovery, design, development, content migration, testing, and launch.
At Jamie Thomson Designer, we’ve guided dozens of small businesses and nonprofits through redesigns. The most common mistake we see is underestimating how long the process takes. Clients often expect a quick turnaround, then face surprise when approvals, content decisions, or technical work extend the schedule.
The real timeline depends on three factors: your website’s size, how much custom work you need, and how quickly your team can make decisions. A five-page brochure site rebuilds faster than a 100-page e-commerce platform.
Website Redesign Timeline by Project Scope
Project scope determines your baseline timeline more than anything else. A small redesign and a large one follow the same phases, but the hours invested in each phase differ dramatically.
Small website redesigns (5-15 pages)
Small websites typically take 8 to 12 weeks from kickoff to launch. These are usually brochure sites, portfolio sites, or simple service websites with straightforward navigation and minimal custom functionality.
A small site moves through discovery in one week. You’ll define goals, audit your current site, and identify what needs to change. Design and planning takes two weeks. The team creates wireframes, concepts, and gets your feedback.
Content migration and copywriting takes two weeks for small sites. You’re moving existing content and refreshing copy on maybe 10-15 pages. Testing and revisions run one to two weeks. Launch and post-launch support wraps in one week.
The advantage of small projects: fewer stakeholders, faster approvals, less content to move, fewer integrations to test.
Medium website redesigns (15-50 pages)
Medium-sized websites typically take 12 to 16 weeks. These include multi-section sites, small e-commerce platforms, or membership sites with moderate complexity.
Discovery expands to two weeks. You’re mapping more pages, understanding user flows across more sections, and identifying technical debt. Design and planning takes three to four weeks. More pages mean more design variations and more rounds of feedback.
Content migration becomes a bigger job: three to four weeks. You’re auditing and refreshing 20-50 pages. Testing and revisions take two to three weeks. More pages and features mean more scenarios to test. Launch and post-launch support takes one to two weeks.
Medium projects often hit delays in the content phase. Clients underestimate how long it takes to refresh 40 pages of copy.
Large website redesigns (50+ pages)
Large websites typically take 16 to 24 weeks or longer. These include complex e-commerce sites, platforms with user dashboards, or enterprise websites with extensive content libraries.
Discovery takes two to three weeks. You’re analyzing dozens of pages, user flows, and technical architecture. Design and planning takes four to six weeks. More pages and variations mean more design work and more stakeholder feedback. Development becomes the longest phase: eight to twelve weeks.
Content migration and copywriting takes four to six weeks. You’re refreshing or rewriting 50+ pages. Testing and revisions take three to four weeks. The more pages and features, the more edge cases to find. Launch and post-launch support takes two to three weeks.
Large projects often stretch beyond initial timelines because of scope creep and approval delays.
The Website Redesign Process: Phase-by-Phase Breakdown
Every redesign follows the same core phases. Understanding what happens in each phase helps you plan buffer time and identify where delays typically occur.
Discovery and strategy (1-2 weeks)
Discovery is where you define what the redesign actually needs to accomplish. This phase includes auditing your current website, understanding your audience, and documenting requirements.
Your team and the design team will review your existing site’s performance, user behavior, and technical structure. You’ll identify what’s working and what needs to change. You’ll also clarify business goals: are you redesigning to improve conversions, reduce support requests, refresh your brand, or rebuild for mobile?
This phase is short but critical. Skipping discovery leads to redesigns that don’t solve real problems. A clear discovery phase prevents rework later.
Design and planning (2-4 weeks)
Website Design creates the visual direction and user experience for your new site. This phase produces wireframes, mockups, and design concepts for your team to review and approve.
The designer creates wireframes showing page structure and user flows. These get feedback from stakeholders. Once wireframes are approved, visual design begins. Colors, typography, imagery, and component styles get developed. Most teams go through two to three rounds of feedback before design is locked.
This is where your approval speed matters most. If decision-makers are available and responsive, design moves fast. If approvals slow down, this phase extends.
Development and implementation (3-8 weeks)
Development is building the actual website. Developers write code, set up the CMS, integrate third-party tools, and build custom functionality.
The timeline here depends heavily on complexity. A simple site with standard features might take three weeks. A site with custom functionality, e-commerce integration, or complex workflows takes six to eight weeks.
During development, your team should start preparing content. Don’t wait until development is done to begin content work.
Content migration and copywriting (2-4 weeks)
Moving content from your old site to your new site takes longer than most people expect. You’re not just copying and pasting. You’re reviewing each page, updating outdated information, improving copy, and organizing content in the new site structure.
If your content is already organized and up-to-date, this phase moves faster. If you’re discovering outdated pages, broken links, or unclear messaging, this phase extends. Many teams use this phase to improve their content, not just move it.
Testing, feedback, and revisions (1-3 weeks)
Testing catches bugs, broken links, and performance issues before launch. Your team tests functionality, checks that forms work, verifies that integrations are connected, and reviews the site on different devices and browsers.
Feedback from your team generates revision requests. These might be small tweaks or bigger changes. Budget time for two rounds of revisions. If you request major changes during testing, the timeline extends.
Launch and post-launch support (1-2 weeks)
Launch is moving your new site live. This includes final checks, switching DNS, setting up redirects from old pages, and monitoring for issues in the first days.
Post-launch support is critical. Issues always emerge once real users access the site. Your design team should be available for the first week to fix bugs and address unexpected problems. Ongoing Website Maintenance keeps your site secure, fast, and up-to-date after launch.
Factors That Affect Website Redesign Duration
Several factors can compress or extend your timeline. Understanding these helps you plan more accurately.
Website complexity and custom functionality
A site with standard features (contact forms, image galleries, blog) rebuilds faster than a site with custom functionality. Custom features require more development time, more testing, and more planning.
If your site needs a custom dashboard, a unique filtering system, or specialized workflows, budget extra weeks in development.
Third-party integrations and e-commerce requirements
Connecting your new site to existing tools (email marketing, CRM, analytics, payment processors) takes time. Each integration requires setup, testing, and troubleshooting.
E-commerce sites need payment gateway setup, inventory management, order processing, and shipping integration. These add two to three weeks to development.
Client availability and approval timelines
Your team’s availability directly impacts the timeline. If decision-makers are busy or hard to reach, approvals slow down. Design feedback that takes three weeks instead of one week extends the entire project.
Set clear approval expectations upfront. Define who approves what and commit to a feedback timeline.
Content readiness and migration complexity
If your content is disorganized or outdated, the migration phase stretches. If you’re rewriting copy, it takes longer. If you’re reorganizing your site structure, content mapping becomes complex.
Prepare your content inventory before the project starts. Audit which pages you’re keeping, which you’re removing, and which you’re rewriting.
SEO preservation and technical migration
Moving content to a new site structure requires redirects from old pages to new pages. Setting up these redirects takes time and requires careful planning to avoid breaking search engine rankings.
If SEO matters to your business, budget extra time for migration planning and testing. Work with your design team to preserve your site’s search visibility.
Website Redesign Project Plan: Creating Your Timeline
Creating a realistic timeline requires defining scope, building in buffer time, and establishing clear approval workflows.
Define scope and requirements upfront
Before the project starts, document what you’re redesigning and why. Define the number of pages, required features, integrations, and business goals. A clear scope prevents scope creep and keeps the timeline realistic.
Scope creep is the biggest timeline killer. If you add features or pages midway through the project, the timeline extends. Agree on scope upfront and treat changes as separate projects.
Build in buffer time for revisions
Every project needs buffer time for unexpected delays. Build in one to two weeks of buffer across the timeline. This accounts for slower-than-expected approvals, technical challenges, or content delays.
Don’t schedule the launch date so tightly that one delay derails everything.
Establish clear approval workflows
Define who approves what and when. Assign one or two decision-makers for each phase. Create a feedback deadline: stakeholders have three business days to provide feedback, then the team moves forward.
Clear workflows prevent endless rounds of revision and approval delays.
How to Prepare for a Website Redesign
Preparation before the project starts accelerates the timeline and prevents delays during the project.
Audit your current website and content
Before the redesign starts, review your current site. Document what pages exist, what content is outdated, what functionality you use, and what integrations are connected.
This audit informs the discovery phase and helps the design team understand your current setup.
Organize your content inventory
Create a spreadsheet listing every page on your site. Note the page title, URL, current content status, and whether you’re keeping, removing, or rewriting it.
An organized content inventory saves weeks during the migration phase.
Identify decision-makers and approval contacts
Designate who approves design work, who approves content, and who makes final decisions. Share this list with your design team before the project starts.
Clear decision-making prevents bottlenecks during the project.
Document your goals and user experience priorities
Write down what you want the redesign to accomplish. Are you redesigning to improve conversions, refresh your brand, improve mobile experience, or reduce support requests?
Clear goals keep the project focused and help the design team make decisions aligned with your business.
Common Delays and How to Avoid Them
Most redesign delays fall into predictable categories. Knowing these helps you avoid them.
Slow approvals. The most common delay is stakeholders taking too long to review and approve work. Set approval deadlines upfront.
Unclear scope. Projects without clear scope expand during the project.
Content not ready. Many teams start development before content is ready. Content delays the launch.
Technical surprises. Integration issues, performance problems, or technical debt discovered during development can extend timelines. Budget extra time for technical problem-solving.
Insufficient testing. Rushing testing leads to bugs in production. Allow adequate time for testing and revisions.
Unclear requirements. If stakeholders don’t agree on what the redesign should accomplish, the project drifts.
A website redesign takes time because it involves multiple phases, many decisions, and coordination across your team.
The key is planning realistically, preparing your content and requirements upfront, and establishing clear approval workflows. If you’re planning a website redesign, contact us to discuss your project timeline and requirements.
Frequently Asked Questions
What are the main stages of a website redesign?
A typical website redesign progresses through six key stages: discovery and strategy, where you define goals and audit your current site; design and planning, which includes wireframes and visual concepts; development and implementation, where the new site is built; content migration and copywriting, moving and refining your content; testing and revisions, ensuring everything works correctly; and finally launch and post-launch support. Each stage builds on the previous one, and the time required depends on your website's complexity and size.
How long does a website redesign timeline typically last for a small business?
A small website redesign (5-15 pages) typically takes 8-12 weeks from kickoff to launch. This assumes straightforward requirements, standard WordPress or website builder setup, and timely client approvals.
What can delay a website redesign?
Common delays include slow client approvals, incomplete content preparation, scope changes mid-project, complex third-party integrations, and technical issues discovered during development. Client availability for feedback and decisions is often the biggest factor. Planning ahead, establishing clear approval workflows, and preparing your content inventory before the project starts can significantly reduce delays.
How should I prepare for a website redesign to keep it on schedule?
Start by auditing your current website and organizing your content inventory. Identify who needs to approve decisions at each stage, and document your redesign goals and user experience priorities. Have your content ready or assign someone to handle copywriting early. Clarify your budget, timeline expectations, and any technical requirements upfront. The more prepared you are before the project begins, the smoother the process will be.
