SEO

Redesigning Your Website Without Losing Your Rankings

A new website shouldn't cost you your Google traffic. Our website redesign SEO checklist for before, during and after launch, from URL mapping to 301 redirects.

F

Force Media Team

7 min read
Laptop showing a website on a wooden desk by a window with potted plants

Photo: Michał Parzuchowski on Unsplash

The new site looks wonderful. The launch party has happened. And three weeks later, someone notices the enquiry form has gone quiet, because half the pages Google used to send people to now show a "page not found" error.

It's one of the most avoidable problems in web design, and one of the most common. A redesign changes URLs, content, structure and code all at once, and each of those can quietly undo years of search visibility.

The fix isn't complicated. It's a checklist, worked through in order. This is the website redesign SEO checklist we use on every relaunch, split into before, during and after.

Website redesign SEO: why redesigns lose traffic

Google ranks pages, not websites. Each URL on your current site has its own history: links pointing at it, a ranking for certain searches, a place in Google's index. A redesign tends to break that history in one of four ways:

What happensWhy it hurts
URLs change with no redirectsGoogle, and anyone following an old link, lands on a 404. The page's ranking history is lost.
Content is cut or thinned outThe text that ranked for a search is gone, so the page no longer matches it.
Structure and internal links changeImportant pages end up buried, or orphaned with nothing linking to them.
Technical settings slip throughA "noindex" tag from the test site, a blocked robots.txt or a slow new theme can hide or hobble the whole site.

Every item on the checklists below exists to prevent one of those four.

Illustrative organic traffic around a relaunch (weekly visits)

03036059081210-4 wks-2 wksLaunch+2 wks+4 wks+8 wks
  • Planned redesign
  • No redirects or checks
An illustration, not real data. Google says to expect some temporary fluctuation during any move; the difference is whether traffic recovers or settles at a new, lower level.

Before the redesign: take stock

Most of the work happens before a single new page is built. You can't protect what you haven't measured.

Before you start

  • Crawl your current site and save a full list of URLs (tools like Screaming Frog do this in minutes).
  • Export your top pages by organic traffic and by conversions from Google Analytics and Search Console.
  • Note which pages have links from other websites, using Search Console's Links report or an SEO tool.
  • Record current rankings for your most important search terms, so you have a baseline.
  • Save copies of the page titles, meta descriptions and headings of your best-performing pages.
  • Decide, page by page, what happens to each URL: keep, merge, or retire.

During the build: protect what works

Designers sketching paper wireframes and sticky notes beside a laptop
The wireframe stage is the cheapest time to get the page structure right for search, before anything is built. Photo: UX Indonesia on Unsplash

Build a redirect map

This is the single most important document in a redesign. For every old URL, write down where it should go on the new site. Google's own site move guide calls mapping old URLs to new ones "important", and recommends permanent redirects (301 or 308).

Old URLNew URLNote
/services/web-design.html/services/web-designSame page, cleaner URL
/blog/2019/10-seo-tips/blog/seo-tipsPost kept and updated
/team/john-smith/aboutPage retired; closest relevant page
/old-promo-2021(none: let it 404 or 410)Nothing relevant to send people to

Two rules make a redirect map work. Redirect to the most relevant page, not to the homepage by default; sending everything to the homepage throws away the relevance the old page had. And avoid chains: redirect straight from the old URL to the final new one, not through two or three hops.

During the build

  • Every old URL with traffic or links has a redirect to the closest matching new page.
  • Page titles, headings and key content on top pages are kept or improved, not cut.
  • Internal links in menus, footers and body text point to the new URLs directly.
  • The staging site is blocked from search engines with a password, not just a noindex tag that might be copied to live.
  • New pages load quickly on a phone; check Core Web Vitals before launch, not after.
  • Structured data, analytics tags and conversion tracking are rebuilt on the new templates.

Launch day

  1. Before switching

    Final checks on staging

    Test a sample of redirects, confirm tracking fires, and check page titles on key templates.

  2. Go live

    Switch and remove the blocks

    Remove staging passwords and any noindex tags. Check robots.txt allows crawling. It is surprisingly easy to miss.

  3. First hour

    Test the redirects for real

    Run your old URL list through a crawler and confirm every one returns a 301 to the right place, with no 404s or chains.

  4. Same day

    Tell Google

    Submit the new XML sitemap in Search Console. If the domain changed, use the Change of Address tool as well.

  5. First week

    Watch closely

    Check Search Console daily for crawl errors and 404s, and fix any redirect you missed straight away.

The most expensive line of code in a redesign is the "noindex" tag someone forgot to remove.

After launch: monitor and fix

Google warns that you should "expect temporary fluctuation in site ranking during the move", and that for a medium-sized site it can take a few weeks or more for the new URLs to replace the old ones in results. A dip in the first few weeks is normal. A dip that doesn't recover is a signal something on the checklist was missed.

The weeks after launch

  • Search Console's Pages report shows the new URLs being indexed, with no surge in 'Not found (404)'.
  • Organic traffic to your top pages is compared with the baseline you saved before the redesign.
  • Rankings for your key search terms are re-checked at two, four and eight weeks.
  • Any new 404s showing up in Search Console get a redirect.
  • Sites that link to you heavily are asked to update their links to the new URLs (a nice-to-have, not essential).
  • Redirects stay in place for at least a year; Google suggests keeping them as long as possible.

The short version

A redesign doesn't have to cost you your rankings. Measure everything before you start, map every URL that matters, keep the content that works, remove the staging blocks on launch day, and watch Search Console closely for a couple of months. Most traffic disasters come from skipping one of those steps, not from the redesign itself.

For the technical groundwork, our technical SEO checklist and Core Web Vitals guide go deeper. If you're also rethinking your content for AI-driven search, read SEO in the age of AI answers.


Force Media redesigns and rebuilds websites for businesses in Sri Lanka, Australia and beyond, with redirect mapping, SEO checks and post-launch monitoring built into every project. Planning a new website? Talk to us first, and we'll help you keep the traffic you've earned.

Speak to our experts

From AI agents to secure, fast websites, we build technology that does real work for your business.

Get in touch
FAQ

Common Questions

Everything you need to know about working with Force Media.

Ask Us Anything
We primarily serve businesses in Sri Lanka and Australia, but our remote-first approach means we can work with clients globally.
Project timelines vary by scope. A standard website takes 2–4 weeks. Custom software projects range from 6–16 weeks depending on complexity.
Yes. All our projects include a support period, and we offer ongoing retainer packages for maintenance, SEO, and feature development.
Absolutely. We specialize in integrating with existing platforms, APIs, and legacy systems to extend their capabilities.