Table Of Contents
Introduction
A new law firm website can improve your firm’s branding, make legal services easier to understand, and create a better experience for prospective clients. But a redesign or migration can also affect the URLs, content, internal links, and technical settings that support your existing search visibility.
The risk is not limited to changing domains. Moving to a new content management system (CMS), rebuilding practice-area pages, reorganizing attorney profiles, or launching a new website design can introduce SEO problems if important details are overlooked.
For law firms, the consequences can extend beyond website traffic. A missing practice-area page, broken consultation form, or incorrect redirect can affect how prospective clients discover the firm and contact its attorneys.
The solution is to treat the migration as both a website project and an SEO project. Before launch, identify valuable pages and document what will change. During launch, verify the implementation. After launch, monitor search performance and investigate unexpected issues.
This guide explains how to approach a law firm website migration with a practical, step-by-step checklist.
What counts as a law firm website migration?
Before planning the work, identify exactly what is changing. Different migration types require different SEO checks.
| Migration type | What changes | Main SEO priority |
| Website redesign | Layout, templates, navigation, or content presentation | Preserve useful content, internal links, metadata, and functionality |
| CMS migration | The system used to manage the website | Check URL rules, canonicals, page content, indexability, and structured data |
| Domain migration | The website moves to a different domain | Map URLs, implement redirects, update links, and monitor both domains |
| URL restructure | Page addresses or folder structures change | Map old URLs to relevant new destinations |
| Website consolidation | Two or more websites become one | Assess overlapping content, backlinks, page destinations, and retirement decisions |
| Hosting migration | The hosting provider or infrastructure changes | Test availability, server responses, crawling, and performance |
A redesign can leave every URL unchanged, while a CMS migration can change hundreds of URLs. A project may also combine a domain change, a redesign, and a platform migration.
The first task is to document the actual scope. This helps the firm and its development team choose the appropriate migration process instead of applying the same checklist to every type of change.
The 12-step law firm website migration checklist
Step 1: Establish a baseline before making changes
Before developers begin rebuilding or moving the website, record how the existing site performs. This baseline helps you identify which pages matter most and gives you a reference for evaluating changes after launch.
Start by reviewing the firm’s available SEO and website data.
Record the following:
- Organic clicks, impressions, and important search queries from Google Search Console.
- Landing pages that attract organic visitors.
- Practice-area pages generating relevant enquiries.
- Attorney profiles and office pages that receive search traffic.
- Contact forms, consultation requests, telephone interactions, and other configured conversions.
- Existing backlinks pointing to important pages.
- Known technical issues, including broken links, duplicate URLs, and indexing problems.
Export the available URL lists from your website crawler, CMS, XML sitemap, and analytics tools. Combine these sources where practical because no single source necessarily captures every URL worth reviewing.
Also record the date range used for your baseline. Comparing the same periods before and after launch can help you avoid mistaking seasonality or changing search demand for a migration problem.
Why it matters: Without a baseline, you may notice that traffic has declined without knowing which pages were affected, whether the decline began before launch, or whether enquiries changed alongside organic visibility.
Step 2: Inventory every important legal website URL
A law firm’s website is more than a collection of generic service pages. Its URL inventory should account for the different types of legal content and the purpose each page serves.
Build an inventory covering:
| Page type | What to review |
| Practice-area pages | Main legal services, sub-practice areas, existing visibility, and intended replacements |
| Attorney profiles | Individual profile URLs, verified credentials, biography content, and internal links |
| Office and location pages | Real office locations, relevant contact details, and existing local search visibility |
| Legal articles and guides | Useful educational content, organic traffic, and backlinks |
| Case results and representative matters | Accuracy, approved content, existing links, and appropriate replacement pages |
| Contact and consultation pages | Forms, telephone links, booking journeys, and conversion tracking |
| PDFs and downloadable resources | Existing URLs, relevant backlinks, and whether assets need to move |
For every important URL, record its current status code, page title, canonical URL, indexing status, content purpose, and proposed action. Include available search performance and backlink data where appropriate.
Pay particular attention to valuable pages that might not appear in the main navigation. An older legal guide, for example, may still attract useful search visits or links from another website.
Do not assume every existing page must remain unchanged. The purpose of the inventory is to make migration decisions deliberately instead of allowing useful pages to disappear during development.
Step 3: Decide which pages to keep, improve, consolidate, or retire
Once the inventory is ready, determine what should happen to each important page.
There are five common options.
Keep the existing URL. If the page’s purpose remains the same and there is no compelling reason to change its address, retaining the URL can simplify the migration.
Update the page. Improve the content, design, metadata, usability, or technical implementation while keeping the page’s purpose and destination clear.
Consolidate overlapping content. If several pages genuinely cover the same subject, you may decide to combine them into a stronger replacement. The decision should reflect user needs and the actual relationship between the pages.
Redirect an old URL. If the page is moving to a relevant new destination, configure an appropriate redirect from the old address to the replacement.
Retire the page. If content is no longer needed and no suitable replacement exists, it may be appropriate to remove it and return a proper HTTP 404 or 410 response.
For legal websites, consolidation deserves particular attention. A general personal injury page, a car accident page, and a wrongful death page may serve different user needs. Combining them without evaluating their purposes can remove useful distinctions.
Similarly, avoid removing attorney biographies simply because the redesigned website has fewer profile templates. Review the content, its links, and its role before making the decision.
Step 4: Create an old-to-new URL mapping document
A redirect map is one of the most useful documents in a URL-changing migration. It tells the SEO, content, and development teams where each important existing URL should lead.
For every relevant URL, document the old address, intended destination, migration decision, and validation status.
For example:
| Existing URL | Proposed destination | Action |
| /personal-injury/ | /practice-areas/personal-injury/ | Redirect if this is the appropriate replacement |
| /attorneys/jane-doe/ | /attorneys/jane-doe/ | Retain the URL and validate the page |
| /blog/car-accident-guide/ | /resources/car-accident-guide/ | Redirect if the new page serves the same purpose |
| /outdated-resource/ | No replacement | Review whether to retire the page |
These are illustrative examples, not URLs from an actual client migration.
A useful mapping spreadsheet can also include current status codes, page titles, traffic data, backlinks, the reason for the change, and the person responsible for testing.
Follow these redirect principles:
- Redirect old URLs to their most relevant replacement destinations.
- Use server-side permanent redirects, commonly HTTP 301 or 308 responses, where technically appropriate.
- Avoid unnecessary redirect chains and loops.
- Do not send every retired URL to the homepage.
- Update internal links to point to the final destination directly.
- Test redirect behavior before launch and again on the live website.
An irrelevant redirect can confuse visitors and may be treated by search engines as a soft 404. When several pages have genuinely been consolidated into one appropriate replacement, however, redirecting those pages to the consolidated destination can make sense.
Step 5: Preserve valuable legal content and internal links
A migration can change more than URLs. Page content may be shortened, navigation may be reorganized, and links between related pages may disappear.
Before approving the new website, compare important pages with their existing versions.
Check that:
- Practice-area pages still explain the relevant legal services clearly.
- Attorney biographies retain accurate, approved professional information.
- Location pages represent genuine offices and relevant service areas.
- Useful legal guides and articles have not been removed without review.
- Page titles, headings, and descriptions remain appropriate to the content.
- Contextual internal links still connect relevant practice areas, attorneys, offices, and resources.
- Important images, PDFs, and other assets remain accessible.
- Consultation calls to action are still visible and functional.
A redesign is also an opportunity to improve outdated content, but changes should be deliberate. Do not copy old legal information unquestioningly simply because the page previously performed well. Any legal deadlines, eligibility requirements, statutes, or jurisdiction-specific explanations should be checked for current accuracy before being carried forward.
Internal linking deserves a separate review. A useful attorney profile may link to the person’s practice areas, while a legal guide may help visitors find the relevant service page. Those relationships should continue to work when the new site structure is introduced.
Step 6: Validate the technical SEO setup
Before launch, test the new website in an appropriate staging environment.
The objective is to identify implementation problems before the production website becomes the primary destination for visitors and search engines.
Crawlability and indexability
Check that intended production pages can be crawled and indexed. Review robots.txt, page-level robots directives, HTTP responses, and canonical tags.
Staging websites often use access controls or temporary indexing restrictions. Document how those restrictions will be handled at launch so they do not accidentally block the live site.
Canonical URLs
Canonical tags should reflect the intended preferred URLs. Review them when domains, URL paths, CMS templates, or page duplication rules change.
A new practice-area page should not accidentally point its canonical tag to an unrelated old URL.
XML sitemaps
Generate and validate the sitemap for the new website. It should reflect the intended canonical, indexable URLs rather than simply reproducing every historical address.
Submitting a sitemap can help search engines discover new URLs, especially on larger websites, but it does not guarantee that every URL will be indexed.
Internal links and status codes
Crawl the new website and check for broken internal links, unexpected redirects, server errors, and links that still point to obsolete URLs.
Pay attention to site navigation, breadcrumbs, attorney profiles, practice-area pages, and related-resource links.
Mobile experience and performance
Test priority page templates on mobile devices. Check navigation, page rendering, image loading, forms, and other important interactions.
Review performance and Core Web Vitals where relevant. A new design should not introduce avoidable problems that make the website slower or harder to use.
Structured data
If the old website uses structured data, verify that it remains accurate and appropriate after the migration. Do not carry forward outdated addresses, incorrect attorney information, or properties that no longer match the visible content.
Step 7: Test consultation forms and conversion tracking
A website migration can affect business outcomes even when search engines can access the new pages.
For a law firm, the most important conversion paths may include consultation forms, click-to-call links, online booking, and intake workflows.
Test these journeys from beginning to end.
Contact forms: Submit test enquiries and verify that the expected confirmation and notification processes work.
Telephone links: Confirm that mobile visitors can tap the correct telephone number.
Consultation bookings: Verify that booking links lead to the intended destination and that the journey remains functional.
Analytics: Check that existing analytics and configured conversion events continue to work after the migration.
Privacy and data handling: Ensure that measurement and testing follow the firm’s applicable privacy requirements. Do not place confidential client or case information into analytics events.
Also review the website’s external entry points. If URLs change, update important links from the firm’s verified business profiles, social profiles, advertising campaigns, and other relevant properties where feasible.
This step matters because organic traffic alone does not show whether the website is generating enquiries successfully.
Step 8: Plan the launch carefully
Once the new website has passed its staging checks, prepare a launch checklist with clear responsibilities.
Choose a launch window that allows the team to monitor the website and respond if something goes wrong. Where practical, avoid periods when the firm expects unusually high enquiry volume or has limited technical support.
For larger websites, a phased move may be an option. However, smaller or medium-sized sites that change URLs are generally easier to manage when their URL changes are coordinated rather than fragmented without a clear reason. The correct approach depends on the website’s size and technical setup.
Launch-day checklist
- Confirm that the production website is publicly accessible.
- Test a representative sample of high-priority URLs.
- Verify that redirects lead to the intended final destinations.
- Check for unexpected 404 and server errors.
- Confirm that important pages are not unintentionally blocked from indexing.
- Review production canonical URLs.
- Verify the new XML sitemap.
- Test internal navigation and important page links.
- Submit the new sitemap in Google Search Console where appropriate.
- Test consultation forms, telephone links, and booking pathways.
- Confirm that analytics and conversion tracking are working.
- Record any issues that need immediate attention.
For a move to a different domain or subdomain, verify the relevant old and new properties in Search Console. Google’s Change of Address tool applies to eligible domain moves; it is not required for every redesign, hosting change, or internal URL restructure.
Step 9: Monitor the new website after launch
The work does not end when the new website becomes available.
Search engines need to discover and process changed URLs. Google notes that for a medium-sized website, it can take a few weeks for most URLs to move in search, while larger websites may take longer. This is general guidance, not a guaranteed recovery schedule.
Organize post-launch monitoring into three stages.
Immediately after launch
Check availability, important redirects, status codes, canonical tags, indexability, and the functionality of important enquiry paths. Address widespread server errors or incorrect redirects promptly.
During the first week
Review Search Console for unexpected indexing problems, crawl errors, sitemap issues, and changes affecting priority pages. Re-test the areas that required corrections during launch.
During subsequent weeks
Compare search clicks, impressions, queries, and landing-page performance with the baseline. Check whether new URLs are appearing as expected, monitor changes to important practice-area pages, and review configured enquiry tracking.
For domain and URL migrations, keep the redirect map and old URL list available during monitoring. They help the team trace problems to specific implementation decisions.
Keep permanent redirects for as long as possible. For URL moves, maintaining them for at least a year is a useful general recommendation, while longer retention may benefit visitors and external links that still use the old addresses.
Step 10: Investigate traffic drops without jumping to conclusions
A decline in organic traffic after a migration deserves attention, but the timing alone does not prove that the migration caused it.
Start by identifying what has changed. Did clicks and impressions decline across the site, or only on a group of practice-area pages? Did rankings change, or did impressions remain stable while clicks fell? Did organic search decline while analytics tracking also stopped working?
Use the evidence to narrow the investigation.
| Observed issue | What to check first |
| Important pages disappear from search | Indexability, canonical tags, robots directives, and HTTP responses |
| Old URLs return errors | Redirect mapping, destination URLs, and server responses |
| One practice area loses traffic | Page content changes, redirects, internal links, and search performance |
| New URLs are not appearing as expected | Sitemap, crawlability, canonicalization, and internal discovery |
| Impressions remain similar but clicks fall | Search position, titles, snippets, and changes in search results |
| Analytics declines while Search Console appears stable | Analytics configuration, consent settings, and conversion events |
| Consultation enquiries fall | Forms, telephone links, booking journeys, and tracking |
Also consider other explanations, including seasonality, changes in user demand, and broader search-ranking changes. Comparing relevant date ranges and affected pages can help distinguish a migration defect from other causes.
Avoid making several major changes at once without documenting them. A focused investigation is more useful than repeatedly rewriting pages without knowing why performance changed.
Step 11: Avoid common migration mistakes
Even a visually polished website can underperform if key migration tasks are overlooked.
Redirecting every old page to the homepage. Redirects should lead to relevant replacement content. An unrelated destination is not a good substitute for a page that has been removed.
Deleting valuable legal pages without an audit. Review practice-area pages, attorney profiles, and resources before removing them.
Changing URLs unnecessarily. If an existing URL still suits the page’s purpose, retaining it may reduce the number of migration variables.
Leaving development restrictions on the production site. Recheck robots directives and indexing settings as part of launch QA.
Forgetting canonical tags and internal links. Confirm that the new site consistently uses the intended URLs.
Assuming the sitemap fixes every problem. A sitemap helps discovery but does not replace correct redirects, accessible pages, useful internal links, and appropriate canonical tags.
Stopping monitoring after launch. Keep a record of errors, fixes, and performance changes so the team can investigate issues as they appear.
Step 12: Document ownership, responsibilities, and completion
A migration checklist is only useful when someone is responsible for completing and validating each task.
For each item, record the responsible person, the expected outcome, the validation method, and whether follow-up is required.
A practical responsibility breakdown might look like this:
| Responsibility | Typical owner |
| Existing URL inventory and baseline | SEO team |
| Content decisions and attorney profile review | Firm marketing team and relevant approvers |
| Redirect implementation | Developer or hosting administrator |
| Technical staging checks | SEO and development teams |
| Legal content accuracy | Firm-approved legal reviewers |
| Forms and intake testing | Firm operations or intake team |
| Search Console and analytics monitoring | SEO or analytics team |
| Final issue prioritization | Project lead and relevant technical owners |
The exact allocation depends on the firm’s team and the agency or developer responsible for implementation. Some migration tasks require server or CMS access; others require approval from attorneys or the firm’s marketing team.
Before declaring the migration complete, verify that high-priority tasks have passed their checks, unresolved problems have named owners, and post-launch monitoring will continue.
Frequently asked questions
Will a law firm website migration affect rankings?
It can. Significant changes to URLs, content, internal links, canonicals, or indexability may affect organic visibility. Ranking fluctuations can occur as search engines recrawl and process changed pages. Careful planning can reduce avoidable errors, but no process guarantees unchanged rankings.
Should every old URL receive a 301 redirect?
No. Use a permanent redirect when an old URL has an appropriate replacement. Genuinely retired content without a suitable replacement may need a 404 or 410 response. Redirecting unrelated pages to the homepage is not a suitable default.
Does a law firm website redesign require SEO migration work if URLs remain unchanged?
A redesign with unchanged URLs may require less URL-mapping work, but it can still affect content, headings, internal links, structured data, mobile usability, performance, and conversion tracking. Review the actual changes rather than assuming an unchanged URL structure removes all SEO risk.
How long does it take Google to process a website migration?
There is no universal timeline. Google indicates that a medium-sized site can take a few weeks for most URLs to move in search, while larger websites may take longer. Processing depends on factors including the number of URLs and how efficiently search engines can crawl the new site.
What should we do if traffic falls after launch?
Compare Search Console data and analytics against the pre-migration baseline. Check affected URLs, redirects, indexability, canonicals, internal links, content changes, and tracking. Also assess other potential causes instead of assuming the migration explains every decline.
Can we improve SEO during a migration?
Yes. A migration can provide an opportunity to improve content, page structure, internal linking, technical issues, and the user experience. However, large changes should be documented and prioritized so the team can identify what may have influenced performance.
Final takeaway: Make migration an SEO project, not just a website launch
A law firm website migration requires more than publishing a new design. It involves decisions about important pages, URL destinations, redirects, legal content, technical settings, enquiry journeys, and post-launch measurement.
Start with a reliable baseline. Inventory valuable URLs. Decide which pages should remain, improve, consolidate, redirect, or retire. Validate the new website before launch, then monitor performance and investigate issues using evidence.
For firms planning a domain move, major redesign, CMS migration, or website consolidation, specialist support can help coordinate the SEO requirements with the technical implementation.
XSquareSEO provides technical SEO and related search optimization services for businesses across international markets. Begin with a review of the existing website to identify potential issues and determine which migration checks may be needed.
Request a free SEO audit or book a consultation.
For migration-specific support, link this guide to XSquareSEO’s dedicated Law Firm Website Migration SEO service page once that page is published.