Redesign the website without erasing the demand it already earns.

A contractor website redesign does not have to cost rankings or leads. Before launch, inventory the pages and queries already producing demand, map every changed URL to its closest replacement, preserve useful content and internal links, test crawlability and conversion tracking, then submit the new sitemap and monitor Search Console. The design is only one part of the move; continuity is the part that protects the pipeline.

A new website often begins with a reasonable complaint: the old one looks dated, loads slowly or does not turn enough visitors into calls. Trouble starts when the project team assumes everything old is disposable. A plain service page may look unimpressive to a designer and still be the page homeowners find for “emergency plumber near me” or “heat pump repair.” Removing it can remove a working entrance to the business.

Google says significant site changes can cause temporary ranking fluctuations while its systems recrawl and reindex pages. That does not make redesigns a bad idea. It means the agency should identify avoidable risk, explain what will change and show how the launch will be checked.

First decide what kind of redesign this really is

A visual refresh that keeps the domain, URL paths, core copy and navigation is different from a migration. Changing from one builder to another may still preserve public URLs. Moving to a new domain, consolidating service pages and changing every path is a much larger event.

Write down which of these will change: domain, HTTPS or host, content management system, URL structure, page inventory, navigation, copy, forms, phone tracking, structured data and analytics. The longer the list, the more rigorous the migration plan needs to be.

Google recommends changing one thing at a time when possible. A contractor changing domain, CMS and layout in one launch will have a harder time locating the cause if organic calls fall. If a domain change is not commercially necessary, separating it from the redesign usually makes diagnosis cleaner.

Record the baseline before anyone deletes a page

A migration cannot be judged without a before picture. Export at least the previous 12 months when seasonality matters, then note:

• organic landing pages, clicks, impressions and queries from Search Console;
• pages receiving external links or regular referral traffic;
• calls, forms and booked jobs by landing page where tracking allows;
• current URLs from the sitemap, CMS and a crawl of the site;
• titles, descriptions, canonicals, headings and structured data;
• internal links from navigation, service pages and articles;
• Google Business Profile, ad and directory links pointing to the site; and
• current form submissions, click-to-call events and phone-number behavior.

Do not keep a page merely because it exists. Keep or improve it because it serves a real search need, earns links, supports another page or contributes to enquiries. A page with little traffic may still answer an essential question before a homeowner calls.

This is also the point to find duplicate, outdated and weak material. Migration planning is not a demand to preserve every word. It is a demand to make consolidation decisions with evidence.

Build an old-to-new URL map

The URL map is the working document that tells developers, marketers and search engines where every old page belongs. Give each current URL one status: unchanged, moved, consolidated or retired.

When a URL changes, send it with a server-side permanent redirect—normally a 301 or 308—to the closest relevant replacement. An old “furnace repair in Leeds” page should lead to the new equivalent, not the homepage. If three thin boiler pages have genuinely become one complete boiler-service guide, all three can point to that consolidated page.

Google warns against sending many unrelated old URLs to one irrelevant destination such as the homepage because that can be treated as a soft 404. It also advises redirecting straight to the final destination instead of building chains such as old page → temporary page → new page.

If content has no honest replacement and no continuing value, return a proper 404 or 410. A clear missing-page response is better than misleading a homeowner to an unrelated service.

Preserve search intent, not just keywords

A redesign frequently compresses ten specific pages into a polished but vague “Services” page. That may simplify the menu while weakening the answers searchers need. Roof repair, replacement, storm inspection and commercial roofing are different decisions. So are AC repair, installation and maintenance. Drain clearing and whole-home repiping do not belong to the same stage of a plumbing purchase.

For every valuable page, identify the primary service, customer situation, service area, proof and next action. The redesigned version should answer that intent at least as well. Improve thin copy, but do not replace specific explanations with generic claims about quality and care.

Keep accurate licence, certification, financing, warranty and availability information visible where it matters. Never invent local offices, testimonials or years of experience to make a template look complete. The best migration is an opportunity to make the facts clearer, not larger.

Rebuild the internal paths that help customers and crawlers

Redirects catch old visits, but the new site should link directly to new destinations. Update navigation, breadcrumbs, page copy, related articles and footer links so they do not pass through redirects.

Make important services reachable through normal HTML links. A visitor reading an air-conditioning installation page may need financing, service-area and maintenance pages next. A search crawler needs those same connected paths to understand the site.

Preserve useful contextual links inside existing articles. For example, a guide about contractor service-area pages should still lead readers to the appropriate local services. The site architecture should reflect how the business sells and delivers work, not only the shapes available in a theme.

Run technical and conversion QA before launch

A staging site can look finished while still carrying a site-wide noindex directive. It may block crawling in robots.txt, canonicalize every page to the staging domain or load forms that never reach the office. Test the rendered site, not only the design file.

• Confirm production pages return the intended 200 status and important retired URLs redirect once.
• Remove staging-only passwords, robots blocks and noindex rules at launch.
• Use a self-referencing canonical on each indexable new URL.
• Update internal links, image paths, hreflang if used, canonicals and sitemap entries.
• Check titles, descriptions, one clear page heading and visible business details.
• Validate structured data against the content people can see.
• Test menus, call buttons, forms and thank-you states on real mobile devices.
• Place test calls and confirm dynamic phone-number replacement does not break the published business number.
• Verify analytics, consent behavior and conversions without recording duplicate events.
• Crawl the site for broken links, redirect chains, orphan pages and accidental duplicates.

Page speed deserves attention, but it should not become an excuse to strip away the content or proof that helps someone hire the company. Aim for a site that is quick, understandable and persuasive.

A practical launch sequence

Before launch: verify Search Console ownership, preserve verification files or tags, back up the current site, freeze the URL map and prepare the redirects. Schedule the switch during a lower-demand window when the team can respond.

At launch: publish the redirects, remove staging blocks, test a representative sample of high-value and long-tail URLs, check the canonical domain, submit the sitemap and confirm calls and forms arrive correctly. If the domain or subdomain changed, use Search Console’s Change of Address process after the redirects are working.

After launch: watch indexing, page errors, queries, landing-page clicks and lead outcomes on both old and new properties. Compare the pages that lost visibility with the URL map. Fix incorrect redirects, blocked pages or missing content before assuming the change is a normal fluctuation.

Google recommends keeping migration redirects for as long as possible and generally at least one year. Old bookmarks, directory listings and backlinks can keep sending people for much longer, so useful redirects often deserve to remain indefinitely.

What should the owner ask the agency?

• Which existing pages and queries currently produce qualified enquiries?
• Which URLs will change, and can I see the full redirect map before launch?
• What content is being removed or consolidated, and what evidence supports that decision?
• Who tests crawlability, canonicals, forms, calls, analytics and redirects?
• What is the rollback plan if lead capture breaks?
• Which Search Console and booked-job measures will be checked daily and weekly?
• Who owns the domain, website, analytics, tracking numbers and source files?

“We will resubmit the site to Google” is not a migration plan. A credible answer includes a page inventory, one-to-one decisions, technical tests and business outcome checks.

Trade-specific risks to catch

US, Canada and UK details

United States: preserve state and local licence details, branch or franchise boundaries, ZIP-oriented service information and GBP landing-page links. Do not merge real branch pages into invented metro coverage.

Canada: maintain province-specific credentials and bilingual or regional versions where they genuinely exist. Map English and French URLs carefully rather than pointing both to one generic page.

United Kingdom: retain Gas Safe or other applicable factual credentials, realistic postcode coverage and call-out information. Keep location pages tied to actual service capability rather than a list of towns.

Frequently asked questions