Law Firm Website Migration Checklist: Protect SEO, Enquiries and Tracking During a Redesign
Website MigrationTechnical SEOWebsite RedesignAnalytics QARedirects

Law Firm Website Migration Checklist: Protect SEO, Enquiries and Tracking During a Redesign

SSolicitor.live Editorial Team
2026-11-21
7 min read

Use this law firm website migration checklist to protect SEO, enquiries, tracking, redirects and trust signals during a redesign or relaunch.

A law firm website migration can improve usability and conversion, but an uncontrolled redesign can also remove valuable URLs, break enquiry routes and make performance data unreliable. This checklist gives solicitors a practical pre-launch, launch-day and post-launch workflow for protecting search visibility, enquiries, tracking and trust signals during a website redesign, CMS change or domain move.

Overview

A website migration is any significant change to a site’s platform, domain, URL structure, design, content, templates or hosting. A visual redesign may be a migration even when the domain stays the same. The risk increases when several changes happen together, such as moving from one CMS to another while rewriting practice-area pages.

The safest approach is to treat the law firm website as both a search asset and an operational intake system. Every important page should have a planned destination, every contact route should be tested, and every key conversion should remain measurable. Assign one person to own the migration, even if developers, designers and marketing specialists are involved.

Keep a dated copy of the current site inventory, analytics configuration, form settings and redirect plan. Do not rely on memory or on a staging environment that has never been compared with the live website.

For wider enquiry and conversion checks, use this law firm website conversion audit checklist. If the project changes privacy notices, cookies or enquiry forms, review the GDPR workflow for law firm websites before launch.

What to track

1. URLs, redirects and indexability

Export or compile a list of current URLs, including practice-area pages, location pages, solicitor profiles, articles, FAQs, contact pages, downloadable resources and useful landing pages. Record their current status, page title, organic visits where available, links, and intended replacement.

Create a redirect map before development is complete. A redirect should normally send a retired page to its closest relevant replacement, not automatically to the home page. Avoid redirect chains: map the old URL directly to the final destination.

Old URLReason for changeNew URLRedirect statusOwner
/family-law/divorceURL structure revised/family-law/divorce-solicitorTo testSEO lead
/about/firmPage consolidated/aboutTo testContent owner

Check that the new site has a crawlable internal-link structure, a usable XML sitemap and appropriate robots controls. Staging sites should be kept out of search results while under development, but those controls must be reviewed before launch. Confirm that canonical tags, page titles, descriptions, headings and structured data have not been replaced with generic defaults.

2. Practice-area content and trust information

Compare every important practice-area page with the approved content inventory. Check that the new version still explains the service clearly, identifies the relevant location where appropriate, provides a sensible next step and avoids promises about outcomes. Review family law, conveyancing, personal injury, employment, immigration and other specialist pages separately rather than assuming one template suits every service.

Retain or deliberately revise solicitor and office details, regulatory information, complaints information, privacy notices, accessibility information, opening hours, emergency guidance and any required professional disclaimers. Make sure claims, testimonials, accreditations and case examples remain accurate and appropriately qualified. Marketing requirements can vary by jurisdiction and professional body, so obtain a suitable compliance review rather than treating a technical migration as a substitute for legal or regulatory advice.

3. Enquiry forms, telephone numbers and intake routes

List every conversion path: general contact forms, practice-area forms, callback requests, live chat, email links, telephone numbers, booking tools and downloadable resources. Confirm that submissions reach the intended mailbox or case-management workflow and that someone is responsible for monitoring them.

Use a form-and-call test script for each route:

  1. Submit a test enquiry with a unique reference such as “MIGRATION-TEST-01”.
  2. Confirm the success message, email notification and any CRM or intake record.
  3. Check that required fields, error messages and consent choices work on desktop and mobile.
  4. Test telephone numbers from the header, footer, contact page and practice-area pages.
  5. Verify that tracking records the intended event without exposing unnecessary personal data.
  6. Delete or clearly label the test record so it cannot be mistaken for a genuine lead.

Review the site’s lead qualification and follow-up workflow after launch. A technically successful form is not enough if enquiries are routed to an unattended inbox or lose their source information.

Document the events that matter before the new site goes live. These may include form submissions, telephone-link clicks, email clicks, booking completions and downloads. Record the event name, trigger, destination and whether it should be counted as a primary conversion.

MeasurementPre-launch checkPost-launch check
Form completionTest event fires once after successful submissionCompare recorded completions with inbox or CRM records
Telephone clickTest links on mobile and desktopCheck event volume and call records where available
Organic landing pageConfirm page and campaign classificationsReview traffic, engagement and conversions by landing page
Consent controlsTest before and after consent choicesConfirm tags behave according to the configured choices

Check that consent language, privacy links and cookie controls match the firm’s current approach. Do not assume that copying a tag container makes the new implementation compliant. Also test keyboard navigation, focus states, colour contrast, image alternatives, heading order, form labels and error messages. Accessibility checks protect usability for prospective clients as well as supporting a more robust website operation.

Cadence and checkpoints

Before launch

  • Freeze the URL inventory and approve the redirect map.
  • Crawl the staging site and resolve broken links, missing titles, duplicate pages and accidental noindex instructions.
  • Compare key practice-area pages, internal links, contact details and disclaimers with the approved current version.
  • Test forms, telephone links, email links, booking tools and confirmation messages.
  • Check analytics events, consent behaviour, accessibility basics and mobile layouts.
  • Back up the current site and record the rollback procedure, responsible people and decision threshold.

On launch day

Launch during a period when the firm can monitor enquiries and technical issues. Remove staging restrictions, apply redirects, submit or update the XML sitemap and inspect a sample of old and new URLs. Test the home page, every core practice area, location pages, contact routes and the most important historical URLs.

Record the exact launch time and any deployment changes. Ask a staff member who was not involved in development to complete the main enquiry journey on a phone and desktop. Fresh eyes often reveal unclear labels, missing buttons or confusing confirmation messages.

After launch

At day seven, review indexability, redirect errors, crawl findings, rankings, organic sessions, form completions and calls against a comparable pre-launch period. At day thirty, separate temporary volatility from persistent technical or content problems. At day ninety, assess practice-area visibility, qualified enquiries, conversion rate and the quality of data reaching the intake team.

Use a simple issue log:

Date foundIssueImpactPriorityActionResolved
Day 2Old profile URL returns an errorPossible lost visit and poor user experienceHighAdd direct redirectOpen

How to interpret changes

Do not diagnose a migration from one metric or one day of data. A fall in organic traffic may reflect seasonality, tracking failure, changed consent behaviour, a lost page, an indexing restriction or a genuine ranking change. First confirm that measurement is working, then compare landing pages and query groups rather than relying only on total sessions.

If rankings fall for pages that changed URL, inspect redirects, canonicals, internal links and content equivalence. If traffic is stable but enquiries fall, test forms, telephone visibility, page speed, calls to action and the quality of the traffic. If enquiries rise but qualified matters fall, review practice-area messaging and intake questions rather than celebrating volume alone.

Keep an annotated record of launches, redirect changes, campaign activity, major content edits and tracking updates. This makes later comparisons more useful and supports better lead-source attribution.

When to revisit

Reuse this checklist for every redesign, domain move, CMS change, URL restructuring project and major release. Run a short technical and conversion review monthly during the first three months, then move to a quarterly review once performance is stable. Revisit sooner when the firm changes telephone systems, enquiry software, consent tools, practice areas, office locations or professional marketing requirements.

Set calendar reminders for seven, thirty and ninety days after launch. At each checkpoint, save the same core measures: indexed pages, redirect errors, organic landing-page performance, form completions, calls, qualified enquiries and intake response. Refresh the checklist at least twice a year, and whenever search, analytics, accessibility or consent platforms change in a way that affects the implementation.

Finally, keep the completed inventory, redirect map, test results and issue log with the firm’s operational records. A migration should be a repeatable process, not a one-off rescue exercise. That discipline protects the website’s search value while making it easier for prospective clients to contact the right solicitor at the right time.

Related Topics

#Website Migration#Technical SEO#Website Redesign#Analytics QA#Redirects
S

Solicitor.live Editorial Team

Legal Marketing and Operations Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.