A redesign brief usually lists everything the site should look like. It rarely lists everything the migration needs to protect. This post is the checklist for the second list.
Why a redesign can lose rankings is covered in detail elsewhere. This post assumes that part and moves straight to the practical question: what does a redesign brief actually need to include, beyond the visual direction, to avoid finding out the hard way.
Before the build starts
A law firm website design project needs an inventory of the current site before anyone touches the new one. That inventory covers every existing URL, its current ranking position, its inbound links, and a mapped destination on the new site. Skipping this step is the single biggest cause of the ranking loss covered in why redesigns lose rankings, and it has to happen before design work starts, not after.
The same inventory should flag which pages carry the firm’s most specific content: detailed practice-area explanations, FAQ pages answering exact client questions, anything with genuine depth. Those are the pages most at risk of being flattened into shorter, more general copy during a redesign, and they’re worth marking for protection early.
A rollback plan belongs in this stage too, not as an afterthought.1 The new site gets built and tested on a staging environment with restricted access, checked thoroughly there, and the plan for reverting to the old site stays documented and ready in case something breaks after launch. A migration with no way back turns a fixable problem into a genuine crisis.
During the build
Redirects are one line item on a longer technical list, not the whole list. A complete pre-launch technical checklist covers:
Redirect mapping. Every old URL pointed to its exact new equivalent, not to a generic category page or the homepage. A firm’s specific “unfair dismissal” page redirecting to a broad “employment law” page loses everything the specific page had earned.
Schema markup carried across. Structured data identifying the firm, its services, and its practice areas needs rebuilding on the new site, not assumed to transfer automatically with a template change.
Meta titles and descriptions audited, not regenerated by default. Many website builders auto-generate these from page content. A title that took months to refine for a specific search term can get silently overwritten unless someone checks.
Accessibility carried forward. Colour contrast, alt text on images, and keyboard navigation are compliance considerations independent of SEO, and a visual refresh can break all three without anyone noticing until a user reports it.
Mobile performance tested on the actual new build, not assumed from how the previous site performed. A heavier template can quietly regress the loading and responsiveness metrics search engines use as part of how a site is evaluated. Specific usability details matter here too: phone numbers clickable on every page, and enquiry forms usable one-handed on a phone, since a redesign can pass a desktop review and still fail the exact conditions a prospective client is searching under.
Compliance carried across as carefully as the copy itself. Ad copy, testimonials, and specialisation claims written for the old site often get lifted straight into the new one. A redesign is a natural point to check that content still holds up against current advertising rules, since the words don’t become compliant again just because the template around them changed. This connects directly to the obligations covered in what Rule 36 means for the words published under your name.
Analytics and conversion tracking reconnected before launch, not after. A site that goes live without tracking in place loses visibility into its own first weeks of performance, which is exactly when problems are cheapest to catch.
After launch
The technical work continues after launch. The weeks immediately after are when problems are still cheap to fix and easy to miss without deliberately checking. That means watching for crawl errors, confirming redirects resolve directly with a single hop, and comparing organic traffic and rankings against the pre-launch baseline on a fixed schedule.
One check specific to the current search environment is easy to miss because it’s newer than most checklists: confirming AI crawlers can still access the site after launch.2 A new robots.txt file, a WAF rule carried over from the old server, or a forgotten llms.txt update can quietly block ChatGPT-User, ClaudeBot, or PerplexityBot even while the site works perfectly for a human visitor and for Googlebot. This is worth its own line item precisely because it produces no visible symptom on the site itself.
None of these items are complicated individually. What’s usually missing is a single document that lists them all against a single project, so nothing depends on someone remembering.
If a redesign is being scoped and this list is missing from the brief, request a pre-launch technical review. Adding it before the build starts costs far less than adding it after.
Frequently asked
What’s the most commonly missed item in a website redesign checklist?
Redirect mapping for the full long tail of specific content pages, beyond the handful of main pages firms usually remember. Those specific pages are often the ones quietly earning rankings on their own, and they’re the easiest to overlook.
Does schema markup transfer automatically when a website is redesigned?
No. Structured data is typically tied to the specific template or plugin configuration in use, so a new design usually needs schema markup rebuilt from scratch.
How soon after launch should a redesigned site be checked for problems?
Immediately, and then on a fixed schedule for the following weeks. Crawl errors, broken redirects, and ranking movements are cheapest to fix in the first few weeks, before search engines have fully processed the change.
Does old website copy need to be reviewed for compliance during a redesign?
Yes. Ad copy, testimonials, and specialisation claims carried over from the old site aren’t automatically compliant just because the design around them changed. A redesign is a practical point to check that content against current advertising rules before it goes live again.
Should a law firm have a rollback plan before launching a redesigned website?
Yes. Building and testing the new site on a staging environment first, with a documented plan for reverting to the old site if something breaks, keeps a launch problem fixable and manageable, well before it becomes a crisis discovered in production.
Can a redesign accidentally block AI crawlers like ChatGPT or Claude from accessing the site?
Yes, and it often produces no visible symptom. A new robots.txt file, a carried-over WAF rule, or an outdated llms.txt can block AI crawlers while the site works normally for human visitors and for Google, so this needs a specific check on its own, separate from confirming the site looks fine.
This post is for informational purposes only and reflects general website migration practice. It does not describe any specific client’s website or project. Current as at 10 October 2026.
References
1. Aleyda Solis, Orainti, SEO Guides, Checklists and Tools For Web Migrations; and Patrick Stox, Ahrefs, A Website Migration Takes More Than A Checklist To Be Successful. Both treat staged validation on a restricted-access environment and a documented rollback plan as standard migration practice. ↩
2. Not a third-party citation. Grounded in Felicity Jane Digital’s own operational history: the VentraIP server migration and ongoing ClaudeBot/WAF crawler-accessibility investigation confirmed this as a real, recurring risk during infrastructure changes. ↩
Jane Cluff is the founder of Felicity Jane Digital, a legal SEO agency for Queensland law firms. She studied psychology and urban and regional planning, and has worked in digital marketing since 2014.