Law Firm Website Migration Without Losing Rankings

Most law firms rebuild their website for the right reasons. The old theme looks dated, the site loads slowly on phones, the practice-area pages read like they were written in 2015, and the intake forms leak leads. The rebuild is justified. What is rarely justified is the ranking collapse that follows, the one where a firm that sat in the local pack for “car accident lawyer” wakes up on page three the week after launch and spends the next four months clawing back ground it already owned.

That collapse is not inevitable. It is the predictable result of treating a migration as a design project instead of a search-equity project. The pages ranked because Google had indexed specific URLs, learned what they were about, and accumulated authority signals pointed at those exact addresses. When a rebuild changes those addresses, strips the on-page structure, or quietly drops pages nobody remembered, the equity has nowhere to land. This is a walkthrough of how to move a law firm website without paying that tax, and where the Cube30 method forces the checkpoints that keep rankings stable through the cutover.

What actually gets lost during a migration

Rankings do not live in your homepage or your brand. They live at the URL level. Google indexed yourfirm.com/practice-areas/truck-accidents and associated a stack of signals with that specific string. Inbound links from a bar association directory point at it. Internal links from your blog point at it. The page has a crawl history, a click history, and a relevance profile built over years.

A migration puts four of those signal sources at risk at the same time.

• The URL itself. A new CMS or a new information architecture almost always changes URL paths. If /practice-areas/truck-accidents becomes /services/trucking-collisions and nothing connects the two, the old URL 404s and every signal pointed at it evaporates.
• The on-page content. Redesigns love to “simplify.” That often means a 1,400-word practice-area page that ranked gets replaced with a 300-word design showcase. The URL survived, but the relevance that earned the ranking did not.
• Internal link equity. A new template with a thinner footer and a stripped nav quietly removes dozens of internal links that were distributing authority to deep pages.
• Technical accessibility. A staging site left with a live noindex tag, a bloated new theme that tanks load speed, or a robots file that never got switched back to production can suppress the whole domain.

Every one of these is preventable. None of them prevents itself.

The redirect map is the whole game

If you take one thing from this, take this. A 301 redirect is a permanent server instruction that tells search engines and browsers that a URL has moved for good. Google treats a properly implemented 301 as the signal to transfer the old URL’s ranking equity to the new one and to update its index accordingly. Google has confirmed that 301 and 302 redirects both pass ranking signals, but a 301 is the correct instruction for a permanent move because it also gets the old URL swapped out of the index for the new one over time. For a migration, permanent is what you mean, so 301 is what you use.

The redirect map is the spreadsheet that pairs every old URL with its single best new destination. Building it well is unglamorous and it is where migrations are won or lost.

How to build a redirect map that holds

1. Crawl the full current site first. Before anyone touches the new build, generate a complete list of live, indexable URLs from a crawler and cross-reference it with your analytics and Search Console data. You are not just mapping the pages you remember. You are mapping every URL that has ever earned a click or a link, including that old blog post from 2019 that still pulls “statute of limitations personal injury” traffic.
2. Pull the pages that have links and traffic to the top. Sort by inbound links and organic entrances. These are your equity-bearing pages and they get one-to-one redirects to the closest matching new page. Never point a high-value old page at the homepage as a shortcut. A redirect to an irrelevant destination is treated by Google as a soft 404 and passes little to no equity.
3. Map one-to-one wherever a true equivalent exists. Old truck accident page goes to the new truck accident page. Match intent, not just topic. The closer the new page matches what the old page ranked for, the more cleanly the equity transfers.
4. Consolidate deliberately, not lazily. If you are merging three thin location pages into one, redirect all three to the survivor. That is legitimate consolidation. What is not legitimate is bulk-redirecting a hundred orphaned pages to a category page because mapping them individually was tedious.
5. Avoid redirect chains. If the site has old redirects already in place, a new migration can stack a redirect on top of a redirect on top of a redirect. Flatten every chain so each old URL points directly to its final destination in a single hop. Chains waste crawl budget and dilute the signal at each step.
6. Decide what to retire on purpose. Some pages should genuinely die. A page with no links, no traffic, and no strategic value can be allowed to 404 or return a 410. Make that a decision, not an accident.

Search Engine Land’s ongoing coverage of migrations and redirects reinforces the same principle that practitioners learn the hard way, which is that the redirect map has to be built against real crawl and analytics data rather than someone’s memory of the site. You can read their SEO guide for the broader technical framing, then apply it at the URL-by-URL level your firm’s site actually requires.

Phased cutover beats a big-bang launch

The riskiest migration is the one where a new site replaces the old one at midnight with a redirect list nobody stress-tested. A phased cutover trades drama for control.

The core idea is that you validate everything on a staging environment that search engines cannot see, then flip production in a controlled window, then verify aggressively in the hours and days after. The Cube30 approach treats the cutover as a sequence of gated checkpoints rather than a single event, and no gate opens until the prior one is verified.

The pre-launch gate

• Staging is fully blocked from indexing while it is being built, and that block is confirmed removed before launch. A staging noindex that survives into production is one of the most common and most damaging migration failures.
• The redirect map is loaded and tested in staging. Every old URL is checked to confirm it returns a single 301 to a live, indexable 200-status destination.
• Title tags, meta descriptions, heading structure, and body content for every equity-bearing page are carried over or improved, never thinned. This is where disciplined on-page work for practice-area pages protects the relevance that earned the ranking in the first place.
• Canonical tags point to the correct new URLs, XML sitemaps are regenerated to list only the new live URLs, and structured data for LegalService and Attorney entities is preserved.
• Internal links are updated to point at the new URLs directly, so authority flows through clean links rather than bouncing through redirects.

The launch window

Launch during your lowest-traffic window and keep the old site’s server reachable long enough for redirects to fire. The moment production is live, confirm the robots file allows crawling, confirm the sitemap is accessible, and submit it in Google Search Console. Do not wait for Google to stumble onto the new structure. Tell it directly.

The post-launch verification gate

The hours after launch are when problems are cheapest to fix. Run a fresh crawl of the live site and confirm there are no unexpected 404s, no redirect chains, and no orphaned pages. Watch Search Console coverage reports for a spike in errors. Spot-check your highest-value old URLs by hand to confirm each one lands on the right new page. A temporary ranking wobble in the first week or two is normal as Google recrawls and reprocesses the move. A sustained drop past that is a signal that something in the map or the technical setup is wrong and needs a same-week fix.

Common migration questions from law firm owners

Will we lose rankings even if we do everything right

You may see a short, shallow fluctuation while Google recrawls and re-evaluates the new URLs. That is the index catching up, not equity leaking away. Done correctly, most sites recover to their prior positions within a few weeks and many rebuilds end up ranking better because the new site is faster, cleaner, and more relevant than what it replaced. What you are preventing is the deep, months-long drop, and that one is entirely avoidable.

How long should we keep the redirects in place

Keep 301 redirects live permanently, or at minimum for a year after Google has fully processed the move and any external links have been updated. Removing them too early re-breaks the old URLs that still carry links. Redirects are cheap to keep. Removing them is where firms accidentally undo their own work.

Should we change our URLs at all if we do not have to

If your existing URLs are clean and descriptive, the safest migration keeps them exactly as they are. Every URL you preserve unchanged is a URL you never have to redirect and never risk. Only change URL structure when the new architecture is genuinely better for users and search, and when it does change, map every single one.

What about our Google Business Profile and local pack rankings

Your local pack presence is anchored to your Google Business Profile, not directly to your website URLs, so a website migration does not reset it the way it can reset organic rankings. The risk is indirect. If the website your profile links to slows down, drops relevant content, or starts returning errors, the local signals weaken over time. Keep the profile’s linked landing page fast and relevant through the cutover.

Where firms get burned and how to avoid it

The migrations that fail tend to fail for a small set of repeatable reasons. Redirects pointed at the homepage instead of the true equivalent page. Staging noindex tags that shipped to production. Content thinned in the name of a cleaner design. Redirect chains stacked from prior migrations. Internal links left pointing at dead URLs. Redirects torn down a month after launch because someone thought the job was finished.

Each of these is a decision, or a missed decision, not bad luck. A migration run as a search-equity project with gated checkpoints simply does not produce these outcomes, because each one is something a checkpoint is designed to catch before it reaches production.

Move the site, keep the rankings

A rebuild is one of the few moments where a law firm can either lock in years of accumulated search equity or throw a large share of it away in a single night. The difference is not luck and it is not the design agency’s front-end talent. It is a complete redirect map built against real data, a phased cutover with checkpoints that do not open until the prior one is verified, and disciplined post-launch monitoring while Google reprocesses the move.

If your firm is planning a redesign or a replatform, the time to protect your rankings is before the new site ships, not after the traffic drops. Our team runs migrations for law firms as an equity-preservation project first and a launch second. If you want the rebuild you already planned without the ranking risk that usually rides along with it, book a strategy call and we will map the safe path for your specific site. You can also see how we structure this work as a dedicated law firm SEO agency engagement built to hold rankings through change, not gamble with them.