A new website should bring you more enquiries, not fewer. Yet redesigns regularly cause search traffic to drop, usually for avoidable reasons: pages disappear, addresses change without redirects, or content that Google trusted is replaced with something thinner.
The good news is that a redesign done carefully protects what you've earned and gives you a stronger base to grow from. This guide walks through the process step by step. It's the same process we're following to rebuild our own website, which is moving from WordPress to Next.js on the same domain.
What to expect: Google itself says to expect temporary fluctuation in rankings during a move (Google Search Central (opens in a new tab)). A careful migration limits the risk. It can't guarantee rankings, and no honest developer will promise that.
Step 1: Take an inventory of every URL
Before changing anything, list every address your current website has, including the ones you rarely think about:
- pages and blog posts
- category and tag archives
- author pages
- feeds and old sitemaps
- important images and PDF files that people link to
Pull these from your sitemap, a crawl of the site and Google Search Console. In our own rebuild, the inventory came to 166 URLs, including 109 blog posts, category and author pages, feeds and old sitemap files. Many of them weren't visible anywhere in the main navigation.
Step 2: Find out what's actually working
Not every page deserves to be kept, but you need evidence before you remove anything. In Google Search Console:
- Performance → Pages (last 12 months): which pages earn impressions and clicks
- Performance → Queries: what people search to find you
- Links → Top linked pages: which pages other websites link to
Pages with traffic, rankings or backlinks need the most care. When we reviewed our own data, one article (an ecommerce cost guide) had earned more search impressions than all our other blog posts combined. It became our top priority to rewrite at its existing address, rather than move.
Step 3: Decide keep, rewrite, merge or redirect
For each URL, make one of four decisions:
| Decision | When | What happens to the URL |
|---|---|---|
| Keep | The page performs and its content is still right | Same address, carried over or refreshed |
| Rewrite | The page ranks, but the content is weak or outdated | Same address, new content |
| Merge | Several pages cover the same topic | One page keeps or gets the address; the others redirect to it |
| Redirect | The page has no future of its own | Permanently redirected to the closest relevant page |
The golden rule: don't change addresses you don't need to change. A URL that stays the same needs no redirect and loses nothing.
Avoid redirecting everything to the homepage. Point each old URL to the page that best matches what the visitor was looking for. Google warns that redirecting many old URLs to one irrelevant page, such as the homepage, can confuse users and might be treated as a "soft 404", in other words as a missing page (Google Search Central (opens in a new tab)). If a page is gone and nothing similar replaces it, letting it return a 404 is better than a misleading redirect.
Step 4: Use the right kind of redirect
Redirects send visitors and search engines from an old address to a new one. The type matters:
- Permanent (301 or 308): "this page has moved for good." Google treats the new address as the main version (Google: redirects (opens in a new tab)). Use these for pages you've merged or replaced.
- Temporary (302 or 307): "this is short-term." Google generally keeps showing the original address. Use these only when the page is coming back, for example a post that's being rewritten and will return at the same URL.
Google also recommends:
- server-side redirects wherever possible, rather than JavaScript-based ones
- no redirect chains (A → B → C)
- keeping redirects in place for generally at least one year, or indefinitely for visitors (Google Search Central (opens in a new tab))
In our rebuild, posts we're rewriting use temporary redirects until their new versions are published. Posts merged into other pages use permanent ones.
Step 5: Carry the SEO details across
For every page that stays or is rewritten, check:
- Title and meta description: don't lose ones that perform; improve weak ones deliberately
- Headings and main content: keep what made the page rank, and make it better
- Internal links: update them to point straight to the new addresses, not through redirects
- Canonical tags: each page should point to its own final address
- Structured data: carry over or add, matching what's visible on the page
- Images: keep descriptive file names and alt text
Step 6: Test before you switch
Build the new site somewhere private first, such as a staging address with search indexing blocked, and test:
- every old URL from your inventory, checking that it either loads or redirects in one step to a page that exists
- forms, payments and enquiry tracking
- speed and mobile layout on real phones
- that the live site isn't blocking search engines. A leftover "noindex" setting or
robots.txtrule from staging is a common and costly mistake.
We automated the first check for our own site. A script runs every old address against the new redirect rules and confirms all 166 resolve to a live page.
Step 7: Launch and monitor
On launch day and in the weeks after:
- Submit the new sitemap in Google Search Console and remove the old one
- Check the Pages report for errors and pages that drop out of the index
- Test your top pages manually: the ones with the most traffic and links
- Compare performance against your 12-month baseline: clicks, impressions and the queries that matter to your business
If you're keeping the same domain, you don't need Google's Change of Address tool. It's only for moves between domains (Google Search Central (opens in a new tab)).
A redesign checklist
- Full inventory of old URLs (pages, posts, archives, feeds, files)
- 12 months of Search Console data saved as a baseline
- Keep / rewrite / merge / redirect decided for every URL
- Important URLs kept unchanged wherever possible
- Permanent redirects to the closest relevant page; no chains, no blanket homepage redirects
- Temporary redirects only for pages that are coming back
- Titles, content, internal links, canonicals and structured data checked
- Every old URL tested before launch
- Search engines allowed on the live site
- New sitemap submitted, and performance monitored against the baseline
Questions to ask your developer
- How will you find every URL on our current site?
- Which pages will keep their addresses, and how did you decide?
- How will redirects be set up and tested?
- What will you check on launch day, and who monitors Search Console afterwards?
If the answers are vague, see our guide on how to evaluate a website development proposal.
How we can help
We plan redesigns and platform moves with search visibility in mind, from the URL inventory to launch-day checks. Explore our website development services and website design services. After launch, our website maintenance services keep the site healthy and up to date.
Frequently asked questions
Will I lose my Google rankings if I redesign my website? Some temporary fluctuation is normal, and Google says to expect it. Keeping important URLs unchanged, redirecting the rest to relevant pages and preserving strong content limits the risk. No one can guarantee rankings.
How long should I keep redirects? Google recommends keeping redirects generally for at least one year, and suggests keeping them indefinitely for visitors where you can.
Should I use a 301 or 302 redirect? Use 301 (permanent) when a page has moved for good. Use 302 (temporary) only when the original page will return at the same address.
Can I redirect all my old pages to the homepage? It's best not to. Redirect each old page to the most relevant new page. Google warns that mass redirects to an irrelevant page such as the homepage might be treated as soft 404s, so they help neither visitors nor rankings.
Do I need to tell Google if I keep the same domain? You don't need the Change of Address tool, which is only for moving between domains. Submit your new sitemap and monitor Search Console.
Planning a redesign?
Tell us about your current site and what you want the new one to do. We'll plan the move with your search visibility in mind and give you a clear, fixed quote.
Talk to us about your redesign · Explore website development
