What Should You Check for SEO Before a Website Redesign?

Before a website redesign goes live, confirm whether URLs will change, build an old-to-new URL map, set server-side permanent redirects, remove staging noindex or robots blocks, verify Search Console ownership on every property you still need, and plan a monitoring window. Those checks matter more than a prettier homepage if you want to keep organic traffic intact. This article gives you a Change Risk Ladder, a Redesign SEO Gate Scorecard, and a realistic worked example so you can approve launch with evidence instead of hope.

Bottom line: A redesign is not only a design project. It is a crawl, redirect, and measurement event. Google’s site-move guidance recommends changing one major thing at a time when possible, preparing thoroughly, and expecting temporary ranking fluctuation while Google recrawls and reindexes. Permanent redirects such as 301 or 308 do not cause a loss of PageRank according to Google, but weak mapping and broken redirects do create avoidable damage.

Key takeaways

• Classify the redesign before you brief designers: same URLs, path changes, domain changes, or hosting-only changes. Each level needs a different SEO gate.

• Do not launch URL changes without a complete old-to-new map and tested server-side permanent redirects.

• Remove development noindex rules and temporary robots blocks before go-live; Google lists leftover crawl blocks as a common site-move mistake.

• Keep redirects live long enough for Google and users to finish the transition—Google generally recommends at least one year for redirects after a URL move.

Why redesigns quietly erase organic gains

Teams often approve a redesign because the brand looks dated, lead forms feel weak, or the CMS is hard to edit. Those are real problems. SEO risk shows up later, when high-impression URLs disappear, redirects point to the homepage, staging robots rules stay in production, or Search Console verification breaks on launch day.

Pages that already earn impressions in Google Search Console’s Performance report are discovery assets. If those URLs change without a clean handoff, Google must rediscover the new destinations. For medium-sized sites, Google notes that it can take a few weeks or more for new URLs to gradually replace old ones; larger sites take longer. If you are still choosing repair, redesign, or rebuild, settle that first—then run the SEO gate before creative sign-off becomes irreversible.

The Change Risk Ladder

Score the project by the type of change—not by how expensive the design looks. Google’s guidance is explicit that stacking a domain move, CMS change, and layout overhaul at once makes problems harder to diagnose. Prefer sequencing.

Most “redesigns” that later cause traffic loss were L2 or L3 projects sold as L1. Force the vendor or internal team to state the level in writing before design production begins.

The Redesign SEO Gate Scorecard

Score each factor from 0 to 3. Launch only when every factor that applies to your risk level is at least 2, and the total for applicable factors is strong enough that you would defend the go-live decision to a skeptical peer.

Interpretation: Treat a total of 15–18 across the six factors as launch-ready for L2/L3. Scores of 12–14 may proceed only with a named owner fixing the weak factors within a fixed window. Below 12, delay launch. For L1 template-only work, URL mapping and redirects may score N/A, but indexability, canonical hygiene, content parity, and measurement still apply.

What to finish before launch day

1. Build the URL inventory the business actually relies on

Google recommends starting with important URLs from sitemaps, analytics or server logs for high-traffic pages, and Search Console’s links data for pages with internal or external links. Include images, PDFs, and other downloadable assets that already receive search or referral traffic. Do not rely only on the CMS page list—orphaned landing pages and campaign URLs often live outside neat menus.

2. Map every kept URL to a relevant destination

For path or domain changes, prepare an old-to-new mapping before redirects go live. Google warns against redirecting many old URLs to one irrelevant destination such as the homepage, because that can confuse users and may be treated as a soft 404. Consolidation is fine when multiple old pages truly become one new page—document that intent instead of dumping everything onto the home page.

3. Prefer server-side permanent redirects

Google recommends server-side permanent redirects such as HTTP 301 or 308 when a page’s URL should change in search results. Temporary redirects are for temporary situations. JavaScript redirects are a last resort because rendering can fail. Avoid long redirect chains; Googlebot can follow multiple hops, but Google advises redirecting to the final destination directly and ideally keeping chains to no more than three hops, and fewer than five.

4. Clear staging blocks and fix robots rules

If the new site used noindex or a disallow-all robots.txt during development, remove those blocks when the move starts. Google lists leftover noindex or robots.txt blocks among common migration mistakes that prevent the new site from being indexed completely. Also prepare correct 404 or 410 responses for content you are intentionally not migrating.

5. Update canonicals, internal links, and sitemaps

After redirects are active, Google’s site-move checklist calls for self-referencing rel="canonical" tags on the new URLs, updated internal links, and a sitemap containing the new URLs. Submit the new sitemap in Search Console. For domain or subdomain moves, use the Change of Address tool after redirects are in place; do not use that tool for HTTP to HTTPS alone, www/non-www swaps on the same domain, or hosting-only changes.

6. Protect Search Console verification

Verify every relevant old and new property variant you need—www and non-www, HTTP and HTTPS where applicable. If you verify with an HTML file, meta tag, or Google Analytics association, make sure those tokens survive the redesign. Losing verification on launch day means you lose the dashboard you need to diagnose problems.

Worked example: a professional-services redesign with new slugs

Consider a hypothetical accounting firm redesigning from an aging CMS to a modern site. Leadership wants cleaner service URLs. Search Console shows that five service pages account for most non-brand clicks. The redesign plan originally pointed every unmatched old URL to the homepage “to keep it simple.”

Change Risk Ladder: L2 (same domain, new paths). Gate Scorecard before intervention: inventory 2, mapping 0, redirects 0, indexability 2, canonical hygiene 1, measurement 2 → total 7. Launch would be reckless.

The corrected plan maps each high-traffic service page one-to-one, consolidates two overlapping tax-advisory articles into one stronger guide with both old URLs redirecting to that guide, updates navigation to the final URLs, removes staging noindex, and schedules two weeks of Search Console and analytics review after launch. Gate Scorecard after remediation: 3, 3, 3, 3, 3, 3 → 18. The visual redesign can still ship—just not without the mapping work.

This is a hypothetical scenario used to show the method. It is not a claim about a specific client result.

How to monitor after go-live

Google recommends monitoring both old and new traffic with Search Console and analytics. Useful reviews include:

• Index coverage or page indexing graphs for unexpected error spikes on the new site.

• Sitemaps: indexed counts should rise on the new URL set over time.

• Performance report queries and pages: new URLs should begin earning impressions and clicks as indexing progresses.

• Server logs for redirect failures, unexpected 404 spikes, and crawl volume changes.

Expect temporary fluctuation. Google states that rankings can move while systems recrawl and reindex, then settle over time. Do not treat the first few volatile days as proof the redesign “killed SEO,” and do not ignore sustained 404 spikes or soft-404 patterns either.

Common failure patterns

• Homepage dumping: Redirecting many unrelated old URLs to the home page.

• Staging leftovers: Shipping with noindex or a blocking robots.txt still enabled.

• Design-first sequencing: Approving visuals before the URL map exists, then treating redirects as a last-minute ops task.

• Stacked changes: Domain move, CMS migration, and layout rewrite in one cutover, against Google’s “change one thing at a time” recommendation when sequencing is possible.

• Short-lived redirects: Removing redirects after a few weeks while Google and external sites still reference old URLs.

Limitations and exceptions

This framework assumes you can access Search Console and control redirects on the hosting or CDN layer. Some managed builders make permanent redirects harder—minimize URL changes or choose a platform that supports server-side redirects before you redesign. Under a hard deadline, keep URL structure stable for the first release and rewrite paths later. Clean redirects also cannot rescue thin service pages or broken conversion paths; the SEO gate protects discovery equity, not weak content.

Recommended next steps

1. Write the Change Risk Ladder level into the project brief before design production expands.

2. Export the last 90 days of Search Console pages and queries as your baseline.

3. Complete the Redesign SEO Gate Scorecard with your developer or agency; block launch on any factor scored 0–1 that applies to your level.

4. Test redirects with URL Inspection for samples and a crawler or script for the full map.

5. Schedule a 14-day and 45-day post-launch review focused on indexing errors, top-query coverage, and 404 rates—not vanity design feedback alone.

If you want help turning a redesign plan into a redirect-safe SEO launch plan, Oasbit’s search engine optimization services include migration readiness reviews alongside ongoing organic growth work. For teams still choosing between repair, redesign, and rebuild, see our guide on how to choose the right website intervention. When the redesign also changes your technical stack or storefront, our website and SaaS development services can coordinate the build with the SEO gate instead of treating redirects as an afterthought.

If your redesign is already underway and you need a second set of eyes on URL mapping, redirects, and Search Console readiness before launch, book a growth strategy session and bring your current sitemap plus the proposed URL list.

Sources

• Google Search Central — Site moves with URL changes

• Google Search Central — Changing your hosting (no URL changes)

• Google Search Central — Redirects and Google Search

• Search Console Help — Change of Address tool

• Search Console Help — Performance report (Search results)