30 to 60 days, kickoff to launch.
The website redesign process at WebsiteRedesign.com runs six deliberate phases: review, plan, rewrite, design and build, launch, improve. The order keeps decisions in sequence — content gets locked before design starts, design gets locked before build, and launch ships with measurement in place. Most sites move through it in 30 to 60 days.
Six phases, 30 to 60 days.
- Review: Week 1
- Plan: Week 1–2
- Rewrite: Weeks 2–4
- Design and build: Weeks 3–6
- Launch: Week 5–8
- Improve: Ongoing
Each phase has a deliverable and a sign-off before the next one starts.
Six phases, deliberate order.
Read the current site
Existing pages, content equity, search signals, forms, visitor paths, and proof get reviewed before any redesign decision gets made. The audit produces a list of what to protect, what to rebuild, and what to retire. Skipping this step is how most redesigns lose useful work that was already paying off.
Set the redesign direction
With the audit in hand, we lock the goal for the new site, the page priorities, the message direction, and the success metric. This is where the buyer's actual decision path gets mapped — and the metric becomes the reason every later choice gets made the way it does.
Map the structure
Sitemap, navigation, internal linking, URL strategy, and page hierarchy all get planned before any visual design starts. URL decisions in particular need to lock early — they drive the redirect plan, the SEO migration, and the build estimate.
Rewrite the important pages
High-value pages — homepage, services, industries, contact — get rewritten and restructured around how your buyers actually read. Headers, section order, proof placement, and CTAs all get rebuilt deliberately. Most of the conversion work happens at this layer.
Build and test the site
Visual system, components, forms, mobile, redirects, analytics, accessibility, and page speed all get implemented and verified. The pre-launch QA pass catches the issues that turn into post-launch fires.
Launch and measure
Sitemap submitted, priority URLs inspected, Search Console watched, analytics confirmed firing. The launched site becomes the baseline against which every later change gets measured. The early post-launch window drives the first round of improvements.
What happens when.
Week 1 — Audit.
Current-site review, search data analysis, content equity inventory. Kickoff call sets the goal. Deliverable: a written audit and the redesign brief.
Week 1–2 — Plan.
Sitemap, navigation, page priorities, URL strategy, success metric. Deliverable: an information architecture document signed off by the client.
Weeks 2–4 — Rewrite.
High-value page rewrites: homepage, services, industries, contact, FAQ. Headers, section order, proof, CTAs. Deliverable: page-level copy decks signed off page by page.
Weeks 3–6 — Design and build.
Visual system, component library, forms, mobile, redirects, analytics, schema, accessibility. Deliverable: a staging environment ready for review.
Week 5–8 — Launch.
Final QA pass, sitemap submission, Search Console setup, priority URL inspection. Deliverable: the new site live, monitored for 30 days.
Ongoing — Improve.
Monthly cycle of observation, hypothesis, test, measurement. Deliverable: a monthly memo with one to three prioritized changes per cycle.
Site size and stakeholder count shift the timeline within that 30-to-60-day band. Both ends of the range produce the same outcome: a launched site and a measurement baseline.
Three things that keep a redesign on time.
Sign-offs happen at phase boundaries
The audit gets signed off before the plan starts. The IA gets signed off before the rewrite. The copy gets signed off before the design. Phase-gated sign-offs prevent the most common cause of redesign drift: late-stage rework on early-stage decisions.
Decisions are made by the right number of people
One or two decision-makers on the client side keep velocity. Five-person committees turn a 30-day redesign into a 90-day one. We scope at kickoff for the team shape on both sides.
Content lands early
Copy gets written in Weeks 2 through 4 — before the design starts. This is the reverse of how most agencies work, and it's the single biggest reason our timelines land.
Frequently asked questions.
Can a redesign land in under 30 days?
Short answer: Sometimes. A focused project — single landing page, homepage refresh, or small site with one decision-maker — can land faster than the standard band. Below a certain size, the audit phase compresses past the point where it produces useful evidence.
What slows a redesign down?
Short answer: Usually one of three things: too many stakeholders signing off at each phase, late-stage rework on early decisions, or content that arrives in week 5 instead of week 2. We flag these risks at kickoff.
Do we get to see work in progress?
Short answer: Yes, at every phase boundary. The audit is delivered as a written document. The IA is reviewed before copy starts. Copy decks come page by page. Design lands in a staging environment for review. Build progresses against the approved spec.
What happens if priorities change mid-engagement?
Short answer: Small priority shifts are normal and handled within the scope. Major rescopes — new goal, new audience, new structure after Week 3 — usually mean restarting an earlier phase. We talk through the impact before agreeing to changes.
Can the process work with our existing developer or build team?
Short answer: Yes. We deliver designs and copy as a developer-ready spec. Your team handles implementation. Pre-launch QA can be ours, yours, or split — we agree at kickoff.
Tell us when the new site needs to launch.
Send the URL, the goal, and the rough timeline you're working with. We'll be in touch to schedule a call.