> For the complete documentation index, see [llms.txt](https://legal-web-agency.gitbook.io/legal-web-agency-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal-web-agency.gitbook.io/legal-web-agency-docs/readme.md).

# Law Firm Website Launch Checklist

Welcome to your team’s developer platform

A law firm website rarely fails on launch day because of the design. It fails because of small things nobody checked: a phone number that can't be tapped, a redirect that was never added, or a results page with no disclaimer. We use this list before any site goes live.

### Calls and intake

* Every phone number is a tappable link on mobile. In our audit of 14 law firm homepages, 6 had no tap-to-call link.
* Submit every contact form yourself and confirm the message reaches a monitored inbox.
* Each practice page has one clear next step above the fold.

For more on structure, read our [lawyer website design guide](https://legalwebagency.com/lawyer-website-design/).

### Speed, tested in the field

* Check real-user Core Web Vitals, not only a lab score. In our tests, one site scoring 91 in the lab failed in the field while one scoring 51 passed.
* Compress images and remove unused plugins. Homepage weight varied 17x across the sites we measured.

The details are in our [Core Web Vitals study of law firm websites](https://legalwebagency.com/core-web-vitals-law-firm-websites/).

### Bar advertising rules

* Check testimonials, case results and words like "specialist" against your state's rules.
* Add required disclaimers and the responsible attorney where your state asks for them.

Start with our [attorney advertising rules by state](https://legalwebagency.com/attorney-advertising-rules-by-state-law-firm-website/).

### Search and redirects

* Remove any noindex left over from the staging site.
* Redirect every old URL to its closest new page, and test the redirects.
* Give each page a unique title and description, and submit the sitemap in Search Console.

Rebuilding an existing site? Our [website redesign guide](https://legalwebagency.com/law-firm-website-redesign-guide/) covers protecting rankings, and our [law firm SEO guide](https://legalwebagency.com/law-firm-seo-guide/) covers what to do next.

### Final check

Run the live site through our [free law firm website scan](https://legalwebagency.com/free-website-scan/) to catch speed, SEO and accessibility problems.

*Published by Legal Web Agency. General marketing information, not legal advice.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legal-web-agency.gitbook.io/legal-web-agency-docs/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
