Client Redesign: SEO Must-Dos & Pitfalls

dailygrind

I've been through this with several clients and I'll tell you - the redesign phase is where most SEO value gets nuked. Before you even touch a wireframe, export everything. URLs, meta data, rankings, top pages - I pull all of that from Google Search Console, Ahrefs, and Screaming Frog. If you don't have a snapshot of the current state, you're flying blind.

Here's my process:

Backup the entire site structure - all current URLs, title tags, H1s, internal links. Use Screaming Frog to crawl and export. Then map every old URL to a new equivalent, even if the new design changes the navigation. Without a proper 301 redirect map, you'll lose link equity and rankings overnight.
Keep the core content intact - don't rewrite everything just for the sake of a shiny design. Preserve the key pages that drive organic traffic. If the design requires different copy lengths, adapt but keep the topic and intent aligned.
Test the new site on a staging environment first - block it from search engines via robots.txt and make sure Google Analytics and tracking scripts fire correctly. I've seen people launch with no tracking at all because the developer forgot to move the GA snippet.
Run a full technical audit post-launch - check for broken internal links, missing meta descriptions, crawl errors in GSC, and any accidental noindex tags. A colleague once launched a redesign where the entire blog was accidentally noindexed. That took two months to recover from.
Monitor rankings and traffic for at least 4 weeks - if you see a sudden dip, cross-reference with the redirect map. Usually the culprit is a missing 301 or a new URL that doesn't pass authority.

One more thing: conversion optimisation should inform the design, not the other way around. But that's a whole other conversation. Focus on the technical groundwork first, because a beautiful site nobody can find is just an expensive art project.

metricsmuse

Honestly, the biggest thing I see people mess up? Treating a redesign like it's only about how it looks, not what's already working under the hood. You've got to protect your existing traffic first.

Map out every current URL and set up 301 redirects before you touch a thing. Keep the content, titles and H1s on your best-performing pages exactly as they are - don't fix what isn't broken. Also make sure your canonicals, sitemap and robots.txt are solid before launch. Preserve (or ideally improve) your internal linking, check Core Web Vitals and page speed, and re-implement any schema you were running (organisation, article, that sort of thing). Then do a full crawl before you go live and another one straight after.

Most traffic loss comes from broken links and missing signals, not the design itself.

cpaoptimizer

Before you even think about touching the design, export every current URL, ranking position, and top-performing page you can get your hands on. The single biggest mistake i see is redesigning a site and then changing all the URLs without proper 301 redirects - you basically flush your organic traffic down the toilet. Keep the same core content, title tags, and internal link structure wherever you can. Also, run the new site in a staging environment first. Test that Google can crawl it, that your Analytics and GTM tags fire correctly, and that nothing accidentally blocks search engines before you flip the switch.

ppcnerd

Don't touch the URLs unless you've mapped every single 301 redirect yourself. I've seen too many businesses treat backlinks like they're permanent-they're not. Change a URL without redirecting and all that link equity you spent months (or years) building evaporates overnight. It's like tearing down the foundation of a house and wondering why the roof collapses.

metricsmuse

first thing: export every URL, meta description, the lot. then plan the design around conversion optimisation and content placement

marketingmule

Oh god, where do I even start with redesign SEO nightmares? Before you touch a single line of code, crawl the existing site with Screaming Frog (free tier handles 500 URLs). Export every URL, title tag, H1, meta description - the lot. Have a backup you can actually restore from, not just a screenshot.

The real killers I've seen:

URL changes without 301s. New CMS almost always means new slugs. Map old → new one-to-one before launch. Do not redirect everything to the homepage. One client lost 80% of their organic traffic in a week because their devs got lazy.
Staging environment going live with noindex still on. Check robots.txt and the <meta name="robots"> tag the second it goes live. Had a client launch and sit with noindex for two weeks. Traffic wiped out. Took months to recover.
Designers 'cleaning up' content to make pages pretty. They cut copy. Make sure the new versions keep the same topics, entities, and keyword context. Pretty pages don't rank.
Internal link loss. New navigation often means old pages lose their internal link equity. A page that used to get 20 internal links might now get 2. That's a ranking drop waiting to happen.
Speed regression. Every redesign ships heavier than it replaced. Run Lighthouse/Google speed test immediately. Don't assume the new template is faster.
Schema gone. FAQ, Review stars, Organisation markup - devs often forget to rebuild it. Check every schema type that existed before.

What's the biggest redesign disaster you've seen? I've got a few more horror stories if anyone wants them.

leadgen

Oh, I've been down this road more times than I care to count. One client redesigned their site without telling me - assumed it was purely cosmetic. Cue two weeks of panicked SEO triage.

If your client is sticking to a pure redesign (no IA changes, same status codes for existing pages), here's what I'd double-check based on painful experience:

First, compare Core Web Vitals before and after. Staging environments can reveal trouble before anything goes live - I once spotted a massive CLS jump from a lazy-loaded hero image that wasn't there in the mockups.

Second, watch internal links like a hawk. Redesigns love to silently strip out breadcrumb links, footer paths, or that sidebar you rely on. Ask for the Figma file and trace every link manually. It's tedious, but catching a broken internal chain before deployment saves your rankings.

Third, make sure the devs aren't using HTML tags for styling. I've seen H1s turned into H5s overnight because someone decided the new font size looked better with a different heading level. Insist on a tag audit in staging - check every main heading matches what's live.

One more thing: test your main pages on the staging environment with a proper crawler. Clients love to say "it's the same" until you point out the meta description is now an empty string.

adcraft

Staging site? Fine, that's the bare minimum. But duplicating the whole site and redesigning from the duplicate doesn't address the real headache - preserving your existing SEO authority while changing structure. I've seen too many people clone a site, redesign it on the staging copy, then push live and wonder why rankings tank.

Make sure you're mapping every URL from old to new before you even touch designs. And don't forget to block the staging environment from search engines from day one. A colleague of mine once forgot that and had the staging version indexed with broken links - absolute nightmare.

Also, if you're changing the URL structure or content layout, test those redirects with a crawler before going live. Otherwise you're just gambling on Google figuring it out.

pixelperfect

I've been through this exact situation with a client recently, and honestly, a checklist like this is gold - but only if you frame it around what the redesign actually means for the people visiting the site. Here's my take, based on what I've learned the hard way:

Audit current traffic, rankings, conversions - don't just pull numbers, ask why people land on certain pages. That feeling of "I used to find you easily" is fragile.
Full website backup - you'd think this is obvious, but I've seen designers wipe everything without a second thought. Never trust the staging environment alone.
Export all URLs - every single one. Even the 404s matter if someone saved an old bookmark.
Protect top-performing pages - these are your client's bread and butter. Changing them without care is like moving a customer's favourite chair to a dark corner.
Keep URLs the same or use proper 301 redirects - broken expectations hurt trust more than slow load times.
Save meta titles and descriptions - you'll want to replicate the emotional resonance, not just the keywords.
Maintain internal links - those connections are the unsung heroes of navigation. Losing them feels like a shop rearranging aisles overnight.
Keep important content - even if it's "just" a paragraph. Clients' customers often quote that text back to them - it's part of the relationship.
Mobile-friendly design, page speed, Core Web Vitals - non-negotiable. People judge a business in under three seconds on mobile.
Set 301 redirects, update sitemap, check robots.txt and indexing - the technical bones. If these break, the whole thing feels like a ghost town.
Keep or improve schema - especially for local businesses. That little star rating in search results is a subtle trust signal.
Set up GA4 and Search Console from day one - don't wait until after launch. You need benchmark data before you can celebrate improvements.
Fix broken links, optimise images, improve navigation and UX - these are the polish that makes users go "wow, this just feels better."
Keep strong CTAs - don't change the wording unless you've tested it. "Get started" can perform twice as well as "sign up" depending on your audience.
Test on staging with real user flows - not just technical checks. Get someone who doesn't know the project to try booking a service or buying a product.
Monitor after launch and compare with old data - the first week is emotional. Give it at least a month of normal traffic before drawing conclusions.
Avoid peak-time launch - Monday morning? No. Thursday afternoon or a quiet weekend is kinder to everyone's sanity.
Plan content updates - a redesign is a chance to refresh copy, not just layouts. But do it gradually so users don't feel like they've walked into a stranger's house.
Protect content connected to backlinks - those backlinks are votes of confidence from other sites. Lose them and it's like a friend vouching for you and you've changed your name.
Ensure HTTPS security - obvious, but worth saying. No one trusts a padlock that's broken.

All of this boils down to one thing: make the change feel like an upgrade, not a rebrand. Your client's customers shouldn't have to relearn how to use the site - they should just feel it's smoother, faster, and still unmistakably the same business they trusted.

tiktokguru

Before you start the redesign, run a full site audit to map out your top-performing pages, keywords, and backlinks - otherwise you risk losing all that hard-earned traffic.

🔹 Keep existing URLs where possible, or set up 301 redirects
🔹 Preserve core SEO elements: title tags, meta descriptions, headings
🔹 Use the redesign as a chance to improve page speed, mobile experience, and site structure
🔹 Preview everything on a staging environment first (tools like Netlify or TiinyHost work well for quick checks)

Once it goes live, submit an updated sitemap and keep a close eye on Google Search Console and Analytics. Good luck to your client - you've got this covered!

communityfirst

oh, that's a huge topic with endless possibilities depending on the client's goals. from what I've seen, the absolute priority is keeping your URL structure and folder hierarchy intact - losing that can wipe out years of SEO value

digitalnomad

Absolutely! My biggest tip: run everything on a staging version first - never touch the live site until the new design is fully tested. Saves a tonne of SEO headaches. Once everything's solid, push it live.

gmbpro

Most redesigns tank rankings because nobody audits the existing setup first. before touching a single page:

Document current URLs, backlinks, and GA4 events (don't lose your conversion tracking)
Set up 301 redirects for every changed URL - one broken link can cost you 15-20% of organic traffic
Run a full GA4 property audit pre-launch, clean up any messed-up event parameters while you're at it

Fix the tracking before you break the rankings

nightowl

redesign or re-stacking - it's the difference between refining your PPC structure and tearing down the whole account. Custom builds? devs get caught up in the aesthetics and forget the fundamentals - canonicals, redirects, even basic tags. Like reorganising a warehouse without checking what's actually on the shelves.

adcraft

Let's be blunt - if your client is redesigning without a clear strategy for how it impacts their organic traffic, they're basically burning money. URL changes and 301s are table stakes. The real question nobody asks: why are they redesigning? If it's just to look pretty, you're about to watch rankings tank for no good reason.

A lot of "consistency" talk in threads like this misses the point. UI/UX changes often mess with page speed and user intent signals. No one cares about your beautiful new layout if load time jumps 2 seconds. Also, updating the sitemap is obvious, but submitting it via GSC and monitoring crawl errors for weeks after launch is what actually saves you.

Honestly, without knowing whether this is a full replatform, a CMS migration, or just a visual refresh, any "tips" are just noise. Get the client to define success metrics before touching a single div.

nightowl

The redesign rarely kills rankings on its own - it's the disconnect between the designer and whoever handles the technical SEO that does the damage. before anything goes live, i always run a full crawl with Screaming Frog (or an equivalent tool) to capture the entire inventory of existing URLs, redirect chains, meta data, and internal link structures. if URLs change without a proper 301 mapping, you're essentially demolishing the equity those pages have built, and clawing it back takes months - sometimes longer.

Beyond redirects, you need to lock down the new build's speed, verify the CMS handles canonicals and indexing directives correctly, and check whether any structural changes alter Google's current crawling path. rankings can absolutely drop if you disrupt crawl behaviour, even unintentionally. think of it like renovating a house: you don't pull out the load-bearing wall just because you want a bigger kitchen. if that crawl path gets broken, the recovery is a slog. fixing it all post-launch is always more painful than getting it right before the switch

dailygrind

Right, URL migration is one of those things that looks simple on paper but destroys your organic traffic if you get it wrong. I've been through this exact scenario - static HTML to WordPress - and the key is a bulletproof redirect map.

Here's what I'd do, step by step:

Crawl the current site with Screaming Frog (free tier is fine for smaller sites). Export all URLs into a spreadsheet. This gives you the full list of old paths you need to redirect.
Map old → new URLs before a single page goes live. Don't just redirect everything to the homepage. That's a traffic killer. Use the same content hierarchy where possible. For pages that don't have an equivalent, redirect to the closest relevant category or a related post. Document this in your spreadsheet.
Set up 301 redirects on the WordPress side. You can use a plugin like Redirection or add the rules directly to your .htaccess file. Test every redirect after launch using a tool like Redirect Path or Screaming Frog's redirect checker.
Update internal links in the new WordPress site. A quick Ahrefs site audit or Screaming Frog crawl will show you broken internal links pointing to old HTML pages. Fix those before users see them.
Update Google Search Console - submit a change of address if the domain stays the same (just scheme or structure change, not domain). Also submit the new sitemap as soon as it's live.
Monitor traffic - keep an eye on GSC coverage errors and organic traffic drops for at least two weeks. If you see a spike in 404s, you missed a redirect. Fix it immediately.

Without a proper redirect map, you're basically flushing whatever link equity the old site had. What's the page count on the current HTML site? That'll determine how tedious the mapping exercise is.

ppcnerd

Don't change the URLs. I've seen this sink more redesigns than almost anything else. It sounds like a simple technical task-just update the links-but in practice it breaks every backlink you've built up and confuses Google's cache. If the structure has to shift, set up proper 301 redirects from the old paths, and keep them live for at least a year. Even then, you lose some equity. The smartest move is to preserve the URL structure entirely, then layer the new design on top. Feels limiting, but it's the difference between a smooth migration and a six-month traffic dip.