Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Checklist · 10 min read

Website redesign checklist: keep your Google rankings

By the Red Balloon team · Updated · Part of Website designing company in Gurgaon (Gurugram)

A new website should bring in more enquiries than the old one, yet many redesigns do the opposite for months. The design is better, the pages are faster, and organic traffic still drops, because Google can no longer find the pages it used to rank, or finds them with thinner content, missing titles and broken links.

A website redesign without losing SEO is mostly a matter of discipline rather than clever tactics: record what the old site ranks for, map every valuable URL to a new home, keep the content that earned the rankings, protect the staging site, check everything on launch day and watch Search Console closely afterwards.

This checklist follows that order. Use it whether you are rebuilding in-house or briefing an agency, and ask your vendor to show you each deliverable before launch.

Why redesigns lose rankings

Google ranks individual URLs, not websites. When a redesign changes addresses, removes pages or rewrites content, each affected URL has to be rediscovered and re-evaluated. If the old address returns a 404 error, the signals it built up, including links from other sites, are no longer connected to a working page.

Most traffic losses after a launch trace back to a handful of causes: missing or incorrect redirects, pages dropped because they looked unimportant, content cut down to fit a new design, the staging site's noindex tag carried over to production, and internal links still pointing to old URLs. None of these is hard to prevent. They happen when SEO is treated as a launch-week task instead of part of the project plan from the start.

Step 1: crawl and benchmark the current site

Before anyone touches the design, take a complete snapshot of the old site. You cannot protect what you have not recorded, and once the old site is gone the data is much harder to recover.

  • Crawl every URL with a crawler such as Screaming Frog or Sitebulb, and save titles, meta descriptions, headings, canonical tags, status codes and word counts.
  • Export the Performance report from Google Search Console for at least the last twelve months: clicks, impressions and queries by page.
  • Export landing-page data from Google Analytics, including organic sessions and conversions by page.
  • Pull your backlink profile from a backlink tool and list the pages that other sites link to.
  • Download the XML sitemap and note any URLs it contains that the crawl did not find.
  • Record Core Web Vitals and the Page indexing report so you can compare like for like after launch.

Combine these into one spreadsheet with a row per URL. Mark the pages that bring organic traffic, conversions or backlinks. These are the pages that must survive the move, and they become the core of your redirect map.

Step 2: map every URL and plan 301 redirects

If any address will change, every old URL with traffic, conversions or backlinks needs a permanent redirect to its closest equivalent on the new site. A 301 status tells browsers and search engines that the move is permanent, and Google uses it as a strong signal that the new URL should replace the old one in its results.

Old URLNew URLActionNotes
/services.php?id=4/services/website-design/301Ranks for core service terms; content carried over in full
/about-us.html/about/301Direct one-to-one replacement
/blog/2019/09/seo-tips//blog/seo-tips/301Has backlinks; update internal links to the new URL
/offers/diwali-2021/None410Expired offer, no traffic or links; let it drop out
/gurgaon-office/ and /gurugram-office//contact/gurugram/301 (both)Duplicate pages merged into one
/cheap-pills-buy-now/None410Spam page injected through an old plugin; never redirect

Some rules make the map more reliable. Redirect one to one wherever possible, to the most relevant new page rather than the home page; Google may treat a mass redirect to the home page as a soft 404. Avoid chains, where an old URL redirects to another old URL before reaching the new one. Point redirects straight to the final destination. Use server-level or CMS-level redirects, not JavaScript or meta refresh, and keep them in place for at least a year, as Google's site-move guidance recommends, and longer if the old URLs still have links.

Step 3: keep content parity on pages that rank

A redirect moves the address. It does not protect rankings if the new page says less than the old one. Redesigns often cut copy because a designer wants shorter pages, or because content was not part of the brief. If the old service page answered six buyer questions and the new one answers two, expect it to rank for fewer searches.

For each page marked as important in your benchmark, compare the old and new versions side by side. Check that the main topics, headings, FAQs, specifications, prices or price drivers, location details and supporting images are still present. Improving content is welcome; removing it should be a deliberate decision backed by data, not a side effect of the layout.

Be careful with content hidden behind tabs, sliders or accordions that only load when clicked, and with text turned into images. Google can index content in accordions when it is in the page's HTML, but text inside images or loaded only after an interaction may be missed.

Step 5: keep the staging site out of Google

The new site will live on a staging address for weeks while it is reviewed. If Google finds and indexes it, you end up with a duplicate site competing with your live one. The safest protection is password protection at server level, which stops crawlers from seeing anything. A noindex meta tag or HTTP header also works, but only if crawlers can fetch the page to see it.

Blocking staging with robots.txt alone is not reliable, because a URL blocked by robots.txt can still be indexed if other pages link to it. The bigger risk is the reverse: a noindex tag or a blanket robots.txt disallow copied from staging to production at launch. Put "remove staging protection" on the launch checklist, and check it on the live site, not just in the CMS settings.

Step 6: launch-day checks

Launch early in the week and early in the day, when your team and your agency are available to fix problems. Avoid launching just before a long weekend or during a major campaign. Then work through this list in order.

  1. Confirm the live site has no noindex tag and that robots.txt does not block important sections.
  2. Test your redirect map in bulk with a crawler, checking that every old URL returns a single 301 to the correct new page.
  3. Crawl the new site for 404 errors, redirect chains and internal links that still point at old URLs.
  4. Check canonical tags, titles and structured data on a sample of each template.
  5. Submit the new XML sitemap in Search Console and use URL Inspection on your most important pages.
  6. If the domain itself has changed, use Search Console's Change of Address tool after the redirects are live.
  7. Test every form, phone link and WhatsApp button, and confirm leads reach the CRM with their source.
  8. Check that analytics and tag manager fire on the new templates and that conversions are recorded.

Tracking is often the last thing checked and the first thing broken. Our GA4 setup checklist is a useful companion for this step.

Step 7: monitor Search Console for the following weeks

Some movement in rankings after a redesign is normal while Google recrawls the site and processes the redirects. Google's documentation notes that a site move can cause temporary fluctuation and that a medium-sized site may take a few weeks for most pages to be reprocessed. What matters is the trend and whether specific pages are failing.

  • Page indexing report: watch for rising counts of "Not found (404)", "Excluded by noindex tag" or "Crawled, currently not indexed".
  • Performance report: compare clicks and impressions by page against your benchmark, using the same period length.
  • Sitemaps report: confirm the new sitemap is processed and its URLs are being indexed.
  • Crawl stats: check for spikes in server errors or slow response times.
  • Core Web Vitals report: confirm the new templates meet the thresholds of LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less.

Check daily for the first week, then weekly for at least two to three months. If an important page drops sharply, compare the old and new versions again: the cause is usually a missing redirect, thinner content or a broken internal link, and it can be fixed.

Common failure modes, and how we avoid them

  • Every old URL redirected to the home page instead of to its closest match.
  • Staging noindex or robots.txt rules copied to the live site.
  • Blog, resource or location pages dropped because no one checked their traffic.
  • URL structure changed for no reason other than a new CMS's defaults.
  • Redirects removed a few months later during a server move or plugin clean-up.
  • Tracking broken at launch, so no one can tell whether leads fell or just stopped being recorded.

When Gurugram businesses ask us to rebuild a site that already ranks, the redirect map, content comparison and launch checklist are part of the scope from the first week, not an add-on. As a website designing company in Gurgaon, we export every URL with traffic or backlinks, map each one before design is signed off, remove spam pages properly and watch indexing after launch until it settles.

If you are planning a rebuild, see how our website redesign service works, or talk to our web design agency in Gurugram through the contact form.

FAQ

Questions people also ask

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

Will a website redesign affect my Google rankings?

It can, in either direction. Rankings often fluctuate for a few weeks while Google recrawls the site. Lasting drops usually come from missing redirects, removed or thinner content, or a noindex tag left on the live site. With a full URL map, content parity and post-launch monitoring, most sites recover and many improve.

    Should I use a 301 or 302 redirect after a redesign?

    Use a 301 for any page that has moved permanently. A 301 tells search engines the new URL should replace the old one. A 302 signals a temporary move and is meant for short-term cases such as maintenance or a seasonal page. Google can eventually treat a long-standing 302 as permanent, but a 301 states your intent clearly.

      How long should I keep redirects in place?

      Google's site-move guidance recommends keeping redirects for at least one year, and longer is better if the old URLs still receive links or visits. Removing redirects during a later server move or plugin clean-up is a common cause of traffic loss long after the redesign.

        Can I change my URL structure during a redesign?

        Yes, if there is a good reason, such as replacing parameter-based URLs with readable ones. Each change needs a one-to-one 301 redirect and updated internal links. If the current URLs are already clean, keeping them removes a large share of the migration risk.

          How do I stop Google indexing my staging site?

          Protect it with a password at server level, which blocks crawlers entirely. A noindex tag also works if crawlers can reach the page. Do not rely on robots.txt alone, and make sure none of these protections are copied to the live site at launch.

            What should I do with old pages that have no equivalent?

            If a page has traffic or backlinks, redirect it to the most relevant new page, such as the parent category. If it has no value, let it return a 404 or 410. Spam or hacked pages should always be removed rather than redirected.

              Start with an audit

              Ready for
              lift?

              A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

              Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

              A person from the team replies to every enquiry.

              What do you need?
              Your details are sent over a secure, encrypted connection and only used to reply to you.