A new website should bring in more visitors, not fewer. Yet many businesses launch a redesign and watch organic traffic fall within days. The cause is usually a missed redirect, a staging setting left on, or page titles that disappeared during the rebuild.

Search traffic rests on URLs, content and signals Google has learned over years, and a redesign can change all three at once. Google expects temporary fluctuation during a move, but lasting losses usually come from mistakes a checklist would catch.

This guide walks through a website redesign SEO checklist in four phases: before you start, during the build, on launch day and in the first 30 days. Every step applies to any platform, with specific notes for WordPress. If you want a team to plan and build the new site with SEO handled from the start, see our WordPress development services.

Editorial note: this article contains no affiliate links. Facts were checked against Google Search Central, web.dev and WordPress.org documentation on November 9, 2026, and any other sources are credited where used. Search engine guidance and tool features can change, so confirm current details in the official documentation before you launch.

Why Redesigns Lose Traffic

Google ranks individual URLs. A page that moves without a redirect leaves an error behind and starts over with no history. A page that keeps its URL but loses content, headings or internal links becomes a weaker page.

Google’s site move guide lists the common mistakes: leftover noindex tags or robots.txt blocks, redirects to pages that do not exist, crawl error spikes, servers that cannot handle extra crawling, and outdated sitemaps. Each one is preventable.

For medium-sized sites, Google says new URLs can take a few weeks or more to appear, and larger sites take longer. A short dip is normal. A drop that keeps going means something is broken.

Phase 1: Benchmark Traffic, Rankings and Conversions

You cannot tell whether a redesign hurt SEO without a baseline. Export it before work begins and again just before launch.

In Google Search Console

• Export the Performance report for the last 3 to 12 months: clicks, impressions, average position, top queries and top pages.
• Save the Page indexing report counts and current errors, so old problems are not mistaken for new ones.
• Export the Links report, which shows your top linked pages and the sites linking to you.
• Verify every version of the site (www, non-www, HTTP, HTTPS) and keep the verification tag in the new build, as Google advises.

In Google Analytics 4

• Record organic sessions, key events (conversions) and revenue by landing page.
• List the landing pages that drive the most organic traffic and the most leads or sales.
• List every tracking tag on the site (GA4, Google Ads, Meta, call tracking) so none are lost.

If you use a rank tracker, record positions for your priority keywords. Otherwise the Search Console query export is a usable baseline.

Phase 1: Crawl the Current Site and Build a URL Inventory

Google suggests collecting old URLs from your sitemaps, server logs, analytics, the Search Console Links report and your CMS, including images, videos, JavaScript and CSS. Then crawl the live site with an SEO crawler and record, for each URL:

• The URL and its status code.
• The title tag, meta description and H1.
• The canonical tag and any noindex rule.
• Organic clicks and conversions from your Phase 1 exports.
• External backlinks, from the Links report or a backlink tool.

On WordPress, also export post, page, category, tag and product URLs. Archives often carry traffic nobody remembers until it breaks.

Decide what to keep, merge or remove

Give every URL one of four labels:

• Keep: the page stays, ideally at the same URL.
• Move: the page stays but gets a new URL. It needs a 301 redirect.
• Merge: two or more thin or overlapping pages become one stronger page. Each old URL redirects to the merged page.
• Remove: the page has no traffic, no links and no replacement. Google’s Page indexing help says a 404 is not necessarily a problem when a page is removed without a replacement.

Any page with backlinks or steady organic clicks should be kept or redirected, never simply deleted.

Phase 2: Keep the Staging Site Out of Google

If Google indexes your staging copy, you get duplicate content and sometimes staging URLs in search results.

Google’s guidance on private content is clear: if content must stay private, password protect it so only authorized users can reach it. HTTP authentication on the staging domain is the most reliable option. Many managed WordPress hosts offer password protection as a setting on staging sites.

A noindex rule is a useful second layer. Google’s guide for moving to new hosting suggests blocking indexing of a test copy with noindex. Keep two details in mind:

• Google says that for noindex to work, the page must not be blocked by robots.txt. If robots.txt blocks crawling, Google never sees the noindex rule, and the URL can still appear in results if other pages link to it.
• In WordPress, the “Discourage search engines from indexing this site” box under Settings > Reading adds a robots meta tag to every page since WordPress 5.3. WordPress.org notes that this does not block access, and search engines must choose to honor it.

Write down every block you add to staging. Each one must come off on launch day.

Phase 2: Keep URLs Where Possible and Build a 301 Redirect Map

The safest URL change is no change. In WordPress, match the permalink structure under Settings > Permalinks and keep slugs, category bases and WooCommerce product bases the same. When URLs must change, build a two-column redirect map (old URL, new URL) and follow Google’s guidance:

• Use permanent server-side redirects. Google recommends 301 or 308 redirects. Its redirects guide says permanent redirects show the new target in search results, while temporary 302 or 307 redirects keep showing the old page. Use JavaScript redirects only as a last resort.
• Redirect to the closest equivalent. Google warns against sending many old pages to one irrelevant destination, such as the home page.
• Avoid redirect chains. Redirect straight to the final URL. If that is not possible, Google says to keep chains short, ideally no more than three hops.
• Keep redirects for at least one year. Google suggests keeping them longer if you can. It also says not to worry about losing link credit, because 301 redirects do not lose PageRank.

On WordPress, add redirects at the server level or with a plugin. Rank Math includes a redirections module, and Yoast offers a redirect manager in Premium. Import the full map and test it before launch.

Google also says to update internal links, canonical tags and hreflang annotations so they point directly to the new URLs, rather than relying on redirects.

Phase 2: Preserve On-Page SEO Elements

A new theme or page builder rewrites the HTML of every page, and rankings can slip unnoticed. Compare each important staging page against your Phase 1 crawl.

• Title tags and meta descriptions: carry them over exactly unless you are deliberately improving them. On WordPress, confirm your SEO plugin settings and per-page data migrated with the content.
• Headings: keep one clear H1 per page and the same heading structure. Designers sometimes turn headings into styled paragraphs.
• Body content: do not cut copy to fit a cleaner layout without checking which pages rank on that text.
• Internal links: Google’s link guide says every page you care about should have a link from at least one other page on your site, and that crawlable links must be <a> elements with an href. Check that new menus, footers and buttons use real links.
• Structured data: keep your schema markup (Organization, Product, Article, FAQ, Breadcrumb and so on) and test it again after the theme change.
• Images: keep alt text and file names.

Phase 2: Check Core Web Vitals and Mobile Before Launch

Heavy themes, sliders and large images can make a new site slower. web.dev defines the Core Web Vitals and their “good” thresholds at the 75th percentile of page loads, measured separately on mobile and desktop:

• Largest Contentful Paint (LCP): 2.5 seconds or less.
• Interaction to Next Paint (INP): 200 milliseconds or less.
• Cumulative Layout Shift (CLS): 0.1 or less.

On staging you only have lab data. web.dev notes that Lighthouse measures LCP and CLS but not INP, using Total Blocking Time as a proxy. Real-user field data in PageSpeed Insights and Search Console arrives only after launch. Test your key templates on staging and fix the worst issues first. Our guide to the best Core Web Vitals tools compares options for testing and monitoring.

Google indexes the mobile version of your site. Its mobile-first guide says mobile should have the same content, headings and structured data, and equivalent titles and meta descriptions, as desktop. Do not lazy-load primary content on user interaction, because Google will not click or swipe to reveal it.

Finally, check capacity. Google says it crawls a newly moved site more heavily than usual, so confirm your hosting and firewall rules will not slow or block Googlebot.

Phase 3: Launch Day Checklist

Work through this list in order, and check every item on the live site, not on staging.

Remove indexing blocks and test redirects

Search the page source of several templates for “noindex”, and open yoursite.com/robots.txt to confirm it blocks only what you intend. Google adds that if you have no robots.txt, that URL should return a proper 404. Then run your old URL list through a crawler: every moved URL should return a single 301 or 308 to the right page, with no loops or chains.

Check canonicals

Google advises absolute URLs in canonical tags, and your canonical tag, sitemap and redirects should all name the same final URL. Make sure no canonical still points to staging.

Submit the XML sitemap

WordPress has generated a core XML sitemap at /wp-sitemap.xml since version 5.5, and SEO plugins such as Rank Math and Yoast usually replace it with their own. Whichever you use, confirm it lists the new URLs, then submit it in the Search Console Sitemaps report. Google recommends submitting the new sitemap after the redirects are live. You can also add a Sitemap line to robots.txt.

Confirm analytics and tracking

Using your Phase 1 tag list, check that GA4 records page views, key events fire on forms and checkout, and ad tags are in place. Lost tracking makes any traffic change much harder to diagnose.

Phase 4: The First 30 Days After Launch

Google says a move is complete only once Googlebot has visited every old and new URL at least once.

Week 1

• Check the Sitemaps report to confirm Google has read the new sitemap without errors.
• Run your top pages through the URL Inspection tool.
• Watch the Page indexing report for new “Not found (404)”, “URL marked noindex” and “Blocked by robots.txt” issues.

Weeks 2 to 4

• Compare Search Console clicks and impressions by page against your baseline.
• Compare GA4 organic sessions and key events by landing page.
• Track rankings for your priority keywords.
• Look at the Search Console Core Web Vitals report as field data starts to arrive.

Fixing what you find

Redirect any 404s that have backlinks or traffic, and restore missing titles, content or links on pages that dropped. After fixing an issue in the Page indexing report, click Validate Fix. Google says validation typically takes up to about two weeks.

“Page with redirect” entries for old URLs are expected. What you want to see is traffic on old URLs going down while traffic on new URLs goes up.

Website Redesign SEO Checklist by Phase

Share this one-page summary with your designer, developer and content team.

Frequently Asked Questions

Will a website redesign hurt my SEO?

It does not have to. Google expects temporary fluctuation, but lasting drops usually come from missing redirects, indexing blocks or lost content.

How long does it take rankings to recover after a redesign?

Google says new URLs on a medium-sized site can take a few weeks or more to appear, and larger sites take longer. If traffic is still falling after a month, investigate.

Should I use 301 or 302 redirects for a redesign?

Use permanent redirects, 301 or 308, for URLs that have moved for good. Google treats temporary 302 and 307 redirects as keeping the old page in search results.

How long should I keep redirects in place?

Google recommends at least one year, and longer if possible.

Can I just redirect all old pages to the home page?

No. Google advises redirecting each old URL to its most relevant new equivalent and warns against sending many pages to one irrelevant destination.

Is robots.txt enough to hide a staging site?

No. It does not guarantee a URL stays out of results and hides any noindex tag from Google. Use password protection.

Do I need the Search Console Change of Address tool?

Only if you are moving to a new domain or subdomain. Google says it is not for HTTP to HTTPS, www to non-www or path changes on the same domain.

What should I check first if traffic drops after launch?

Check for noindex tags, robots.txt, the WordPress search engine visibility setting and 404s on top pages.

Final Take

A redesign does not have to cost you search traffic. The steps that protect it are not complicated: know your baseline, map every URL, redirect what moves, keep what ranks, hide staging properly and remove every block on launch day. Google’s documentation covers each of these, and most traffic losses come from skipping one of them.

Treat the first 30 days as part of the project. Check Search Console every few days, fix problems quickly, and compare against your saved baseline. If you want specialists to run the migration checks and monitoring for you, our WordPress SEO services team can help.

Sources

• Google Search Central: Site moves with URL changes
• Google Search Central: Moving a site without URL changes
• Google Search Central: Redirects and Google Search
• Google Search Central: Block search indexing with noindex
• Google Search Central: Control what you share with Google
• Google Search Central: Build and submit a sitemap
• Google Search Central: How to specify a canonical URL
• Google Search Central: Mobile-first indexing best practices
• Google Search Central: Link best practices
• Search Console Help: Page indexing report
• web.dev: Web Vitals
• WordPress.org: Settings Reading Screen
• Make WordPress Core: New XML Sitemaps Functionality in WordPress 5.5

About the author

Jaykishan Panchal

Founder & CEO, TechCognate · SEO Strategist & WordPress Expert

Jaykishan Panchal is the founder of TechCognate and an SEO strategist with 15+ years of hands-on experience driving organic growth for businesses worldwide. He specialises in technical SEO, content strategy and GEO (Generative Engine Optimisation), helping brands stay visible in both traditional search and AI-driven discovery.

• Technical SEO
• Content Strategy
• AI & GEO
• Google Ads
• E-Commerce SEO

LinkedInX / @TechCognateAll articles