Smotrów Design is a global design and technology company. Our commitment
- office@smotrow.com
- Smotrow Signature
- Smotrów Related
- Local time: 2:22 PM
Smotrów Design is a global design and technology company. Our commitment
A technical guide to SEO migration for law firm websites - from migration audit and URL mapping to structured data transfer.
A law firm website redesign should make things better - better design, better architecture, better performance, better search visibility. But for many firms, the opposite happens. The new website launches, and within weeks, organic traffic drops by 30%, 50%, sometimes 80%. Pages that ranked on the first page of Google for practice-specific keywords disappear from search results entirely. Inquiries through the website slow to a trickle. The firm that invested months and significant budget in a new website finds itself less visible than before the project started.
It is the most common outcome of law firm website redesigns that treat SEO migration as an afterthought. And it is almost entirely preventable.
At Smotrów Design, we approach migration as an integral part of every redesign project - not a checklist item for the final week, but a parallel workstream that runs from the first content audit through post-launch monitoring. We touched on this briefly in our guide on when and how to approach a law firm website redesign. This article goes deeper into the technical process.
This article is part of our series on designing websites for law firms, which includes guides on five key elements of a law firm website, homepage content, attorney profile pages, practice area pages, contact page design, photography, website SEO, CRM integration, website technology, lead generation, publications and insights, GEO and AI visibility, how to choose a website design agency, international law firm websites, the About page, and when to approach a redesign.
Most migration failures share the same root cause: the redesign team and the SEO process operate independently. The designers and developers build a new site with new URLs, new page structures, and new content - and someone (often an external SEO consultant, often brought in too late) is asked to "handle the redirects" in the final days before launch.
By that point, the damage is structural. URLs have already changed without mapping to the old ones. Content has been rewritten without preserving the keywords that drove traffic. Internal linking architecture has been rebuilt without considering the link equity that the old structure distributed. Structured data has been dropped entirely because the new templates were built without it. The result is a website that looks better but performs worse - sometimes catastrophically worse.
The most common cause of migration failure is treating SEO as a separate task from the redesign itself.
For law firms specifically, the stakes are higher than for most businesses. A corporate law firm's website may have spent years building authority for practice-specific keywords - "M&A law firm Kyiv," "banking regulation legal advice," "cross-border dispute resolution." These rankings represent a direct pipeline to prospective clients. Losing them means losing business - not temporarily, but for months while the new site rebuilds authority that the old site had already earned.
Not every website change is a migration. Understanding the distinction helps calibrate the level of planning required.
The design changes but the URL structure, content, and CMS remain the same. This is the lowest-risk scenario. Migration planning is minimal - but page speed, heading structure, and internal linking should still be verified.
Moving from one content management system to another - WordPress to Strapi, or a legacy CMS to a modern headless platform. URLs almost always change. Content models change. Template rendering changes. This is a high-risk migration that requires comprehensive planning. As we discussed in our guide to website technology, the technology choice affects everything from URL generation to schema markup to server-side rendering.
Practice areas are reorganized, page hierarchies change, content is consolidated or expanded. Even if the CMS stays the same, this changes the URL structure and internal linking patterns. High-risk.
Moving from one domain to another (firm.ua to firm.com, or after a merger). The highest-risk migration type. Google must reassess domain-level trust entirely.
Technically a site-wide URL change. Lower risk if handled correctly, but still requires redirect mapping for every URL.
Most law firm redesign projects involve at least two of these simultaneously - typically a CMS migration combined with an information architecture overhaul. This is where the complexity multiplies.
Before anything is designed or built, the migration team must establish a complete picture of the current site's search performance. This audit serves two purposes: it identifies the assets that must be protected (the pages, keywords, and links that generate the most value), and it creates the benchmark against which post-migration performance will be measured.
Export the following from Google Search Console for the past twelve months: every page that has received at least one click from organic search, with total clicks, impressions, average position, and top queries for each. Export from Google Analytics: traffic by page, conversion events by page (form submissions, phone clicks, consultation bookings), and user behavior metrics (engagement time, pages per session). This data tells you which pages matter most to the business - not which pages the firm thinks are important, but which pages actually generate traffic and inquiries.
Crawl the entire current site using a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit. The output is a complete list of every URL on the site, with status codes, canonical tags, meta data, heading structure, internal links, and response times. This inventory becomes the foundation of the redirect map.
Export the site's backlink profile from Ahrefs, Moz, or Google Search Console. Identify which pages receive the most external links - these are the pages with the most accumulated authority. If a page with 50 quality backlinks is deleted without a redirect during the redesign, that authority evaporates. For law firm websites, the pages with the strongest backlink profiles are typically the homepage, key practice area pages, high-profile attorney profiles, and publications that have been cited by media or legal directories.
Document all existing schema markup - Organization, LegalService, Person, Article, LocalBusiness, FAQPage. As we covered in our guide to law firm website SEO and GEO guide, structured data is critical for both traditional search and AI visibility. If the old site has structured data that the new site does not replicate, the firm loses visibility signals that took years to build.
From all of the above, compile a protected assets list - the pages that absolutely cannot be lost during migration. For a typical mid-sized law firm, this includes the homepage, all practice area pages, senior attorney profiles, the top 20-30 publications by traffic, the contact page, and the About page. Every page on this list must have a direct, one-to-one redirect mapped before the new site launches.
This phase runs parallel to the design process. While the design team works on visual concepts, the migration team works on the structural mapping between old and new.
Every URL on the old site must be mapped to a corresponding URL on the new site. This is the most important technical artifact of the entire migration. The map should include: old URL, new URL, redirect type (301 permanent in nearly all cases), the reason for any URL change, and a flag for protected assets.
For law firm websites, common URL changes include practice area path restructuring (/services/corporate-ma becomes /practices/corporate-and-ma), attorney profile path changes (/team/john-smith becomes /professionals/john-smith), and publication path changes (/news/article-title becomes /insights/article-title). Every one of these changes requires a 301 redirect.
Not all content from the old site will exist on the new site in the same form. Practice areas may be reorganized - two separate pages might be combined, or one page might be split into several. The content mapping document tracks these changes and ensures that no valuable content is lost in the restructuring.
The new site's internal linking architecture should be planned before development begins. As we described throughout our series - from homepage content to practice area pages to attorney profiles to publications - every page should be connected to related pages through meaningful links. The new architecture should preserve (and ideally strengthen) the link equity distribution that the old site had built.
During development, the migration requirements are built into the new site - not added after.
All 301 redirects from the URL map are implemented in the server or framework configuration. For modern frameworks like Next.js, redirects are typically configured in the application's routing layer - which means they are version-controlled, testable, and deployed alongside the code. For WordPress, redirects may be managed through plugins (Redirection, Yoast) or server configuration (.htaccess) - which is less controlled and more prone to errors.
Critical rules for redirects: every redirect must point directly to the final URL (no chains - A redirects to B which redirects to C), every old URL must return a 301 status (not a 302 temporary redirect), and internal links in the new site must point to the new URLs directly (not relying on redirects for internal navigation).
The new site must include all structured data types that the old site had - and ideally more. As we covered in our guide to GEO, structured data is generated programmatically in modern frameworks - every new page automatically receives the correct schema based on its content type. This is one of the key advantages of building on a headless CMS: the structured data is derived from the content model itself, not manually added per page.
Title tags, meta descriptions, and heading structures from the old site should be preserved where they are performing well (driving traffic for target keywords) and updated where they need improvement. Never discard meta data entirely and start from scratch - this is one of the most common causes of post-migration ranking drops.
Before the new site goes live, test it thoroughly in a staging environment. Verify that all redirects work correctly and return 301 status codes, all pages return 200 status codes with correct canonical tags, structured data validates without errors (use Google's Rich Results Test), internal links point to new URLs directly (not through redirects), meta data matches the planned values, robots.txt does not block any pages that should be indexed, and the XML sitemap includes all new URLs and excludes old ones.
One critical check: ensure that the staging environment blocks indexing (via robots.txt or meta robots noindex) and that these blocks are removed before launch. A surprising number of migration failures are caused by staging-environment noindex tags leaking into production.
The launch itself should be a controlled event - not a gradual rollout.
Switch DNS or deploy the new site to production. Verify that all redirects are working in the production environment. Remove any staging-environment indexing blocks. Submit the new XML sitemap to Google Search Console. Request indexing of all protected asset pages. Verify that Google Search Console shows no coverage errors. Monitor for any 404 errors in real time during the first 24 hours.
Submitting the new sitemap is essential - it tells Google that the site structure has changed and provides a complete list of new URLs to crawl. For domain changes, use Google Search Console's Change of Address tool. For CMS migrations and architecture changes on the same domain, the new sitemap is usually sufficient.
Migration is not complete at launch. It is complete when the new site's search performance matches or exceeds the old site's performance - which typically takes four to twelve weeks for a well-executed migration.
Monitor Google Search Console daily. Check for coverage errors (404s, redirect errors, noindex pages that should be indexed). Check that Google is crawling and indexing the new URLs. Watch for any sudden drops in impressions for protected asset pages.
Compare impressions and clicks for key pages and queries against the pre-migration baseline. Some fluctuation is normal - Google is re-evaluating the site's content and structure. Significant drops (more than 30% for a protected asset) should be investigated immediately.
By this point, the site should be approaching or exceeding pre-migration performance levels. If it is not, the most common causes are missing redirects for pages with significant backlinks, redirect chains that dilute authority, missing or incorrect structured data, internal links that still point to old URLs (through redirects rather than directly), and canonical tag errors.
A well-executed migration should show recovery to pre-migration levels within four to eight weeks. If recovery takes longer than twelve weeks, there is likely a technical issue that needs to be identified and resolved.
This is the argument at the center of this article. Migration is not a task that should be outsourced to a separate SEO consultant after the new site is built. It must be integrated into the design and development process from day one.
The agency that designs the information architecture determines the new URL structure. The developers who build the templates determine how structured data is generated. The content strategists who plan the new pages determine how old content is mapped to new content. The engineers who configure the server determine how redirects are implemented. Every decision that affects migration is made by the team building the new site.
When choosing an agency for a law firm website redesign, ask how they handle SEO migration. If the answer is "we work with your SEO consultant" or "we can recommend someone" - that is a red flag. The agency should be able to describe a comprehensive migration process that is built into their project workflow, not bolted on as an optional extra.
The single most common and most damaging mistake. Without a complete redirect map, old URLs return 404 errors, and every backlink pointing to those URLs loses its value. For a law firm with years of accumulated backlinks from legal directories, media mentions, and bar association profiles, this can destroy the site's domain authority.
URL A redirects to URL B, which redirects to URL C. Each hop in the chain dilutes the authority transfer and adds latency. After two or three hops, Google may stop following the chain entirely. Every redirect should point directly to the final destination.
The old site had Organization schema, Person schema for attorneys, and Article schema for publications. The new site launches without any of it. Google's Knowledge Panel disappears. Rich results vanish. AI systems can no longer identify the firm as a structured entity. This is particularly damaging for GEO - AI visibility depends heavily on structured data.
The staging environment had robots.txt rules blocking all crawlers. Those rules were copied to production. Google cannot crawl the new site. Rankings collapse. This is a five-minute fix - but if not caught immediately, the damage accumulates daily.
The new site's navigation points to new URLs, but hundreds of internal links within content (in publications, practice area descriptions, attorney profiles) still point to old URLs. These links work because redirects catch them - but every internal redirect is a missed opportunity for direct link equity transfer and a signal to Google that the site's internal architecture is not fully resolved.
A law firm website migration is not a technical footnote at the end of a redesign project. It is the mechanism that determines whether the new site inherits the old site's search authority or starts from zero. Every URL mapped, every redirect implemented, every piece of structured data transferred, every internal link updated - these are the details that separate a redesign that strengthens the firm's digital presence from one that undermines it.
The technology stack matters: modern frameworks handle redirects, structured data, and rendering in ways that minimize migration risk. The content architecture matters: a well-planned information architecture reduces the number of URL changes needed. And the agency matters most of all: the team that designs the new site must own the migration process from audit to recovery.
This article is part of our series on designing websites for law firms. For guidance on specific pages and elements, explore our guides on homepage content, practice area pages, attorney profile pages, contact page design, photography, website SEO, CRM integration, website technology, lead generation, publications and insights, GEO and AI visibility, how to choose a website design agency, international law firm websites, the About page, and when to approach a redesign. For a broader perspective, start with five key elements of a law firm website.
