Website relaunch without losing SEO: how to keep your Google rankings through a redesign

Short answer: a website relaunch without losing SEO comes down to three things: a complete inventory of your old URLs, a 301 redirect for every URL that has traffic or links, and keeping the content that ranks. Google itself says a small to medium site needs a few weeks for most pages to move and recommends keeping redirects for at least a year. Plan 4–12 weeks of close monitoring, and the dip, if any, stays small and short.

A relaunch is the moment many businesses lose traffic they spent years building. Not because the new site is worse. Usually it is faster, clearer and better looking. The traffic goes because Google suddenly cannot find the pages it used to rank: the URLs changed, the redirects were never set up, or the text that answered a search was cut in the redesign.

We build websites in Vienna and most of our projects are relaunches, not first websites. The process below is the one we run on every website project. It is not complicated, but it has to start before the design does, not the week before launch.

Why do relaunches lose Google traffic?

Google ranks individual URLs, not your brand. When /services/roof-repair has ranked for years and the new site calls the page /leistungen/dach, Google treats the new page as unknown. Without a redirect, the old URL returns a 404, the page drops out of the index and the links pointing at it lead nowhere.

In our experience, nearly every traffic loss after a relaunch traces back to one of these causes:

• Missing or wrong redirects: old URLs end in a 404, or everything is pointed at the home page.
• Content removed: the redesign shortened texts or merged pages, and the paragraphs that matched searches are gone.
• Noindex left on: the staging site was blocked from Google, and the block went live with the launch.
• Titles and headings rewritten: the new copy sounds better but no longer contains the words people search for.
• Internal links broken: menus and body links still point to old addresses, so Google wastes time on redirect hops.
• Slower pages: heavy hero videos or a page builder push load times up, especially on phones.

All six are preventable. None of them requires an SEO budget, only a plan and someone who checks the details on launch day.

Start with a full URL inventory

Before anyone designs a page, export everything the old site has. This list becomes the basis for the redirect map and for deciding which content must survive. We collect it from four sources:

• A crawl of the live site, for example with Screaming Frog (free up to 500 URLs): every URL, status code, title, meta description, H1 and canonical.
• Google Search Console: the Pages report in Performance, sorted by clicks over the last 12–16 months. The interface exports up to 1,000 rows, which covers most small and medium sites.
• The XML sitemap and the CMS: pages that are published but not linked anywhere, old blog posts, PDFs and images that get traffic.
• Backlinks: which of your URLs other websites link to. Search Console shows this under Links; external tools show more.

Put it all into one spreadsheet, one row per old URL. Add clicks, impressions and backlinks per row. Now you can see which 10–20 % of pages carry most of your traffic. Those pages get the most care in the redesign.

Also save a copy of the old site: a full crawl export and screenshots or an HTML archive of the top pages. Weeks after launch, when someone asks what the old page said, you will want it.

Build the 301 redirect map

The redirect map is a two-column list: old URL, new URL. Every old URL that has clicks, impressions, backlinks or is in the sitemap gets a row. The rules we follow:

• Use 301 (or 308) redirects, not 302. Google's guidance is to use permanent, server-side redirects for a site move.
• Redirect to the closest equivalent, not to the home page. If a service page became part of a broader page, redirect there. Redirecting hundreds of URLs to the home page tends to be treated like a 404 anyway.
• No chains: old URL to final URL in one hop. If you already have redirects from an earlier relaunch, update them to point straight to the new address.
• Keep the protocol and host consistent: decide on https and www or non-www, and redirect every variant in one hop.
• Really gone? Then let it go: a page with no traffic, no links and no successor can return a 404 or 410. That is fine and honest.

On Next.js, which we build with, redirects live in the project configuration and are deployed with the site, so they are versioned and cannot get lost in a hosting panel. If you are moving away from WordPress, read our article on switching from WordPress to Next.js; the URL structure is the part to plan first.

For shops the map is larger: products, categories, filter URLs and images. In our e-commerce migration package the 301 plan and SEO preservation are fixed line items, not an afterthought.

Keep the titles and content that rank

A relaunch is a good time to improve your copy. It is a bad time to throw away what works. For every page in your top list, check before rewriting:

• Which search terms bring clicks to this page (Search Console, Queries tab, filtered by page)?
• Are those terms in the title, the H1 and the first paragraphs? Then they stay there in the new version.
• Which sections answer specific questions (prices, process, location, opening hours)? They survive, even if the layout changes.

Shorter is not automatically better. If the old page had 900 words answering ten questions and the new one has 150 words of slogans, the rankings will follow the words. Design can make long content easy to read. It should not replace it.

This is also where you can win: clearer headings, an FAQ that answers real searches, structured data and a page that AI search can quote. Our GEO service builds that in. More on it in how to get cited by ChatGPT.

Staging and noindex: the most expensive mistake

During development the new site runs on a staging address. It must not show up in Google, so it is blocked, usually with a noindex tag, a robots.txt Disallow: / or password protection. That is correct. The problem starts when the block goes live with the launch.

A noindex on the live site tells Google to drop every page. A robots.txt block stops Google from crawling the site at all, so it cannot even see your redirects. Both happen more often than anyone admits, because the staging and live versions share the same code.

• Prefer password protection for staging. It keeps Google out without touching the site's own robots rules.
• Use one switch, not settings scattered across templates. This very website ran with noindex on every page and robots.txt blocking all crawlers before launch, controlled by a single launch flag that is flipped on go-live.
• Check right after launch: open the source of three pages and look for noindex, open /robots.txt and run the URL Inspection tool in Search Console.

What to do on launch day

Launch early in the week, not on a Friday afternoon, so someone is there when something breaks. Then work through this order:

1. Deploy the new site with the redirects active.
2. Remove the noindex and robots blocks and check the live robots.txt.
3. Test the redirect map: run the list of old URLs through a crawler and confirm every one returns a 301 to a page with status 200.
4. Check canonicals: every new page points to itself, not to the staging domain.
5. Submit the new XML sitemap in Search Console.
6. Moving to a new domain? Use the Change of Address tool in Search Console. Google says it is only for domain or subdomain changes, not for http to https, www changes or new paths on the same domain.
7. Check analytics, the cookie banner, forms and conversion tracking on the live domain.
8. Update the links you control: Google Business Profile, social profiles, directory listings, email signatures.

Monitoring: the 4–12 weeks after launch

Google does not process a relaunch in a day. For small to medium sites it says most pages move within a few weeks, and rankings can fluctuate during that time. That is normal. What is not normal is a drop that keeps growing after week two.

Compare page by page, not just total traffic. If the total looks fine but one service page lost 80 % of its clicks, a redirect or a section of text is probably missing. Fix it the same week. The longer a page stays broken, the slower it recovers.

Common relaunch mistakes we keep seeing

• Redirects planned in the last week: the redirect map is a content task, not a hosting task. Start it with the sitemap.
• Changing domain, URL structure, content and platform at once: possible, but every change adds risk. If you can, keep URLs that work.
• Language versions without a plan: adding English or moving German to a subfolder changes URLs too. Every old URL still needs its redirect, and hreflang must point to the right pair.
• Images and PDFs forgotten: they get image search traffic and links. They need redirects just like pages.
• Deleting the old site immediately: keep access to the old CMS and an archive until the new site has settled.
• No baseline: if you did not export clicks per page before launch, you cannot tell what changed.

The relaunch SEO checklist

When you do not need all of this

If your current site gets almost no search traffic (a few dozen clicks a month in Search Console) and has hardly any backlinks, there is not much to protect. Do a quick crawl, redirect the handful of URLs that matter, and focus on making the new site findable in the first place.

The same goes for a pure visual refresh where URLs and texts stay the same. Then the main risks are noindex and speed, not redirects. The full process pays off when the old site brings real enquiries through Google, which is the case for most established businesses.

How we handle relaunches

At 404media the URL inventory and redirect map are part of the strategy phase of every relaunch, not an extra. Staging runs from week one, SEO architecture is set up from day one, and after launch we keep monitoring and optimising: you do not have to become your own webmaster. A typical website takes 8 to 12 weeks, confirmed in a fixed-price quote.

A relaunch can be about more than keeping rankings. For the premium meat producer Aumaerk we redesigned the website and backed the new shop with Google and social campaigns. If you are planning a relaunch in Austria, ask about funding: the federal digitalisation funding has ended, but regional programmes may fit (apply before the project starts). Status and alternatives: our funding article. What a relaunch costs is covered in website costs in Austria.

Written byChristoph SpeiserProject lead & sales

Meet the team →