A website redesign takes about 12 weeks for a focused business site and 6 months or more for a larger or more complex one. The spread comes from scope, content, and how fast your team gives feedback. Below we break the timeline into phases, show where the time goes, and list what you can do to shorten it.
TL;DR
- A tight, well-prepared redesign can follow a 12-week plan: discovery, design, build, testing, launch.
- A university web team's guide puts a full redesign at 6+ months when planning, approvals, and larger builds are included.
- Content and approvals cause more delay than code. Name one decision maker and set review windows early.
- Launch is not one day. Plan the weeks before and the week after.
- Protect your search rankings with a URL map and redirects before you go live.
The short answer: 12 weeks to 6+ months
There is no single number. The answer depends on what you are redesigning.
One published example is a 12-week website plan. It puts discovery in weeks 1 to 2, design in weeks 3 to 6, development in weeks 6 to 10, QA and content migration in weeks 9 to 11, and launch in week 12. Note that phases overlap. That overlap is how a plan stays at 12 weeks.
A slower, more formal path looks different. The University of Arkansas WEBFirst guide says a redesign can take 6+ months. Its stage estimates are:
| Phase | Estimated time |
|---|---|
| Discovery | 2 to 4 weeks |
| Planning | 4 to 6 weeks |
| Design | 6 to 8 weeks |
| Development | 4 to 16 weeks |
| Final approval and launch | 1 to 4 weeks |
Add the ends of those ranges and you get roughly 17 to 38 weeks. That guide also says the estimate is only an estimate. It notes that holidays, vendor selection, bids, and RFP work may need to be added on top.
So which one fits you? A small site with clear goals, ready content, and one decision maker sits near the short end. A site with many page types, a custom portal, or several stakeholders sits near the long end.
What happens in each phase
Discovery and strategy
This is where you decide what the site must do. We look at your goals, your audience, what your current site does well, and what it fails to do. We also list every page and every integration.
Skipping this phase feels fast. It usually costs weeks later, when a missing feature shows up during build.
Planning and site structure
Here you agree on the page map, navigation, and content plan. If your site has ranking pages, this is also when you map old URLs to new ones. Our site migration SEO checklist covers the prelaunch checks that protect your rankings.
Content
Content is the phase most owners underestimate. Someone has to write, edit, approve, and gather photos for every page. Start this while design is underway, not after.
Visual design
Design moves in rounds. A first round shows direction. A second refines it. A third should be small tweaks. If every round reopens the big decisions, the schedule slips.
Development and build
This is the widest range in the Arkansas guide, 4 to 16 weeks, because a brochure site and a site with a dealer portal, booking system, or custom tools are very different builds. The more custom the logic, the longer the build.
Testing and launch
The Arkansas guide describes this stage as building or changing pages, fixing bugs or change requests, and user testing. We cover launch in its own section below.
What slows a redesign down
Most delays are about people and decisions, not technology. These are the ones we plan around:
- Late content. Pages cannot be finished without real copy and images.
- Slow or split approvals. Three people with three opinions can add weeks.
- New requests mid-build. A feature added in week 8 pushes testing and launch.
- Vendor selection and bids. The Arkansas guide says vendor selection, bids, and RFP work may need to be added to its timeline.
- Holidays and vacations. A review that takes three days in March can take two weeks in late December.
- Complex integrations. CRMs, payment tools, and member logins need extra build and test time.
The 12-week example above handles risk in a useful way. It applies 25% contingency buffers to higher-uncertainty work such as research synthesis, CMS integration, and cross-browser testing. You can borrow the idea. Add padding where the unknowns are, not evenly across the plan.
How to keep your project on schedule
You control more of the timeline than you think. Four habits help most.
- Name one approver. The same example sets five milestones, each with a named approver and a maximum three-business-day review window. That structure is simple and works.
- Gather content early. Collect logos, photos, team bios, service descriptions, and testimonials before design starts.
- Freeze scope at a set point. New ideas go on a phase-two list.
- Agree on how you will communicate. A weekly check-in and a shared task list beat long email threads. Here is our guide to building a project communication plan that people actually use.
Also decide up front what must be in the new site. Accessibility is cheaper to build in than to retrofit, so use our web accessibility checklist while design is still on paper. Speed matters too. See what to measure and fix for a faster site.
Testing and launch: plan a window, not a day
Launch is a stretch of time. One operations runbook describes preparing from 30 days before launch, a sequenced cutover with owners and rollback steps, verification in the first 24 hours, and monitoring through day 7 after.
Testing should cover more than "does it look right." The Web Project Guide lists user acceptance, accessibility and usability, load, penetration, device compatibility, and regression testing. It also suggests setting up the final production environment at about the two-thirds point of the project and pushing code often, so deployment problems surface early. It adds that you should run a full regression test right after launch, because a domain name change can introduce bugs you could not see before.
If you are changing URLs or domains, validating the production environment and testing after launch is the step that protects the traffic you already have.
A practical launch plan:
- Freeze content and features.
- Finish redirects and test them.
- Back up the old site so you can roll back.
- Go live on a weekday morning, not a Friday afternoon.
- Check forms, checkout, tracking, and key pages in the first hours.
- Watch errors and search performance for the first week.
Our perspective
Most timelines go wrong before a designer opens a file. The plan is vague, the content is not ready, and nobody owns decisions.
We work as a hands-on partner. You see progress throughout, you know what we need from you and when, and you hear from us plainly if something shifts. We think that transparency does more for a schedule than any tool.
We also build automation into the sites and tools we make, so repetitive work like lead routing and follow-up stops eating your week once the site is live. A redesign is a good moment to fix those workflows, not only the look.
Loic
Work with us on your redesign
We design and build custom websites, apps, and AI and automation workflows for business owners in Canada and the US. We are an independent studio based in Kelowna and Vancouver, BC. Every project is scoped to your goals, so your timeline reflects your site, not a template.
See our web design and development services, or get in touch and tell us what you want to change. If you run a plumbing, HVAC, or electrical company, take a look at our contractor websites.
FAQ
How long should a website redesign take?
For a focused business site, plan on about 12 weeks, as in the 12-week example plan. Larger or more formal projects can run 6+ months, according to the University of Arkansas guide. Content readiness and approval speed decide where you land.
What are the main stages of a redesign?
The core stages are discovery, planning, content, design, development, testing, and launch. The Arkansas guide groups them as discovery, planning, design, development, and final approval and launch. Phases can overlap, especially content and design.
Can I speed up a redesign?
Yes. Name one approver, set short review windows, deliver content early, and hold new requests for a later phase. Cutting testing is the wrong shortcut, because bugs found after launch cost more to fix.
Will a redesign hurt my search rankings?
It can if URLs change without redirects. Map every old URL to a new one and test after launch. Our prelaunch checks walk through the steps.
Sources
- Project Flow Overview, WEBFirst, University of Arkansas
- Project Plan Example: A Complete, Annotated Walkthrough, ClickUp
- Test and Launch the Site, The Web Project Guide
- Launch Runbook: What Everyone Runs on Launch Day, RampStack
