Resources / Website migration
Law firm website migration: an SEO handover checklist.
Your new website needs an agreed plan for the pages, enquiries and search visibility the existing site supports. Use this guide to brief your designer, developer and independent SEO reviewer before launch.

Write down the change you are buying.
A visual refresh, a platform replacement and a domain move create different workloads. List the changes actually proposed: navigation, page content, URLs, hosting, forms, booking tools and analytics. Ask for the SEO tasks behind the phrase “SEO included”.
For a UK law firm, include the people who approve practice descriptions, biographies, office details and fee information. Name someone who can decide whether an old service page is still accurate and whether the firm wants enquiries for that work. This guide concerns website planning, rather than advice on a client’s legal matter.
Use the SEO planning guide for solicitors to connect the migration brief to the practice areas you want to grow. A redesign is a useful point to review that plan, but every new page still needs a purpose.
Give each decision an owner.
Use names in your actual plan. A task assigned to “the agency” can still fall between suppliers if both assume the other owns it. Include who can authorise a fix and what happens when that person is unavailable.
| Responsibility | Firm | Designer or developer | SEO reviewer |
|---|---|---|---|
| Existing page inventory | Confirm priority services and accepted work. | Export current routes and explain platform constraints. | Review search evidence and propose page decisions. |
| Content and user journey | Approve firm facts and legal explanations. | Build the agreed pages, navigation and contact journey. | Review intent, links and search presentation. |
| URL and launch checks | Approve important changes and launch authority. | Implement mappings, site configuration and fixes. | Check the evidence against the agreed launch criteria. |
| After launch | Review enquiry quality and flag intake issues. | Own technical support and recovery tasks. | Monitor agreed search measures and investigate changes. |
Make a page decision log.
Record the current URL, page purpose, relevant search evidence and proposed action before the build removes the old structure. Keep the original exports and reporting dates. A page with few recent visits may still be useful to existing clients or receive relevant external links.
The example below illustrates the decisions to resolve. It is a planning template, not a recommendation to change these routes on your site.
| Illustrative old route | Proposed action | Evidence to record |
|---|---|---|
| /employment-law/ | Keep the route and improve the page. | Approved employment scope and existing query/page evidence. |
| /our-people/jane-example/ | Move to an approved replacement biography only if necessary. | Confirmed destination, current role and implementation owner. |
| /news/old-office-opening/ | Review for historical value and current relevance. | Decision to retain, update or remove, with the reason recorded. |
Check the move before opening the new site.
Google’s site-move guidance recommends mapping changed URLs and using permanent server-side redirects to relevant destinations. Update internal links and canonical references, check indexing controls and provide the new sitemap. Temporary ranking fluctuations can occur while Google processes the move.
Ask for a review record you can inspect: the page or journey checked, the expected behaviour, the result, the person responsible and the resolution. A single screenshot of the homepage does not establish that the important service and contact journeys are ready.
- Choose representative service, office, team and guide pages to review alongside the full route inventory.
- Check that each chosen page contains the approved copy, readable mobile layout and correct contact destination.
- Test enquiry delivery using an agreed test procedure and destination, with the intake owner expecting the test.
- Confirm the actual production settings and access needed for launch, including who can fix an urgent issue.
- Document remaining defects and obtain the named launch owner’s decision about any unresolved issue.
Agree what happens after launch.
Put an observation schedule and an issue owner in the handover. Include the launch timestamp, important page changes and any campaign changes that affect the comparison. Compare the same country, device and search type when using Search Console; record filters alongside the export.
Separate a broken enquiry journey from a change in search visibility. The former needs an immediate operational response. For the latter, investigate which pages and queries changed, whether URLs can be accessed and indexed, and whether the reporting period is comparable before deciding on more content.
Our technical SEO service covers agreed implementation or developer briefs. If you need the rebuild itself, see website redesign for law firms. The Scarsdale Solicitors case study provides a relevant website delivery example with its own reporting context.
Take a concrete brief to your suppliers.
Download the checklist and fill in the named owner, evidence and status for each task. Adapt the checks to the size and scope of your move. Add the current site, any staging access, launch target and the decisions you need the review to support.
For an independent review, ask which pages and systems are covered, what access is required, how findings are delivered and who implements them. The free RankMyFirm strategy call helps scope that work. A substantive audit and any implementation are quoted separately.
Your questions, answered.
Can our designer stay in place while you review the SEO?
Yes. The review can be scoped alongside your existing designer or developer. Agree access, the decisions to review, the findings format and who implements each approved change.
Should every URL change when a law firm redesigns its site?
A redesign does not automatically require new URLs. Review the existing routes and the reason for each proposed change. Where a change is necessary, document the relevant destination and implementation checks.
Can a migration guarantee the same rankings?
No. Search engines decide how to process and rank the new site. A documented plan, tested implementation and agreed monitoring help the team identify and address issues; they do not guarantee rankings.
Sources & further reading
Primary references checked on 8 September 2026.
Give your relaunch
a clear SEO brief.
Bring your current website, relaunch plans and the work your designer is handling. We’ll discuss the review you need in a free 30-minute strategy call.
Book a strategy call Free 30-minute consultation
