Situation language has no destination
Queries describe events, not practice labels. If those events share one hub, the market job is unfinished.
Legal market map
A person rarely starts with a firm org chart. They start with a situation they can barely name. This page maps that market path. It is not legal advice. It is not the law-firm operating system for practice URLs, rooftops, and intake.
Position
Search intent here is a person trying to name what happened and which kind of help might fit. They may say custody, a contract stall, a workplace claim, or a property dispute. Keyword targeting gives each of those classes a destination that names a practice type the business actually offers.
A named firm's practice URLs, rooftops, biographies, and intake HTML. If the missing object is a CMS path or a form in initial HTML, open that door.
Open Law firmsDelivery for real offices and local discovery after the practice type is already named.
Open Local SEOThe delivered search program. This industry map does not reprint retainers or production methods.
Open SEO servicesChoose another industry door when the operator type is still unknown.
Open IndustriesTopical relevance means the page answers that situation and hands the reader to a practice type, not to a city clone or a verdict story. Semantic keywords belong only when they are the words a searcher already uses for that situation.
This URL is the market map. Law firms owns the named-firm OS: durable practice URLs, rooftops, biographies, and crawlable intake. Local SEO delivers location work after the market job is clear. This page does not give legal advice and does not promise rankings.
When this fits
Use this map when the organization has real practices, but public pages still speak in one legal blob. The reader cannot tell which type fits the situation, so inquiry arrives as noise.
Queries describe events, not practice labels. If those events share one hub, the market job is unfinished.
A menu of six types with identical paragraphs does not help a searcher choose. Each type needs a distinct public object.
Advice-like lines, outcome claims, and invented jurisdictions fail this review. Publish less until facts can be owned.
A city name in a heading is not a served market. Name only places the organization can support.
Process
The sequence follows how a searcher actually decides. It is not a CMS rebuild and not a ranking promise.
Collect the situation phrases people already use. Attach each phrase to one practice type the business offers. Leave unmatched phrases as gaps.
Outcome A situation inventory with one destination per class.
Write practice-type pages that a non-lawyer can tell apart. Keyword targeting stays inside that type. Do not merge types to harvest volume.
Outcome Practice-type pages with distinct scope and next steps.
People, offices, and scope must be current. Entity optimization uses the names the organization already uses in public. Unsupported claims become gaps.
Outcome A fact register with owners and review dates.
The inquiry should sit beside the practice type, not beside a generic legal essay. It must not look like legal advice.
Outcome An inquiry path tied to a named type.
Deliverables
The output is a situation-to-type contract, not a firm intranet rebuild.
Each public situation class, the practice type it should reach, and the page that currently fails or succeeds.
Which types have a real URL, which share copy, and which exist only in navigation.
Lines that sound like advice, outcomes, or unserved locations, with a keep, cut, or move decision.
Where a cautious question belongs relative to each practice type.
Who updates situation language, type scope, and inquiry copy, and how often.
Benefits
Each demand class has a public object. Search intent is no longer guessed at a homepage.
A swap-test with law firms should fail. This page never becomes rooftop NAP.
Published people and offices stay tied to someone who can verify them.
The form sits beside a type, not beside a slogan.
Methodology
We test live situation queries against live practice pages. We do not start in the CMS sitemap.
We write what the searcher knows, open the page meant to help, and see whether a practice type becomes obvious. If the page talks about offices and intake widgets first, the job has slipped onto law firms.
Every recommendation names an audience, a fact source, a page owner, and a handoff. Rankings are not promised.
AI search and AIO still need those stable type names. Generative search cannot invent a practice the organization does not publish.
First working session
Pick a real query from last month. Open the URL a searcher would hit. Stop at the first moment the practice type is unclear.
We write the situation in the searcher's words. We do not rewrite it into a partner's preferred label until the public page can support that label.
We follow links to type, trust, and inquiry. Interruptions are missing type, advice-like copy, or a jump into firm OS work that belongs on law firms.
We leave with a first page to fix and a clear handoff if the break is rooftops or intake HTML.
Answer engines
AI search can summarize only what the source states. This work does not promise a mention, citation, or placement.
AIO and generative search compress situations. If two types share one paragraph, the summary will blur them. Entity optimization keeps type names consistent across pages. Semantic keywords help only when they match how people name the event. LLM visibility sampling belongs on a measurement URL, not on this market map.
Use the same practice-type labels the organization uses in public, not seasonal slogans.
People, offices, and scope must be visible on the page a model might cite.
Prompt samples and mention tracking are a separate program.
Schema
Structured data may identify the organization, people, and services that are visible. It may not mint practices or results.
Use the legal-business name the site already publishes.
Link only published people and practice types. Do not invent specialties in JSON.
Markup is not a verdict generator.
Who we work with
Bring whoever can confirm which situations the organization actually accepts. Intake HTML owners can join later on the law firms page.
Confirms which situation classes the business will serve in public.
Owns practice-page templates without turning them into firm OS work.
Reports which questions arrived on the wrong type.
Questions
It maps a public situation to a practice type a person can recognize, then to a cautious inquiry. It does not staff a named firm's CMS, rooftops, biographies, or intake HTML. Those belong on law firms.
No. Copy may name practice types, locations the business actually serves, and how to inquire. It may not tell a reader what to do in a matter, predict an outcome, or invent credentials.
Situation pages that name a real practice type, practice-type pages that stay inside published scope, trust pages with facts the organization can keep current, and an inquiry that does not pretend to be counsel.
Keyword targeting assigns one situation class to one destination. A family-law query should not land on a generic legal hub. A commercial-lease query should not share a URL with criminal defense.
A page is relevant when it answers the situation it claims and points to the next practice-type decision. Filling the page with nearby legal words does not create relevance.
No. Keyword density is not a metric here. Repeating practice names cannot replace a clear situation, a named type, and a supported inquiry.
AI search, AIO, and generative search can compress a situation only if the source names practice types in stable language. Entity optimization starts with those names. LLM visibility measurement lives on its own program, not on this market map.
Live practice pages, the situation queries they are meant to catch, and one inquiry that was the wrong type. Do not bring rooftop spreadsheets as if they were the market job.
Legal market architecture
Share two live practice pages, the situation queries they are meant to catch, and one inquiry that landed on the wrong type. We will mark where the market map breaks before anyone talks about CMS templates.
Work from live practice pages and real situation queries. Do not start with rooftop NAP.