How Long Does a Website Redesign Take? A Realistic Timeline
A focused redesign of a small business website commonly takes 6 to 12 weeks from kickoff to launch. Larger sites with multiple templates, content rewriting and a URL migration typically run 12 to 20 weeks or more. The single biggest variable is not design or development capacity — it is how quickly content and approval decisions get made on your side.
Realistic ranges by project size
| Project | Typical duration | What drives it |
|---|---|---|
| Visual refresh on existing templates | 3–6 weeks | No new IA, no migration, content stays put |
| Small business redesign (5–10 pages) | 6–12 weeks | New structure, some content rewriting, simple redirects |
| Mid-size marketing site (15–30 pages) | 12–20 weeks | Several templates, substantial content work, full redirect map |
| Redesign plus replatform or migration | 16 weeks+ | URL mapping, data migration, staging parity checks |
These are working ranges for planning, not quotes. Two projects with identical page counts can differ by two months purely on content readiness.
Where the weeks actually go
Discovery and inventory — 1 to 3 weeks
Analytics review, URL inventory, content audit, and agreement on what the redesign is meant to fix. Skipping this stage does not save time; it moves the cost to later, when structural questions surface mid-build and force rework.
Structure and wireframes — 1 to 3 weeks
Information architecture, page structure and conversion paths, resolved before visual design. Changes here are cheap. The same changes after visual design is approved are expensive, which is exactly why this phase should not be compressed.
Visual design — 2 to 4 weeks
Design of key templates rather than every page, plus the component and state definitions developers need. Duration depends more on how many rounds of feedback the approval process generates than on the number of templates.
Content — runs in parallel, and usually decides the date
Writing, editing, approvals, images. This is the phase that most often blows out, because it depends on people whose main job is something else. Starting content in parallel with design — rather than waiting for finished layouts — is the most effective single scheduling decision available to you.
Build and QA — 3 to 6 weeks
Template development, CMS configuration, responsive behaviour, accessibility checks and cross-browser testing. On a migration this is also when the redirect map is implemented and crawled on staging.
Launch and stabilisation — 1 to 2 weeks
Cutover, redirect verification, sitemap submission, and monitoring for 404s and indexation. Treat this as scheduled project time, not something that happens after the project ends.
The four things that reliably add months
- Content that is not ready. Design and build can be resourced; waiting for copy cannot. Decide who writes each page before kickoff, not at the halfway point.
- Unclear approval authority. When feedback comes from several people with conflicting views and nobody can settle it, each round costs days. Name one decision-maker per phase.
- Scope added mid-project. A booking system or a new template introduced in week eight is a new project attached to an existing one. It is legitimate — but it moves the date, and it should be acknowledged as doing so.
- Migration complexity discovered late. Finding out in week ten that the old site has 400 indexed URLs nobody knew about is why the inventory happens first. See the website migration checklist.
How to genuinely go faster
The honest levers are narrow, and none of them involve the agency working harder:
- Have content ready before kickoff. The single largest accelerant available.
- Reduce template count. Fewer distinct page types means less design, build and QA.
- Keep the URL structure. If addresses do not change, the migration work largely disappears.
- Name one decision-maker. Consolidated feedback within a fixed window turns approval rounds from days into hours.
What does not work is compressing QA, accessibility or redirect planning. Those are the phases whose absence is invisible at launch and expensive three months later.
How Devoq schedules redesigns
Website redesign at Devoq is scoped after the URL and content inventory, so the timeline reflects the actual site rather than a page count. Full redesigns with SEO-safe migration start from $10,000 AUD ex GST, with complex migrations typically $25,000+ AUD ex GST. To sanity-check a budget before you brief anyone, the free website cost calculator gives an indicative range by scope. If you are still deciding whether the rebuild is warranted, when to redesign your business website is the better first read.
Frequently asked questions
How long does a website redesign take in Australia?
A focused redesign on a small business site commonly runs 6 to 12 weeks from kickoff to launch. Larger sites with multiple templates, content rewriting and a migration typically run 12 to 20 weeks or more. The variable that moves the timeline most is not design or development — it is how quickly content decisions get made.
What slows a website redesign down the most?
Content. Design and build work is schedulable; waiting for copy, approvals and asset decisions is not. The second-biggest delay is unclear approval authority — when feedback arrives from several people with conflicting views and nobody can settle it, each round takes days instead of hours.
Can a website redesign be done in four weeks?
Only in narrow circumstances: a small site, existing finished content, a template-led approach rather than custom design, one decision-maker, and no migration. Compressing a genuine custom redesign into four weeks usually means skipping discovery, accessibility or redirect planning — the parts whose absence shows up months later.
How long before we see SEO results after a redesign?
Expect short-term volatility for a few weeks while search engines recrawl the new structure, then gradual stabilisation. If the redesign included content and structural improvements, gains typically show over the following months rather than immediately. Anyone offering a specific recovery date is guessing.
Should we launch all at once or in phases?
Phased launches suit sites with meaningful traffic or revenue, because moving one template at a time limits the damage of any single mistake. A single launch is simpler and faster for smaller sites. The trade-off is risk concentration against total programme length.
Ask Devoq for a scoped timeline — inventory first, dates after.
