Chosen
Website Redesign Timeline: What Actually Happens From Planning to Launch
See what happens at each redesign stage, what your team must provide and which decisions affect the schedule.

Milan Gohil
·
9 min read
OVERVIEW
Here is a short version of what I write.
A website redesign timeline should cover discovery, scope, structure, content, design, build, migration, testing, launch and monitoring. Duration depends on the amount of change and how quickly dependencies are resolved.
Define the scope and review existing content first.
Assign content preparation and approval responsibilities.
Include migration, integration checks and launch testing.
Allow for review rounds and post-launch monitoring.
If someone tells you:
“Your website redesign will take six weeks.”
your next question should be: What exactly is happening during those six weeks? A 15-page website where most content and URLs stay the same is not the same project as a 150-page website moving to a new CMS with rewritten content, new navigation and changed URLs. So instead of starting with a number of weeks, understand the work first.

That is the basic journey. Some stages can overlap. Some websites need much more work inside each stage.
Stage 1: Review the website you already have
Before anyone redesigns anything, understand what exists. For an existing website, this usually means looking at:
important pages
services/products
current navigation
traffic-generating pages
enquiries/conversions
content that still matters
outdated content
forms
integrations
CMS/platform
obvious technical limitations
What you may need to provide
access to analytics/Search Console
CMS access
business goals
known problems
new services/products
plans for the next few years
What should come out of this stage
Something clearer than:
“The website looks old.”
You should know:
what works
what does not
what should be protected
what probably needs changing
Stage 2: Decide how much is actually changing
This is where you avoid paying for the wrong project. You might discover:
Keep
current CMS
blog
most existing URLs
useful service content
Change
homepage
navigation
visual design
service-page structure
Add
new services
case studies
stronger contact journey
Remove or merge
outdated pages
duplicate content
old campaigns
This is also where refresh vs redesign vs rebuild becomes much easier to decide.
Stage 3: Decide which pages the new website needs
Before designing the homepage, decide the broad website structure. For example:
HOME
SERVICES
Service A
Service B
Service C
INDUSTRIES
WORK / CASE STUDIES
ABOUT
RESOURCES
CONTACT
The exact structure depends on the business. But you should know:
which pages stay
which pages merge
which pages disappear
which pages are new
what belongs in navigation
before every screen gets designed.
Your role as the business owner
You should be able to confirm:
what you actually sell
which services matter most
customer types
locations
future plans
business priorities
You should not need to personally design the sitemap if you hired someone to handle strategy/UX.
Stage 4: Decide what each important page needs to say
You do not necessarily need every final sentence before design begins. But someone should know what the page needs. For a service page that might include:
What is the service?
Who is it for?
What problem does it solve?
What is included?
How does the process work?
What proof do we have?
What questions do buyers ask?
What should they do next?
This prevents an important problem: A designer creates a beautiful page with three small cards. Later you realise the service actually needs:
comparison table
technical details
case studies
six service variations
FAQs
Now the design has to be rebuilt around information nobody planned for.

Stage | Business provides | Website team handles |
|---|---|---|
Discovery | Goals, problems, access | Audit/research |
Sitemap | Services, priorities | Structure/navigation |
Content | Expertise, proof, approvals | Structure/copy support if included |
Design | Feedback | UX/UI |
Development | Required access | Build/integrations |
Migration | Missing business data | Move content/URLs/files |
QA | Business review | Technical/function checks |
Launch | Final approval | Deployment |
After launch | Business feedback | Monitoring/fixes if included |
This is much more useful than assuming:
“The agency will just handle everything.”
Some things can only come from the business.
Stage 5: Review designs before development starts
This is usually the first time the new website feels real. You may see:
homepage
service template
product/category page
article/resource template
contact page
mobile layouts
reusable components
You do not necessarily need a completely unique design for every page. But you should understand how the major page types will work.
What you should check
Not:
“Do I like the colour?”
Start with:
Can I understand the page?
Is important information missing?
Does this work for the customer journey?
Is the proof in the right place?
Is the next step clear?
Does the design work with real content?
Visual preference matters. But function matters first.
Stage 6: Development begins
Once important structures and designs are approved, the website gets built. Depending on the project, this may include:
page templates
CMS
responsive behaviour
forms
animations
search/filtering
ecommerce
CRM connections
analytics
third-party integrations
For a business owner, this is usually a quieter stage. You should not need to supervise the code. But you may still need to provide:
account/API access
CRM credentials
payment/service information
final content
missing images/files
This is why access problems can delay projects unexpectedly.
Stage 7: Existing content and SEO need to move safely
If the website already receives search traffic, this is not something to think about the night before launch. Before launch, you should know:
which URLs stay
which URLs change
which pages were merged
which pages were removed
where changed URLs redirect
what content/media is migrating
whether metadata/internal links changed
whether analytics/Search Console remain connected
Google recommends preparing an old-to-new URL mapping when URLs change, updating internal links, using appropriate redirects and monitoring the site after the move. It also notes that significant migrations can cause temporary ranking fluctuations while Google recrawls and processes changed URLs. Google: site moves with URL changes.
One question worth asking your website provider
“Which existing URLs are changing, and where can I see the redirect/migration plan?”
If an established site is being heavily restructured and nobody has considered that question, investigate before launch.
Stage 8: Test the actual website
Do not approve a redesign only from Figma. Test the built website. Try the things customers need to do:
find an important service
contact the company
submit the main form
use it on mobile
open important downloads
use filters/search if relevant
purchase/book where relevant
navigate between important pages
Also check the business information:
phone numbers
addresses
pricing
service areas
staff details
legal information
email destinations
The website can be technically correct and still contain incorrect business information. That is something the business owner is best placed to catch.
Stage 9: Launch
Launch should not mean:
“The developer pushed it live. Done.”
At minimum, someone should confirm:
□ Main pages load correctly
□ Important forms work
□ Mobile layouts work
□ Analytics is collecting data
□ Search engines can access the site
□ Redirects work where URLs changed
□ Sitemap is correct
□ Important integrations work
□ Contact details are correct
□ No temporary staging restrictions remain
Google specifically warns site owners to remove temporary noindex or robots.txt restrictions used during development before the live migration, because leaving them in place can stop important pages from being indexed. You do not need to perform those technical checks yourself. You need to know somebody is responsible for them.
Stage 10: Watch what happens after launch
The new website going live is not proof that the redesign worked. During the first period after launch, watch things like:
enquiries
forms
sales/bookings
traffic
important landing pages
Search Console
indexing
broken pages
customer feedback
If URLs changed, monitoring matters even more. Google recommends watching both user and crawler traffic and checking for unexpected errors while a site move is processed. This is also why your redesign should have a before-launch baseline. Otherwise, later you only know:
“The new site feels better.”
not:
“The new site performs better.”
How long should all this take?
There is no useful universal answer. Instead, look at complexity.

Lower complexity
15–30 pages
Same CMS
Most URLs stay
Existing content mostly stays
Few integrations
One decision-maker
Higher complexity
100+ pages
New CMS
New sitemap
Content rewrite
Many URL changes
Ecommerce
CRM / API integrations
Multiple languages
Multiple decision-makers
The second project should not be expected to follow the same schedule as the first.
Before accepting a timeline, ask these 10 questions
This is the part worth keeping next to any website proposal.
1. How many existing pages are actually being reviewed?
Not:
“Up to 20 new pages.”
What happens to the other 120 URLs already on the site?
2. Who is responsible for the content?
Are you providing final copy? Is copywriting included? Is existing content simply being copied?
3. Is the sitemap/navigation being reconsidered?
Or is the old structure simply getting a new design?
4. Are we keeping the same CMS?
If not, what is being migrated?
5. Are existing URLs changing?
If yes, is redirect planning included?
6. Is SEO migration included?
Not:
“Basic SEO.”
Ask what that actually means.
7. What integrations need to keep working?
Examples:
CRM
booking
payments
forms
email marketing
product feeds
8. What will you need from us, and when?
This exposes dependencies before they become delays.
9. How many review/approval stages are included?
If five stakeholders need to approve every screen, plan for it.
10. What happens after launch?
Is monitoring/fixing included? For how long?

Not every delay comes from development. Often the project was never ready for the next stage.
Want AI to review a redesign timeline or proposal for you?
If an agency, freelancer or internal team has already given you a proposal, paste it into an AI tool with this prompt.
I am planning to redesign this website:
CURRENT WEBSITE:
[PASTE WEBSITE URL]PROPOSED SCOPE / AGENCY PROPOSAL:
[PASTE PROPOSAL, SCOPE OR TIMELINE]Review this as a business owner who wants to understand exactly what is included before approving the project.
Do not judge the proposal only by how many weeks it takes.
First identify:
1. What is actually changing?
2. What appears to stay the same?
3. Whether the CMS/platform changes
4. Whether the sitemap/navigation changes
5. Whether existing content is being reviewed
6. Whether new content is being written
7. Whether existing URLs will change
8. Whether SEO migration is included
9. Whether analytics/tracking is included
10. Whether forms/integrations need rebuilding
11. Whether existing images/files/content need migrating
12. Whether post-launch monitoring is includedThen create a simple stage-by-stage explanation:
STAGE
What happens.BUSINESS NEEDS TO PROVIDE
What information, content, access or approval I will need to give.AGENCY / FREELANCER SHOULD HANDLE
What I should reasonably expect the website team to deliver.POSSIBLE DELAY
What could hold this stage up.OUTPUT
What should exist before moving forward.Then identify:
- important work that appears missing
- unclear responsibilities
- things the proposal assumes I will provide
- decisions that need to happen early
- SEO/migration risks
- anything being left until too close to launchDo not invent work that is not written in the proposal.
Finish with:
- what looks clear
- what needs clarification
- the 10 questions I should ask before approving the project
This is especially useful when two proposals have very different prices or timelines. Instead of comparing:
6 weeks vs 10 weeks
you can compare:
What is actually included?
Your job is not to manage every website task
If you hire a good team of people like (Webshunya team🙂↔️), you should not need to become:
UX designer
SEO specialist
developer
migration expert
QA engineer
But you should understand enough to know: what is happening next what they need from you what must be protected what is included what is missing and what “finished” actually means That is what makes a redesign timeline useful. Not the number of weeks printed at the top of a proposal.
Sources
All Blogs
All Blogs & Articles
© 2026 Webshunya Studio®. All rights reserved.







