A practice manager commissioning a website in 2026 shouldn't need an opinion on frameworks. But there's a shorter, sharper list of questions worth asking, about AI visibility, ownership, editing, integrations, compliance and what a website actually costs over five years, not just to build.
Five Years Ago, the Website Brief Was Different
Five years ago we built a website for Shine Lawyers as a headless build, a decoupled front end, an API-driven content layer, deployed through Netlify. At the time, that was genuinely new territory for the legal sector. The principle was right: separate content from presentation and deliver finished pages quickly.
What has changed is the buying decision. A practice manager commissioning a website in 2026 should not have to develop an opinion about frameworks. You should be asking: will the site still be maintainable in five years? Can our team edit it? Can we move it if we change agency? Will AI systems be able to read our substantive content? Can it connect to our practice management and CRM systems? Can we add useful intake tools without every improvement becoming another development project? What will all of that cost to operate?
Those questions have changed how we build at Practice Proof. Our direction is deliberately simple: HTML for structure and substantive content, CSS for presentation, structured JSON for reusable firm data, and JavaScript for behaviour rather than for hiding content behind a browser process.
This is not a technology preference for its own sake. It is an operating model for a law firm website: easier to read, easier to move, easier to extend, easier to audit and less dependent on a treadmill of framework upgrades.
The Short Answer Before the Long One
A modern law firm website has to serve three audiences at once: the prospective client, the people inside the firm who manage it, and the machines increasingly involved in discovery and recommendation.
For the client it needs to be fast, clear, credible and useful. For your team it needs a sensible editing experience, reliable data and integrations. For search engines and AI crawlers, substantive content should be available in the page they receive rather than depending on code executing later.
Major AI crawlers do not all behave like Googlebot. Google has long invested in rendering JavaScript. GPTBot, ClaudeBot and other crawlers can fetch JavaScript resources without necessarily executing client-side JavaScript to reconstruct a page. If practice-area copy, lawyer information, FAQs or fee explanations only appear after scripts run, some machine readers may receive an incomplete page.
Our practical rule is simple: JavaScript handles behaviour, never substantive content.
Start With the Business Problem, Not the Technology
Most website briefs begin with pages, colours, competitors and a CMS preference. Start instead with what the website has to do over its useful life.
It should help the right clients take the next step; support Google, local and AI-assisted discovery; keep lawyer and office information consistent; connect with CRM and practice-management systems; let non-technical staff publish safely; support new practices and locations; allow useful tools to be added quickly; remain portable if the firm changes agency; and provide predictable support.
That is how Practice Proof approaches website work: strategy first, custom design, conversion-centred UX, integration with systems such as Smokeball, LEAP, Clio and Actionstep, ongoing optimisation and predictable support.
The Rendering Gap AI Created
Google can render JavaScript and has done so for years. Research published by Vercel and MERJ found Google successfully rendered effectively all indexable pages in its study. For Google, client-side rendering is often survivable, although it introduces another processing step.
AI crawlers can behave differently. Vercel's analysis found large request volumes from GPTBot and ClaudeBot, but the important distinction was behavioural: these crawlers requested JavaScript files without executing them like a browser.
There are exceptions, including systems benefiting from Google's rendering infrastructure. The sensible procurement assumption is nevertheless that substantive content should not depend on client-side execution to exist.
For legal services this matters because enquiries so often begin as questions. Assistants are designed to answer questions. Machine-readable, structured, specific and attributable content gives the firm the opportunity to be understood and cited. It does not guarantee a citation, authority and expertise still matter, but unreadable delivery creates an unnecessary barrier. This is the discipline behind our AEO and technical SEO work.
What Your Team Actually Edits
One concern practice managers reasonably have when they hear HTML, CSS and JSON is whether every content change will require a developer. It should not.
The editing experience and delivery architecture are separate decisions. Your marketing team can still work through a familiar content-management interface. The difference is what happens after they press publish.
A lawyer's name, admission date, practice areas, languages, accreditations, office and contact details can live in one structured record and be used wherever the site needs them. That solves an ordinary law-firm problem: information drift.
A lawyer becomes accredited. Their profile is updated but an old practice-area page is not. An office changes telephone details. A directory is current but structured markup is stale. Nobody intended the inconsistency; the site simply stored the same fact in too many places.
Structured content turns this into information governance. It also makes the same data portable to a portal, proposal generator, internal tool, digital signage or an AI application.
Who Owns It, and What Happens If You Leave?
This should be asked before a contract is signed, not when a relationship ends. Understand who owns the code, content, structured data, domain, analytics accounts and integrations; what can be exported; and what assistance is required to move elsewhere.
Practice Proof is built around long-term partnerships, but longevity should come from value rather than technical captivity. Our website offering includes training and handover, ongoing hosting, security and technical support, with fixed or predictable pricing rather than surprise hourly invoices.
Make the exit mechanics explicit in the scope. A good architecture should make portability easier, not use complexity as a retention strategy. See how we work for how we structure that from day one.
What Happens After Launch?
A launch is not the finish line. Search behaviour changes, lawyers arrive, services expand, regulations change and conversion opportunities become visible once real users move through the site.
Practice Proof's current website offering includes ongoing hosting, security updates, technical support, performance optimisation and ongoing support options. The real cost is therefore not only the build; it is the five-year cost of keeping the site secure, current, fast and commercially useful.
When comparing proposals, ask agencies for the implementation cost and the likely five-year operating cost, including framework upgrades, hosting, licences, support and routine improvements.
Bespoke Functionality Isn't a Five-Figure Conversation Anymore
For years, custom functionality on a legal website usually meant a plugin, third-party embed or substantial development quote. That pushed most firms toward the same default: a contact form.
Agentic coding tools have materially changed the economics of implementation. We use Claude Code in our development workflow. It accelerates implementation; it does not make strategic or legal decisions. Simpler, conventional code is easier for both humans and modern tools to understand and improve.
That opens a more useful client-experience brief: matter eligibility pathways, jurisdiction-aware limitation indicators, conditional intake forms, fee estimators where appropriate, settlement illustrators that educate without predicting outcomes, and document-readiness checklists.
Done properly, these tools turn a website into a service layer: helping a prospective client understand what happens next while collecting better information for the firm. This is the discipline behind our client experience design and conversion optimisation work.
The Compliance Layer Cannot Be an Afterthought
A legal website tool is not just software. An eligibility pathway can make statements about legal position. A fee estimator can make representations about cost. An outcome illustrator can stray into claims about what a firm may achieve.
Australia has advertising and touting obligations under professional regulation, with additional restrictions in some jurisdictions and practice areas. US firms operate under state bar rules informed by ABA Model Rules 7.1–7.3. England and Wales has the SRA Code and Transparency Rules. Canadian firms operate under provincial law societies informed by the Federation's Model Code.
The design discipline should be consistent: keep tools indicative rather than determinative; gate by jurisdiction; put disclaimers at the point of output; avoid outcome or quantum claims; version the logic; and require lawyer or principal sign-off.
That review belongs in the project plan, not as a disclaimer pasted in after development.
AI in the Build Process
We use AI-assisted development because it makes implementation faster. We do not outsource judgement to it.
Architecture, positioning, messaging, user journeys, compliance decisions and the definition of what a tool should do remain human decisions. Implementations still require review for responsive behaviour, accessibility, browser compatibility, performance, search visibility and maintainability.
The same principle applies inside a law firm: a tool can accelerate drafting and implementation, but a practitioner remains accountable for what goes out the door.
A Website Still Needs a Brand People Remember
None of this replaces positioning, brand or good writing. A technically pristine website for an indistinguishable firm is still an indistinguishable website.
Our website work starts with strategy: understanding the firm, its ideal clients, competitive position and the action the website needs people to take. Our StoryBrand-informed approach positions the client as the central character and the firm as the guide.
The delivery architecture should make good strategy easier to express: fast for people, legible to machines, consistent across the site and flexible enough to keep improving. See our SEO and website design pages for how those pieces fit together.
Audit Your Own Site This Afternoon
Failure does not automatically mean rebuild. Many sites server-render core content and client-render selected components. That may call for a targeted fix rather than reconstruction. Here's how to check.
- View source, search for a distinctive sentence.
Pick a high-value practice-area page. Search the raw page source for a sentence you know is on it. If it is absent, investigate how the content is being delivered.
- Turn off JavaScript and reload.
Check whether substantive practice-area copy, lawyer profiles, office details and contact information remain available.
- Ask the AI assistants directly.
Ask ChatGPT, Claude, Perplexity and Google's AI experiences the questions clients actually ask in your city and practice area. Treat this as observation, not a deterministic ranking test.
- Check server logs, not just Search Console.
Server logs can show whether AI crawlers reach the site and what status codes they receive.
- Test on a real phone using mobile data.
Wi-Fi in an office masks problems your actual clients experience on the street.
- Ask for a third-party script inventory.
What loads, why it loads, who owns the data, and whether each script earns its place.
What to Ask Any Agency Pitching You a Website
The Takeaway
The website decision facing a law firm in 2026 is not React versus HTML, headless versus traditional, or one CMS versus another. It is whether the firm is buying a website that will remain useful as client behaviour, search and AI discovery change.
Three principles guide our answer. Substantive content should be delivered in a form humans and machines can read without depending on client-side execution. Firm information should be structured so it stays consistent and reusable. And the codebase should be simple enough that useful client experiences can be added without turning every idea into a major project.
Put those principles underneath strong positioning, distinctive design, good legal content, integrations, compliance review and ongoing optimisation, and the website becomes something more valuable than a brochure. It becomes infrastructure for growth and client experience.
Start with the source test on your busiest page. Then ask your agency the procurement questions above. If you would like a second opinion on what people and machines currently receive from your site, that is exactly what a technical and AI-visibility audit is for.
Sources
- Google Search Central — Understand JavaScript SEO Basics
- Google Search Central — Intro to structured data
- Vercel / MERJ — The rise of the AI crawler
- Vercel / MERJ — How Google handles JavaScript throughout the indexing process
- Cloudflare — The crawl-to-click gap
- Clio — 2025 Legal Trends Report