StackLift
All playbooks

Playbook

Website Redesign Plan

A redesign plan that protects what already works. It starts with goals and a content audit, maps every old URL to a new one, and ends with launch checks and monitoring.

Best reader

Marketing leads, founders and product owners planning a new site or a major refresh

Outcome

A plan with goals, a page inventory, a redirect map, a launch checklist and a post-launch review.

Use this sequence

1

Set goals and name the pages that earn traffic and leads today.

2

Audit content and keep, merge, rewrite or retire each page.

3

Design the new sitemap and map every old URL to its new home.

4

Build on a hidden staging site and review against the audit.

5

Run launch checks: redirects, metadata, analytics, speed, accessibility.

6

Monitor for weeks after launch and fix what slipped.

Do not restyle without a reason

A redesign should serve a goal such as clearer messaging, faster pages or easier editing. Without one, you only change the look.

Write the goal in one sentence

List pages that must not lose ranking

Decide what content moves as is

Treat URLs as an asset

Changing addresses without redirects breaks links and search visibility. A redirect map is the single most important document in the project.

One row per old URL

Permanent redirects to the closest match

Images and documents included

Launch is a process

Compare staging with the live site, submit the new sitemap and watch the numbers for several weeks.

Crawl before and after

Check indexing and errors

Review analytics against the baseline

Start in 60 seconds

Turn this checklist into a scoped plan.

Answer a few questions and get an AI-assisted, architect-reviewed scope, cost range, and timeline for your software project.

Frequently asked questions

Will a redesign hurt our search rankings?

It can if URLs, content and metadata change without a plan. With a content audit, a complete redirect map and post-launch checks, the risk is much lower.

Should we redesign or rebuild the site?

Redesign when the platform works and the problem is messaging or layout. Rebuild when the platform blocks speed, editing or integrations.

The complete guide

Website Redesign Plan: the complete guide

Updated November 18, 2026 ยท Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

A website redesign plan sets a goal, audits the existing content, designs a new sitemap, maps every old URL to a new one, builds on a hidden staging site, runs launch checks and monitors results afterward. The step most teams skip is the redirect map, and it is the one that protects your search traffic.

Why redesign a website, and when is it the wrong move?

A redesign is worth doing when it serves a goal you can name: clearer messaging, faster pages, an easier editing workflow, a better path to a sale or sign-up, or a platform that no longer supports what you need. If you cannot state the goal in one sentence, you are likely about to restyle the site, not improve it.

It is the wrong move when the real problem is something a redesign cannot fix, such as thin content, an unclear offer or no traffic source. In that case fix the content and the offer first. When the platform itself blocks you, a rebuild may fit better; see the web application cost range and the CMS and website cost range for what drives the work.

What are the steps in a website redesign?

  1. Set goals and a baseline. Output: one-sentence goal, current traffic, leads and speed numbers recorded. Involve the marketing lead and owner.
  2. Audit content and URLs. Output: a page inventory marked keep, merge, rewrite or retire. Involve marketing and an SEO owner.
  3. Plan the new structure. Output: a sitemap, page templates and a redirect map. Involve design, SEO and engineering.
  4. Design and write. Output: approved designs and final copy for key pages. Involve design and content owners.
  5. Build on staging. Output: a working site hidden from search engines and tested. Involve engineering and QA.
  6. Launch and monitor. Output: a launch checklist completed and a weekly review for several weeks. Involve everyone above.

The sections below give you the checks for each step. If the site is part of a product launch, pair it with the SaaS MVP launch plan.

What should you measure before you change anything?

You can only judge a redesign if you know where you started. Record the numbers that matter to your goal now, before the work begins, and keep a copy outside the analytics tool.

Baseline to record
AreaWhat to captureWhere it comes from
Search visibilityPages that earn organic traffic and the queries behind themSearch Console
Traffic and conversionVisits, sign-ups, enquiries and orders by pageAnalytics
SpeedLoad and responsiveness on key pagesA performance test tool
Technical stateA full crawl: status codes, titles, headings, canonicals, redirectsA crawler
LinksPages other sites link toA backlink report
Business resultsLeads and revenue tied to the siteCRM or store

If your analytics setup is unreliable, fix it first. See the Google Analytics 4 integration guide for what to track.

How do you run a content audit?

List every page, with its address, purpose, traffic, links and conversion role. Then decide what happens to each page. The audit prevents two classic mistakes: deleting pages that quietly earn traffic, and carrying over dead weight.

Content decisions
DecisionWhen to use itWhat happens to the URL
KeepPage performs and is accurateSame URL, or a redirect if the address must change
RewriteRight topic, weak or outdated copySame URL, new content
MergeSeveral thin pages on one topicRedirect old pages to the merged one
RetireNo traffic, no purpose, no linksRedirect to the closest relevant page, or remove with the right status
CreateGap found in the auditNew URL and a place in the sitemap

Include images, documents and downloads, not just pages. Files with their own addresses can carry links and traffic as well.

How do you plan URLs and redirects?

A redirect map is a table with one row per old URL and its new destination. When an address changes, a permanent redirect tells visitors and search engines where the page went, and passes along most of its standing. Without it, old links and bookmarks lead to errors and rankings suffer.

  • Keep URLs the same wherever you can. The fewest changes are the safest.
  • Redirect each old URL to the closest equivalent page, not to the home page.
  • Avoid chains: redirect straight to the final address.
  • Cover old images, documents and media files that have links.
  • Plan canonical tags, hreflang and the new XML sitemap together with the map.
  • Test the whole map on staging with a crawler before launch.

Moving between platforms makes this more important. See the guides for WordPress, Webflow and Shopify for platform notes.

How do you build and review on staging?

Build the new site on a staging address that search engines cannot reach. Password-protect it or block it, and remember to remove the block at launch. Review against the audit, not against taste: does each kept page carry its title, description, headings, structured data and links?

Staging review
CheckWhat good looks like
MetadataUnique titles and descriptions carried over or improved
StructureOne main heading per page and a sensible heading order
Internal linksNo links to staging addresses or to retired pages
RedirectsEvery row of the map tested
Forms and trackingSubmissions arrive and analytics events fire
AccessibilityKeyboard use, contrast and text alternatives checked
SpeedKey pages load quickly on a mid-range phone

If the site needs custom features, treat it like any software release and follow the production readiness checklist.

What should the launch checklist include?

Launch during a quiet period and keep the old site available for rollback until you are sure. Run through a short list, in order, and assign each item to a person.

  1. Take a final backup of the old site and a final crawl.
  2. Deploy the new site and switch the address.
  3. Remove any search-engine block left over from staging.
  4. Test the redirect map on the live site with a crawler.
  5. Confirm analytics, forms, payments and email alerts work.
  6. Submit the new XML sitemap and check Search Console for errors.
  7. Watch traffic, errors and conversions daily for the first weeks.

What happens after launch?

Expect some movement in search results as engines re-crawl the site. Compare against your baseline each week, fix new errors, and restore any page that was dropped by mistake. Redirects should stay in place for a long time, not weeks.

Then plan for upkeep: content updates, plugin and dependency updates, backups and monitoring. The post-launch maintenance plan gives a template. To scope a redesign or rebuild, run the free estimate or contact us.

Questions people ask

Will a redesign hurt our search rankings?

It can if addresses, content and metadata change without a plan. A content audit, a full redirect map and post-launch monitoring reduce the risk, though some movement is normal while engines re-crawl.

What is a 301 redirect?

A permanent redirect that tells browsers and search engines a page has moved to a new address. It passes visitors to the new page and signals that the old address should be replaced in results.

Should we keep the old site live during the build?

Yes. Build on a separate staging site hidden from search engines and keep the old site running until launch. Keep a backup or the old environment available for rollback.

Do we need to redesign every page?

No. Focus on pages that earn traffic or leads and on the templates they use. Leave low-risk pages for later, and carry over what already works.

How long should redirects stay in place?

As long as the old addresses still receive links or visits, which is often for years. Removing them early recreates the errors the map was meant to prevent.

Should we change platform during a redesign?

Only if the platform blocks your goals. Changing platform and design together raises risk, so some teams move the platform first and redesign after, or the reverse.

Sources

Sources and further reading

The standards, rules, research and official documentation this page draws on.