What to Retain When Migrating a Trades Website

By Blackbird Marketing
When a trades business migrates its website, the safest approach is to retain the parts that search engines and customers already recognise, then improve the design or technology around them. That usually means protecting important URLs, useful service content, page titles, local information, enquiry routes, tracking and the domain itself.
In short: do not treat a new website as a blank canvas. Create a record of the current site, map every valuable old URL to the right new page, test phone and form enquiries, and only then make the switch.
A change of platform, design or developer can be worthwhile, but a new appearance does not automatically justify removing established pages. If a page currently attracts relevant visitors or explains a service clearly, preserve its purpose even if its layout changes.
Start by deciding what kind of migration is taking place
The risks depend on what is changing. A visual redesign on the same platform is different from moving to a new content management system, changing the domain, restructuring services or combining several sites. The more changes made at once, the harder it is to identify the cause of a problem after launch.
If this is the stage you are working through, you can also use How to Organise Problem-Led Navigation Without Hiding Core Services for the next practical checks.
Before work begins, write down which of these apply:
New design, with the same domain and page addresses.
New platform or hosting arrangement.
Changed domain name or company branding.
Rewritten service pages or a different page structure.
Removal, merging or renaming of older pages.
Changes to forms, telephone numbers, email routing or tracking.
This list is not paperwork for its own sake. It tells you which evidence to collect and whether redirect mapping, technical testing or enquiry checks need particular attention. A redesign may mainly require content and functionality checks; a domain change can also affect how visitors and search engines find the business.
Retain a complete record of the current site
Do not rely on memory or on a handful of pages saved in a browser. Export or record the current site’s important addresses before anything is removed. Include service pages, location pages that genuinely matter, useful advice articles, contact pages, quote pages and any other URL that receives visits, links or enquiries.
For each important page, record:
The current URL and the proposed new URL.
The page title, main heading and meta description.
The main service or question the page addresses.
Whether it receives organic visits, enquiries or referral visits.
Any internal links pointing to it.
Whether another page will replace it, or whether it should remain available.
Search Console, analytics and the existing content management system may each show different parts of this picture. A page with modest search traffic may still be valuable if it generates a telephone enquiry, supports another service page or is linked from a local listing.
Save a copy of the current sitemap, robots instructions and key technical settings where possible. Also keep a list of tracking tags, conversion events and integrations, because these are easy to omit when a new template or form is installed.
Do not remove pages simply because they look old
An older page can still answer a specific customer question or provide a useful route into a service. Removing it may reduce the number of ways a potential customer can find the business, even when the replacement homepage looks more polished.
If two pages genuinely cover the same subject, merging them may be sensible. The replacement should then cover the useful information from both pages, and the old address should point to the most relevant new destination rather than to the homepage by default.
For a wider look at how service-page depth affects a trade website, see How Many Service Pages Should a Trade Website Have?. The important migration decision is not a fixed page count; it is whether each retained page has a clear purpose for a customer and a sensible place in the new structure.
Keep the URLs that already earn attention where practical
The best option is often to keep the same address for a valuable page. If the page remains about the same service and there is no strong technical reason to change its URL, leaving it in place reduces avoidable disruption.
When an address must change, create a redirect map before launch. Each old URL should have one clear, relevant new destination. A service page should normally lead to the equivalent service page, not to a generic homepage simply because that is easier to configure.
Check the map for:
Old pages that have no proposed destination.
Redirect chains, where one old address points through another address.
Redirect loops that prevent a page loading.
Several unrelated old pages all being sent to the homepage.
Old image, document or campaign URLs that are still linked externally.
A redirect is not a substitute for relevant content. If an old page about a specific service is redirected to a page about a different service, the visitor may not find what they expected and the change may not preserve the page’s original value.
Check internal links as well as redirects
Redirects help visitors who use an old address, but the new site should not keep linking to old addresses unnecessarily. Update navigation, service menus, footer links, related-page links, buttons and calls to action so they point directly to the live destinations.
Review links in important articles and local pages too. A migration can appear successful while quietly sending visitors through several redirects or leaving them on a broken page after they follow a useful older reference.
Retain the content and page signals that explain each service
A new design should not erase the information that helps a customer decide whether to make contact. Retain accurate service descriptions, the areas served where genuinely relevant, clear limitations, useful process information and the language customers use to describe their problem.
Preserve or deliberately review these page signals:
Page titles that accurately describe the service and location, where a location is genuinely part of the page.
Meta descriptions that set a clear expectation rather than making unsupported promises.
A single, clear main heading and sensible subheadings.
Image alternative text where the image conveys useful information.
Internal links between related services and advice pages.
Structured data and other technical page details, if they are being used appropriately.
Retention does not mean copying every sentence without review. A migration is a good point to remove inaccurate claims, outdated areas, duplicated wording and weak pages. The safeguard is to make each deletion or rewrite a conscious decision, supported by the page record created before the build.
Take care with local information. Keep genuine business details consistent across the site and other listings, but do not add towns or service areas merely to create more location pages. A page should exist because it helps a real customer, not because its address contains another place name.
Protect the routes that generate enquiries
SEO visibility is only part of the outcome. A migration has failed commercially if visitors can find the new site but cannot call, submit a form or understand what to do next.
Before launch, list every enquiry route and test it from the customer’s point of view:
Telephone numbers in the header, contact page, service pages and mobile menu.
Forms on contact, quote and service pages.
Email addresses, including the mailbox or system receiving submissions.
Click-to-call links on mobile devices.
Confirmation messages after a form is submitted.
Any booking, chat or third-party enquiry tool that the site uses.
Use a test submission with a clear subject, then confirm where it arrives and whether the notification is readable. Check required fields, error messages, attachment handling and consent wording. A form that appears to submit successfully but does not reach the business is more damaging than a visible error.
If this is the stage you are working through, you can also use Agency Handover Terms: What Trades Businesses Should Check First for the next practical checks.
Keep a record of the current telephone number, email destination and form behaviour before the switch. If any of these are changing, agree who is responsible for checking the new route and when the old route can safely be retired.
Enquiry design also includes the questions asked. Removing every useful detail may create more incomplete enquiries, while adding too many fields can make the form harder to finish. Keep the information needed to understand the job, and make the next step obvious.
For an example of the decisions involved in arranging information around an enquiry route, see How Electricians Should Structure Website Enquiries. The same principle applies more broadly: the form and call-to-action should match the type of work the page discusses.
If this is the stage you are working through, you can also use Warning Signs Your Trades Website Is Attracting the Wrong Enquiries for the next practical checks.
Retain measurement, access and control
Make a written inventory of the accounts and settings connected to the current site. This should include the domain registrar, hosting, analytics, Search Console, business listing access, form systems, advertising accounts and any tag-management arrangement in use.
Do not assume a new developer or platform will automatically carry these across. Confirm who owns each account, who can access it and which tracking codes or conversion actions need to be installed again. Keep ownership with the business rather than allowing access to depend on one individual’s login.
Before launch, save a baseline of useful measurements. Depending on what is available, this might include landing pages, organic visits, enquiries, telephone clicks, form completions and indexed pages. The purpose is not to promise that every figure will remain unchanged; it is to give the business something specific to investigate if performance changes.
After launch, check the new site rather than waiting for a monthly report. Look for broken pages, unexpected no-index settings, blocked resources, missing analytics, incorrect canonical references, sitemap problems and redirect errors. Also check the main service pages in a normal browser and complete the enquiry process again.
Use a controlled launch and a clear fallback plan
Ask for a staging review before the new site replaces the old one. Check representative service pages, the homepage, contact route, mobile menu, forms, redirects and any important local information. A staging site may not show every live integration, so note what still needs a production check.
At launch, make sure the agreed redirects, sitemap, tracking and domain settings are released together where possible. Keep a dated copy of the redirect map and launch checklist so problems can be traced to a specific change rather than debated from memory.
Plan who will inspect the site after launch and what would trigger a correction or rollback. A broken contact form, widespread redirect failure or accidental blocking of search engines needs a faster response than a minor wording issue. The appropriate action depends on the scale and cause, so define the owner and escalation route in advance.
A structured build matters here. Blackbird’s published website design information describes a review, plan, build and launch/improve approach, which is a useful way to frame the work: agree what is being retained before design decisions make the old site harder to compare.
If the migration involves a substantial redesign, new platform or changed service structure, you can review Blackbird’s website design service information and ask whether the planned work suits the requirements of the existing site.
A practical handover checklist
Before approving the switch, ask the person responsible for the migration to confirm the following in writing:
Which existing URLs are staying the same?
Which URLs are changing, and where does each one redirect?
Which pages, images or documents are being removed, and why?
Have titles, headings, useful copy and internal links been reviewed?
Are the domain, hosting and search accounts controlled by the business?
Have forms, phone links, email notifications and confirmation messages been tested?
Are analytics, conversion tracking, Search Console and the sitemap working on the new site?
Has the site been checked on a mobile device as well as a desktop browser?
Who will check errors after launch, and what happens if a critical route fails?
The central test is simple: can an existing customer find the same service, understand the next step and contact the business, while a search engine can still connect the old page signals with the new site? If the answer is unclear, the migration is not ready to sign off.
Planning a website move? Protect the pages and enquiry routes that already matter before changing the structure. Discuss the website design requirements with Blackbird Marketing.
.png)
.png)
.png)


