Pre-Launch SEO Checklist for a New or Redesigned Website
Launching or relaunching a site without an SEO check can wipe out the visibility you already have. Use this checklist to protect your URLs and redirects, keep the site indexable, submit a sitemap, set up analytics, and verify everything after go-live.
Introduction
- The problem: a new design goes live and search traffic drops, because old URLs now return errors, the site is still blocked from indexing, or titles and content were lost in the move.
- Why it matters: if your current site already brings enquiries, a careless relaunch can erase that, and rebuilding visibility takes time. For a brand-new site, a clean start prevents avoidable delays.
- What this article covers: a step-by-step checklist before, during and after launch: audit, URL mapping and redirects, content, technical settings, sitemap and robots, analytics, and the first weeks of monitoring. No one can promise ranking outcomes; this list reduces the risk of self-inflicted damage.
Is this a new launch or a relaunch?
The risks differ.
| Situation | Main risk | Main job |
|---|---|---|
| Brand-new site | Staying invisible: blocked, not submitted, no tracking | Make it crawlable, indexable and measurable |
| Redesign, same domain | URLs and content change, rankings drop | Map every old URL to the right new one |
| New domain or migration | Losing all history signals | Redirects, Change of Address, careful monitoring |
| Platform change | Settings lost: titles, canonicals, schema | Compare old and new settings page by page |
Phase 1: Before you build (relaunch only)
- Crawl the current site with a crawling tool and export every URL, with title, description, headings and status code.
- Export performance data from Google Search Console and analytics: which pages get impressions, clicks and conversions. These are the pages to protect first.
- List pages with links from other sites, if you can see them in a backlinks tool or Search Console. Their URLs matter.
- Decide what to keep, merge or remove. Do not keep weak pages just to keep them, and do not delete pages that earn traffic without a plan.
- Take a full backup of the old site and keep it until the new one has settled.
Phase 2: Map URLs and plan redirects
This is the single most important step in a relaunch.
| Old URL situation | What to do |
|---|---|
| Same URL on the new site | Nothing; keep it identical |
| URL changed, same page content | 301 redirect from old to the exact new page |
| Several old pages merged into one | 301 each old URL to the merged page |
| Page removed with a close alternative | 301 to the closest relevant page |
| Page removed, no equivalent | Allow a 404 or 410 and make the error page helpful |
Rules that save trouble:
- Use 301 (permanent) redirects for permanent moves.
- Redirect to the most relevant page, not everything to the home page. Mass redirects to the home page are often treated like errors.
- Avoid redirect chains (A to B to C). Point the old URL straight to the final one.
- Test the redirect map on a staging copy before go-live, and test a sample again after.
- Keep redirects live for a long time, usually at least a year, and longer where practical.
- Include language versions and URLs with or without a trailing slash, and the old
httpandwwwvariants.
Phase 3: Content and on-page checks
- Every important page has a unique title and meta description that match what the page covers. Use our title and meta description guide.
- One clear H1 per page, with a sensible heading structure.
- Preserve good content that ranks. If the redesign shortens or rewrites a high-traffic page, think carefully about what you remove.
- Images: descriptive file names, alt text, sensible sizes. See practical website speed.
- Internal links point to the new URLs directly, not through redirects.
- Structured data such as Organization, LocalBusiness or FAQ is present where relevant and valid.
- Bilingual sites: each page has its counterpart and correct hreflang. See Bilingual SEO and hreflang.
- Canonical tags point to the correct preferred URL, and not to a staging address.
- Social preview tags (Open Graph) so shared links look right.
Phase 4: Technical settings
| Check | What to confirm |
|---|---|
| Indexing allowed | Remove any "noindex" tag or blocking set during development. This is the most common launch mistake. |
| robots.txt | Does not block important folders; references the sitemap. Remove "Disallow: /" left from staging |
| XML sitemap | Lists only live, indexable, preferred URLs; updates automatically |
| HTTPS | Whole site on HTTPS, valid certificate, http redirects to https |
| One preferred version | www or non-www, one chosen, the other redirects |
| Mobile | Works well on phones; text readable, buttons tappable |
| Speed | Key pages tested on mobile; no obvious heavy elements |
| Error pages | A helpful 404 page; no broken links in menu or footer |
| Staging site | Blocked from search or password protected, and not linked from the live site |
Explanations of robots and sitemaps are in sitemap and robots explained.
Phase 5: Analytics and tracking
- Install analytics (for example GA4) and confirm it records visits on the live domain.
- Set up conversion tracking: form submissions, phone and WhatsApp clicks, bookings or purchases. See conversion tracking setup.
- Verify the site in Google Search Console, preferably as a domain property, and add the sitemap.
- Check that tracking tags are not duplicated and that old tags from the previous site are removed or kept deliberately.
- Make sure your internal traffic and test submissions do not distort reports, or at least note the launch date as an annotation.
- Record a baseline of key numbers from the old site, so you can compare after launch.
Phase 6: Go-live day
- Take a final backup of both old and new.
- Publish the new site and switch the DNS or deployment if needed.
- Confirm the site is not blocked by
noindexorrobots.txt. - Test top redirects: the home page, main service pages and pages with the most links or traffic.
- Click through the main journey: home page, service page, contact form, thank-you page. Confirm the tracking fires.
- Submit the sitemap in Search Console and inspect a few important URLs.
- Test on a real phone.
- If the domain or structure changed substantially, use the relevant tools in Search Console and keep notes of what you did.
Phase 7: First weeks after launch
- Watch Search Console daily at first, then weekly: indexing and coverage reports, crawl errors, security issues.
- Look for 404s with traffic or links; add missing redirects.
- Compare analytics against the baseline. Short-term movement is normal after a relaunch; sustained drops on key pages need investigation.
- Check key pages' titles in the search results after Google re-crawls them.
- Fix issues in order of impact: broken important pages, blocked indexing, then missing redirects, then smaller items.
- Be patient. Search engines need time to re-process a changed site, and results vary.
Common mistakes
- Leaving the development "noindex" on after launch.
- No redirect map, so old URLs return 404 and lose their history.
- Redirecting everything to the home page.
- Changing URLs unnecessarily just because the platform made it easy.
- Launching without analytics, then having no baseline or evidence.
- Forgetting the staging site, which gets indexed and competes with the real one.
- Deleting high-traffic content during a redesign without checking what it was doing for you.
- Launching on a Friday evening with no one available to fix issues.
What does Xposio do?
- We audit the existing site before redesigning, so we know which pages and URLs carry visibility and conversions.
- We build and test a redirect map on a staging copy, and verify it again after go-live.
- We run a launch checklist covering indexing settings, robots, sitemap, canonicals, hreflang, HTTPS and structured data.
- We set up analytics and conversion tracking before launch, and record a baseline for comparison.
- We monitor the first weeks and report issues plainly. We cannot promise rankings, only a careful, documented process that reduces avoidable loss.
Internal link: Learn about the Technical SEO service at
/en/services/technical-seo, and the SEO & Search Visibility service at/en/services/seo-search-visibility.
You can also order a Digital Snapshot report at /en/report, or browse sample report formats at /en/reports.
Conclusion
- Treat relaunch SEO as risk management: protect what already works.
- Map every old URL to the best new page with 301 redirects, and test them before and after launch.
- Remove any development "noindex" or robots block on go-live day.
- Submit a clean sitemap and verify the site in Search Console.
- Install analytics and conversion tracking before launch and record a baseline.
- Monitor closely for several weeks and fix the highest-impact issues first.
Related reading
Frequently asked questions
+What should I check before launching a website for SEO?
Make sure the site is not blocked by noindex or robots.txt, every page has a unique title and description, redirects are in place, HTTPS works, a sitemap is ready, and analytics and Search Console are set up.
+Will redesigning my website hurt my SEO?
It can if URLs, content or settings change without a plan. With a proper URL map, 301 redirects and careful checks, the risk is reduced, though some short-term movement is normal.
+What is a 301 redirect and why do I need one?
It is a permanent redirect from an old URL to a new one. It sends visitors and search engines to the right page and helps carry over the old page's signals.
+How long does it take for Google to index a new website?
It varies from days to weeks depending on the site and its links. Submitting a sitemap and verifying the site in Search Console helps Google find it, but timing is not guaranteed.
+Should I redirect all old pages to the home page?
No. Redirect each old page to the most relevant new page. Sending everything to the home page is often treated as an error and gives visitors a poor experience.
+What is the most common mistake when launching a new site?
Leaving a noindex tag or a robots.txt block in place from development, which keeps the live site out of search results. Check this first on launch day.
Ready to apply what you read?
Let's build your next digital project together.
