SEO Before a Website Redesign: What Not to Break
You finally get the new site mockups back from the designer, and they look sharp: a cleaner homepage, bigger job photos, a booking widget instead of a plain contact form. You approve the launch. Three weeks later, the phone that used to ring from search traffic has gone quiet, and when you search your own trade, a competitor who used to sit below you now sits above you. Nothing about your work changed. The site did.
This is one of the most common ways a home-service business loses ground it never meant to give up. A redesign is a visual and technical project first, run by a designer or developer whose job is to make the site look and function better. Search visibility is a separate concern, and if nobody intentionally owns it, it gets treated as an afterthought and quietly breaks. None of this is a reason to skip the redesign; an outdated, slow, confusing site costs you jobs too. It's a reason to run it as two projects at once: the new look, and the preservation of what already works.
Why A Redesign Puts Rankings You Already Earned At Risk
Every page that ranks does so because Google has built a track record for that exact address: how long it's existed, what links point to it, how visitors behave once they land, and how closely its wording matches what people search. A redesign touches nearly all of those signals at once: addresses change, copy is rewritten for a fresher tone, navigation is restructured, and templates are swapped for new code that loads differently. None of that shows up in a design review, since a design review checks how a site looks, not how a search engine reads it.
The failure pattern is almost always the same: the new site launches, old addresses stop resolving, and the index still has the old ones on file. Instead of carrying the ranking history forward, the search engine treats the old page as gone and the new one as unproven, with no history behind it. A business can lose months of ranking progress in a single afternoon this way, and the cause is rarely a mistake anyone made on purpose. It's a step nobody assigned to anyone.
Audit What's Already Working Before Anyone Touches A Page
Before a new page goes into production, get a plain list of what your current site does right. Pull your top-performing pages by traffic and ranking position (Search Console and your Google Business Profile insights both hold this), and note the exact address, the phrase it ranks for, and roughly how much traffic it brings. This list serves as the map for everything that follows, and it should also flag which pages are linked to from elsewhere on your site, since those internal links helped build a page's standing in the first place. Skip this step, and the redesign team can't tell a quiet top performer from dead weight that's safe to cut.
Map Every Old Address To Its New One And Redirect It
A new site rarely keeps the old URL structure: folder names change, service pages get renamed, blog posts get reorganized. That's fine, as long as every old address is mapped to its closest new match and a 301 redirect is set before launch, not after someone noticed traffic dropped.
A 301 redirect tells a search engine (and a browser) that a page has permanently moved, and it carries most of the page's accumulated ranking signal to the new address. Skip it, and a visitor clicking an old bookmark lands on a dead page while Google treats the old address as gone and the new one as unproven. This is the single most common cause of a post-redesign traffic drop, and a simple spreadsheet, old address in one column and its new match in the next, prevents almost all of it.
Resist Rewriting Everything Just Because It's New
A redesign tempts most owners into the same trap: since the whole site is getting a fresh look, why not rewrite all the copy too? The instinct makes visual sense, but it can undo years of ranking progress in an afternoon. A page that already ranks does so partly because its wording matches the language real searchers use, refined by whichever version happened to perform. Replace that copy wholesale with a "fresher" rewrite from someone who never saw the performance data, and you're trading proven language for a guess.
The better move: treat top-performing pages as the starting point, not a draft to discard. Update the design around that copy, tighten sentences, add new photos, but keep the structure and phrases that were already earning clicks. Save the full rewrite for pages that were never performing anyway; those have nothing to lose.
Don't Let A Prettier Template Slow Everything Down
New templates arrive loaded with features the old site never had: video backgrounds, animated sliders, a chat widget, high-resolution galleries. Each one adds weight, and page speed factors into both ranking and how many visitors stick around long enough to call. A homeowner searching on their phone with water on the floor won't wait through a slow-loading hero video before hitting back and calling the next name on the list.
Before launch, check the new site's mobile load time against the old one's, not just how it looks on an office monitor. Oversized images and auto-playing video are the usual culprits, and both fix easily: compress images to the right file size, and let video load on click instead of automatically.
Protect The Internal Links That Hold The Site Together
Internal links, the links from one page on your site to another, tell a search engine which pages matter most and how everything connects. A redesign that trims a "Services" dropdown into a simpler menu, or drops a footer full of links to individual service pages, often breaks this structure without anyone noticing, since the new menu still looks clean to a human visitor.
Before launch, map which top pages were receiving links from the homepage, the main navigation, or other high-traffic pages, and confirm that the new site preserves an equivalent path to each. A page with no internal links pointing to it becomes an orphan: still live but harder for search engines to find, crawl, and trust as they once did.
Rebuild Schema Markup, Don't Skip It
Schema markup is the structured code behind a page that tells search engines facts your site already shows visually: business hours, service area, the review rating on the page, and the type of service offered. Search engines use this code to build the rich results that show up in search, like star ratings next to your listing or an FAQ that expands directly in the results.
Schema is invisible on the page itself, so a developer building the new site from scratch has no reason to notice it's missing unless it's on the checklist. Before launch, confirm the schema types on the old site (review, service, local business, FAQ, whichever apply) are rebuilt on their new equivalents, not left for "later."
A Quick-Reference Table For What Breaks And What Fixes It
| Redesign Change | What It Risks | Pre-Launch Fix |
|---|---|---|
| New URL structure | Old pages error out; rankings and saved links stop working | Map every old address to its new match and set a 301 redirect |
| Full copy rewrite | Wording that matched real searches gets replaced with a guess | Keep the proven page as the base; revise around it, not over it |
| Simplified navigation | Pages lose the internal links that told search they mattered | Preserve an equivalent link path to every top-performing page |
| Feature-heavy template | Slower mobile load times cost rankings and impatient callers | Compress images and delay auto-playing media until clicked |
| Missing schema markup | Star ratings and FAQ snippets disappear from listings | Rebuild the same schema types on each new page before launch |
A Pre-Launch Checklist Before The New Site Goes Live
Run through this with whoever is building the new site, not after it's already live:
- A list of current top-performing pages, their addresses, and the terms they rank for
- A 301 redirect mapped for every changing address, tested before launch
- Proven page copy carried into the new design instead of replaced wholesale
- A mobile load-time comparison between the old site and the new one
- Every top page's internal link path preserved in the new navigation or footer
- Schema markup rebuilt for reviews, services, and local business details
- A staging version of the new site reviewed in full before the old one goes dark
None of this slows a redesign down by months; it just requires someone- you, your developer, or a marketing partner- to own search continuity as its own task instead of assuming the design team handles it by default.
What To Watch In The First Weeks After Launch
Even a well-planned redesign deserves close attention right after it goes live. Check Search Console for a spike in crawl errors or pages marked "not indexed"; that's the fastest sign a redirect was missed, or a page got blocked from search by accident. Compare call volume week over week rather than day over day, since rankings can take time to settle around a new structure. If one page's traffic drops sharply, first check whether its old address redirects to the correct new one; that single fix resolves most post-launch drops.
A redesign is worth doing. An outdated site that loads slowly costs you credibility with every visitor who compares you to a competitor's newer-looking page. The goal isn't to skip the redesign; it's to walk in with a plan that carries your search visibility forward, rather than leaving it as a step nobody owns.
Frequently Asked Questions
When redirects and content are handled correctly, most sites see rankings hold steady or dip only briefly before recovering within a few weeks, since search engines still have to re-crawl and re-confirm the new pages. When redirects are missing or point to the wrong pages, recovery can take months longer because the engine has to rebuild trust in a page from scratch rather than transfer it.
Sending every address to the homepage is a common shortcut, but it passes almost none of the original page's ranking signal forward, since search engines expect a redirect to point to the closest equivalent content. A plumbing page should redirect to the new plumbing page, even if mapping that out takes longer.
Yes, and it carries more risk than a template change, since every page address is different, not just the folder structure underneath it. It needs a full redirect map covering every existing page, plus updated citations across directories and your Google Business Profile, since a mismatched web address across listings undermines the consistency search engines use to confirm a business is real.
The profile itself isn't affected by a site redesign, but the website link, service list, and any linked booking pages need updating to point at the new addresses, or customers clicking through from the profile will land on broken pages.
A staged rollout, where sections of the new site go live gradually while the rest stays up, lets you catch a missed redirect on a handful of pages before it affects the whole site. An all-at-once launch is faster, but any oversight in the redirect map hits every page at once, which is why a staging review matters more than the launch date itself.
Page speed is one factor among several, so a faster site tends to help rankings and keep more visitors from leaving before the page loads, but it won't offset damage from missing redirects or lost content on its own. Speed gains show up first in visitor behavior: more people staying on the page and calling, before they show up as a ranking change.
Get a pre-redesign SEO review — protect the rankings, traffic, and content you've already earned before your new site goes live. Green Thumb Local helps home-service businesses get found, get chosen, and get more calls with local SEO, Google Business Profile optimization, and content. Call (480) 360-0101.
