Organizations › Services › GeneralContractor

Service Areas Blueprint — General Contractor

Your service areas page tells AI exactly where you work. This blueprint structures your geographic coverage into machine-readable city, county, and region entries so AI systems can confidently recommend you for location-specific construction queries.

View Prompt View JSON

What this page needs

Location is the most common filter in contractor searches. When someone asks AI "find a general contractor in Lakeville" or "who does remodels in the Twin Cities metro," AI needs structured geographic data to match you. A service areas page without structured data forces AI to parse paragraph text for city names — and it misses most of them.

areaServed with explicit entries. The areaServed array on your GeneralContractor node should list every city, county, or region you serve. Each entry should use the appropriate Schema.org type: City, AdministrativeArea, or State.
City entries for specific coverage. List each city by name using City type. This is the most precise signal and directly matches "contractor in [city]" queries.
AdministrativeArea for counties or regions. If you serve entire counties or metro regions, use AdministrativeArea with the region name. This catches broader queries like "contractor in Hennepin County."
WebPage with geographic context. The WebPage node should describe this as a service areas page so AI understands the purpose of the content.

Without structured area data, AI may know you exist but cannot confirm whether you serve the location the user is asking about — so it recommends a competitor whose coverage is 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

GeneralContractor

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.
areaServed: AI filters service recommendations by coverage zone. Without this, AI may recommend you for queries outside your area or exclude you from local 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 General Contractor Service Areas 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. Company name
3. County
4. Domain
5. Faq answer
6. Faq question
7. Phone number
8. Service areas page description
9. Service areas page title
10. State

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 General Contractor Service Areas"
- 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. Add or remove entries in the areaServed array to match every city and region you actually serve.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "GeneralContractor",
      "@id": "https://YOUR_DOMAIN.com/#organization",
      "name": "YOUR_COMPANY_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "telephone": "YOUR_PHONE_NUMBER",
      "areaServed": [
        {
          "@type": "City",
          "name": "YOUR_CITY_1"
        },
        {
          "@type": "City",
          "name": "YOUR_CITY_2"
        },
        {
          "@type": "City",
          "name": "YOUR_CITY_3"
        },
        {
          "@type": "City",
          "name": "YOUR_CITY_4"
        },
        {
          "@type": "City",
          "name": "YOUR_CITY_5"
        },
        {
          "@type": "AdministrativeArea",
          "name": "YOUR_COUNTY_1"
        },
        {
          "@type": "AdministrativeArea",
          "name": "YOUR_COUNTY_2"
        },
        {
          "@type": "State",
          "name": "YOUR_STATE"
        }
      ]
    },
    {
      "@type": "WebPage",
      "@id": "https://YOUR_DOMAIN.com/service-areas/",
      "name": "YOUR_SERVICE_AREAS_PAGE_TITLE",
      "description": "YOUR_SERVICE_AREAS_PAGE_DESCRIPTION",
      "isPartOf": {
        "@id": "https://YOUR_DOMAIN.com/#website"
      },
      "breadcrumb": {
        "@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://YOUR_DOMAIN.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Service Areas",
          "item": "https://YOUR_DOMAIN.com/service-areas/"
        }
      ]
    },
    {
      "@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

Should I list every city I serve or just the major ones?

List every city you genuinely serve. AI matches location queries literally — if someone asks for a contractor in Eagan and Eagan is not in your areaServed array, you will not appear in the recommendation. The more complete your list, the more location queries you match.

What is the difference between City and AdministrativeArea?

Use City for specific municipalities and AdministrativeArea for counties, metro regions, or other administrative boundaries that contain multiple cities. For example, "Minneapolis" is a City while "Hennepin County" is an AdministrativeArea. Using both gives AI precise and broad coverage data.

Can I include areaServed on other pages too or just the service areas page?

You can and should include areaServed on your homepage and services page as well. The service areas page is where you provide the most comprehensive list, but repeating your primary areas on other pages reinforces the signal. Use the same @id for the GeneralContractor node across all pages so AI treats them as the same entity.