Website Redesign Timeline: What to Expect, Week by Week

Website Redesign Timeline: What to Expect, Week by Week

Most redesigns of a small business website run about 8 to 14 weeks from kickoff to launch. A simple site of a handful of pages can be faster. A site with dozens of pages, custom features or a slow approval process takes longer. The biggest swing factor is rarely the design. It is how quickly you deliver content and decisions.

This guide breaks the timeline into phases, shows what each one needs from you, and explains where projects slip. It also covers the part most timelines skip: redirects before launch and the weeks after it.

TL;DR

• Plan on roughly 8 to 14 weeks for a typical 10 to 30 page small business site. Very small sites can be quicker, and larger ones run 12 to 24 weeks.
• Content and feedback delays cause more slippage than design or development. Name one decision maker and set review deadlines up front.
• Map old URLs to new ones during planning, not the week before launch. Skipped redirects are the costliest redesign mistake.
• Launch is the start of a 30-day stabilization window, not the finish line.
• Scope drives the calendar. A focused refresh and a full rebuild are different projects with different timelines.

Table of Contents

• How long a website redesign takes by site size
• The phases, and what each one needs from you
• A sample 12-week schedule
• What makes a redesign take longer
• Protect your search visibility during the redesign
• After launch: the first 30 days
• Our perspective
• Where Picshaw fits
• How to keep your own timeline on track
• FAQ
• Sources

How long a website redesign takes by site size

Published estimates vary because agencies define “redesign” differently. Still, the ranges cluster. One recent guide puts 8 to 14 weeks as the typical range for a business site of 10 to 30 pages. We treat that as a sensible planning band, not a promise, because your own content readiness moves it.

A rule of thumb that matches what we see in how projects are structured:

These are planning ranges drawn from what the industry publishes, not Picshaw quotes. Treat them as a starting point and adjust for your own situation.

One project template for a standard marketing site on a CMS assumes about nine weeks from kickoff to go-live, plus a week of fixes after launch. That fits the lower middle of the small business band: a tidy site, prompt feedback, no surprises.

The phases, and what each one needs from you

A redesign is a chain of linked phases. A project manager’s job is to map the dependencies between them. Planning dependencies, risks and handoff points before design starts is what keeps stakeholders aligned and prevents scattershot feedback from derailing a schedule. Here is the typical sequence for a small business site.

Phase 1: Discovery and goals (1 to 2 weeks)

This is where you decide what the new site is for. Who are the customers, which services make the most money, what does the current site do badly, and what counts as success? For a home service company, success might be more quote requests from the right neighborhoods. For a consulting firm, it might be fewer unqualified calls.

What you provide: access to your analytics, your hosting and domain logins, a list of your best-selling services, and a list of sites you like and dislike. Delays here are usually about logins. Find them before kickoff.

Phase 2: Structure and sitemap (1 to 2 weeks)

The sitemap decides which pages exist, how they link and what each one has to answer. This is also where you decide what happens to every page on your current site: keep, merge, rewrite or retire.

This is the right moment to build the redirect map. State web standards guidance describes a simple rule: use a 301 for a direct replacement, a 410 for content you removed on purpose, and a 404 only for URLs that never existed. Doing it now, while you are deciding page by page, is far easier than reconstructing it at launch.

Phase 3: Content and copywriting (2 to 4 weeks, overlapping)

Content is the most common bottleneck. Owners underestimate how long it takes to write clear service pages, gather project photos, collect testimonials and get licensing or insurance details right.

Content also matters for how AI-powered search reads your site. Clear service descriptions, plain headings, service areas stated in text and answers to the questions customers actually ask are what let both people and AI answer engines understand what you do. If you want the diagnostic side of this, our guide on why a business website is not appearing in Google covers the common causes.

What you provide: approved copy or interview time, real photos, prices or price ranges you are willing to state, and your service area. Writing can start as soon as the sitemap is agreed, and it should overlap with design.

Phase 4: Visual design (2 to 4 weeks)

Design covers the homepage, the main interior page templates and the mobile layouts. Most projects include a set number of revision rounds. The timeline stretches when feedback arrives from five people who disagree, a pattern project managers call scattershot feedback.

How to keep it tight: consolidate feedback into one document, one person signs off, and each round has a deadline.

Phase 5: Build and development (2 to 4 weeks for small sites)

The design becomes a working site: templates, CMS setup, forms, call tracking, analytics, mobile responsiveness and page speed. Larger or custom-built sites can take twice this long. Moving content into the new pages often runs in parallel.

What you provide: quick answers on form routing (who gets the lead and how fast), and any third-party tools you use such as scheduling or payment software.

Phase 6: Review, testing and QA (1 to 2 weeks)

Test every form, phone link, redirect and page on real phones and common browsers. Check that titles, headings and metadata survived the move. Confirm the analytics fire and that your contact form reaches a human inbox. Skipping this phase is how a site goes live with a broken quote form.

Phase 7: Launch and stabilization (1 day, then 30 days)

Launch day itself is short. What follows is not, and we cover it below.

A sample 12-week schedule

Here is how a typical small business project can look when feedback comes back within a few days. The numbers are an illustration of the sequence, not a Picshaw commitment.

1. Weeks 1 to 2: Discovery, access, goals, audit of the current site.
2. Weeks 2 to 3: Sitemap, page inventory and redirect map.
3. Weeks 3 to 6: Copywriting and photo collection, starting once the sitemap is agreed.
4. Weeks 5 to 8: Visual design and revisions, starting as the first copy lands.
5. Weeks 8 to 10: Build, form setup, analytics, redirects staged.
6. Weeks 10 to 11: Testing, fixes and final approval.
7. Week 12: Launch, then a monitoring window.

Notice the overlaps. Copy, design and build are not strictly sequential, which is why a well-run project is shorter than the sum of its phases.

What makes a redesign take longer

In our experience of how these projects go wrong, the same causes come up repeatedly:

• Late content. Design cannot be finished honestly with placeholder text. Missing copy is the number one delay.
• Too many reviewers. Each extra approver adds a round. Name one decision maker.
• Scope creep. A new page here, a booking system there. Write the scope down and price changes separately.
• Unplanned redirects and URL changes. Discovering at the end that 80 old pages have no destination can push launch back by days.
• Third-party dependencies. Waiting on a domain registrar, an old developer or a payment provider.
• Seasonality. Home service businesses often want a new site live before their busy season. Work backward from that date and add a buffer.

If your website is small and mostly sound, you may not need a full rebuild. We wrote about what a $1,000 website refresh includes and when you need a rebuild, which helps you decide how much project you actually need. A smaller scope is the most reliable way to shorten a timeline.

Protect your search visibility during the redesign

Redesigns can cause what practitioners call SEO regression, a drop in visibility after launch, most often because old URLs were not redirected properly. Three habits prevent most of it.

Map every URL before design is final

Export every indexed page from your current site. Assign each one a status: 301 to its direct replacement, or 410 if you intentionally removed it. Redirecting deleted pages to the homepage creates what are known as soft 404s and hurts both search visibility and user trust. The same guidance recommends keeping your mapping records for the long term, and storing the mapping in version control if your developer works that way.

Treat SEO and UX as part of the build

Clear response codes, mobile adaptability and sensible structure are technical decisions made during the build, not extras added at the end. They affect how well search engines and AI systems crawl and index your content. If you serve several neighborhoods or cities, plan location pages at the sitemap stage. Our guides on local landing pages and SEO for multiple locations explain how.

Keep what already works

Before the old site goes away, record which pages bring in calls and form fills, and keep their titles, headings and useful copy where they still serve customers. A redesign should improve those pages, not erase them.

After launch: the first 30 days

Launching is not the end of the project. Practitioners describe the first month as a stabilization window and warn that businesses often disengage right after go-live. The suggested plan includes daily monitoring for errors and tracking regressions for at least 14 days, then weekly performance tuning through weeks 3 to 8.

A practical checklist for the first month:

• Submit the new sitemap and check for crawl errors.
• Test your contact forms and call tracking daily for the first week.
• Watch for 404s and fix any missed redirects.
• Compare calls, form submissions and top landing pages against your pre-launch baseline.
• Ask a few customers to try the quote or booking flow and tell you what confused them.

Announcing the new site

An announcement works better as a short campaign than a single email. One guide recommends a two-week teaser period before launch and a follow-through campaign afterward, including posts about why you made the changes and early results. For a local business, that can be as simple as a note to past customers, an updated Google Business Profile and a few social posts.

Our perspective

We build and fix websites for local service businesses in Los Angeles, and we see the same pattern. Owners ask how many weeks the design will take. The better question is how many weeks it will take them to supply the content and make the decisions.

We also think a redesign should be scoped to the business, not to a template. A contractor with eight service pages and decent copy does not need the same project as a consulting firm consolidating three old sites. That is why we start with what is actually holding the site back, and we talk to you directly rather than passing you through layers of account managers.

One more opinion: build for answer engines from the start. People now ask AI tools who to hire for a job, and those tools favor sites that state clearly what you do, where, and for whom. Doing that in the sitemap and copy phases costs almost nothing. Retrofitting it after launch costs a second project.

If you are not sure how much redesign you need, ask for an audit before you ask for a quote. It is cheaper to learn the site needs a refresh than to buy a rebuild.

— Ash

Where Picshaw fits

If you want the timeline scoped to your own site, we offer website redesign packages for small businesses: a Website Refresh at $1,000 one-off, a Growth Site from $2,500 one-off, and a Monthly Partner plan from $500 per month for ongoing work. We do not publish a fixed calendar for each, because the schedule depends on your page count and how quickly content arrives. We scope it with you. If you first want to know what is holding your site back in AI search, start with our AI Visibility Audit.

Home service companies can also see how we approach web design for contractors, and our contractor website checklist is a good pre-redesign review.

How to keep your own timeline on track

A few commitments from your side do more for the schedule than any tool:

1. Name one decision maker and give them authority to approve.
2. Set feedback deadlines in writing, such as two business days per round.
3. Gather content early: photos, testimonials, licenses, service areas and prices you will state.
4. Freeze scope after the sitemap is approved. New requests go on a post-launch list.
5. Pick a launch window away from your busiest week, with a buffer of one to two weeks.
6. Reserve time for QA. Test the site the way a customer would, on a phone, with a real inquiry.

A timeline template can help you visualize this. A timeline in project-management terms is a chronological view of milestones and tasks, and even a simple shared spreadsheet works for a small site.

FAQ

How long should a website redesign take?

For a typical small business site of 10 to 30 pages, plan on 8 to 14 weeks from kickoff to launch. Very small sites can finish sooner, and sites with many pages or custom features take longer. Your own content and approval speed is the biggest variable.

How often should a website be redesigned?

One agency guide suggests a new site should last about 3 to 5 years, though the right moment depends on results, not the calendar. Redesign when the site is hard to use on phones, does not explain your services, or stops generating inquiries. Smaller refreshes in between can extend its life.

What are the main stages of a website redesign?

The common sequence is discovery, strategy and sitemap, content, visual design, development, testing and launch. Good projects overlap content, design and build to save time. The post-launch month is part of the project too.

How do I announce a website redesign?

Treat it as a short campaign. Tease the change for about two weeks, announce on launch day by email and your business profiles, then follow up with posts about what changed and why. Tell past customers directly if you serve repeat clients.

Sources

• Website Project Gantt Chart Template, NeoGantt
• The Role of a Project Manager in Web Projects, Webstacks
• Search engine optimization, California Webstandards
• What’s a website timeline?, Markup.io
• LOW/CODE

Recommended

• What a $1,000 website refresh includes—and when you need a rebuild
• Website redesign for small businesses
• 12 contractor website checks before you pay for more traffic