A legacy small-business website usually fails in three places at once: it is slow on a phone, it cannot be edited without a contractor, and Google has quietly stopped sending the traffic it used to. The instinct is to buy a new theme. The better move is a modernization — keep the equity, replace the risk.
1. Inventory what already works
Before anyone opens Figma, export a crawl. List every URL that earns impressions or inbound links. Note the pages that convert (quote form, booking, phone). Those URLs are assets. A rebuild that invents a new slug for “about” and 404s the old one is how a shop loses a decade of local search in a weekend.
Write a one-page inventory: keep, merge, redirect, kill. If a page has no traffic, no conversions, and no legal reason to exist, it does not get a new design. It gets a 301 to the page that should have been there.
2. Separate content from the CMS accident
Twenty years of enterprise migrations taught us the same lesson every time: the danger is not the visual design. It is the CMS, the plugin pile, and the person who is afraid to touch either. Pull copy, images, and offers into a simple inventory. Decide the future stack based on who will maintain it — a Next.js site a founder can edit, a sober CMS, or a static site with a form service — not based on what a vendor wants to resell.
3. Rebuild on an indexable stack
Google ranks pages it can read. That means real HTML for titles, headings, and the first screen of content. Client-rendered shells with empty documents lose. Fast TTFB, compressed images, and a form that submits on a 4G parking lot are part of the product.
- One canonical per page, HTTPS, trailing-slash policy you actually keep.
- XML sitemap and robots.txt that point at the real URLs.
- Structured data for the business, the services, and any FAQ you are willing to stand behind.
- Internal links from service pages to the contact path — that is the top of the lead funnel.
4. Protect the funnel while you cut over
Launch with the redirect map live, Search Console on the new property, and the old analytics events mapped to the new forms. Call-tracking numbers and GBP categories do not change on launch day unless that is an explicit project. Local businesses die in the gap between “pretty new site” and “the quote form 500s.”
Audit week one. Ship a maintainable rebuild by week six. The risk was never the typeface.
5. What “done” looks like
You can edit a service page without a developer. A phone user can request a quote in under a minute. Search Console shows the important URLs as indexed. Core Web Vitals are in the window you agreed up front. Then you write the next three pages that match how people actually search — that is how a modernization becomes a lead engine instead of a rebrand souvenir.
If you are choosing between a coat of paint and a new platform, read rebuild vs. redesign. If you want the work done, that is our website modernization practice.
Continue in the practice: related service.