A website relaunch only costs you rankings when old URLs simply disappear instead of being redirected properly. If you audit every existing URL before launch, set up 301 redirects, and carry over the content that already ranks, you can ship the new site without giving up what Google has already awarded the old one. Two phases decide the outcome: careful preparation before launch, and close monitoring in the weeks immediately after.
In this article we walk you through why relaunches cost rankings, how to build a complete inventory, what a redirect plan looks like, and what to do on launch day and during the first 30 days, including a checklist you can work through step by step.
Why do website relaunches cost rankings?
A relaunch almost always changes more than the design. New URL structures, renamed pages, rewritten copy, reorganised categories or a new system such as a headless setup, each of these is a signal to Google that something moved. And that is when the machine starts recalculating:
- Changed URLs without redirects mean that rankings, backlinks and stored search terms point at a page that no longer exists.
- Changed content: when copy is rewritten, Google may re-interpret the page for a different topic, with different search terms.
- Technical changes: load time, structure, meta tags, image alt text, even small differences can affect visibility.
- Indexing: Google has to recognise, crawl and index the new pages again. The messier the handover, the longer that process takes.
The good news: nearly every one of these is under your control, if you treat the relaunch as an SEO project, not just a design refresh.
What inventory do you need before a relaunch?
The inventory is the foundation of the whole project. The cleaner you build it, the fewer surprises later. Work through these points in order:
1. Capture every URL
Save a complete list of every reachable URL on your current website. A crawling tool that walks your site and collects all reachable pages, subpages, blog posts, category pages and PDFs included, is the easiest way. Cross-check against Search Console's page indexing report to see which pages are actually indexed.
2. Document rankings and search terms
For each URL, note: what position does it currently hold, and which search terms bring traffic? Search Console's performance report or any SEO tool of your choice works for this. The point is that you end up knowing which pages actually carry weight, not just how many pages exist in total.
3. Check backlinks
Not every URL has backlinks, but the ones that do are especially valuable. A backlink list shows which external sites link to which of your pages. If such a page disappears in the relaunch, the links disappear with it and so does part of the authority Google assigns to it.
4. Record tracking and tools
Which tracking codes, analytics tools, conversion trackers or cookie banners are currently running? Write down every ID you will need to set up again after the relaunch. Miss this, and you lose important data and spot problems too late.
What does a redirect plan look like?
The redirect plan is the most important working document of the whole relaunch. For every old URL you decide which new URL takes over its place. The standard is a 301 redirect: it signals to Google that the page has permanently moved and transfers most of the previous signals.
Here is what such a map looks like:
| Old URL | New URL | Type |
|---|---|---|
/about-us | /about-us/ | 301 (one-to-one) |
/services/website-design | /services/digital-platforms | 301 (one-to-one) |
/blog/old-post-2019 | /blog/new-post | 301 (merge) |
/old-contact | /contact | 301 (one-to-one) |
Two principles guide the mapping:
- One-to-one redirects for strong pages: a page with good rankings and backlinks gets a content-matching new URL. The closer the content aligns, the better.
- Deliberate merging for weak pages: when several old pages overlap in content or get little traffic, you can point them at one strong page. The merge should be justified, not just "send everything to the homepage", which dilutes the signal.
What should you test before going live?
Before launch, at least check these points, ideally in a staging environment that already reflects the final URL structure:
- All redirects work: every old URL lands on the correct new page, with no detours or loops.
- Tracking works: analytics, conversion events and the cookie banner capture data as expected.
- Load time: the new site loads in acceptable time, noticeably slower than the old one is a risk.
- Mobile display: the site renders correctly on common smartphone sizes.
- Meta tags and titles: titles, descriptions and alt text are present and correct.
- Forms and links: all forms and internal links work, no dead ends.
Launch day: the go-live checklist
Launch day itself should run calmly and in a structured way. These points belong on your list:
- All 301 redirects are set up on the production server and tested
- The old website is still reachable, or the redirects are already running
- Tracking codes are live on the new site and capturing first data
- Search Console reflects the new domain or new URL structure
- A screenshot log of the first checks is in place
- The responsible people know what to do if something breaks
- A short sync slot is scheduled for the following day
The first 30 days after launch
After going live, the most important phase begins and the one where most relaunches reveal their problems. Work through these points daily or weekly:
Week 1: check daily
- Search Console: new errors, warnings or pages that failed to index? Handle each new warning the same day.
- Rankings: strong pages should be back at their level within one to two weeks. Deviations of more than a few positions are a signal to investigate.
- Tracking: is the data arriving where it should be? If an event is missing, better find it now than in four weeks.
Weeks 2 to 4: stabilise and adjust
- Check redirect chains: are there detours you could shorten? Every extra hop slows things down.
- Close content gaps: is a page missing that was in the inventory but lost in the relaunch? Now is the moment to add it back.
- Monitor performance: load time, Core Web Vitals, mobile: the first real users deliver the first real data.
- Sync with your team: what works, what does not yet? A short weekly check keeps everyone aligned.
Conclusion: a relaunch is an SEO project, not just a design refresh
A website relaunch does not have to be a rankings gamble, if you treat it as an SEO project. The inventory before launch, a clean redirect map and close monitoring in the first 30 days are the three pillars that make the difference. Handle those three well, and you can ship the new site without putting your current Google performance at risk.
And if you are not sure whether your current URL structure will survive a relaunch: talk it through with us: we will look at your inventory, redirects and content together and figure out what matters for your relaunch. For more on architecture, see WordPress as a headless CMS or Next.js, and for what a new website costs in 2026, see our website cost guide.
