A website relaunch checklist exists for one reason: the most expensive redesign mistake isn't ugly — it's invisible. A new site goes live, looks better than ever, and three weeks later the enquiries stop because Google can no longer find the pages that used to bring them in. These seven steps are how we relaunch sites without losing rankings, and they follow Google's own guidance on site moves with URL changes.
For the general pre-launch list (domain, SSL, forms, speed), use the website launch checklist alongside this one.
What is different about a relaunch?
A new site starts from zero. A relaunch starts with something to lose: URLs that rank, links from other sites, and content Google already trusts. The job is to carry all three across.
Step 1: Benchmark the current site
Before you change anything, export the last 12 months of:
- Search Console top pages and queries (Performance report).
- Analytics landing pages and conversions.
- Core Web Vitals for mobile.
- Rankings for your 10–20 most valuable searches.
Without a benchmark you can't tell whether the relaunch helped or hurt.
Step 2: Crawl and list every old URL
Combine a crawl of the live site with the URLs in Search Console, analytics, the old sitemap and any backlink report. Sites with blogs, products or tag pages often have far more URLs than anyone remembers.
Step 3: Decide what happens to each page
| Decision | When | Action |
|---|---|---|
| Keep | Page ranks or converts | Same URL if possible; improve content |
| Merge | Two pages target the same search | Combine into one; 301 the other |
| Improve | Page is thin but on-topic | Expand it; keep the URL |
| Retire | No traffic, no links, no purpose | 301 to the closest relevant page |
Never delete the content that ranks. Restructure it, improve it, but keep what earned the position.
Step 4: Map 301 redirects
- Map every changed or retired URL one-to-one to its closest new page.
- Avoid chains: the old URL should land on the final URL in one hop.
- Don't send everything to the home page; Google may treat those as soft 404s (Google on redirects).
- Update internal links to point straight at the new URLs.
- Keep the redirects in place for at least a year — in practice, indefinitely.
Step 5: Test on staging
Check redirects (a sample with a crawler), canonicals, structured data, titles and descriptions, forms, analytics events and mobile speed on a staging site protected by a password or noindex. Then make sure that protection doesn't ship to production — a leftover noindex is one of the most damaging relaunch bugs there is.
Step 6: Launch and resubmit
Switch DNS during a quiet period, remove staging blocks, confirm every page returns 200 and every redirect 301, and confirm canonicals point at the live domain (Google on canonicals). Submit the new sitemap in Search Console and Bing Webmaster Tools, and request indexing for your most important pages.
Step 7: Monitor for 60 days
Weekly, check:
- New 404s in Search Console's Page indexing report; redirect any you missed.
- Rankings for your benchmark searches.
- Conversions from organic traffic against the benchmark.
- Core Web Vitals once 28 days of field data exist.
What does a relaunch cost?
A relaunch costs the same as a new build plus the migration work: crawling, redirect mapping and content moves. Our fixed prices start at $999 for up to five pages (about ₹88,000), and every relaunch we do includes the redirect map plus monitoring for the package's support window (14 to 90 days). See pricing or get a range from the website cost calculator.