A small business website redesign typically takes a few weeks to a couple of months, a medium project with custom features runs a few months, and a large or e-commerce site can take several months or more. Your first move should be a short audit or discovery session to lock scope and spot dependencies before any design work starts. If search rankings matter to you, plan for extra migration steps like redirects, sitemap updates, and change-of-address settings.
TL;DR:
- Small sites can typically go live within 4 to 8 weeks if they use templates and have minimal third-party integrations.
- Medium projects usually require 8 to 16 weeks due to custom templates, content migration, and multiple stakeholder reviews.
- Large or e-commerce sites often take 16 to 36 weeks or longer, especially with staged launches and complex integrations.
- Delays often stem from approval bottlenecks, content still being prepared, or complex legacy system integrations, rather than technical issues.
- To protect SEO rankings, build and test redirects early, keep them active for at least 180 days, and handle domain changes carefully with Google’s tools.
Table of Contents
- How long does a website redesign take for small, medium, and large sites?
- What happens in each phase of a website redesign?
- What causes website redesign delays, and how do you avoid them?
- How do you protect SEO rankings during a website redesign?
- How do you keep approvals and content decisions from stalling your project?
- How do you turn a sample timeline into a real project plan?
- What we’ve learned scoping redesign timelines for small businesses
- Ready to start your website redesign?
- FAQ
- Sources
How long does a website redesign take for small, medium, and large sites?
Your timeline depends almost entirely on scope, not ambition. A simple five-page site with a template-based design and no custom integrations can be live in 4 to 8 weeks, especially when one person can approve each stage quickly. A medium project, think custom page templates, a content migration, and a booking or payment integration, usually needs 8 to 16 weeks because it involves more stakeholders and more testing. Large projects, like multi-location businesses or e-commerce catalogs with hundreds of products, often run 16 to 36 weeks or longer, particularly when launches happen in stages.
Small site:
- Five to ten pages, mostly template-based layouts
- Minimal third-party integrations
- A single decision-maker who can sign off fast
Medium site:
- Custom templates and a content migration plan
- Integrations like booking calendars or payment processors
- Multiple stakeholders reviewing design and copy
Large site:
- Multi-location pages or large product catalogs
- Complex integrations with CRM, ERP, or inventory systems
- Staged launches to reduce risk and get core pages live sooner
When your project has a lot of moving parts, a phased rollout, launching your homepage and top service pages first while secondary pages catch up, can shorten the time until the site actually earns its keep.
What happens in each phase of a website redesign?
Every redesign moves through the same core phases, even if the names change from agency to agency; many legal professionals turn to specialized Law Firm Website Redesign Services to ensure compliance and sector-specific needs are met. Knowing what belongs in each one helps you assign real deadlines instead of guessing.
- Discovery and audit: You inventory existing pages, review analytics, run technical SEO checks, and set clear goals for the new site.
- UX and wireframes: Your team maps customer journeys and builds low-fidelity prototypes, with a limited number of feedback rounds built in.
- Visual design: Designers finalize screens, assets, and accessible components that match your brand, though extra revision rounds can extend this phase.
- Development: Developers build templates, configure the content management system, wire up integrations, and test everything in a staging environment.
- Content migration and creation: You decide what gets migrated as-is, what gets rewritten, and what gets cut, then prepare media and import everything into the CMS.
- QA and launch prep: Your team tests across devices, checks forms, confirms analytics tracking, sets up redirects, and tunes performance before going live.
Content is usually the phase owners underestimate most. If you’re rewriting copy rather than migrating it, you need writer time built into the schedule, not squeezed in alongside development. Our guide on prioritized speed fixes covers performance work worth tackling during development, before QA even starts.
Pro Tip: Lock your content decisions before development starts so your developers aren’t building templates for pages that might get cut.
What causes website redesign delays, and how do you avoid them?
Most delayed redesigns fail for the same handful of reasons, and almost none of them are technical.
- Approval bottlenecks: too many reviewers or no clear final decision-maker, often the single biggest schedule risk on any project.
- Content readiness: migrating existing copy is fast, but rewriting it requires writer time and extra review cycles.
- Custom integrations and legacy platforms: older systems or complex APIs add real development time that’s easy to underestimate.
- Too many design revision rounds: each extra round of feedback adds days, sometimes weeks, to the design phase.
- Domain or URL changes: moving to a new domain or restructuring your URLs adds migration work and a longer monitoring window afterward.
Pro Tip: Before the project starts, name one person who has final sign-off authority on design and content. Everyone else gives input, but only one person decides.
How do you protect SEO rankings during a website redesign?
Search visibility is the easiest thing to lose in a redesign, and often the hardest to win back. The fix is mostly procedural: build your redirect map early and follow a few well-documented steps.
Want this running in your business without doing it yourself?
Book a Free Consultation →- Build a complete redirect map before launch, matching every old URL to the most relevant new URL. Avoid catch-all redirects that send everything to your homepage, since Siteimprove’s guidance notes these can be treated as soft 404s and tend to tank traffic.
- On launch day, deploy your redirects, submit an updated sitemap through Google Search Console, and confirm the new site can be crawled properly in staging first, following Google’s sitemap guidance.
- If you’re changing domains, use Search Console’s Change of Address tool only after your redirects are already live, and work through its pre-move checklist.
- Keep your 301 redirects active for at least 180 days after launch, longer if you still see traffic hitting old URLs, and consider renewing your old domain for a year to keep it out of someone else’s hands.
Google’s own Change of Address guidance recommends maintaining redirects for at least 180 days after a domain move so search engines have enough time to transfer ranking signals to your new site. Keep an eye on indexation, 404 errors, and traffic dips for several weeks after launch, and be ready to adjust redirects or canonical tags if something looks off. For ongoing monitoring once you’re live, our SEO services page covers what post-launch tracking should include.
How do you keep approvals and content decisions from stalling your project?
Governance sounds bureaucratic, but on a redesign it’s really just a handful of rules that stop the project from stalling.
- Name one final decision-maker and keep your reviewer list short, with each person’s responsibility spelled out.
- Set a fixed review window, three business days per round is reasonable, and cap design revisions at two or three rounds.
- Build a content governance spreadsheet that tracks which pages get kept, removed, or migrated, who owns each decision, and the deadline.
- Run parallel tracks where you can, writing new content while templates are being built, so dependencies don’t pile up at the end.
Documenting these decisions early, as research on stakeholder content management notes, prevents duplicate work and keeps large redesigns from drifting past their deadline.
Pro Tip: A one-page spreadsheet with columns for page, decision, owner, and deadline solves more scheduling problems than any project management software.
How do you turn a sample timeline into a real project plan?
Start with the milestone list, discovery, wireframes, design, development, content, QA, launch, and assign one owner to each. Build in slack for the two things that always run long: stakeholder approvals and content creation, usually an extra week per phase is enough cushion. If your site is large, plan a phased rollout that puts your homepage and top service pages live first while secondary content finishes behind the scenes.
- Milestone deliverables: a signed-off wireframe, an approved design file, a tested staging site, a completed redirect map.
- Dependency checks: confirm content is ready before development locks templates.
- Buffer placement: add slack after every review step, not just at the end of the project.
Our website preview workflow shows how staging and pre-launch checks fit into this kind of milestone plan.
What we’ve learned scoping redesign timelines for small businesses
Most timeline problems start before a single page gets designed, they start with scope nobody wrote down. We begin every project with a free audit specifically to pin down realistic deadlines before committing to a schedule. Keeping design, development, and content in-house removes the back-and-forth that happens when three different vendors are coordinating one launch. We also prioritize fixes that show up fast, broken forms, slow core pages, missing analytics, so owners see progress before the full redesign wraps.
— Cristo
Ready to start your website redesign?
If you’re an owner-operator who wants a clear timeline instead of a vague promise, a free audit is the fastest way to find out what your redesign actually needs.
Projects are scoped comprehensively from design through development and SEO to streamline timelines and communication. Check our pricing page to see plan options, or start with a free SEO audit to get a realistic timeline for your own project.
FAQ
How long should a website redesign take?
Most small business redesigns take a few weeks to a couple of months, medium projects with integrations typically require several months, and large or multi-location sites often take many months or more. The biggest factor isn’t page count, it’s how quickly stakeholders approve each phase.
How do I announce a website redesign?
Plan your announcement around your launch date, once redirects are live and the new site has passed QA testing. A short email or social post pointing customers to the new site, paired with monitoring for broken links in the first few weeks, covers most small business needs.
Is web design still worth it in 2026?
Yes. A redesign that fixes slow pages, broken forms, and outdated content still drives measurable gains in leads and customer trust, and following proper SEO migration steps like sitemap resubmission protects the rankings you’ve already earned.
What are the 5 stages of website development?
Most projects move through discovery, design (including wireframes and visual design), development, content migration, and QA and launch. Timelines vary widely by phase depending on project size, but each stage builds directly on the one before it.
Sources
- Use the Change of Address tool – Search Console Help
- Sitemaps – Google Developers
- How to manage stakeholder feelings in content decisions for website redesigns – Little Language Models
- Siteimprove — Website maintenance glossary
Recommended
Less reading. More growing.
We build the systems these articles describe. Websites, AI follow-up, reviews, automation. And run them for you.
Keep reading
