Legal AXO Guide

One rule generates most of this page. The sentence is the unit of delivery, so the sentence has to carry its own jurisdiction, its own date, and its own limits. Everything you built around it is page furniture: the disclaimer in the footer, the "serving clients throughout Ohio" strapline, the practice-area heading two scroll-lengths up. Page furniture does not travel with an extracted passage.

Jurisdiction has to be inside the sentence

This is the highest-value editorial change a legal publisher can make, and it requires no new technology, no schema work, and no engineering ticket. Any sentence stating a rule of law names the jurisdiction that rule belongs to, in that same sentence, ideally before the rule rather than after it.

The failure mode is easy to picture. A San Francisco employment firm writes an accurate page about restrictive covenants for its California clients. An assistant retrieves one clean, declarative sentence from it and hands that sentence to somebody in Dallas who is deciding whether to sign an agreement.

The second version is longer, and the extra length is the entire point. It survives being quoted alone, it tells a reader in another state that the answer changes for them, and it gives an engine something checkable to attribute.

• Front-load the jurisdiction. "Under Illinois law, X" beats "X, under Illinois law". Truncation eats the tail of a passage far more often than the head.
• Name the body of law, not just the state. Federal statute, state common law, a circuit's precedent, and a model code as adopted locally are four different things, and a reader who gets only your sentence has no other way to tell which one you meant.
• Flag variation in the same breath. One clause acknowledging that other states differ is what stops a state-specific rule being read as a national one.
• Deadlines need the jurisdiction and the caveat together. A limitations period stated without its state, and without noting that discovery rules and tolling can move it, is the single most dangerous unqualified sentence a firm can publish.
• Do not lean on the page title. "Texas Divorce Guide" is a title. Titles are metadata, and metadata is exactly what gets discarded when a passage is pulled into an answer.

Legal information, legal advice, and what extraction does to the line between them

Publishing general legal information to the public is ordinary and protected. Applying law to a specific person's facts, for that person, is the practice of law, and doing it in a jurisdiction where you are not admitted is a professional-responsibility problem rather than a content-strategy one.

Retrieval sharpens the problem in a way that deserves stating plainly: the language keeping you on the safe side of that line is structurally the language most likely to be dropped. Summarization removes hedges by design. "Depending on the facts", "in most cases", "you should speak to an attorney licensed in your state" — in nearly every other subject these are padding, and a summarizer that strips them is doing its job. In legal writing they are load-bearing.

You can write with real authority and still stay on the information side. The move is to be highly specific about the law and deliberately unspecific about the reader.

• Set out the rule and its elements; do not assess whether the reader meets them. "A claim for breach of fiduciary duty requires a fiduciary relationship, a breach of that duty, and resulting damages" is information. "You have a claim" is a conclusion about facts you have never seen.
• Put the condition inside the sentence that states the consequence. Split across two paragraphs, only the consequence gets quoted.
• Watch the second person. "If your employer misclassified you, you can recover unpaid overtime" reads as an assessment. "An employee misclassified as exempt under the federal executive exemption may be entitled to unpaid overtime" reads as information. There is no magic grammar that converts advice into information, but the shift matters more in an extracted fragment than it does on the page.
• Do not let optimization pressure produce superlatives. State bars regulate what a lawyer may claim about specialization, expertise, and past results, and the rules vary. An AXO rewrite that adds punchy, confident marketing claims to a bio is a bar complaint with good extraction characteristics.
• Keep the disclaimers and stop treating them as protection. A footer notice that no attorney-client relationship is formed is necessary and it will not accompany a single sentence pulled from paragraph nine.

Intake forms and chat widgets deserve their own look. If an assistant summarizes your contact page as an invitation to describe a legal problem, you may start receiving detailed unsolicited fact patterns from people you have not run a conflicts check on. That is a workflow question for whoever owns your intake, not a copywriting one.

Cite the statute, not a blog post about the statute

Legal writing already has a citation culture that most of the web lacks. Use it on the website, not only in the briefs. A citation like Cal. Bus. & Prof. Code § 16600 or Miranda v. Arizona, 384 U.S. 436 (1966) is a stable identifier that resolves to a single authority, survives being stripped of its hyperlink, and can be checked by anyone — human or machine — without trusting you.

Federal statute      42 U.S.C. § 1983
State statute        Cal. Bus. & Prof. Code § 16600
Federal regulation   29 C.F.R. § 541.100
Case                 Miranda v. Arizona, 384 U.S. 436, 444 (1966)
Case (pinpoint)      Brown v. Bd. of Educ., 347 U.S. 483, 495 (1954)

Link each of those to the body that publishes it: uscode.house.gov for the U.S. Code, govinfo.gov for the Federal Register and the C.F.R., your state legislature's own code site for state statutes, and the issuing court for opinions. A link to an official publisher is verifiable in a way that a link to a legal-content aggregator is not, and the aggregator may not be there in three years.

• Name the authority in the prose. "Section 16600 of the California Business and Professions Code provides that…" survives extraction. "The law says" with a hyperlink on "the law" does not.
• Never cite another firm's blog as authority for what the law is. It is a summary written by a competitor's marketing department, it may be years stale, and if it is wrong you have republished the error under your own name and your own byline.
• Distinguish binding from persuasive, holding from dicta. "The Ninth Circuit held" and "a California trial court has suggested" carry very different weight, and an extract preserves that distinction only if the sentence stated it.
• Date the authority. Codes get amended and sections get renumbered. A citation without a year cannot be checked for currency by anyone reading it later.
• Verify every citation a model drafted. Courts have sanctioned attorneys over filings containing fabricated case citations produced by chatbots — the 2023 sanctions in Mata v. Avianca in the Southern District of New York being the widely-reported example. The same failure mode applies to marketing content, and it is likelier there, because nobody reviews marketing content the way they review a brief.

Attorney bios, bar admissions, and how to model them

A named attorney with a bar number, a stated admission jurisdiction, and a link to the licensing authority's own directory entry is one of the few credentials on the open web that a third party will confirm for free. Most firms already publish the bio and then throw away the verifiability by writing the admissions as decorative prose.

On the markup side there is a trap worth knowing about. Schema.org defines Attorney, which looks like the obvious type for a lawyer, and it is the wrong one for a byline: Attorney is a subtype of LegalService, which is itself a LocalBusiness. It describes a practice — an office with an address, a phone number, and opening hours — rather than a human being who wrote something. For an author or a bio page, use Person, and express the admission as hasCredential pointing at an EducationalOccupationalCredential object rather than a bare string. The object gives you recognizedBy for the admitting authority and validIn for the jurisdiction, and validIn is the field that makes an admission machine-readable at all.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "LegalService",
      "@id": "https://example-law.com/#organization",
      "name": "Example Employment Law Group",
      "url": "https://example-law.com/",
      "telephone": "+1-415-555-0142",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "500 Example Street, Suite 900",
        "addressLocality": "San Francisco",
        "addressRegion": "CA",
        "postalCode": "94105",
        "addressCountry": "US"
      },
      "areaServed": [
        { "@type": "State", "name": "California" },
        { "@type": "State", "name": "Nevada" }
      ],
      "knowsAbout": [
        "California wage and hour law",
        "Employee classification under the FLSA",
        "Trade secret and restrictive covenant disputes"
      ],
      "employee": { "@id": "https://example-law.com/#/schema/person/rmensah" },
      "sameAs": ["https://www.linkedin.com/company/example-employment-law-group"]
    },
    {
      "@type": "Person",
      "@id": "https://example-law.com/#/schema/person/rmensah",
      "name": "Rachel Mensah",
      "url": "https://example-law.com/attorneys/rachel-mensah",
      "jobTitle": "Partner",
      "worksFor": { "@id": "https://example-law.com/#organization" },
      "alumniOf": {
        "@type": "CollegeOrUniversity",
        "name": "University of California, Berkeley, School of Law"
      },
      "hasCredential": [
        {
          "@type": "EducationalOccupationalCredential",
          "name": "Admitted to the State Bar of California",
          "credentialCategory": "license",
          "dateCreated": "2011-12-05",
          "validIn": { "@type": "State", "name": "California" },
          "recognizedBy": {
            "@type": "Organization",
            "name": "The State Bar of California",
            "url": "https://www.calbar.ca.gov/"
          },
          "identifier": {
            "@type": "PropertyValue",
            "propertyID": "California Bar Number",
            "value": "000000"
          }
        },
        {
          "@type": "EducationalOccupationalCredential",
          "name": "Juris Doctor",
          "credentialCategory": "degree",
          "educationalLevel": "Doctoral"
        }
      ],
      "sameAs": ["https://apps.calbar.ca.gov/attorney/Licensee/Detail/000000"]
    },
    {
      "@type": "WebPage",
      "@id": "https://example-law.com/practice-areas/non-compete-agreements#webpage",
      "url": "https://example-law.com/practice-areas/non-compete-agreements",
      "name": "Non-Compete Agreements in California",
      "inLanguage": "en-US",
      "datePublished": "2024-03-11",
      "dateModified": "2026-07-22",
      "spatialCoverage": { "@type": "State", "name": "California" },
      "author": { "@id": "https://example-law.com/#/schema/person/rmensah" },
      "publisher": { "@id": "https://example-law.com/#organization" }
    }
  ]
}
</script>

• areaServed on the firm is your jurisdictional declaration. Populate it with the states you actually practise in, as State objects rather than a marketing string like "the Bay Area and beyond". If your admissions and your areaServed disagree, fix the one that is wrong before publishing either.
• spatialCoverage on the page says what the content is about geographically, which is a different claim from where the firm operates. A California firm can publish a page about federal law; the two fields let you say so.
• One credential object per admission. An attorney admitted in three states gets three EducationalOccupationalCredential entries with three different validIn values. Collapsing them into "licensed in CA, NY, and DC" as one string throws away the structure you came for.
• Put the licensing authority's directory URL in sameAs. Most state bars publish a public licensee lookup. That link is independent confirmation that the person exists and holds what you say they hold, which is worth more than any amount of self-description.
• Audit admissions against the registry, not against the bio. Statuses lapse, attorneys move firms, and inactive is not the same as admitted. Markup asserting a current license is a claim about regulated status.

Practice-area pages are already the right shape, and mostly wasted

Law firm sites have a structural advantage over almost every other industry: the practice-area page. It is a topic with a natural scope, a natural jurisdiction, a natural named expert attached to it, and a well-defined set of questions people bring to it. Retrieval systems want exactly that unit — a bounded topic, authored, scoped, and answerable. Firms build the structure and then fill it with brochure copy.

"Our attorneys bring decades of combined experience to complex commercial litigation matters" contains no proposition. Nothing in it can be extracted, cited, contradicted, or checked. It exists because a partner approved it, and it will never appear in an answer, because there is no question to which it is the answer.

What gets cited is the page that answers what someone actually asks at eleven at night: how long do I have, what has to be true for me to have a case, what happens at the first hearing, what does this cost, who pays if I lose. Process and timing questions are badly served across the whole category and they are unusually quotable, because the answers are short, factual, and jurisdictional.

• One practice area, one jurisdiction, one page. A page covering employment claims across three states will be extracted for the wrong one, and there is no way to tell which.
• Answer in the first two sentences. Lead with the question and its answer; the firm's credentials go underneath. This is the opposite of how most practice-area pages are ordered.
• Use the client's words next to the term of art. Somebody searching for how to get out of a lease is asking about commercial lease termination, and the page that contains both phrasings matches the question and the law.
• Link attorneys and practice areas in both directions. The practice-area page names the attorneys who work in it; each bio names the practice areas. Relationships stated from both ends are easier for anything reading the site to resolve into an entity.
• Resist the urge to answer everything. A page that thoroughly answers six real questions about one thing outperforms a page that gestures at forty.

A confidently cited superseded statute is worse than no page at all

Everywhere else, stale content is a quality problem. Here it produces active misinformation, and the confidence is what does the harm. A well-written page from 2019 describing a rule that has since been amended looks identical, to any retrieval system, to a page describing current law. It has a citation. It has an author. It reads authoritatively. The engine will hand the repealed rule to a reader in exactly the same tone it uses for the current one.

Three dates matter and most legal sites record one. When the page was first published, when its text last changed, and when a licensed attorney last confirmed it still states the law are separate facts. The third is the one that carries the risk, and a single dateModified that moves whenever someone fixes a typo actively conceals it. Show the review date, mark it up, and only print it when a review happened.

• Keep a register mapping pages to the authorities they rely on. When a section is amended or a decision is overruled, the question "which of our pages does this break" should take minutes to answer, not a weekend of searching your own site.
• Fix it or take it down. A page you cannot currently verify should not sit live looking current. Unpublishing is a legitimate answer and it is faster than a rewrite.
• Say what changed, in the body. "Updated 22 July 2026 to reflect the amendment effective 1 January 2026" is a sentence that survives extraction and tells a reader they are looking at maintained material. A version banner in the chrome does not.
• Label historical content in its first sentence. Analysis of a repealed provision has genuine value; a reader arriving at a fragment of it needs to learn that from the fragment, not from a badge above the headline.
• Assume caching. Assistants, index snapshots, and aggregators all keep copies. You cannot recall a wrong statement of law once it is out. You can only shorten how long it was published and make the live page unambiguous about its own currency.

There is a retrieval-side argument for the same discipline: Ahrefs' 2026 analysis found that AI-cited URLs skew roughly 25.7% fresher than the web at large (source). Take that as a reason to fund a real review cadence. Do not take it as a reason to bump timestamps on pages nobody read.

Related reading: trust and authority signals for the general credibility patterns, schema markup for the markup mechanics, and the glossary for terminology.

This page is general guidance on publishing practice for law firms and legal information publishers. It is not legal advice, and it is not a statement of any jurisdiction's rules of professional conduct. Advertising rules, unauthorized-practice rules, and admission requirements differ by jurisdiction — check yours, and route content changes through whoever handles your bar compliance. Statutory citations here are illustrative examples of citation form, not legal conclusions.