Lawyer website development is sold at every price point from a templated package bundled into a marketing retainer to a bespoke build costing as much as a junior associate. The difference between them is rarely visible on the surface, because every legal website looks broadly the same: a hero image of a courthouse, practice area tiles, an attorney grid. What separates them is what happens underneath, in structure, speed, intake, ownership and compliance. This guide sets out what a competent build includes, what genuinely moves the price, which contract terms decide how expensive the next five years will be, and how to vet a developer on evidence.
What a competent build actually includes
Start with structure, because it decides how well the site can ever rank. A real practice area architecture gives each matter type and each jurisdiction its own page rather than lumping everything under a department heading, and it leaves room to add situational pages later without breaking the navigation. Then attorney pages that read like a person wrote them, with bar admissions, matter experience and a clear route to contact. Then intake: forms that work on a phone, a visible phone number that is tracked, and a defined path for after-hours enquiries, because the firm that responds first usually gets the matter. Then technical health, meaning fast loading on mobile connections, accessible markup, and structured data describing the firm and its locations. Google publishes the specifications for local business markup and the performance thresholds it measures, and a developer who cannot discuss them is building a brochure rather than an asset.
What moves the price
Four inputs do most of the work. Page count, since a full practice area and jurisdiction architecture is many more pages than a template implies. Whether content is written for you or supplied by you, which is the largest single variable and the one most often left ambiguous in a quote. Custom design versus a configured theme, where custom costs more and is worth it mainly when the firm has a genuine brand position rather than a preference for a different shade of blue. And integrations: case management systems, intake and chat tools, payment portals and document upload each add real work. Migration is the fifth item where an existing site is being replaced, and it deserves its own line: URL mapping and redirects decide whether the new site keeps the rankings the old one earned, and Google documents the correct process for site moves with URL changes.
Ownership and compliance terms that decide the next five years
Before you sign, settle four questions in writing. Who owns the domain, and is it registered in the firm's name with the firm holding the credentials. Who owns the code and content when the relationship ends, and can the site be exported to another host without a rebuild. Is the site built on a proprietary platform the developer licenses, which is a legitimate model but means you are renting rather than owning. And who controls the analytics, tracking numbers and search console property. Separately, remember that lawyer advertising is regulated state by state: claims about outcomes, comparisons, testimonials and required disclaimers are all constrained, and the website is advertising. A developer working in this market should ask who reviews copy for professional responsibility compliance before you have to raise it.
How to vet a developer
Ask for three law firm sites the candidate built in the last two years, then test them yourself rather than reading the case study. Load them on a phone on a normal connection and see how long they take. Submit a contact form and see what happens. Look at whether the practice area pages are real pages or one page with swapped headings. Search a couple of the firms' matter types and see whether the sites appear at all. Then ask process questions: what the discovery stage produces, who writes the copy, how many revision rounds are included, what happens after launch and at what rate, and what the support arrangement costs. Firms that publish their pricing or disclose a minimum are easier to compare and generally more comfortable being held to a scope. Since most legal websites are bought as part of a wider marketing decision, ask whether the developer also handles search and content, or whether you will be coordinating two vendors.
Questions people ask about lawyer website development
Custom build or template?
A well-configured template on a mainstream platform is right for most small and mid-sized firms, provided the structure, speed and intake are done properly. Pay for custom when you have a real brand position to express or an integration a template cannot support. Custom design does not by itself produce more enquiries.
Should the developer also write the content?
Someone must, and the quote should say who. Legal copy written without attorney input reads generically and rarely ranks. The arrangement that works is a writer who interviews an attorney for each practice area and an attorney who edits for accuracy. If content is excluded, budget for it separately rather than launching with placeholder text.
What happens to our rankings when we relaunch?
They depend entirely on the migration. Every old URL needs a mapped destination and a permanent redirect, the new structure needs parity with what ranked before, and someone should crawl the staging site before launch. Ask the developer to describe its migration process specifically, and treat a vague answer as a risk you are absorbing.
How long does a build take?
Eight to sixteen weeks is typical for a mid-sized firm, and content is almost always the bottleneck rather than development. Reduce the risk by assigning one decision maker at the firm, agreeing the page list before design begins, and scheduling the attorney interviews at the start rather than after the design is approved.