Law firm growth
Law Firm Website Redesign: A Migration Checklist
Plan a law firm website redesign that preserves valuable URLs, search visibility, approved claims, accessible intake, tracking, and post-launch control.

Introduction
Editorial note: This guide covers website planning, marketing operations, and SEO. It is not legal advice. Attorney advertising, privacy, accessibility, records, and prospective-client obligations vary by jurisdiction. Have the appropriate attorney or compliance reviewer approve the finished site and intake process.
A law firm website redesign can improve trust, navigation, intake, accessibility, and search performance. It can also erase years of useful work in one launch.
The risk is rarely the new color palette. It is the quiet removal of a practice-area page that earns qualified calls, the change to an attorney biography URL with no redirect, the shorter form that sends sensitive information to the wrong system, or the mobile menu that hides the consultation path.
This guide treats a redesign as a controlled business and search migration. The visual system matters, but it sits inside a larger job: preserve what works, fix what does not, and prove the new site is ready before traffic reaches it.
Quick answer
A law firm website redesign should begin with an inventory, not a mockup.
Before design approval, document:
- Every current URL and its purpose
- Organic traffic, backlinks, calls, forms, and consultations by landing page
- Practice areas, locations, attorneys, and resources that must be preserved
- Claims, testimonials, results, badges, and disclaimers that require review
- Form destinations, CRM fields, booking tools, call tracking, and after-hours routing
- Accessibility, mobile, performance, analytics, and security requirements
Keep valuable URLs when possible. When a URL must change, map it to the closest relevant replacement and use a permanent server-side redirect. Do not send every retired page to the homepage.
Launch only after content, redirects, forms, tracking, mobile behavior, and legal review have passed a written acceptance checklist.
When a redesign is actually justified
A redesign is worth considering when the existing site creates a measurable operating problem.
Common triggers include:
- Prospective clients cannot quickly identify the right practice area or jurisdiction
- Attorney biographies are incomplete, outdated, or difficult to find
- Mobile visitors struggle to call, book, or submit a form
- The CMS prevents staff from maintaining attorneys, offices, or legal updates
- The site is slow, unstable, inaccessible, or difficult for search engines to crawl
- Intake data does not reach the right team or cannot be tied to qualified consultations
- The firm has changed its brand, practice mix, locations, or market position
- The URL structure has accumulated duplicate and abandoned pages
"The site looks old" can be a valid concern, but it is not a complete redesign brief. Translate the concern into tasks. For example: make provider identity clearer, reduce steps to consultation, preserve top organic pages, improve keyboard navigation, and let the internal team update biographies without developer support.
That turns taste into acceptance criteria.
Protect what already works
The first practical step is a preservation audit.
Export the current URL set from the CMS, XML sitemap, analytics, Search Console, and a crawler. These lists will not be identical. Combine them, remove duplicates, and classify each URL.
| URL decision | Use when | Required action |
|---|---|---|
| Keep | The page is useful and the URL still fits | Preserve the URL and improve the page in place |
| Merge | Several pages overlap and one stronger page can serve the intent | Consolidate useful material and redirect each retired URL |
| Replace | The topic remains necessary but the destination changes | Map the old URL to the closest new equivalent |
| Retire | The content is obsolete and has no useful replacement | Return an intentional 404 or 410 after checking links and traffic |
Record current titles, headings, copy, internal links, canonical tags, schema, image references, and conversion actions for high-value pages. A redesign team should know why a page matters before changing it.
Google's site-move guidance recommends preparing and testing the new site, creating an accurate URL map, and configuring redirects from old URLs to their new destinations.
Build the redesign inventory
The redesign inventory should cover more than pages.
Business inventory
- Current and planned practice areas
- Attorneys and support teams
- Offices, jurisdictions, and appointment methods
- Priority matters and referral relationships
- Consultation types, fees, and response expectations where approved
Content inventory
- Practice-area and sub-practice pages
- Attorney and staff biographies
- Office and location pages
- Results, representative matters, testimonials, and awards
- Articles, guides, videos, downloads, and media mentions
- Privacy notices, disclaimers, terms, and accessibility information
System inventory
- Contact and consultation forms
- Call tracking and recorded-line disclosures
- Scheduling tools
- CRM and email routing
- Chat and AI intake
- Analytics, advertising pixels, consent tools, and tag management
- Hosting, DNS, email, security, backups, and monitoring
Assign an owner to each system. A form is not complete because it submits successfully on a developer's screen. It is complete when the correct team receives it, the record is created accurately, the confirmation sets a realistic expectation, and a failed delivery produces an alert.
Redesign the information architecture first
The navigation should reflect how prospective clients identify their problem.
A typical law firm structure may include:
- Practice-area hub and focused matter pages
- Location or office hub and genuine location pages
- Attorney directory and individual biographies
- About, process, fees, or consultation information where appropriate
- Results or testimonials after jurisdiction-specific review
- Resources and legal guides
- Contact and consultation paths
Map each important visitor to the shortest useful route. Someone facing an arrest may need a prominent phone path and after-hours expectation. A business evaluating litigation counsel may need representative matters, industries, attorney depth, and a direct inquiry route.
Those are different journeys, even on the same site.
Use the broader website design for law firms guide when planning page requirements, attorney biographies, and intake UX.
Review content and claims during the build
A redesign often makes old claims more prominent. That creates a review obligation, not automatic approval.
Flag every:
- Case result and settlement amount
- Testimonial and review excerpt
- Award, badge, ranking, and membership
- Experience, specialization, and comparison claim
- Fee, free-consultation, availability, and response-time statement
- Office, jurisdiction, and service-area statement
ABA Model Rule 7.1 addresses false or misleading communications about a lawyer or the lawyer's services. The ABA rules are models; state rules and other applicable requirements control.
Maintain a claim register with the page, exact wording, support, reviewer, approval date, and review date. This is more reliable than asking one partner to review the site from memory the night before launch.
Rebuild intake and accessibility together
Contact design affects both conversion and risk.
The first form should usually collect only what the approved first step needs. Explain that submitting information does not necessarily create an attorney-client relationship, avoid inviting unnecessary confidential detail, and state what happens next.
ABA Model Rule 1.18 addresses duties to prospective clients. The comment explains that electronic communications can constitute a consultation depending on the circumstances and warnings presented.
Accessibility should be designed into:
- Heading structure and landmarks
- Keyboard navigation and visible focus
- Form labels, instructions, and error messages
- Contrast, zoom, readable text, and touch targets
- Alt text and captions
- Chat, cookie, booking, and call widgets
The US Department of Justice provides web accessibility guidance under the ADA. The firm's legal obligations depend on its facts and jurisdiction, but accessibility is also practical client service.
Create the migration plan
The migration plan should be a working document with owners and test results.
For each current URL, record:
- Current URL
- New URL
- Decision and reason
- Redirect status
- New title and canonical
- Internal links that need updating
- Owner and test result
Use permanent 301 or 308 redirects for permanent moves. Avoid redirect chains. Update internal links to point directly to final URLs rather than relying on redirects.
Preserve:
- Canonical URL signals
- Important page content and headings
- Structured data that remains accurate and visible
- Image URLs where practical
- XML sitemap coverage
- Analytics and Search Console access
- DNS, domain, and account ownership
Do not combine a domain move, CMS replacement, URL rewrite, content reduction, and visual redesign unless the business has a compelling reason and a strong migration team. Fewer simultaneous changes make problems easier to isolate.
Use a controlled launch sequence
A safer launch sequence looks like this:
- Freeze the approved content and URL map.
- Crawl and test the staging site while keeping it out of public indexing.
- Test forms, calls, booking, CRM creation, email delivery, and failure alerts.
- Test keyboard, mobile, browser, screen-size, and zoom behavior.
- Validate titles, canonicals, robots directives, schema, sitemaps, and redirects.
- Confirm analytics and conversion events with test submissions.
- Take a backup and document rollback responsibilities.
- Launch during a staffed monitoring window.
- Crawl old and new URLs immediately after deployment.
- Monitor Search Console, analytics, logs, calls, and forms daily during the initial period.
Google recommends responsive design and uses mobile content for indexing and ranking, as explained in its mobile-first indexing guidance.
Monitor business outcomes after launch
A redesign is not validated by a successful deployment.
Compare pre-launch and post-launch performance for:
- Indexed pages and crawl errors
- Organic clicks and impressions by landing page
- Rankings for priority practice and location queries
- Calls, forms, bookings, and chats
- Qualified consultations and retained matters where tracking permits
- Form delivery failures and response time
- Mobile conversion behavior
- Core Web Vitals and page performance
Google's published good Core Web Vitals thresholds are LCP within 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Use field data when available; a single laboratory test is not the whole user experience.
Expect normal fluctuation, but investigate sharp page-level losses, unexpected deindexing, redirect errors, and conversion drops quickly.
Questions to ask a redesign partner
Ask:
- How will you identify and preserve valuable URLs?
- Who owns the domain, code, content, analytics, and design files?
- Who creates and tests the redirect map?
- How will practice areas, offices, attorneys, and resources be migrated?
- How do you test forms and CRM routing end to end?
- How is accessibility tested beyond an automated scan?
- Who reviews attorney advertising claims and when?
- What performance targets and browser checks are included?
- What happens if traffic or lead delivery drops after launch?
- What maintenance and support follow deployment?
A proposal that spends pages describing visual inspiration but barely mentions content, redirects, intake, accessibility, and measurement is incomplete.
Common redesign mistakes
Starting with the homepage
The site architecture and content requirements should shape the homepage, not the reverse.
Rewriting every URL
Cleaner-looking URLs do not automatically justify the migration risk.
Sending retired pages to the homepage
Redirect each valuable URL to the closest relevant destination.
Approving only desktop mockups
Prospective clients and Google often encounter the mobile experience first.
Treating form submission as the finish line
Test routing, response ownership, CRM records, and failure handling.
Deleting useful content for a cleaner design
Reduce clutter, but preserve information that answers real client questions and earns qualified visibility.
Website modernization versus a full redesign
Not every dated firm website needs rebuilding. Modernization keeps the existing structure and fixes what actually dates a site: slow loading, layouts that break on a phone, contrast and focus states that fail accessibility checks, and forms nobody can complete one-handed. It is a smaller piece of work and it preserves every URL by definition.
A redesign is the right call when the structure itself is the problem. Practice areas buried three clicks deep, attorney pages that cannot be found from the page a visitor landed on, or an information architecture that grew by accretion as the firm added services. If people cannot locate the practice area they came for, modernization will not fix it.
The honest test is whether you would keep the current sitemap. If yes, modernize. If the sitemap is the thing you want to change, that is a redesign, and the migration planning in this guide applies.
UX decisions that change intake volume
Law firm UX work concentrates on the few moments that decide whether somebody makes contact. Whether the next step is visible without scrolling. Whether the contact form asks for three fields or eleven. Whether a person arriving at nine in the evening can do anything other than read a phone number. Whether the attorney they were referred to is reachable in one click from wherever they landed.
These are unglamorous and they move enquiry numbers more than any visual refresh. Accessibility belongs in the same category rather than a compliance appendix: keyboard navigation, visible focus indicators and sufficient contrast are usability decisions that happen to also be legal obligations.
FAQ
There is no responsible fixed schedule. Redesign when the site no longer supports the firm's services, users, technology, compliance review, accessibility, or measurement needs. Continuous maintenance can delay the need for a full rebuild.
It can if valuable pages, content, links, metadata, or URLs are lost. A well-managed redesign can preserve and improve performance, but rankings are never guaranteed.
Redirect URLs that moved and have a relevant replacement. Truly obsolete pages without a suitable destination may be better served with an intentional 404 or 410 than an irrelevant homepage redirect.
Keep important permanent redirects for the long term. External links, bookmarks, and old documents can continue sending visitors to legacy URLs well after launch.
Use named owners for brand, legal claims, privacy, accessibility, IT, intake, SEO, and final launch. One broad approval from a partner does not replace specialist checks.
Monitor crawling, indexing, priority landing pages, calls, forms, bookings, qualified consultations, response time, form failures, mobile behavior, and page performance.
References and source notes
These sources support the policy-sensitive and technical recommendations in this guide:
- Google Search Central: Site moves with URL changes
- Google Search Central: Mobile site and mobile-first indexing best practices
- Google Search Central: Core Web Vitals and Google Search results
- Google Search Central: Creating helpful, reliable, people-first content
- US Department of Justice: Guidance on Web Accessibility and the ADA
- American Bar Association: Model Rule 7.1
- American Bar Association: Model Rule 1.18
Next step
Luminous Digital Visions plans and develops law firm websites with migration, technical SEO, accessible intake, and measurement built into the project. Review our law firm website design service, law firm growth systems, and SEO for law firms guide. For the rebuild itself, our law firm website redesign service plans redirects and page ownership before launch.