A redesign is one of the few website projects that can make things worse. A shiny new site that drops half your search traffic is not an upgrade. The good news: almost every redesign disaster comes from skipping the same few steps. This checklist is the order we work through them.
Stage 1: Audit before you change anything
List every page that gets traffic
Export your top pages from Google Search Console (Performance → Pages) and, if you have it, your analytics tool. Note which pages bring visitors, which ones rank for valuable searches, and which ones lead to enquiries. These are the pages you must protect.
Note your inbound links
Search Console's Links report shows which of your pages other websites link to. Those links carry authority. If a linked page disappears without a redirect, that authority is lost.
Take a full backup
Files, database (if there is one) and a copy of every page's text. Even if you hate the old site, you'll want to refer to it.
Stage 2: Decide what stays, changes or goes
| Keep | Fix | Remove or merge |
|---|---|---|
| Pages with steady search traffic | Slow, image-heavy pages | Outdated news and dead offers |
| URLs that other sites link to | Weak titles and meta descriptions | Thin pages with a few lines of text |
| Testimonials and case studies | Layouts that break on phones | Several pages competing for the same search |
| Content customers still ask about | Hidden or confusing contact options | Pages nobody visits and nobody links to |
The aim is a smaller set of stronger pages, not a copy of the old structure in a new coat of paint.
Stage 3: Plan the new structure
- Keep URLs the same where you can. It's the single easiest way to avoid a ranking dip.
- Write a redirect map for every URL that changes: old address in one column, new address in the other. Every old page should point to its closest new equivalent with a 301 redirect, not to the homepage.
- Plan the navigation around customer questions, such as what you do, who it's for, proof, price and how to contact you.
- Decide the platform. A static HTML site is fast and low-maintenance for most service businesses; WordPress suits sites that need frequent editing or many authors.
Stage 4: Build and check on a preview link
Build the new site somewhere private and walk through it on a real phone. Before launch, check:
- Every page has a unique title, meta description and one clear H1
- Images are compressed and have descriptive alt text
- Forms send to the right inbox and you've received a test message
- Click-to-call and WhatsApp links work on mobile
- No pages still point to the old site or to placeholder links
- The preview is blocked from search engines so it isn't indexed early
Stage 5: Launch day
- Take one more backup of the old site.
- Publish the new site and apply the redirect map.
- Remove any "noindex" left over from the preview.
- Test a sample of old URLs to confirm each one redirects correctly.
- Upload the new sitemap.xml and submit it in Search Console.
- Check HTTPS works across the site with no mixed-content warnings.
Stage 6: The first month after
Watch Search Console for crawl errors and "not found" pages, and fix them with redirects as they appear. A small wobble in rankings for a week or two is normal while Google re-crawls the site. A steady decline usually points to missing redirects or removed content, both of which are fixable if you catch them early.
Rule of thumb: if a page brings in traffic or links today, it either stays at the same URL or gets a 301 redirect to its new home. No exceptions.
Want this handled for you?
Get Website Services builds, redesigns and grows websites for small businesses worldwide, with written quotes in USD or INR and one accountable team from start to finish.