Website Migration SEO Checklist for Law Firms

Arslan SEO Insights tells law firms that a website migration is safe only when every indexed URL has a specific, tested redirect in place before launch, not a generic pattern rule applied afterward. The biggest risk in any migration, whether it's a redesign, a new CMS, or a new URL structure, is losing rankings on practice area pages that took a year or more to build. Most of that damage is preventable with the right process, done in the right order, before the new site ever goes live.

We work exclusively with attorneys and law firms, and this checklist is written for that reality specifically, not adapted from a generic small-business migration guide.

A website migration is one of the highest-risk moments in a law firm's search history. It could be a redesign, a new CMS, a new URL structure, or all three at once. Rankings that took a year or more to build on a specific practice area page can disappear within days if the migration is handled carelessly. Most of that damage is avoidable. It comes down to following the right process in the right order, not luck.

This page covers migration SEO specifically. For the full picture of how it fits into a law firm's technical foundation, see our technical SEO for law firms overview.

Why Law Firm Migrations Carry More Risk Than Most

A law firm site is usually made up of dozens or hundreds of practice area and city combination pages, each one built to rank for a specific case type in a specific location. That structure is what makes law firm sites valuable, and it's also what makes migrations dangerous. A generic business site might have twenty pages total. A firm covering ten practice areas across eight cities could have close to a hundred URLs that each earned their own rankings independently. A redirect plan that works for a small brochure site simply does not scale to that structure. Every one of those URLs needs its own decision, not a folder-level rule.

Attorney bio pages add another layer of risk that most migration guides never mention. Bio pages carry schema markup connecting the attorney to the firm, to their bar admissions, and to their credentials. That structured data reinforces the experience and expertise signals Google looks for on legal content, sometimes called E-E-A-T (experience, expertise, authoritativeness, and trust). A new CMS template that looks nicer but wasn't built with the same schema in mind will quietly drop that markup, and nothing on the page will visibly signal that the loss happened.

Before the Migration

The work that happens before launch determines whether the migration succeeds or quietly destroys months of ranking equity.

• Crawl and export the entire current site. Every practice area page, every city page, every attorney bio page, every blog post. Record current rankings and traffic for each one. This is the baseline you will compare against after launch, and without it you cannot tell what broke.
• Build a URL-by-URL redirect map. Not a generic pattern rule like "redirect everything to the homepage" or "strip the old folder structure and hope it matches." Every single indexed URL needs a specific, deliberate destination. A practice area page that ranks well deserves a redirect to its exact new equivalent, not a general category page.
• Audit what content actually drives rankings on each page, not just the page title. A "cleaner" redesign often strips word count, removes FAQ sections, or flattens practice area depth in favor of a shorter, more visual layout. If the new page has half the real content of the old one, expect to lose most of the ranking that content earned.
• Check attorney bio page schema and credentials before migration, not after. Person schema connected to Organization schema, bar admission data, and credential markup are easy to lose in a CMS migration if the new template was not built with the same structured data in mind. A bio page that quietly loses its schema does not throw an error. It just stops reinforcing the E-E-A-T signals it used to carry.
• Confirm the new site's technical basics are correct before launch, not discovered after: robots.txt is not accidentally blocking the whole site, the XML sitemap reflects the new URL structure, canonical tags point to the right pages, and Core Web Vitals scores are not worse than the old site. Google's own site move documentation covers the technical requirements for a URL change in detail and is worth reviewing before a large migration.
• Freeze new content and structural changes for a short window before launch. Publishing new practice area pages or changing navigation structure in the two or three weeks before a migration makes it harder to tell what changed rankings after launch, the migration itself or the last-minute edits.
• Get a written sign-off from whoever built the redirect map, confirming every URL on the pre-migration crawl has a mapped destination. A spreadsheet with gaps is how a handful of high-value pages get missed in a migration covering a hundred or more URLs.

During the Migration

• Turn on redirects the moment the new site goes live. Not later that day, not "once we confirm everything looks right." Every hour a ranking practice area page has no redirect is an hour of lost equity and a bad experience for anyone who clicks an old link.
• Submit the updated XML sitemap in Search Console immediately after launch, so Google has a clear map of the new structure to crawl against.
• Do not launch at a time nobody can monitor. A Friday afternoon launch with no one watching Search Console over the weekend is how a small redirect gap turns into a real ranking loss before anyone notices.
• Spot-check the highest-traffic pages first, within minutes of launch, not hours. The five or ten pages that bring in the most organic traffic and case inquiries should be the first thing anyone checks once the new site is live, before moving on to a full audit of every URL.
• Keep the old site's DNS and hosting active for a short window after launch, in case a rollback is needed. A migration that can't be reversed quickly turns a fixable mistake into an extended outage.

After the Migration

| Timeframe | What to check | Why it matters | |---|---|---| | Daily, first 2 weeks | Search Console coverage report, crawl errors, indexing status | Catches redirect failures and blocked pages while they are still cheap to fix | | Daily, first 2 weeks | Rankings on top practice area and city terms | A sudden drop on a specific page usually points to a specific broken redirect or lost content | | Weekly, first 2 months | Redirect chains and error pages | Redirects that chain through multiple hops or dead-end in a 404 lose value with every extra hop | | Weekly, first 2 months | Backlink profile against the pre-migration list | Confirms external sites linking to old URLs are landing on a working redirect, not a dead page | | Ongoing | Traffic and rankings vs. pre-migration baseline, page by page | Confirms the migration held, not just that the site looks fine |

Testing redirects means actually clicking through a sample of them, not just trusting that a bulk redirect rule was applied correctly. A single misconfigured rule can silently break dozens of URLs at once. It's worth testing redirects from a few different entry points too: a direct URL visit, a click from an old bookmark, and a click from an external site that still links to the old address, since some redirect configurations behave differently depending on how the request arrives.

The Most Common Migration Mistake

The single most common failure is a missing or incorrect redirect on a page that used to rank well. For a law firm, that is often a specific practice area or case-type page that took a year or more to build authority through content depth and internal links. When this happens across several pages at once, which is common when a redirect map is built from generic rules instead of URL by URL, the losses compound fast and can take months to recover, if they recover at all.

The second most common mistake is content loss disguised as a redesign. A new template that looks cleaner but removes the FAQ section, shortens the body content, or drops the internal links that used to point authority toward that page will underperform the old version even with a perfect redirect in place.

A third mistake worth naming directly: redirecting every old URL to the homepage instead of its true equivalent. This is sometimes suggested as a "safe" fallback when a team runs out of time to build the full map. It is not safe. A homepage redirect tells Google the specific page is gone and its content lives nowhere else, which is close to the worst possible signal for a page that used to rank on its own merit.

An Illustrative Scenario

Consider a firm migrating from an older WordPress theme to a new custom build, done by a web design agency with no SEO involvement. The agency builds a beautiful new site and redirects the homepage and a handful of top-level pages, assuming that covers the essentials.

Within three weeks, six practice area pages that used to rank on page one are gone from the results entirely. Each one had a unique URL under the old structure that the new site simply does not have, and there is no redirect for any of them. The fix is not a bigger design budget. It is going back to the pre-migration crawl, building the specific redirect for each of those six pages, and giving Google time to recrawl and recover the lost equity. This is exactly the kind of damage a URL-by-URL redirect map, built before launch, prevents in the first place.

A second scenario is worth mentioning because it's just as common: a firm switches URL structures on purpose, for example moving from `/practice-areas/car-accidents/` to `/car-accident-lawyer/`, believing the new structure reads better for users. The URL change itself isn't the problem. The problem shows up when the redirect map treats this as a simple find-and-replace across every page, without checking that each old URL actually has a live match in the new structure. Pages that don't fit the pattern cleanly get missed, and they're often the ones with the most ranking history because they were built earliest.

Coordinating With Everyone Involved

A law firm migration usually involves more people than a typical business site change: the marketing team or agency, a web developer or design firm, sometimes an IT contractor managing hosting and DNS, and often the firm's own staff who will need to update internal materials that link to the old site. Each of these people needs to know their specific role in the migration timeline, not just a general heads-up that "the new site is launching soon."

The developer needs the full redirect map in the exact format their platform requires, delivered with enough lead time to implement and test it before launch day. The SEO team, whether in-house or an outside partner like an agency, needs write access to Search Console and analytics from day one, not added after something already looks wrong. Anyone managing paid search campaigns needs to know the new URL structure in advance too, since landing pages tied to active ad campaigns can't afford to break even for a few hours.

It also helps to set a single point of contact for the migration itself, someone who owns the checklist and confirms each step is complete before the next one starts. Migrations that go wrong often trace back to an assumption that someone else was handling redirects, or that the developer's "standard process" already covered SEO requirements when it didn't. A five-minute conversation confirming who owns the redirect map, before development starts, prevents most of these gaps.

Special Considerations for Multi-Location Firms

A firm with several office locations, or one that has built out separate pages for a metro area and its surrounding suburbs, has more at stake in a migration than a single-location practice. Each city or location page usually carries its own local relevance signals, sometimes tied to Google Business Profile listings, local schema, or NAP (name, address, phone number) data specific to that office. A migration that consolidates several city pages into one broader regional page, without accounting for the individual ranking history each page built, will almost always underperform the combined total of the pages it replaced.

If consolidation is genuinely the right call, for example because two nearby city pages were targeting nearly identical intent and competing with each other for the same rankings, that decision should be made deliberately before the migration, with a plan for which page survives and gets the traffic redirected to it. It should not happen as a side effect of a template redesign that didn't preserve the original page count.

Frequently Asked Questions

How long does it take to recover rankings lost in a botched migration?

It varies by how much authority the page had and how long it stayed unredirected, but recovery typically takes weeks to a few months once the correct redirects are in place. Some ranking loss from an extended gap may never fully recover, which is why getting the redirect map right before launch matters more than fixing it after.

Can a general web design agency handle SEO during a migration safely?

Only if SEO is explicitly part of the process, not an afterthought. A design agency focused on visual output has no natural reason to prioritize a complete redirect map or preserve content depth on practice area pages, since those are not design concerns. This is one of the most common sources of post-migration ranking loss for law firms.

Does changing CMS platforms (for example, moving off WordPress) carry extra risk?

Yes. A platform change often means the URL structure, schema implementation, and even basic technical settings like canonical tags have to be rebuilt from scratch rather than carried over. Every one of those needs to be checked against the old site's setup, not assumed to work the same way by default.

Should a firm migrate all practice area pages at once, or in phases?

Migrating everything at once, with a complete redirect map ready before launch, is almost always safer than a phased rollout. A phased migration means running two site structures at once, which increases the chance of confusing duplicate content signals and makes the redirect map harder to manage correctly.

Do internal links need to be updated after a migration, or is a redirect enough?

A redirect prevents a broken link from failing outright, but it isn't a full substitute for updating internal links to point directly at the new URLs. Every extra redirect hop a crawler and a user have to pass through adds a small amount of friction and dilutes some of the value passed between pages. After the redirect map is live and stable, going back through the site's internal links and pointing them straight at the new addresses is a worthwhile cleanup step.

What is the single most important thing to get right in a migration?

The redirect map. Nearly every serious migration-related ranking loss traces back to a missing or incorrect redirect on a page that used to earn real traffic. Everything else on this checklist supports that one priority.

Related Reading

This page connects to the broader technical foundation covered in technical SEO for law firms. For the CMS side of a migration, see technical SEO for WordPress. For how a large, migrated site should be structured so crawl budget targets the right pages, see crawl budget optimization for law firms, and for the page experience signals a new site needs to hit, see Core Web Vitals for law firms. If rankings have already dropped since a recent redesign or migration, see why SEO rankings drop after a website redesign for how to diagnose and recover.

Schedule Your Law Firm Technical SEO Audit

If a migration is coming up for your firm's site, get a free SEO audit or get in touch before you launch, not after something breaks. A pre-migration audit is far cheaper than a post-migration recovery.