How to redesign a website without losing SEO: what causes the drop, how to prevent it and how to recover

The short answer

A website redesign loses SEO when it changes the things Google already ranks: URLs that change without redirects, text that gets cut or hidden, internal links that disappear, pages that only render with JavaScript, or a noindex tag left over from the staging site. A new look on its own rarely costs rankings.

To redesign without losing SEO: export a baseline from Search Console, keep the URL of every page that earns clicks (or redirect it one hop to its closest match), keep each of those pages' content and metadata, test everything on a staging site Google can't index, and compare clicks per page for four to eight weeks after launch. This guide covers the SEO side only; the full project plan is in our website redesign checklist, and platform or domain changes are in the website migration SEO checklist.

Will a redesign hurt my SEO?

Not by itself. Google ranks pages on their content, their links and whether it can crawl them; it doesn't rank colour palettes. The risk depends on what else the redesign changes:

Step 1: Find the pages you can't afford to lose

Before anyone opens a design file, record what the current site earns.

• Export Search Console data by page and by query for the last 16 months, the most it keeps. Note each page's clicks, impressions and average position.
• Mark the protected pages. We treat any page with clicks or a top-10 position in the last three months as protected; on most business sites that's a small share of all URLs.
• Crawl the old site and save every URL with its title, H1, meta description, canonical, word count and internal links. This crawl is your reference for content parity later; once the old site is gone, you can't make it.
• Export the Links report to see which pages other sites link to. Those URLs need a destination even if they get no clicks.

Step 2: Map every URL before you design the new structure

The safest URL is the one that doesn't change. Keep the address of every protected page unless there's a reason a visitor would notice, such as two thin pages merged into one.

For every URL that does change, write its new address in a redirect map before the build starts. Google recommends a permanent server-side redirect (301 or 308) "whenever possible", straight to the final address, with no chains. Don't send old pages to the home page: Google can treat a redirect to an unrelated page as a soft 404. A page with no equivalent should return 404 or 410. Our website migration planner reads your sitemap and marks which URLs keep their path and which need a redirect, and the redirect map generator drafts the map.

Step 3: Keep content parity on protected pages

Content parity means the new page answers the same searches at least as well as the old one. Designers often cut copy to make layouts breathe; on a protected page, check what goes.

Compare each protected page's new version against the crawl from step 1. A page that went from 1,400 words to 300 has probably lost what it ranked for.

Step 4: Build on a staging site Google can't index

Put the new site behind a password, not only a noindex tag, so it can't be indexed or confused with the live site. Before launch, run the old URL list against staging: every old URL should return 200 or one redirect to a page that returns 200. Then check for noindex tags, robots.txt rules and canonicals pointing at the staging address. Google's site-move guide names leftover noindex and robots.txt blocks and redirects to "wrong (non-existent) URLs" among the most common mistakes.

Step 5: Launch day

• Redirects live and tested against the full old URL list.
• robots.txt allows crawling; no page carries a noindex it shouldn't.
• The new sitemap lists only final URLs and is submitted in Search Console.
• URL Inspection run on the top protected pages.
• Analytics, key events and forms tested on the live site.

Step 6: Monitor for eight weeks

Google's guidance is to expect fluctuation: after URL changes, "a medium-sized website can take a few weeks for Google to notice the change; larger sites can take longer." Compare like with like.

If traffic dropped after a redesign

Work through it in this order before changing anything else:

1. Is the drop real? Compare the same days of the week, check Search Console's data anomalies notes and Google Trends for seasonality.
2. Which pages lost it? Filter the Performance report by page. A drop concentrated in a few pages points at those pages' URLs or content; a drop everywhere points at something sitewide, such as robots.txt, noindex or rendering.
3. Impressions or clicks? If impressions held but clicks fell, the snippets changed: look at titles and descriptions.
4. What does the Page indexing report say? Look for "Excluded by noindex", "Not found (404)" and redirect errors that appeared at launch.
5. What changed on the page? Compare the old crawl with the new page: title, headings, word count, internal links.
6. Has it been long enough? If URLs changed and nothing is broken, Google says to allow a few weeks.

What a careful move looks like: the Gissi domain move

A domain move is a harder test than most redesigns, because every URL changes. On 23 October 2026 Dardo moved Gissi, a music school in Bogotá, from amediotonomusic.com to gissimusic.com. The redirect map covered 4,379 old addresses in their four forms, 17,516 URLs in all, each answered with one permanent redirect to the same page on the new domain, and a checker requested every one of them after the switch.

Google clicks across both Search Console properties dipped to 47 a day on days 7 to 9, then were back at their pre-move level from 3 November, 11 days after the switch: 86 a day from 3 to 9 November, against 84 a day in the two weeks before. The Gissi case study and how to change your domain name without losing SEO have the details. A redesign that keeps its URLs has less to move and should see less movement than that.

How Dardo can help

Dardo's website redesign service starts from the pages that already earn traffic and plans every URL before design starts. When the redesign also changes platform or domain, the website migration service adds the redirect map, a staging rehearsal and a post-launch comparison against the baseline.