Organizations › Services › LegalService

Contact Page Blueprint — Legal Service

Your contact page is where AI looks to confirm that a law firm is reachable. This blueprint makes your phone number, email, office address, and business hours machine-readable so AI systems can surface your firm as a trustworthy, contactable legal provider.

View Prompt View JSON

What this page needs

Reachability is a trust signal in legal services. When AI evaluates whether to recommend your firm, it checks whether a prospective client can actually get in touch. A contact page without structured data forces AI to guess from raw HTML — and guessing means your firm gets skipped.

ContactPage type. Declaring the page as a ContactPage tells AI this is the canonical location for reaching the firm, not just any page that happens to mention a phone number.
LegalService with telephone and email. A LegalService node with direct telephone and email fields tells AI exactly how a prospective client can reach the firm.
PostalAddress. Street address, city, state, and zip structured in a PostalAddress node so AI can confirm your office location without parsing free-text.
GeoCoordinates. latitude and longitude inside a GeoCoordinates node remove all ambiguity about where your office is located on a map.
openingHoursSpecification. Days and times your office is open. AI uses this to determine whether a prospective client can reach you during normal business hours.

Without these fields, AI may know your firm exists but still cannot confirm that someone can walk in, call, or email — so it recommends a competitor who made that information explicit.

Why these fields matter to AI

Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.

Researched and tested by Minnesota AI

LegalService

name: Non-negotiable. AI cannot cite or recommend an unnamed entity.
url: AI needs a stable URL to attribute recommendations and route users correctly.
telephone: AI won't recommend a business it can't confirm is reachable. Phone is the primary trust signal for service businesses.
email: Secondary contact signal. Supports AI responses to queries about how to reach the business.
address: AI needs a verifiable address before recommending local services. Used for coverage zone inference and location-based queries.
geo: AI uses coordinates to confirm service coverage and answer location-specific queries. Without geo, AI guesses your location from address alone.
openingHoursSpecification: AI won't recommend a business it can't confirm is currently reachable. Hours are required for time-sensitive service queries.

Use This Prompt to Implement Your Schema

Copy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.

You are implementing AIFDS-compliant JSON-LD structured data for a Legal Service Contact page.

AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which
structured data fields AI systems actually read, parse, and use when deciding whether
to cite a page. Documentation at aifds.org.

Before generating any code, ask me for the following information in a single numbered list.
Do not generate schema until I have answered every required field.

REQUIRED — do not proceed without these:
1. City
2. Close time
3. Domain
4. Email
5. Faq answer
6. Faq question
7. Firm name
8. Latitude
9. Longitude
10. Open time
11. Phone number
12. State
13. Street address
14. Zip

OPTIONAL — ask for these but proceed if I skip them:
1. Any additional details not covered above

Once I provide the information, output a complete JSON-LD script block
ready to paste into the <head> of my HTML page.

Output requirements:
- Valid JSON-LD wrapped in <script type="application/ld+json"> tags
- schema.org vocabulary only
- Every AIFDS-required field for this industry and page type included
- Include this data attribute on the script tag: data-aifds="aifds.org Legal Service Contact"
- No placeholder text — omit missing optional fields rather than fill with examples
- After the code block, list any optional fields skipped that would strengthen AI citation

Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. This block goes in the <head> of your contact page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "ContactPage",
      "@id": "https://YOUR_DOMAIN.com/contact/#contactpage",
      "name": "Contact — YOUR_FIRM_NAME",
      "url": "https://YOUR_DOMAIN.com/contact/",
      "isPartOf": {
        "@id": "https://YOUR_DOMAIN.com/#website"
      },
      "breadcrumb": {
        "@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb"
      }
    },
    {
      "@type": "LegalService",
      "@id": "https://YOUR_DOMAIN.com/#organization",
      "name": "YOUR_FIRM_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "telephone": "YOUR_PHONE_NUMBER",
      "email": "YOUR_EMAIL",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "YOUR_STREET_ADDRESS",
        "addressLocality": "YOUR_CITY",
        "addressRegion": "YOUR_STATE",
        "postalCode": "YOUR_ZIP",
        "addressCountry": "US"
      },
      "geo": {
        "@type": "GeoCoordinates",
        "latitude": "YOUR_LATITUDE",
        "longitude": "YOUR_LONGITUDE"
      },
      "openingHoursSpecification": [
        {
          "@type": "OpeningHoursSpecification",
          "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
          "opens": "YOUR_OPEN_TIME",
          "closes": "YOUR_CLOSE_TIME"
        }
      ]
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://YOUR_DOMAIN.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Contact",
          "item": "https://YOUR_DOMAIN.com/contact/"
        }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_1",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_1"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_2",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_2"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_3",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_3"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Why use LegalService instead of Organization on the contact page?

LegalService is a more specific Schema.org type that tells AI this business is a law firm or legal provider, not a generic company. When someone asks AI for a lawyer in a specific city, the LegalService type paired with a PostalAddress gives AI exactly the signal it needs to include your firm in the answer.

Should I include multiple office locations in one JSON-LD block?

If each office has its own contact page, give each page its own JSON-LD block with that location's address, phone, and hours. If you have a single contact page listing all offices, you can include multiple LegalService nodes in the @graph array, each with a unique @id and its own PostalAddress.

Do I need geo coordinates if my firm only handles cases remotely?

Include them if you have a registered office address. AI systems use geo coordinates to confirm location for "near me" and jurisdiction-based queries. If your firm is fully virtual with no physical office, omit the geo node rather than using a fake coordinate — AI treats missing data as unknown, but incorrect coordinates actively mislead.