Website Redesign SEO: How to Relaunch Without Losing Your Rankings

A new website should bring in more business than the old one. Sometimes it does the opposite. The design looks better, the team is proud of it, and three weeks later organic traffic is down by a third and nobody knows why.

In almost every case we have looked at, the drop had nothing to do with the new design. It came from things that got lost in the move: URLs that changed without redirects, pages that were never carried over, and settings from the staging site that went live by accident.

Below is how we handle SEO during a redesign at Ruler, from the work we do before design starts to the checks we run on launch day, including two mistakes we made ourselves.

Does a website redesign hurt SEO?

A redesign does not hurt SEO by itself. Rankings drop when the redesign changes the things Google relies on to understand your site: URLs, content, internal links, page titles and technical settings like indexing rules and canonical tags.

If those stay intact or are moved carefully, rankings usually hold. A short dip in the first two to four weeks is normal while Google recrawls the site. A drop that is still there after six to eight weeks usually means something technical is broken and needs fixing.

Step 1: Take a baseline before anyone opens Figma

Before the design phase, we export and save:

• Google Search Console data for the last 12 to 16 months: clicks, impressions and average position per page and per query.
• A full crawl of the current site: every URL, its status code, title, meta description, H1, canonical tag and word count.
• Analytics landing-page data showing which pages bring in leads or sales, since traffic alone can mislead.
• Backlink targets: which pages other sites link to. These URLs carry authority you cannot afford to throw away.

The baseline shows which pages matter. On most business sites, a small group of pages brings in most of the organic traffic, and those pages get extra care during the redesign, from their URLs and content to their place in the navigation.

Step 2: Inventory content as well as URLs

Most teams skip this step, and we learned it the hard way.

On a portal we rebuilt for a sustainability-sector client, the old site held years of reports, press releases and news items for dozens of organisations. The URL list looked complete. Then the client's team started checking and found that one company's report archive showed 3 of its 20 documents. Filters that users relied on, like an alphabetical index, had not been rebuilt. Some news lists were only partly migrated.

A URL crawl caught none of that, because the pages existed and only the content inside them was missing. Since then, our migration inventory covers:

• Page count per section, old vs new
• Items per listing (reports, products, articles, team members), old vs new
• Downloadable files and whether each one still resolves
• Functional features users depend on (filters, search, archives, forms)

If a page ranked because it had 2,000 words of useful detail, moving it to a new template with 400 words is effectively deleting it. Content parity on the pages that already rank matters more than any design decision.

Step 3: Build a one-to-one redirect map

If a URL changes, it needs a 301 redirect to its closest new equivalent. This is the most important technical step in any redesign.

Our rules for the redirect map:

1. One old URL, one new URL. Do not redirect everything to the home page. Google treats mass home-page redirects as soft 404s, so the authority is lost anyway.
2. No chains. If page A already redirects to B from a previous redesign, and B now moves to C, point A directly to C.
3. Keep URLs that do not need to change. A cleaner URL structure is nice, but keeping your ranking URLs exactly as they are is usually better.
4. Map images and PDFs too. Files often get linked from other sites and appear in image search.
5. Test the map before launch by running the full old URL list against the staging server and checking that each one returns a single 301 to a live 200 page.

We keep the map in a plain spreadsheet with the old URL, new URL, status and a notes column. Of all the redesign documents, that spreadsheet does the most to protect rankings.

Step 4: Rebuild on-page SEO in the new templates

New templates often drop things the old site had. Before launch, check that every important page still has:

• A unique title tag and meta description (carry over the ones that perform well)
• One H1 that matches the page topic
• A logical H2/H3 structure
• Image alt text
• Structured data (Organization, LocalBusiness, Product, Article, FAQ where honest)
• Internal links to and from related pages

Internal links need extra attention. A redesign often simplifies the navigation, which is good for users but can leave important pages with no internal links pointing to them. If a page used to sit in the main menu and now sits three clicks deep, Google will notice.

A redesign is also a good moment to think beyond Google. AI search tools like ChatGPT and Google's AI Overviews prefer pages with clear structure, direct answers and clean markup. We covered the differences in GEO vs SEO. A redesign is the cheapest time to build those foundations into every template.

Step 5: Control what gets indexed

Staging sites and hidden pages cause more launch-day damage than any design choice. There are two things to check.

Before launch, the staging site must be blocked from indexing, ideally behind a password as well as a noindex rule. If Google indexes staging, you end up competing with your own copy.

At launch, the noindex rule must be removed from the live site. It sounds obvious, and it is still one of the most common reasons a brand-new site disappears from search.

We also watch pages that are meant to exist but not be indexed. On a multilingual site for a property developer, the client asked us to keep several language versions hidden until their translations were approved. For a short time those pages were reachable. We hid them again and kept them out of the XML sitemap, but Google had already found and indexed some of them. Hiding them did not take them out of the index, so we had to add a noindex directive in the code, and pages that were already indexed take weeks to drop out of results after that.

A hidden page can still be indexed. Every page that should stay out of search needs an explicit noindex rule from day one, needs to stay out of the sitemap, and needs checking after every major content update as well as on launch day.

Step 6: Launch-day checklist

On launch day, we work through a fixed list:

1. Remove the noindex rule and confirm robots.txt allows crawling
2. Run the full old-URL list against the live site and fix any 404s or chains
3. Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools
4. Check canonical tags point to the live domain, not staging
5. Confirm analytics, Tag Manager and conversion tracking fire correctly
6. Check Core Web Vitals on the main templates (mobile first)
7. Test forms, checkout and any lead paths end to end

Tracking gets its own item because a broken analytics tag leaves you blind at exactly the moment you need data. If traffic looks like it dropped to zero, you want to know whether that is real or a missing tag.

Step 7: Monitor for eight weeks

For the first two weeks after launch, we check Search Console daily for crawl errors, 404s and indexing changes. After that, we check weekly until week eight, comparing against the baseline from Step 1:

• Clicks and impressions for the top pages
• Average position for the main queries
• New 404s (usually old URLs we missed or external links we did not know about)
• Pages dropping out of the index

A 10 to 15 percent dip in the first weeks is common and usually recovers. A sustained drop above 30 percent, or a specific page falling off a cliff, points to a real problem, usually a missing redirect, lost content or an indexing rule.

How a redesign can improve SEO

Handled well, a redesign is one of the best SEO opportunities you get. It lets you fix slow page speed, thin content, messy site structure and missing schema all at once. The sites we build are custom WordPress without page builders, partly for this reason: clean code makes it easier to hit Core Web Vitals targets and keep markup under control. You can read more about how we approach this on our web and digital products page.

Keeping your current rankings is the minimum. The aim is to come out of the launch with a site that has a better chance of ranking higher over the next year than the old one ever had.

FAQ

How long does it take for rankings to recover after a redesign?

With a clean migration, most sites recover within two to four weeks. Competitive keywords can take six to eight weeks. If traffic is still well below the baseline after two months, something is usually broken and worth investigating rather than waiting out.

Should I change my URLs during a redesign?

Only if there is a clear reason, such as a messy or confusing structure that hurts users. Every changed URL needs a 301 redirect and carries some risk. If your current URLs are readable and ranking, keeping them is the safer choice.

Can I redesign my website and change my domain at the same time?

You can, but it compounds the risk. We usually recommend doing one at a time, so that if rankings move you know which change caused it. If both have to happen together, the redirect map and monitoring become even more important.

Do I need an SEO specialist involved in a redesign?

Someone on the project should own SEO from the start, well before launch. Many of the decisions that protect rankings, like URL structure, content scope and navigation, are made during planning and design. By launch week it is often too late to change them cheaply.

Planning a redesign?

We treat SEO migration as part of the build from the start. If you are planning a new website and want to keep the traffic you have already earned, get in touch and we can review your current site before the design work starts. For ongoing search and AI visibility work after launch, see our marketing services.