Schema & Structured Data for Home Services

Search engines read your website the way a person skims a foreign-language menu: they recognize some words, guess at the rest, and hope the picture helps. Structured data removes the guessing. It is a standardized vocabulary, defined at schema.org and supported by Google, Microsoft, and others, that lets you state in machine-readable terms exactly what a page means: this is a plumbing business, here is its phone number, these are the services it offers, this is the area it serves, and these are the questions it answers.

For a home-service business, that clarity translates into real outcomes. Rich results — star ratings, FAQ accordions, and breadcrumbs in the search snippet — can lift click-through rate. And as AI answer engines increasingly mediate how people find local contractors, the pages that are easiest for a machine to parse and attribute have a structural advantage. We explore that second benefit in depth in how to show up in ChatGPT and Perplexity.

This playbook covers the five schema types that matter most for contractors, with copy-adaptable JSON-LD, the testing workflow, and the mistakes that get markup ignored or, worse, penalized. It pairs with our local SEO for contractors guide and the visibility pillar.

---

What Structured Data Is (and Is Not)

Structured data is markup added to a page that describes its content using a shared vocabulary. Google strongly recommends the JSON-LD format: a block of JSON, placed in a <script> tag, that sits alongside your visible content without changing how the page looks.

It is not a ranking factor on its own. Google has said this repeatedly. What it does is make pages eligible for rich results and easier for engines to understand. Treat schema as a clarity-and-presentation layer, not a growth hack.

The cardinal rule, stated plainly in Google's structured data guidelines: only mark up content that is actually visible to users on the page. Invisible or fabricated markup is a policy violation.

---

The Five Types That Matter for Contractors

Schema type	What it describes	Where it goes
LocalBusiness (or subtype)	The business: name, phone, address, hours, area served	Homepage, contact, every page sitewide
Service	A specific job you perform	Each service page
FAQPage	Questions and answers shown on the page	Service pages, guides, FAQ sections
Review / AggregateRating	Real customer reviews and their average	Pages that display genuine reviews
BreadcrumbList	The page's position in the site hierarchy	Every deep page

You will not use all five on every page. The pattern is: LocalBusiness sitewide, Service and FAQPage on service pages, Review/AggregateRating where real reviews appear, and BreadcrumbList on anything below the homepage.

---

LocalBusiness: The Foundation

Start here. The LocalBusiness type (and its trade-specific subtypes like Plumber, Electrician, HVACBusiness, RoofingContractor) describes the business itself. Use the most specific subtype that fits your trade.

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Brand Plumbing",
  "image": "https://example.com/storefront.jpg",
  "telephone": "+1-555-0100",
  "url": "https://example.com",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Main St",
    "addressLocality": "Plano",
    "addressRegion": "TX",
    "postalCode": "75024",
    "addressCountry": "US"
  },
  "areaServed": [
    { "@type": "City", "name": "Plano" },
    { "@type": "City", "name": "Frisco" }
  ],
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "geo": { "@type": "GeoCoordinates", "latitude": 33.0198, "longitude": -96.6989 }
}

The non-negotiable detail: the name, address, and telephone here must be identical to your Google Business Profile and to every citation across the web. Inconsistent NAP data is one of the most common and most damaging local SEO mistakes, and schema is where it often diverges first.

---

Service: One Block Per Job

On each service page, add a Service block describing that single job. This reinforces the service-by-location grid that drives local SEO.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "serviceType": "Water Heater Installation",
  "provider": {
    "@type": "Plumber",
    "name": "Brand Plumbing",
    "telephone": "+1-555-0100"
  },
  "areaServed": { "@type": "City", "name": "Plano" },
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Water Heater Services",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Tankless installation" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Standard tank replacement" } }
    ]
  }
}

Keep serviceType aligned with the page's H1. The closer your markup mirrors the visible content, the cleaner the signal.

---

FAQPage: Structured Answers

If your page displays a genuine question-and-answer section, mark it up with FAQPage. The answers in the markup must match the answers shown on the page word for word in substance.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a water heater installation take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A standard tank replacement typically takes two to three hours. Tankless conversions can take a full day because they often require new gas, venting, or electrical work."
      }
    }
  ]
}

Well-formed FAQ content is also exactly the kind of concise, self-contained answer that AI answer engines like to lift and cite. That overlap is not a coincidence — see how generative AI chooses which sources to cite.

---

Review and AggregateRating: Handle With Care

Review markup is powerful and heavily policed. The review snippet guidelines are strict: the reviews must be genuine, first-hand, and visible on the page. You may not invent ratings, and you may not pull in reviews from third-party platforms you do not control and present them as your own.

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Brand Plumbing",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "126"
  },
  "review": {
    "@type": "Review",
    "author": { "@type": "Person", "name": "J. Martinez" },
    "reviewRating": { "@type": "Rating", "ratingValue": "5" },
    "reviewBody": "Same-day water heater replacement, clean work, fair price."
  }
}

If you do not yet display real reviews on the page, do not add this markup. Fabricated or self-serving review markup is the fastest route to a manual action. The underlying truth is that real reviews move revenue regardless of markup — the evidence is in the science of online reviews and in Google reviews for home service businesses.

---

BreadcrumbList: Show the Hierarchy

BreadcrumbList tells engines where a page sits in your site structure and can produce a breadcrumb trail in the search snippet.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com" },
    { "@type": "ListItem", "position": 2, "name": "Services", "item": "https://example.com/services" },
    { "@type": "ListItem", "position": 3, "name": "Water Heater Installation", "item": "https://example.com/services/water-heater-installation" }
  ]
}

This reinforces the internal-linking hierarchy described in our service and city pages guide.

---

Testing and Deployment Workflow

Never ship schema you have not validated. The workflow:

1. Draft the JSON-LD for the page type.
2. Run the Rich Results Test to confirm eligibility and catch errors and warnings Google cares about.
3. Run the Schema Markup Validator for general schema.org validity beyond Google's specific features.
4. Deploy, then monitor Google Search Console — the Enhancements and rich-results reports flag live errors and which pages are eligible.
5. Re-test after any template change, because schema breaks silently when a developer edits the surrounding markup.

In this project, schema validity is enforced in CI: invalid JSON-LD fails the build. That is the right posture for any serious site — broken schema is worse than no schema.

---

Common Mistakes

• Marking up invisible content. If users cannot see it, do not mark it up.
• Fabricated or borrowed reviews. A guaranteed policy violation.
• NAP mismatches between schema, Google Business Profile, and citations.
• Using generic LocalBusiness when a specific subtype (Plumber, HVACBusiness) exists.
• Stale data: hours, phone, or area served in schema that no longer match reality.
• Never re-testing after a site redesign or template change.
• Over-marking: stacking irrelevant types in the hope something sticks. Mark up what is true and present, nothing more.

---

Conclusion

Structured data will not magically lift your rankings, and any agency that promises it will is selling the wrong thing. What it does is make your pages unambiguous to the machines that decide how you are presented in search results and, increasingly, how you are quoted by AI answer engines.

Start with LocalBusiness sitewide. Add Service and FAQPage to your service pages, BreadcrumbList to deep pages, and Review/AggregateRating only where genuine reviews are displayed. Validate everything, keep your NAP consistent, and re-test after every change. To put this to work, pair it with our service and city pages guide, how to rank on Google Maps, how generative AI chooses which sources to cite, the visibility pillar, and the full blog.