SEO Checklist for Website Redesigns: Protect Rankings Before and After Launch
A redesign should make your site better, not invisible. Most traffic drops after a relaunch are not bad luck, they are missing redirects, lost metadata, and content that quietly disappeared. This is the pre-launch and post-launch checklist we run so a new design ships without erasing years of search equity.
Why redesigns lose rankings (and why it is preventable)
The pattern is familiar: a cleaner, faster, prettier site goes live, and within weeks organic traffic slides. The cause is rarely the new look. It is that URLs changed without redirects, pages that ranked were trimmed or removed, and search engines suddenly treat a mature site like a brand new one. The recovery timeline can be brutal. A widely cited third-party study of 892 domain migrations found the average new domain took roughly 523 days, about 17 months, to match the old domain's organic traffic, and 17% never fully recovered even after 1,000 days. The good news is that almost every one of these losses is self-inflicted and preventable. The fix is to treat SEO as a planning input, not a finishing touch. By the time a new site reaches QA, the highest-risk choices (URL structure, navigation depth, content hierarchy, template-level metadata) are already locked in. Get SEO into the room at the wireframe stage and the rest of this checklist becomes maintenance rather than rescue.
Pre-launch step 1: Crawl, benchmark, and keep the old site
You cannot preserve what you never measured. Before anyone touches the new design, capture a full baseline. Run a complete crawl of the current site with a tool like Screaming Frog or Sitebulb and export every URL, HTTP status code, title, meta description, heading, and canonical. Merge that crawl with your XML sitemaps, your top landing pages from analytics, and any paid campaign destination URLs. Treat that combined file as the canonical inventory of old URLs and freeze it. Then layer on value: tag each URL with its organic traffic, backlinks, keywords, and conversions so you know which pages are load-bearing. One step people skip and later regret: keep a private, password-protected copy of the old site live during the transition. When you hit a mystery 404 or a template question two weeks after launch, being able to look at exactly how the old page was built is a lifesaver. Block crawlers from that staging copy so it never competes with production.
Pre-launch step 2: Decide which pages live, merge, or die
Not every page deserves a seat on the new site, and not every page should be touched. Go through the frozen inventory and assign each URL one clear action: keep (performs well, carry it over largely intact), improve (has value but needs better structure or UX), merge (multiple pages compete for the same intent and should be consolidated), or remove (no meaningful traffic, links, or revenue, and no redirect-worthy equivalent). Two warnings here. First, do not gut content that ranks. Teams often modernize by simplifying layouts, hiding copy in tabs, or compressing text, and then watch rankings fall because the page no longer covers the topic with the depth Google rewarded. If a page ranks, the new version needs to cover the same ground or better. Second, protect the internal links that feed your best pages. Internal links pass equity and signal importance, and pages without external backlinks can depend entirely on internal links to stay indexed. Redesigns routinely orphan pages by rebuilding navigation from scratch.
Pre-launch step 3: Preserve URLs, then map 301s one to one
The simplest way to keep rankings is to keep URLs. Change a URL only when there is a clear technical, structural, or strategic reason. When URLs must change, the redirect map becomes the single most important document of the entire project, and it is where most redesigns either survive or fail. The rules are tight. Give every old URL exactly one destination. Use permanent redirects (301 or 308) because temporary ones (302, 307) do not pass ranking signals reliably. Match by intent, so a product maps to the equivalent product and a guide maps to the updated guide, never to a generic page. Avoid the catch-all homepage trap: dumping every old URL onto the homepage gets read as a soft 404, and the original page's equity is treated as gone. And kill redirect chains. Map A directly to its final destination, never A to B to C. Each extra hop bleeds a little link value, adds latency, and risks bots giving up before they reach the end. Watch for hidden chains too, like a domain redirect that lands on a staging URL that then redirects to live. Treat the map as a living decision register with an owner, not a spreadsheet nobody trusts the week before launch.
Pre-launch step 4: Carry over metadata, schema, and test on staging
A redesign rebuilds templates, and templates carry your on-page SEO. Systematically verify that every element survives the move: title tags, meta descriptions, H1 and heading structure, image alt text, canonical tags, Open Graph tags, the XML sitemap, and structured data. Schema deserves its own pass because it breaks quietly when templates change. Keep JSON-LD as your format, remove any legacy microdata so you do not ship conflicting markup, and make sure the structured data still matches the visible content on the page. Validate two ways before launch: Google's Rich Results Test for rich-result eligibility and the Schema Markup Validator at validator.schema.org for schema.org correctness. A green check confirms valid syntax, not that a rich result will appear, but invalid markup guarantees it will not. Do all of this on staging, never on the live domain. Run a pre-launch crawl of the new build and confirm forms submit, internal links point to final URLs (not through redirects), pages render on mobile, and analytics fires. Then, before going live, script a request to each old URL to record its full redirect path and final status, and diff that against your map to catch broad rules that quietly override specific mappings.
Launch day and the first week: verify, do not assume
Launch is the moment to validate reality against the plan. Immediately after cutover, crawl the full list of old URLs and confirm each returns a single-hop 301 to the right destination with no chains or loops. Generate a fresh XML sitemap containing only canonical, indexable new URLs, submit it in Google Search Console, and use the URL Inspection tool to request indexing for your highest-priority pages. Set expectations on timing: crawling and reindexing can take days to a few weeks, and requesting a crawl more than once for the same URL does not speed it up. Through week one, check Search Console daily for indexing errors and 404 spikes, watch for soft 404s where a page loads but returns thin or mismatched content, and confirm form submissions and conversions are tracking. A useful efficiency note: Google groups similar URLs, so a single template fix often resolves errors across many pages at once. Fix what the crawler actually hits, not just what the spreadsheet says should happen.
Post-launch monitoring and recovery
The work continues for weeks, not hours. Update internal links so the new site points directly to new URLs rather than relying on redirects for everyday navigation, and keep the redirects themselves active for at least 12-18 months (permanently if the URL will never be reused), since removing them too early on high-value pages drops the equity they were passing. Track Core Web Vitals in Search Console, but know that Interaction to Next Paint (INP), the responsiveness metric that targets under 200 milliseconds at the 75th percentile, draws on real-user field data that often is not available yet for a freshly relaunched site. In the meantime, optimize the lab proxy Total Blocking Time by trimming heavy JavaScript and breaking up long tasks, and recheck once field data accrues. Review KPIs against your original goals at three and six months. If traffic dips, do not panic-revert. Diagnose: most post-redesign losses trace back to a missed redirect, a removed or thinned page, or a metadata gap, and each has a clean fix. If you would rather not run this alone, our work spans technical SEO recovery and the kind of fixed-scope rebuild where these safeguards are built in from day one.
Get operations insights weekly
Join service-business operators who get one actionable insight on ops, automation, and growth every week.
No spam. Unsubscribe anytime.
You’re subscribed! Look for our next issue in your inbox.
That did not go through. Please try again, or email [email protected].
Frequently asked questions
Will a website redesign hurt my SEO?
It can, but it does not have to. Traffic drops after a relaunch are almost always caused by avoidable mistakes: URLs that changed without redirects, pages that ranked being removed or trimmed, and metadata or schema lost in new templates. Google's John Mueller has said there is no way to fully guarantee zero traffic loss during a redesign, so the goal is to minimize risk through preparation. If you keep URLs where you can, map every changed URL to a one-to-one 301 redirect, and carry over your on-page SEO, most redesigns hold their rankings or improve.
Should I keep my old URLs during a redesign?
Yes, wherever possible. The simplest way to preserve rankings is to leave URLs unchanged, because every URL change introduces a chance to lose equity or strand a page. Only change a URL when there is a clear technical, structural, or strategic reason. When you do change one, redirect it with a permanent 301 to the closest matching page and update internal links to point at the new URL directly rather than through the redirect.
What is a 301 redirect map and why does it matter so much?
A redirect map is a document listing every old URL and the single new URL it should point to after launch. It matters because it is the difference between a clean cutover and a multi-month traffic slide. The rules are strict: one destination per old URL, permanent 301 or 308 status codes, matching by search intent rather than dumping everything on the homepage, and no redirect chains where one redirect points to another. Map each old URL straight to its final destination so no link value leaks across extra hops.
What is a redirect chain and how do I avoid one?
A redirect chain is when one redirect points to another before reaching the final page, for example A to B to C. Each hop can lose a small amount of link value, adds latency, and risks search bots giving up before they reach the destination. Avoid chains by mapping every old URL directly to its final URL in a single hop. Watch for hidden chains too, such as a domain redirect that lands on a staging URL that then redirects to the live page, which should be collapsed into one 301.
What should I monitor after a redesign launches?
Start by crawling all your old URLs to confirm each returns a single-hop 301 to the right page. Submit a fresh XML sitemap in Google Search Console and request indexing for top pages, then check daily through the first week for indexing errors, 404 spikes, and soft 404s. Watch organic traffic and conversions, and review Core Web Vitals, keeping in mind that INP field data may take time to appear for a new site. Compare KPIs against your original goals at three and six months.
How do I recover if traffic dropped after a redesign?
Do not revert in a panic. Diagnose first, because most post-redesign losses trace to a short list of causes: a missing or wrong redirect, a page that ranked being removed or thinned, lost metadata or schema in the new templates, or orphaned pages from a rebuilt navigation. Crawl the site, compare against your old URL inventory, and fix the specific gap. Recovery is usually faster than starting over, and the same audit that finds the problem prevents it from recurring.
Ready to ship?
Tell us where you are stuck. We will review it and send a focused recommendation within one business day.