Website redesign SEO checklist: why traffic drops after a relaunch, what to check before, during and after launch, and how to keep Google and AI visibility.

In short
a website redesign keeps its SEO when the pages that bring traffic keep their URLs (or get a 301 redirect), their text, titles, headings and internal links, and when the new templates stay crawlable and fast. Most post-launch drops come from deleted content, broken internal links, a forgotten noindex from staging or content that only appears with JavaScript. Crawl the old site before you start, test the new one on a protected staging server, then compare the two after launch.
Want to go further? Ask
Website redesign SEO is the work of protecting rankings while templates, design, navigation, content or the CMS change. This guide covers redesigns that keep the same domain. If the domain or most URLs change, the project is a migration: follow our SEO migration checklist and Google's guide to site moves with URL changes, which warns site owners to expect temporary ranking fluctuations.
Yes, every time. Google and the AI assistants that read the web judge pages on what they find in the HTML: text, titles, headings, links, structured data, speed. A redesign changes some or all of these signals, so search engines re-evaluate the pages. The effect can be positive (faster pages, clearer structure, better content) or negative (thinner pages, lost links). What decides the outcome is how many ranking signals the new templates keep.
| What changes in the redesign | SEO risk | Why |
|---|---|---|
| Colors, fonts, images only | Low | HTML content and URLs stay the same |
| New templates and page layouts | Medium | Headings, text blocks and internal links often move or disappear |
| New navigation and menus | Medium | Link depth and internal authority are redistributed |
| Content rewritten or merged | High | Pages lose the passages and keywords they ranked for |
| New CMS or JavaScript framework | High | Rendering, URLs, redirects and metadata all change at once |
| URL structure changed | High | Every changed URL needs a redirect: treat it as a migration |
The causes repeat from one project to the next. Each one has a simple control:
| Risk | How it shows up | Control |
|---|---|---|
| Content deleted or shortened | Pages drop for long-tail queries | Compare word count and sections per page, old vs new |
| Titles and H1 rewritten | Lower click-through rate, lost positions | Export titles and H1 before, diff them after |
| Internal links lost | Deep pages lose rankings, orphan pages appear | Compare internal links received per URL |
| URLs changed without 301 | 404 errors, lost backlinks | Redirect map tested on every old URL |
| Content rendered by JavaScript | Pages indexed empty, AI assistants see nothing | Compare raw HTML and rendered HTML |
| Slower templates | Worse Core Web Vitals, higher bounce | Test LCP, INP and CLS on staging |
| noindex or robots.txt block left from staging | Pages leave the index within days | Check robots.txt and meta robots on launch day |
| Structured data removed | Rich results disappear | Validate schema on each template |
Two of these deserve attention. First, JavaScript: Google renders pages with a headless Chromium, but its JavaScript SEO documentation states that it only discovers links that are standard anchor elements with an href attribute. Menus built with buttons or click handlers hide whole sections. Our guide to JavaScript SEO details the rendering options. Second, speed: Google's Core Web Vitals guidance sets the "good" thresholds at an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, measured at the 75th percentile of visits. Heavy hero videos and sliders are the usual reason a new template fails them.
Run a full crawl of the live site and export every indexable URL with its title, meta description, H1, word count, canonical, status code and number of internal links received. This crawl is your baseline: after launch, you will compare the new site against it line by line. Save the structured data and the robots.txt file too.
Export 12 to 16 months of Search Console data (clicks and impressions per page and per query), the pages that receive backlinks and the pages that convert. These pages are untouchable: keep their URL, their main text and their title, or improve them deliberately. A content audit helps decide what to keep, merge or remove, and gives each removal a destination URL.
The safest redesign keeps every URL. When a URL must change, map it one to one to its closest new page with a 301 redirect, without chains and without sending everything to the home page. Our guide to SEO redirects covers the rules. Google recommends keeping redirects for at least one year.
Designers decide where text goes; developers decide how it is rendered. Give them written requirements: one H1 per template, text served in the HTML, crawlable menus, breadcrumbs, the site architecture with the depth of each section, the schema to keep, and the performance budget. Readability and navigation also count: see our guide to UX and SEO.
Avoid launching during your peak season, before a holiday or on a Friday: the first days after launch are when errors are found, and someone must be available to fix them. Write down who checks what on launch day, and decide in advance which signal triggers a rollback (for example, key pages returning errors or disappearing from the index). Keep the old site available on a backup server for a few weeks, so that a template or a block of text can be restored quickly if a page loses its positions.
Put the new site on a staging server protected by a password (or at least a noindex rule), so that Google does not index a duplicate of your site. Then test before launch:
| When | Checks |
|---|---|
| Launch day | robots.txt allows crawling, no stray noindex, redirects live, XML sitemap updated and submitted in Search Console, analytics tag firing |
| Week 1 | Full crawl compared with the baseline, 404 errors in Search Console, URL inspection of the top pages |
| Weeks 2 - 4 | Clicks and impressions of key pages vs the same weeks before, indexing report, Core Web Vitals report |
| Months 2 - 3 | Queries that lost positions, pages to enrich, internal links to restore |
A broken link checker catches links still pointing to old URLs in menus, footers and articles. Fix those links at the source rather than relying on redirects, and restore the internal linking lost when sidebars or related-post blocks were removed. Some fluctuation during the first weeks is normal. A drop that continues after a month on a group of pages points to a specific cause: compare those pages with their baseline version.
ChatGPT, Claude, Perplexity and Gemini cite pages whose content they can read and extract. A redesign can cut that access in ways Google would forgive. A Vercel analysis of AI crawler traffic (December 2024) found that none of the major AI crawlers, including GPTBot and ClaudeBot, render JavaScript. A page that shows its text only after JavaScript runs is invisible to most AI crawlers.
Every additional change makes a drop harder to diagnose. If you also plan a domain change, a new URL structure or a large content rewrite, split them: launch the redesign with identical URLs and content, wait until traffic is stable, then run the next change. When the calendar forces everything at once, invest more time in the baseline crawl and the redirect map, because they are the only way to find what broke.
A redesign keeps its rankings when the new site carries the same content, links and signals as the old one, in a faster and clearer form. Crawl before, test on staging, compare after. Once the new site is stable, keep adding pages that answer your customers' questions: Sorank writes and publishes SEO and GEO articles in autopilot on the redesigned site.
When URLs, content and internal links are preserved, rankings usually settle within a few weeks. Google warns that rankings can fluctuate temporarily whenever a site changes significantly. If key pages are still below their baseline after one to two months, compare them with the pre-launch crawl to find content, titles or links that changed.
Only if the current URLs are a real problem, for example unreadable parameters or a structure that no longer matches the site. Every changed URL needs a 301 redirect to its closest equivalent, and it adds risk to the launch. Keeping existing URLs is the simplest way to protect backlinks and rankings.
Yes, when it fixes real weaknesses: slow templates, content hidden behind JavaScript, deep navigation, missing headings or thin pages. Gains come from measurable improvements such as better Core Web Vitals, clearer internal linking and richer content. A redesign that only changes the visual style rarely moves rankings on its own.
THEY TRIED SORANK BEFORE YOU
