6 November 2026
How Long Should a Website Redesign Actually Take? A Realistic Timeline
You have a launch in mind: an event, a campaign, a new quarter. Before you brief an agency, you need to know whether that date is realistic. Quotes arrive with timelines that range from “two weeks” to “four months,” and it’s hard to tell which is honest. Here’s what drives the time, how a typical project breaks down, and what usually makes it run late.
The short answer
A simple site can take a few weeks. A typical business website often takes one to three months. Larger or more custom projects take longer. What decides it is rarely the number of pages. It’s how quickly content and feedback arrive, how many features are involved, and how many people need to approve things.
Indicative timelines by project type
| Project type | Indicative range | What mostly drives it |
|---|---|---|
| Landing page | 2 to 4 weeks | Copy and offer clarity, tracking setup |
| Small corporate site (5 to 10 pages) | 4 to 8 weeks | Content readiness, design rounds |
| Larger corporate site (10+ pages, blog, multiple services) | 8 to 12 weeks | Content volume, approvals, SEO migration |
| E-commerce or booking site | 8 to 16 weeks or more | Products, payment gateway, integrations, testing |
| Custom web app or complex integrations | 12 weeks or more | Scope definition, development, testing |
These are not promises. They assume the client supplies content and feedback on time, and that scope doesn’t grow. If an agency quotes much shorter, ask what’s being left out. If much longer, ask why.
The phases, and where the time goes
A redesign isn’t one task. It’s a chain, and a delay in one link pushes everything behind it.
1. Discovery and brief. Goals, audience, competitors, references and what to keep from the current site. Done well, this saves weeks later. (See our post on how we turn reference sites into original designs.)
2. Structure and content plan. The sitemap, what each page must say, and who writes it. This is where many projects quietly stall.
3. Design. Layouts for key pages, usually with a round or two of feedback. Time depends on how quickly decisions are made, not on how fast the designer works.
4. Content creation. Writing, photography, product data, translations. This is the single biggest source of delay, and it’s usually on the client’s side. Content that arrives late means a launch that slips.
5. Build. Turning designs into a working site, including forms, tracking and any integrations.
6. Integrations. Payment gateways, booking systems, CRM, WhatsApp and email tools. Each needs setup, credentials and testing, and some depend on third parties’ approval times.
7. Testing. Phones and desktops, forms, speed, tracking and a content review. Skipping this to save time usually costs more later.
8. Launch. Final approval, going live, and putting redirects in place so you don’t lose existing rankings (see our article on revamping an old website).
9. After launch. Fixing small issues, checking analytics and search visibility, and watching enquiries for the first few weeks.
What usually makes a project late
- Content isn’t ready. “We’ll send it later” is the most common cause of delay. Plan who writes what, and by when.
- Slow feedback. A week between each round adds up fast. A project with five rounds of one-week feedback has already used five weeks.
- Too many decision-makers. Conflicting feedback from several people sends designers in circles. Name one person with final say.
- Scope creep. Each “while you’re at it” adds time. Agree what’s in and out, and put new ideas on a later list.
- Late changes to the brief, especially after design is approved.
- Third-party delays, such as payment gateway approvals, domain transfers, or access to hosting and accounts.
- Underestimating migration. Moving content, products and redirects from an old site takes longer than people expect.
- Rushed testing, which leads to fixes after launch.
How to shorten a redesign without cutting corners
- Prepare content before design starts, or at least agree a content deadline.
- Choose one approver, and agree response times, such as feedback within two working days.
- Fix the scope. Decide on must-haves first, and leave nice-to-haves for phase two.
- Collect access early: domain, hosting, analytics, ad accounts, logos and brand files.
- Prefer a phased launch. Go live with the pages that matter most, then add the rest. A launch in stages beats waiting for everything.
- Decide the platform early.
- Provide real references, with a note on what you like and dislike about each.
What not to speed up
- Redirects and SEO migration. Skipping them can erase years of search visibility.
- Tracking. Without it, you can’t tell whether the new site performs better than the old one.
- Testing on phones. Most visitors use them.
- Content accuracy. Wrong prices, hours or contact details cost trust straight away.
Launch timing
Choose your date around your business, not only the project. Avoid launching just before your busiest period, when you won’t have time to fix issues, and before major holidays when your team is away. Festive peaks like Hari Raya, Chinese New Year and year-end sales are poor times to discover a broken form. Leave a buffer of at least a week or two before any hard deadline.
Warning signs in a proposed timeline
- No time for content or feedback. Real projects include these phases, and a plan that skips them is unrealistic.
- No testing phase, or “testing” folded into launch day.
- A fixed date with an undefined scope. Something will give.
- No mention of redirects, migration or tracking for a redesign.
- Vague milestones. Look for named stages, deliverables and dates.
- A timeline that’s much shorter than every other quote, with no explanation.
Questions to ask an agency
- What are the phases, and how long is each?
- What do you need from us, and by when?
- How many design rounds are included, and how long do they take?
- What happens to the timeline if content arrives late?
- How will you protect our current rankings and tracking?
- What’s included in testing, and who signs off?
- Can we launch in stages?
- What happens after launch?
A sample timeline (illustrative)
This is an example of how a small corporate site might run. Adjust it to your scope.
| Week | What happens |
|---|---|
| 1 | Discovery, brief, references, access collected |
| 2 | Sitemap and content plan agreed, content writing begins |
| 3 to 4 | Design of key pages, feedback round |
| 4 to 5 | Design approved, content arrives, build starts |
| 5 to 6 | Build, forms, tracking, integrations |
| 7 | Testing, content review, fixes |
| 8 | Launch with redirects, post-launch checks |
If content or feedback slips by a week at any stage, the whole schedule moves with it.
A planning checklist
- Goal and success measure agreed
- One person with final say
- Scope written down, with must-haves and later ideas separate
- Content owner and deadline named
- Access to domain, hosting, analytics and accounts gathered
- Feedback turnaround agreed
- Redirect and tracking plan included
- Testing time reserved
- Launch date chosen with a buffer
- Post-launch review booked
The honest summary
A redesign takes as long as its slowest link, and the slowest link is usually content and decisions, not design or code. If you want a date, plan backwards from it with real buffers, fix the scope and prepare your content early. A realistic plan that holds is worth more than a short one that slips.
Planning a redesign and want a realistic timeline for your project, based on your content, features and deadline? [See how we approach web development projects →]