What to prepare for a law firm website redesign

Choose the practice areas the new site needs to explain. For each, note who you help, the work you handle, and the appropriate next step. Keep attorney biographies, admissions, and office information accurate.

Set aside claims that need evidence or approval. California Rule 7.1 prohibits false or misleading communications; its commentary addresses results and testimonials that could create unjustified expectations. Business and Professions Code § 6157.2 also addresses award references and advertiser/office disclosures. Ask your firm's attorney to review the applicable requirements and approve the final wording.

Gather approved photographs, logo files, and permission for any client material you intend to publish. A website partner can help edit and organize the content; your firm remains responsible for approving its legal claims.

Write down the path from a visitor's first question to your team's response. Which fields are needed? Who receives the message? Who checks it? What happens if delivery fails or the usual reviewer is away?

Have your attorney approve the intake instructions and confidentiality wording. California Rule 1.18 protects certain information learned in a prospective-client consultation even when representation does not follow. Its application depends on the circumstances; do not treat a generic website notice as a complete intake policy.

In our Aloha Florals 808 project, wedding and lei inquiries ask different questions. That is an example from another industry of matching the form to the work behind it. For your firm, agree on the tools, permissions, third-party fees, and end-to-end delivery checks before adding an integration. Use test data for those checks.

Before replacing a site, collect its important URLs and review the content they contain. Use available analytics, Search Console information, and referral links to identify pages worth preserving. If you do not have that access, say so at the start.

If URLs change, agree on a map from old pages to relevant replacements and check those redirects after launch. Google recommends permanent redirects for site moves and warns against sending unrelated old pages to the homepage. Also agree who checks the sitemap and indexing settings.

This helps make the transition deliberate. It does not guarantee rankings or inquiry volume; ongoing SEO and content work need their own scope.

List the domain registrar, hosting, website editor, email provider, analytics, and any intake or scheduling tools. Record the account owner, billing contact, and the person who can grant access. A redesign should not accidentally interrupt your firm's email.

Check what the outgoing provider must supply: files, content exports, access, licenses, cancellation terms, or a transition period. Resolve ownership questions before the build depends on those assets. Agree on a suitable way to share access once the project requires it.

Ask for a written scope that makes the deliverables and responsibilities clear. Include the pages, copy support, features, reviews, exclusions, launch approval, and ongoing costs. Name who tests the actual inquiry destination and who approves the site before release.

Include practical accessibility checks, such as keyboard navigation, readable content, form labels, and helpful error messages. W3C's forms tutorial explains how labels, instructions, and feedback help people complete forms. Agree on acceptance criteria rather than assuming a general compliance promise.

Finish with an account inventory, editing instructions, backups and update responsibilities, and a contact for future issues. At Koku & Co., website projects start at $2,500 USD. The proposal defines the actual project; brand identity, business systems, ongoing care, and SEO/content work are scoped separately.