Last reviewed October 2026.
A website redesign blueprint is a ten-step plan that takes you from a clear goal to a safe launch. You set the goal and measure today’s site, decide what to keep, map every old address to a new one, build on a private copy, test, launch with redirects and then watch the numbers. Following the order protects your leads and your search traffic.
This post is the project plan: what to do, in which order, who does it and what must be true before you move on. For the checklist version, see our website redesign checklist. For SEO detail, see how to redesign without losing SEO. For the full guide, see our website redesign guide.
In this guide
- How the website redesign blueprint works
- Step 1: Set the goal and take a baseline
- Step 2: Audit your content
- Step 3: Map every old address to its new one
- Step 4: Choose the scope
- Step 5: Plan the sitemap and the job of each page
- Step 6: Gather the content and photos
- Step 7: Build on a private copy
- Step 8: Test everything
- Step 9: Launch with a checklist
- Step 10: Monitor and fix
- Who does what
- A made-up example: a content audit and URL map
- Questions to ask at the start
- Common mistakes
- Frequently asked questions
- Next steps
How the website redesign blueprint works
A good redesign has gates. A gate is a check you must pass before moving on. Skipping a gate is how sites launch with broken forms, lost pages and no tracking.
The ten steps fall into four phases.
| Phase | Steps | Main output |
|---|---|---|
| Plan | 1 to 3 | Goal, baseline numbers, content decisions, URL map |
| Design | 4 to 6 | Scope, sitemap, written content, photos |
| Build and test | 7 to 8 | A tested private copy of the new site |
| Launch and learn | 9 to 10 | Live site, redirects, monitoring |
Step 1: Set the goal and take a baseline
Write one goal in a sentence. “Get more calls from our top three services” is a goal. “Look modern” is not.
Then record where you are. Export what you can before touching anything.
- Calls and form messages from the last three months.
- Your top pages and top search queries from Google Search Console, which is free.
- Traffic by page from Google Analytics.
- Your current speed result from PageSpeed Insights.
- A full list of current pages and their web addresses.
Who: you, with help from your developer. Gate: you can say in one sentence what success looks like, and you have saved the numbers.
Step 2: Audit your content
Go through every page and sort it. Keep it, merge it with another, rewrite it or drop it. Be honest. Many small sites carry old pages nobody needs.
Google’s helpful content guidance asks whether a page gives original information and whether a reader will leave having learned enough to reach their goal. Use those as your test for each page.
Who: you decide, the designer advises. Gate: every page has a label: keep, merge, rewrite or drop.
Step 3: Map every old address to its new one
This is the step that protects your search traffic. Google’s site move guidance says to collect old addresses, map each to its new destination and update internal links, canonical tags and your sitemap. It says to use permanent server redirects, send each old address straight to its final page, and not to send many pages to an unrelated page such as the homepage.
The guidance also says to return a not-found status for content you are not carrying over, and to keep the redirects for as long as possible, generally at least one year. Read the full Google site move guide if your address will change.
Who: developer, with you checking the key pages. Gate: a spreadsheet with an old address and a new address for every page worth keeping.
Step 4: Choose the scope
Decide how big the project is. A refresh updates the look and content. A redesign changes layout and structure. A rebuild replaces the platform. Our refresh vs. redesign vs. rebuild guide explains the choice. Choosing the smallest scope that solves your goal saves time and risk.
Who: you and the designer. Gate: a written scope that lists what is in and what is out.
Step 5: Plan the sitemap and the job of each page
List the pages and say what each one is for. A service page should sell one service. The homepage should sort visitors. See what pages a small business website needs and what a homepage should include.
Who: designer, with your input. Gate: a one-page map with a purpose for every page.
Step 6: Gather the content and photos
Words and photos are the most common cause of delay. Gather them early. Use real photos of your work. Write for customers, not for search engines. State only facts you can back up.
Our guides on writing website content and small business photos can help.
Who: you, with a writer or designer. Gate: text and images for the main pages are approved.
Step 7: Build on a private copy
The new site should be built where the public cannot see it, on a staging copy. Search engines should not index it either. Google’s guide says to make sure your robots.txt and any noindex rules are right for the move, which also means removing the block when you go live.
Who: developer. Gate: all pages built on the private copy and ready for testing.
Step 8: Test everything
Test before launch, not after. Use a written list.
| Test | How | Pass looks like |
|---|---|---|
| Phone layout | Real phones, two sizes | No sideways scroll, readable, taps work |
| Speed | PageSpeed Insights, mobile | Core Web Vitals in the good range |
| Forms | Submit each one | Email and records arrive |
| Phone numbers | Tap them on a phone | Call starts |
| Links | Click through all menus | No broken links |
| Redirects | Test old addresses | Each lands on the right new page |
| Accessibility | Keyboard and contrast | Menu and forms work without a mouse |
| Tracking | Test events in Analytics | Calls and forms are counted |
Google lists good Core Web Vitals as 2.5 seconds or less for the main content, 200 milliseconds or less for response and 0.1 or less for layout shift. Treat them as targets and not promises of ranking.
Who: developer and you. Gate: every test above passes, or you have a written note on what is left.
Step 9: Launch with a checklist
Small and medium sites should generally move all at once, according to Google. Pick a quiet time, and have your developer on hand.
- Take a full backup of the old site.
- Turn on the redirects.
- Remove any block that told search engines to ignore the staging site.
- Check canonical tags and the sitemap.
- Submit the new sitemap in Search Console.
- Test forms, calls and tracking on the live site.
- Test twenty of your top old addresses.
If your domain changes, Google also asks you to use Change of Address in Search Console. Most small redesigns keep the same domain, so this does not apply.
Who: developer, with you testing. Gate: the live site passes the same tests, and the redirects work.
One more point on timing. Do not launch on a Friday afternoon, before a holiday, or during your busiest week. Problems found on launch day need people available to fix them. A quiet Tuesday morning is a better choice for most service businesses.
Keep the old site backed up and reachable by your developer for several weeks after launch. If a page or form turns out to be broken, you will want to check how it worked before.
Step 10: Monitor and fix
The first weeks after launch decide whether the redesign worked. Check these on a schedule.
| When | What to check |
|---|---|
| Day 1 | Forms, calls, tracking, top pages |
| Week 1 | Search Console errors, broken links, not-found pages |
| Weeks 2 to 4 | Indexing, queries, page speed, lead counts |
| Month 3 | Compare to your baseline from Step 1 |
Expect some movement in search results after a big change. Do not panic at the first dip, and do not ignore a steady drop either. Fix errors first. Be careful about changing many things at once.
Who: you and the developer. Gate: three months of numbers compared to your baseline.
Who does what
| Step | Owner | Developer or designer | Search Console or Analytics |
|---|---|---|---|
| 1. Goal and baseline | Leads | Helps | Source of numbers |
| 2. Content audit | Decides | Advises | Top pages |
| 3. URL map | Reviews key pages | Builds | Source of addresses |
| 4. Scope | Decides | Advises | None |
| 5. Sitemap | Reviews | Builds | None |
| 6. Content and photos | Supplies | Edits | None |
| 7. Build | Reviews | Builds | None |
| 8. Testing | Tests | Tests | Checks tracking |
| 9. Launch | Tests | Leads | Sitemap submission |
| 10. Monitor | Watches | Fixes | Main tools |
A made-up example: a content audit and URL map
Here is a hypothetical audit for a small contractor with 18 pages. The numbers are invented to show the method.
| Decision | Pages | Example | What happens to the old address |
|---|---|---|---|
| Keep | 6 | Homepage, three service pages, contact, reviews | Same address, or a redirect if it changes |
| Merge | 4 | Four thin pages on one service | Redirect each to the one combined page |
| Rewrite | 5 | Old service pages with out-of-date facts | Same address, new text |
| Drop | 3 | An expired promotion and two duplicate pages | Return a not-found status, or redirect to the closest match |
The audit shows that the real project is 11 pages, not 18. That changes the schedule and the plan.
Questions to ask at the start
- Who is the single person who can approve decisions for us?
- Who writes the words, and by what date?
- Where will the private copy live, and how do we review it?
- How will you protect our search traffic, and can I see the redirect map?
- What tracking will be set up before launch?
- What happens in the first month after launch?
Projects slip when no one owns approvals and when words arrive late. A named decision maker and a content date are worth more than a clever design.
Common mistakes
- Starting design before setting a goal.
- Changing addresses with no redirect plan.
- Sending every old page to the homepage.
- Forgetting to remove the staging block at launch.
- Launching without tracking.
- Writing new content after the design is done.
- Changing too many things at the same time and being unable to tell what helped.
Frequently asked questions
How long does a redesign take?
It depends on size, content and how fast you can answer questions. Our guide on how long a website redesign takes breaks down the phases.
Will a redesign hurt my search traffic?
It can if addresses change without redirects or content is removed. A good plan reduces the risk but cannot remove it. Watch Search Console after launch.
Do I need to keep my old addresses?
Keeping them is simplest. If you change them, use permanent redirects from each old address to the matching new one.
What should I save from the old site?
The page list, top queries, analytics numbers, photos, reviews, forms and any code snippets for tracking. Take a full backup too.
Can I redesign in phases?
Large sites can. Google says small and medium sites should generally move all at once, so plan one launch for most small business sites.
Next steps
- Write your one-sentence goal.
- Export your baseline numbers.
- Start the content audit with your top ten pages.
If you would like help with the plan, see our website redesign service or book your strategy call.
More on website redesign
- Website Redesign Guide for Small Businesses
- Website Refresh vs Redesign vs Rebuild
- How to Redesign a Website Without Losing SEO
- How Long Does a Website Redesign Take?
Want help with this in Carlisle or Central PA?
Webfactory Media is a Carlisle, PA agency. See our Carlisle web design and website redesign pages, or call (888) 849-2397 and we will look at your site for free.
