Technical SEO for Law Firms
Most law firm sites do not have a content problem. They have pages that cannot be crawled properly, duplicate versions of the same URL, or a mobile experience that loses the visitor before the content loads. Technical SEO is the work of removing those obstacles.
What technical SEO means for a law firm
Technical SEO is everything that determines whether search engines can discover, crawl, render, index and trust your pages — independent of how good the writing is.
For law firms the stakes are specific: practice-area pages competing with each other, location pages that duplicate a template, attorney bios that outrank service pages, and schema copied from a theme that describes a different business. None of these are content problems, and none are fixed by writing more.
The 12-point audit we run
Each check has a pass condition, not an opinion.
| # | Check | What we verify |
|---|---|---|
| 01 | Crawl access | robots.txt, meta robots, X-Robots-Tag, and whether CSS/JS are blocked |
| 02 | Indexation | Indexed vs submitted URLs, thin pages, utility pages that should be excluded |
| 03 | Canonicals | Self-referencing canonicals, conflicting directives, noindex+canonical combinations |
| 04 | Redirects | Chains, loops, 302s that should be 301s, and whether destinations match intent |
| 05 | Status codes | Soft 404s, 5xx on linked URLs, error pages returning 200 |
| 06 | Duplicate URLs | Protocol, host, trailing slash and index-file variants of the same page |
| 07 | Structured data | Validity, duplicate entities, and whether markup matches visible content |
| 08 | Core Web Vitals | LCP, INP and CLS — field data where available, lab data clearly labelled |
| 09 | Mobile rendering | Viewport, tap targets, horizontal overflow, and content parity |
| 10 | JavaScript rendering | Whether primary content exists in the raw HTML response |
| 11 | Internal links | Depth from the homepage, orphans, and anchor relevance |
| 12 | Sitemaps | Coverage of indexable URLs, exclusion of redirected and noindex URLs, validation |
Field data is reported only when it exists. Lab scores are labelled as estimates.
Pass conditions, stated plainly
No invented benchmarks — these are the conditions we check for.
One URL per page
Every page resolves at exactly one canonical URL. Protocol, host and index-file variants redirect in a single hop.
Server-rendered content
Headings, body copy and links exist in the raw HTML response, not only after JavaScript runs.
Self-referencing canonicals
Every indexable page points to itself. Utility and application screens carry noindex and no canonical conflict.
Schema that matches the page
Organization, Service, FAQPage and Article markup describe what is actually visible.
Shallow, connected pages
No commercial page is more than three clicks from the homepage, and no page depends on a single inbound link.
Errors that stay errors
A missing page returns 404, a removed page returns 410, and neither returns 200.
What we usually find on law firm sites
Competing practice-area pages
Three pages target the same practice area with near-identical copy, so none of them wins and the site competes with itself.
Templated location pages
City pages differ only by the city name. Similarity above roughly 15% of shared phrasing is a reliable warning sign.
Bios outranking services
An attorney profile page ranks for a commercial term while the service page does not, because the bio has more substance and more links.
Schema describing another business
Theme or template markup left in place, sometimes with a different address entirely — the most damaging entity error we see.
Utility pages indexed
Login, signup and form screens returning 200 with no robots directive, diluting the index.
Orphaned clusters
Whole sections of a site with zero internal links from the main navigation, invisible to both crawlers and users.
How the audit is delivered
A spreadsheet and a developer-ready ticket list.
Raw findings
Every check, its status, the evidence (URL, header, response code) and whether it is verified or unverified.
Prioritised fix list
Ordered by impact and risk: index-control first, then duplication, then performance, then schema.
Developer tickets
One ticket per fix, with the exact change, the verification step and the rollback.
Re-crawl and sign-off
After fixes ship, we re-run the same checks and report what actually changed.
Access required to run the audit
We can run a substantial audit from the public site alone. Three things make it materially better:
- Search Console read access — index coverage, Core Web Vitals field data, and the queries each page already receives.
- Hosting or FTP access for server-level checks: redirect configuration, headers, compression and error handling.
- A developer contact who can implement the fix list, or approval for us to implement it.
Honest limits of a technical audit
A technical audit cannot tell you whether your practice-area pages are commercially relevant, whether your titles persuade anyone to click, or whether your intake converts. Those are separate problems with separate fixes.
It also cannot fix a content gap. If a firm has no page targeting personal injury marketing, no amount of technical correction creates one. What the audit does is make sure that when you do publish, the page can actually be crawled, indexed and measured.
We state this because the most common disappointment in SEO is a technically perfect site that still does not rank — usually because the content targets terms nobody at the firm would recognise as a client's question.
Why law firm sites decay without anyone noticing
A redesign that added a builder
Page builders make publishing easy and add JavaScript to every page. Performance degrades gradually and nobody owns it.
A plugin that stopped being updated
Old plugins leave markup, scripts and sometimes schema behind after they are disabled.
A migration with missed redirects
The old URLs still exist in the wild, pointing at 404s. Links break silently; nobody monitors referral errors.
Attorney bios added ad hoc
Each new bio introduces its own template variation, heading structure and sometimes its own schema block.
Location pages copied from a template
Three years of city pages, all 95% identical, all competing with each other and with the main service page.
Schema copied from a theme demo
The most damaging and the least visible. The markup describes a business that is not yours.
Questions law firms ask us.
How is technical SEO different from normal SEO?
Technical SEO covers crawlability, indexation, rendering, duplication, speed and structured data. Content SEO covers what the page says and which queries it targets. A site can fail on either, independently.
Will fixes change how the site looks?
No. Every recommendation in a technical audit is either server configuration, head-level markup, or internal linking. Nothing requires a redesign.
Do you need hosting access?
For a public-site audit, no. For redirect configuration, headers and compression we need hosting or FTP access, or a developer who can apply the changes.
How do you report Core Web Vitals?
Field data from Search Console or CrUX when it exists. Where it does not, we say so and label lab measurements as estimates rather than presenting them as real-user data.
What is the most common single fix?
Index control on utility pages and consolidation of duplicate URLs. It is usually quick, reversible, and removes noise from everything measured afterwards.
Related services and reading
Want the 12 checks run on your site?
We return the raw findings, a prioritised fix list and developer-ready tickets — whether or not you hire us to implement them.