The new site launched on a Tuesday and looked great. A month later, calls from Google were down by a third. Nothing was "broken"; forty old URLs Google had spent years trusting now returned 404s, and the pages that replaced them had half the text. That's how most West Palm Beach businesses lose rankings in a website redesign, and it's entirely preventable.
This is the checklist I run on every migration, in order, whether you're changing designers, switching platforms or just restructuring pages.
Why redesigns lose rankings
Almost every post-launch drop I've diagnosed comes down to one of five causes. Every step below exists to prevent one of them.
| Feature | What goes wrong | Prevented in |
|---|---|---|
| URLs changed without 301s | Old links and Google's index hit dead pages | Phase 2 |
| Thinner content | The ranking page loses the text that made it rank | Phase 3 |
| A staging setting went live | noindex or a robots.txt block reaches production | Phase 4 |
| Titles reset to defaults | "Home | Company Name" everywhere | Phase 3 |
| Internal links reorganized | A key page ends up buried or orphaned | Phase 3 |
Phase 1: Capture what you have first
Do this before the new site is designed, because it should shape the sitemap. Start with a crawl of every URL, with its status code, title, meta description, H1 and word count. Screaming Frog's free version crawls up to 500 URLs, enough for most small-business sites. That export is your "before" snapshot.
A crawl only finds pages linked from your site, so pull the rest from outside sources.
- Search Console → Performance → Pages (last 16 months)
- Search Console → Links → Top linked pages
- Your current XML sitemap, and any old ones
- The website and booking links in your Google Business Profile
- URLs on flyers, vehicle wraps, QR codes and paid ads
- Old PDFs, images and campaign pages
That QR code on a menu pointing at /specials will break just as surely as a Google result. Then save three months of Search Console clicks and impressions by page, plus your top 20 queries and positions. After launch, "are we down?" should be answered with numbers, not feelings.
Phase 2: Build the URL map
This is the heart of a safe migration: a spreadsheet with one row for every old URL that has traffic, links or impressions.
| Feature | New URL | Notes |
|---|---|---|
| /services/ac-repair.html | /ac-repair | Content carried over and expanded |
| /about-us | /about | Straight rename |
| /blog/2019/hurricane-tips | /blog/hurricane-prep-checklist | Merged into newer post |
| /summer-special | /specials | Nearest relevant page |
- Q1Is the old URL still reasonable?YesKeep it identical. The safest redirect is the one you don't need.
- Q2Was its content merged into another page?Yes301 to the page that absorbed it.
- Q3Does it have traffic, links or impressions?Yes301 to the closest equivalent page, never the homepage, which tends to be treated like a missing page.
- Retired with no traffic or links? A 404 or 410 is fine and normal.
One more rule: one hop only. If an old URL was already redirected once, point the original straight at the final destination.
Phase 3: Carry the SEO into the new build
Redesign the layout freely, but keep the substance of any page that earns search traffic: the headings, the questions it answers, the specifics. Don't cut a 900-word service page to 150 words because the mockup looked cleaner.
- Titles (~50–60 characters) and meta descriptions (~150–160)
- One H1 per page that matches its topic
- Canonical tags pointing to the new URL, not staging
- Structured data, re-validated in the Rich Results Test
- Image alt text, with WebP or AVIF files where possible
- Internal links pointing straight at new URLs
- Hours, address and phone matching your Google profile
Keep the staging site blocked from indexing, ideally behind a password. I've seen a leftover noindex tag and a robots.txt Disallow: / both go live on otherwise flawless launches.
Phase 4: Launch day
Launch on a weekday morning with someone available for 48 hours.
- 1Deploy redirects with the siteThe same moment, not "later this week."
- 2Test every URL map rowEach should 301 to a page that returns 200.
- 3Check for blocksView source for noindex; open /robots.txt.
- 4Tell GoogleSubmit the new sitemap; request indexing for your top 5 pages.
- 5Update the outside worldGoogle Business Profile link, analytics and form conversions.
If the domain itself changed, use Search Console's Change of Address tool once redirects are live. It's for domain moves only, not page reshuffles.
Phase 5: Monitor for eight weeks
Some movement is normal while Google recrawls. What you're watching for is a pattern.
- Q1Did everything drop at once?YesCheck for noindex, a robots.txt block or a wrong-domain canonical before anything else.
- Q2Did a single page drop while the rest held?YesCompare it line by line with its old version. It's almost always lost content or a missing redirect.
- Small dip that's recovering? Leave it alone. Rewriting mid-recovery muddies the signal.
Keep the redirects for at least a year. Google's site-move guidance recommends that as a minimum; I leave them indefinitely. They cost nothing.
A West Palm Beach redesign, done two ways
Picture a hypothetical downtown West Palm Beach law office. Its best page is /practice-areas/estate-planning.php: steady clicks, links from local directories and a bar association listing, and 1,200 words the founding partner wrote years ago.
- Launches /estate-planning with three short paragraphs
- No redirect
- so directory links 404
- Google sees a thin page with no history
- 301 from the .php URL
- All 1,200 words carried over and updated
- Title kept close to the original
- Google Business Profile links updated
The same applies to a Palm Beach Gardens practice renaming provider pages, or a Clematis Street restaurant moving its menu from a PDF to a real page. The PDF has a URL too, and it probably ranks. And watch for 302 (temporary) redirects: many platforms default to them, and permanent moves need 301s.
One last trap: switching domains and redesigning in the same week. It can be done, but only with everything mapped and Change of Address in place. If you can, separate the two moves so that if something slips, you know which change caused it. And whatever you do, export your Search Console baseline first. You can't diagnose what you didn't measure.
Frequently asked questions
Will redesigning my website hurt my SEO?
Not necessarily. With a URL map, 301 redirects and preserved content, most redesigns hold their rankings, though some short-term fluctuation is common.
How long does it take Google to recover after a site migration?
For a small site with clean redirects, often a few weeks. Larger or messier migrations can take months, which is why you monitor weekly for two months.
Should I keep the same URLs when I redesign?
Yes, when they're reasonable. Change them only for a real benefit, such as dropping file extensions, and redirect every one you change.
Do I need 301 redirects if I'm only changing the design?
Not if every URL stays identical. But new platforms often change URLs subtly (trailing slashes, .html, category folders), so crawl the new site and compare.
For the broader process, see our step-by-step redesign guide, or check whether you need a rebuild at all with the 12-sign self-audit. When a replatform needs to carry its search history with it, that's what our Search Rebuild service covers; see how we work locally on our West Palm Beach web design page.
