Law Firm Web Design and Development

Law firm web design that’s decided before it’s designed

The visible problem is rarely the whole problem. A site looks dated, so the design gets replaced, and the firm can end up with the same complaints on a better-looking page, because what was actually wrong was never in the design.

The decisive part of this work happens before anything gets styled. What the site needs to become, and how much of what you already have is worth keeping. Those two answers set what gets built, what it costs, and how long it holds up.

That’s the work Urban Geko does for law firms. Website strategy, design, and development, sized to what the situation calls for: a focused improvement to a site that mostly works, or the whole build, from goals and structure through launch and everything after it.

Twenty-five years of digital design and marketing work sits behind how we make those calls. It’s also why we’d rather look at your site than talk about our services in the abstract. Examples of the best law firm websites are useful as decision criteria, but neither answer belongs to law firm websites in general. Both belong to yours, which is where any useful conversation starts.

What changes when the site starts working

Most firms are better than their websites suggest.

The credentials are real, the people are genuinely good at the work, and then a prospective client lands on a homepage that leads with a stock photograph and a promise of dedication, buries the practice they need three clicks down, and describes twelve attorneys in twelve identical paragraphs. Nothing on that page is false. None of it carries what makes the firm worth hiring.

The gap between a site that looks fresher and a site that works shows up in a handful of specific places.

Practice areas people recognize: someone arrives with a problem, not a legal category. Your practice list either names their situation in words they’d use, or it asks them to translate and hope they guessed right.
Attorney profiles that do more than list credentials: a column of admissions and alma maters leaves someone guessing at fit. Connecting each attorney to the work they do, the office they sit in, and the kind of matter they handle gives a reader something to judge, instead of twelve names that all read the same.
Offices that behave like offices: three locations shouldn’t read as one blurred entity behind a general enquiry form.
A visible reason to choose you: whatever separates the firm belongs where people are deciding, not parked on a page they’ll never open.
Contact where the decision happens: a single form at the foot of the site assumes everyone arrives at readiness in the same place. The route to a conversation belongs on the pages where someone might want it.

None of that is styling. Every one of them is a decision about structure, content, and interface, taken long before anyone chooses a typeface.

The view from the other side of the screen

Your side of this is half the story. Whatever the site achieves, it achieves on somebody else’s terms.

They have a problem they’d rather not have. They may be on a phone, with other firms open alongside you, and they aren’t evaluating your design. They’re working out whether you handle their kind of matter, whether anyone there has done it before, whether you’re near enough to be practical, and how to ask a question without committing to anything.

A visitor can be lost long before the design registers. The practice list doesn’t name their problem. A bio runs as an unbroken wall of text on a small screen. The office page offers an address and no way to reach a human. Every one of those is a commercial problem wearing design clothes.

That’s where our UX work starts: with what that person is trying to do, and what’s currently stopping them. It settles more about whether the site works than the visual layer ever will, and it’s why a new design on its own can leave the real problem exactly where it was.

Improve it, redesign it, rebuild it, or start again

Replacement isn’t automatic. The instinct to start over gets expensive when it’s wrong.

Plenty of law firm sites carry a dated visual layer over structure and code that are perfectly sound. Others look current and can’t be changed without a developer on standby. A site that was never really finished, or half migrated and then abandoned, can hold more usable foundation than the people living with it assume. It works the other way too: a redesign gets commissioned, the new version looks better, and every underlying problem is sitting exactly where it was.

Four different answers sit behind that question, and they aren’t degrees of the same thing. Picking the wrong one costs you in both directions: a rebuild nobody needed, or a redesign that leaves the real problem underneath it.

Direction When it’s the right call Where the work concentrates
Focused improvement The foundation holds up and specific things are underperforming Navigation and key pages, content clarity, targeted interface and technical fixes
Redesign The site no longer represents the firm, or can’t hold the content it needs to Strategy, UX, visual design, and the content model, on a foundation that still stands
Rebuild The presentation is defensible, but the build, platform, or publishing model is the real problem Architecture, development, technology choice, maintainability, migrating what’s still good
New build There’s nothing underneath worth saving, or the firm is starting from scratch The whole sequence, from goals and structure through launch

Those are patterns, not a formula. Telling them apart takes a look at your actual site, not the category it falls into.

A site can look better and still carry every problem it had before. The fix isn’t always in the layer that got redesigned.

How we read the site you already have

Telling those four apart is the first useful thing a partner can do for you, and it comes from reading your site rather than the category.

Structure and navigation, to begin with. Law firm sites can strain there in recognizable ways. Practice areas added one at a time. Attorneys grouped by seniority instead of by what a client is looking for. Offices bolted on as extra pages.

The content model comes next: whether the site treats attorneys, practices, and locations as connected things that can be published and updated, the same foundation that content marketing for law firms depends on, or as a stack of hand-built pages that break in a fresh way every time somebody edits one.

Underneath that sits the build itself, which means what it runs on, how well it’s been looked after, how much of it depends on plugins or custom work nobody documented, and how it holds up on the devices your clients actually use.

Then the question that decides most of it. Can this foundation carry what the firm wants next? Another office, a practice group you’re growing, a content program, an intake path that has to connect to something else. If the foundation can’t carry where the firm is heading, improving it buys less than it appears to, however presentable the site looks today.

That read is judgment applied to specifics rather than a default answer: which shortcuts stay harmless, which ones turn into the reason a site gets replaced earlier than it should be, and when a visible complaint is a symptom of something structural. It doesn’t replace looking at your site. It’s what makes looking at it worth anything.

Settle it before a budget gets attached to a direction. Show us what you’ve got and we’ll tell you what we see.

That read is judgment applied to specifics, not a default answer. It doesn’t replace looking at your site; it’s what makes looking at it worth anything.

The decisions that will not sit still

Websites rarely fail inside one discipline. They fail in the seams between them.

A design gets approved on its own merits, then a developer inherits it along with a set of decisions nobody flagged as decisions. The content model gets settled after the templates are built, so adding a practice area means rebuilding a page. A platform gets chosen because it’s familiar, and the firm pays for that choice every time it wants to change a headline.

These aren’t stages that hand off to each other. They constrain each other.

What the firm wants the site to do decides how it gets organized. That’s structure, not a menu.
Structure sets the journeys people take, and UX settles those long before the site has a look.
Those journeys tell visual design what has to be prominent, what repeats, and what still has to work at the width of a phone.
Design and the content model together decide what the build has to support, which is why the content model can’t wait for templates to exist.
The build and the technology under it decide what launch takes, and what every change after launch costs you.

Each link inherits the quality of the one before it. That’s how a project can look healthy at the design review and still land as a site the firm’s own people can’t update without asking for help.

Structure, journeys, and the moment someone decides to call

Law firm sites carry a particular structural load: several practices, a lot of individual people, often more than one office, and visitors arriving with different combinations of the three in mind.

Someone lands on an attorney profile from a search, likes what they read, and now wants the practice, the office, and a way to make contact without going back to the homepage to start again. Multiply that by every entry point the site has, and information architecture stops being a diagram. It becomes the thing that decides whether your expertise is findable at all, which is also the ground that law firm SEO works on.

How practices group, and what they’re called: internal department names and the words a client would search rarely match. Use theirs.
How attorneys connect: each profile tied to its practices, its office, and the matters that make that person a credible answer to a specific question.
What belongs to a location: a multi-office firm needs each office to feel like a place with people in it, not a line in the footer.
Where contact belongs: which action fits which page, and what happens to someone after they take it.

Then the smaller decisions, which shape the experience more than anyone expects. Whether a long bio stays readable on a phone. Whether tapping a phone number dials it. Whether a practice filter helps or just adds a step. Whether the site behaves the same way for someone who starts on a laptop at the office and finishes on a phone at home. Left to the end of a project, those get made by whoever notices them last.

Building on what the requirements actually call for

By the time structure and journeys are settled, the technology question has largely answered itself. Which is the opposite of the usual order.

Urban Geko builds across a broad range of frameworks, languages, platforms, and integrations, and that range exists so the recommendation can follow the requirements instead of a habit. WordPress for law firms is a sensible answer for plenty of sites. It isn’t the only one, and it isn’t automatically the right one for yours.

What decides it is a short set of questions. Who needs to change the site without calling a developer, and how often? What does it have to connect to, from intake forms to the tools your team already runs on? How much of the content is relational, attorneys tied to practices tied to offices, and how much of that should be managed rather than hand-built? And what does the firm expect to be doing in three years that this build has to survive?

Maintainability belongs in that conversation, not in a different one after launch. A build only its author can safely touch is a liability the firm inherits on day one.

What stops happening when one team carries it

All of this assumes somebody is accountable across the full span. That’s not a given.

The familiar version: a designer produces something the firm likes, a developer builds an approximation of it, a writer supplies copy that doesn’t fit the layout, a marketing team asks for changes the build can’t support, and the firm becomes the translator between four parties who each did their own part correctly. When something falls through, everyone can point somewhere else and be honest about it.

Urban Geko covers that whole span. Strategy, UX and interface design, full-stack development, content, search, launch, maintenance, and the wider digital work a site has to support. Not as a package you have to take whole. A firm that needs three pages fixed gets three pages fixed. A firm rebuilding its presence across several offices and practices can have as much of that span coordinated under one team as the work calls for.

What goes away is the gap. Interface decisions get made with the build in view. Content decisions get made with the templates in view. Launch is part of the same piece of work rather than a handover between separate ones. None of that is dramatic. It’s just the difference between a project that holds its time and quality and one that leaks both into the seams.

What shapes the investment

Website costs vary because website projects vary, which is no help when you’re trying to plan. What helps is knowing which decisions move the number, and which of them are still open to you.

The starting point: improving a sound foundation and replacing an exhausted one are different amounts of work. It’s why the improve, redesign, rebuild, or new build call comes before anything else gets priced.
How much site there is: practices, attorneys, offices, and languages multiply pages, relationships, and templates. A boutique firm in one location and a fifty-attorney firm across four aren’t the same project, even when they want the same thing.
How far the design and UX work goes: refining a structure that broadly works sits well below designing a new one around new journeys.
Who writes and moves the content: an easy line to underestimate. Writing new copy, reworking existing copy, and migrating old copy are three different jobs, and how much of each the firm takes on is worth deciding early rather than late.
What has to connect: integrations, forms that route into the firm’s systems, anything that has to talk to software you already depend on.
How it gets built: platform choice, how much is custom, how much has to stay editable by people who don’t write code.
How much we carry afterwards: handing over a finished site is one arrangement. Maintaining it, or working across the firm’s wider digital activity, is another.

Those are the variables a number is actually made of, which is the argument for settling scope in conversation before anyone writes a proposal. Three quotes describing three different projects aren’t a comparison.

The site after launch day

Launch isn’t the finish line. It’s the first day the site has to hold up with real people using it.

What happens next decides how long it stays good, and the decline is never dramatic. Updates queue because nobody owns them. A new partner’s bio sits unpublished. A page gets edited by whoever was free and quietly breaks the template. Dependencies drift. The design stops matching how the firm presents itself now. Nothing fails outright. The site just slides, until the firm concludes it needs a new website when what it needed was somebody paying attention.

Website maintenance and continuing digital support are part of what we do, and how much of it we carry is settled with each firm rather than assumed. Where we do carry it, the work is deliberately unglamorous. It’s meant to keep a site functioning, maintainable, and able to change as the firm does:

the platform, dependencies, and build attended to as a matter of course rather than when something breaks;
changes handled with the whole build in view rather than as isolated edits;
the site kept in step with the firm as attorneys join, a practice group grows, another office opens, or a page needs rethinking;
and the groundwork for what comes next, whether that’s a content program, search work, or a campaign that needs somewhere credible to land.

When a firm wants the site working alongside its content, search, and broader law firm digital marketing, we can coordinate that too. When the firm would rather keep the upkeep in house, that’s a workable arrangement as well. What matters is that somebody owns it.

Where a firm should start

The most useful preparation isn’t a brief. It’s clarity on four things, and it comes from the people who already know the firm rather than from anyone outside it.

What the site has to achieve, in plain commercial terms: more of a particular kind of work, better presentation of a practice you’re investing in, a firm that’s easier to take seriously at first contact.
What currently works, so it doesn’t get thrown out along with everything that doesn’t.
What can’t break: an intake route, a phone number, the pages people already arrive on.
What’s coming next: an office, a practice group, a hiring push, a merger. The site should be built for that firm, not this one.

With those in hand, a conversation about your actual site is worth more than a shelf of general recommendations. Yours has a specific structure, a specific build, a history of decisions that made sense to somebody at the time, and things it already does well that shouldn’t be lost in the rebuild. It’s also the only point at which improve, redesign, rebuild, or start again gets answered honestly, because it’s the first time anyone is looking at what you have rather than at what firms tend to need.

Ready When You Are

Talk With Urban Geko About Your Next Project

So let’s look at the real thing. If there’s a site, we’ll start with where it’s letting the firm down. If there isn’t one yet, we’ll start with what the firm is trying to become. Either way, it begins as a conversation, not a commitment.

Talk to us about your site