Website Redesign Process: 8 Steps, Timeline and Checklist

Most redesigns that go wrong were planned as visual projects. The team agrees on a new look, the agency delivers it, and three weeks after launch organic traffic is down by a third because half the old URLs now return 404. Or the site looks better and converts worse because nobody checked which pages were doing the selling.

A website redesign is a product decision with a visual layer on top. This guide covers the process we use at Glow for startup and SaaS sites: how to decide whether you need a full redesign, the eight steps from audit to post-launch monitoring, how to keep your rankings, realistic timelines and a checklist you can copy.

Redesign vs refresh: do you need a full redesign?

Not every tired website needs a rebuild. Before you commit budget and two months of your team's attention, figure out which of three jobs you actually have.

A full redesign usually makes sense when one of these is true:

> * Your product or positioning has moved. The site still sells the thing you built two years ago, or speaks to an audience you no longer target.

> * The structure fights you. Adding a new feature page means hacking the nav, and visitors can't find pricing without a search.

> * The platform blocks the team. Marketing waits on developers for every text change, or the CMS can't handle the content model you need.

> * Performance and accessibility problems are baked into the templates, so fixing them page by page costs more than rebuilding.

> * Analytics show a clear leak: high traffic to key pages, low movement to demo, signup or contact.

If none of these apply and the site simply looks dated, a refresh is cheaper and keeps your SEO intact. A website UX audit is a good way to settle the question with evidence instead of opinions.

The website redesign process in 8 steps

1. Audit the current site and record baselines

You can't call a redesign a success if you never wrote down where you started. Before anyone opens Figma, export the numbers you'll compare against after launch:

> * Organic clicks, impressions and top queries per page from Google Search Console

> * Sessions, engagement and conversions per landing page from GA4

> * Core Web Vitals for your main templates

> * Backlinks per URL from Ahrefs, Semrush or a similar tool

> * A full crawl of the current site (Screaming Frog or Sitebulb) with every URL, title, meta description, H1 and status code

The crawl matters more than people expect. It becomes the source list for your redirect map in step 4, and it's the only reliable record of what existed once the old site is gone.

Alongside the numbers, do a qualitative pass. Watch ten or fifteen session recordings on your key pages, read support tickets and sales call notes, and note where people get stuck. This tells you which problems the redesign must solve, and which pages are quietly doing their job and should be left alone.

2. Set goals and scope

"Make it look modern" is not a goal. Tie the redesign to two or three outcomes you can measure against the baselines: demo requests from the pricing page, trial signups from organic traffic, fewer support questions about a confusing flow.

Then fix the scope in writing:

> * Which page templates are in scope, and how many unique layouts that means

> * Whether content is being rewritten, migrated as is, or a mix

> * Whether the platform changes

> * Who approves design decisions, and how many rounds of feedback each stage gets

> * What is explicitly out of scope (blog redesign, new integrations, localization)

Scope creep is the most common reason redesigns slip. Someone sees the new homepage and asks for a new careers section, then a resource hub, then a partner portal. A written scope gives you a reason to put those in a second phase. If you're working with an agency, a solid web design brief covers most of this before the contract is signed.

3. Research users and competitors

The research stage answers two questions: what do the people landing on your site need to decide, and how are your competitors framing the same decision?

For users, five to eight interviews with recent customers and lost deals usually surface the same handful of themes: the words they used to search, the objections they had, the proof that convinced them. Pair that with what you learned in the audit. If your recordings show visitors scrolling past the hero straight to the integrations section, that's a signal about what the hero should say.

For competitors, pick four or five sites your buyers also look at. Map their positioning, page structure, pricing presentation and proof (case studies, logos, numbers). You're not copying layouts. You're finding the claims everyone makes, so you can avoid sounding like everyone, and the gaps nobody covers.

4. Plan content, sitemap and the URL map

This step decides whether your redesign keeps its search traffic. It has three outputs.

The new sitemap. Group pages by what visitors need: product, use cases or industries, pricing, proof, resources, company. Keep the main nav to five to seven items. If a page doesn't fit anywhere, ask whether it needs to exist.

The content plan. For every page in the new sitemap, decide whether content is kept, rewritten, merged or new. Assign an owner and a due date. Content is the step that delays launches most often, because designers finish layouts while copy is still in a shared doc with forty unresolved comments. Writing copy before or during wireframing, not after, removes most of that delay.

The URL map. Take the crawl from step 1 and add a column for each old URL's new destination. Every old URL needs one of three outcomes: it stays the same, it redirects to the most relevant new page, or it is deliberately retired with a 410 because nothing equivalent exists. Prioritize the rows with organic traffic or backlinks, but map them all. A spreadsheet works fine.

At Glow, the positioning brief and the sitemap are signed off by the end of week one, before wireframes start. Changing the structure later costs much more than changing it on paper.

5. Wireframes and prototypes

Wireframes test structure and hierarchy without the distraction of colors and photography. Start with the pages that carry the most traffic or revenue, usually the homepage, pricing, a main product page and one use case or industry page. Lay them out with real copy, or at least realistic copy length. Lorem ipsum hides problems: a headline that looks fine as two placeholder words breaks the layout as a real twelve-word value proposition.

Clickable prototypes are worth building for flows with several steps, like signup, demo booking or a pricing calculator. Put them in front of three to five people from your target audience and give them a task. You'll find the confusing step in an afternoon instead of after launch.

6. Visual design and design system

Once the structure is approved, apply the visual layer. For a startup site, the design should do two things at once: look like the brand and stay buildable and maintainable by a small team.

That second part is where a component library pays off. Instead of designing every page as a one-off, design reusable sections (hero variants, feature grids, testimonial blocks, pricing tables, CTAs) and assemble pages from them. Your marketing team can then build new landing pages in the CMS without a designer, and the site stays consistent a year later.

Check accessibility at this stage, not after the build: color contrast, focus states, text size, touch target size, alt text plans for images. Retrofitting contrast into a finished visual system usually means redesigning half the components.

7. Build, migrate content and test

Development turns the design system into templates and the templates into pages. Whatever the stack, two technical decisions affect SEO and AI search directly:

> * Rendering. Search engines and AI crawlers should get the main content in the HTML response. A site that renders content only in the browser through JavaScript can be indexed late or partially. We cover the trade-offs in SPA vs MPA.

> * Performance. Set budgets for page weight and test Core Web Vitals on the staging site. Google's thresholds for a "good" experience are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1.

Content migration runs in parallel. Move pages into the new CMS, then check that every page has its title tag, meta description, H1, canonical tag, alt text and structured data where you used it before. Old blog posts are the usual victims here: they get migrated in bulk, and the metadata quietly disappears.

Before launch, test on staging (blocked from indexing with a password or noindex):

> * Every form, with submissions reaching the CRM

> * Analytics and conversion events firing on the new templates

> * Main browsers and real mobile devices, not just a resized desktop window

> * Redirects from the URL map, tested in bulk with a crawler in list mode

> * Internal links pointing to new URLs directly, not through redirects

8. Launch, redirect and monitor

Launch early in the week, when the team is around to fix problems. Avoid Fridays and the day before a big campaign.

On launch day, remove the staging noindex (forgetting this is more common than anyone admits), deploy the redirects, submit the new XML sitemap in Search Console and crawl the live site to catch broken links and redirect chains.

Then watch. Some ranking movement in the first weeks after a structural change is normal while Google recrawls and processes the redirects. What you're looking for is anything that doesn't recover: pages that dropped out of the index, queries that lost positions and stayed down, 404s showing up in Search Console's indexing report. At Glow we monitor the first 30 days after launch and compare against the baselines from step 1.

How to protect SEO during a website redesign

Most of the SEO work sits inside the steps above, but it's worth pulling the rules together, because this is where redesigns lose the most value. For the full step-by-step checklist, see our guide to website redesign SEO.

Keep URLs where you can. The safest redirect is the one you don't need. If a page keeps its purpose, keep its URL, even if the slug isn't perfect.

Redirect one to one. Each old URL should redirect to the closest equivalent page, with a 301 or 308 status. Pointing hundreds of old URLs at the homepage looks like a shortcut, but Google tends to treat those redirects as soft 404s, so the old pages' signals don't carry over.

Avoid redirect chains. If your old site already had redirects, update them so that every legacy URL points straight to its final destination. Chains of three or four hops waste crawl budget and slow down users.

Keep redirects in place for a long time. Google's guidance on site moves recommends keeping them for at least a year. In practice, keep the ones with backlinks indefinitely.

Carry the on-page signals over. A page that ranked for a query did so partly because of its title, headings and content. If the redesign rewrites that page, keep the topic and the main terms, and don't cut the sections that answered the query.

Update internal links and the sitemap. Internal links should point to final URLs. The XML sitemap should list only live, indexable pages.

Check that AI crawlers can read the site. Assistants like ChatGPT and Perplexity are a growing source of referral traffic for B2B products. Many of their crawlers don't run JavaScript the way Googlebot does, so content that only appears after client-side rendering may be invisible to them. Check your robots.txt as well: some new templates ship with rules that block these bots by accident.

How long does a website redesign take?

Timeline depends mostly on the number of unique templates and on how ready your content is. Page count matters less than people think: a 200-page blog uses one template, while a 15-page marketing site can have 12 distinct layouts.

For a typical startup site at Glow, the work takes 6 to 10 weeks: research, positioning and sitemap in week one, then wireframes, visual design, build and QA, with the redirect map ready before launch. Projects with many templates or a platform migration run 12 weeks or more. A landing page takes 2 to 3 weeks. More on what's included is on our web design services page.

The usual delays are predictable: copy that isn't ready, feedback that takes a week instead of two days, and new pages added mid-project. Plan for client review time in the schedule, not just design and development time.

Website redesign checklist

Common website redesign mistakes

Starting with visuals. Moodboards are fun and quick to approve. They also lock in decisions before anyone has looked at what users need or what the content says.

Cutting pages that rank. A page that looks like clutter to the marketing team may bring in a third of your organic signups. Check the data before you delete or merge anything.

Leaving copy until the end. Designing around placeholder text produces layouts that break when real copy arrives, and the launch date slips while everyone rewrites.

Designing by committee. When eight people can comment on every frame, feedback turns into compromise. Name one decision maker per stage and keep everyone else in a consulted role.

Treating launch as the finish line. The first month after launch is when you find what testing missed. Budget time for fixes and for a round of improvements based on real behavior.

How much does a website redesign cost?

Cost follows the same drivers as timeline: number of templates, how much content is rewritten, platform changes and integrations. According to Clutch's pricing survey, the average web design project costs around $38,000, and most US agencies bill between $100 and $149 per hour. Freelancers come in lower, larger agencies with research and strategy included come in higher.

For a full breakdown of pricing models and what each one includes, see our guide to web design agency pricing.

FAQ

How can I redesign my existing website?

Start with an audit: export your analytics and Search Console data and crawl every URL on the current site. Set measurable goals, plan the new sitemap and map each old URL to its new home. Then move through wireframes, visual design, build and testing, launch with redirects in place and monitor results against your baselines for at least a month.

How much does it cost to have a website redesigned?

It depends on scope. A landing page or small refresh can cost a few thousand dollars, while a full redesign of a startup or SaaS marketing site with research, copy and a CMS build typically runs from the high teens to the mid five figures. Clutch puts the average web design project at about $38,000.

How long does a website redesign usually take?

A small marketing site takes 6 to 10 weeks, a landing page 2 to 3 weeks, and larger SaaS sites with many templates 10 to 14 weeks or more. Enterprise and multi-language sites can take three to six months. Content readiness and feedback speed affect the timeline as much as design and development do.

What are the 7 steps in web design?

Most versions of the process list discovery, planning, wireframing, visual design, development, testing and launch. For a redesign we add an eighth: post-launch monitoring, because comparing results against your baselines is the only way to know whether the redesign worked.