Yes — Service schema (a Product subtype) is the right choice for service businesses. Don't use the generic Product schema for services; use Service, with proper offers, areaServed, and provider properties.
One of the most common schema mistakes among service businesses is implementing generic Product schema (designed for physical goods) instead of the appropriate Service schema.
**The right schema for services:**
Use `@type: "Service"` (or for local services, `@type: "LocalService"` if applicable, though this is less standardized). Service is a proper Schema.org type with full property support.
Basic structure:
{ "@context": "https://schema.org", "@type": "Service", "serviceType": "Plumbing services", "provider": { "@type": "LocalBusiness", "name": "Your Business Name", "url": "https://yoursite.ca" }, "areaServed": [ {"@type": "City", "name": "Ottawa"}, {"@type": "City", "name": "Kanata"}, {"@type": "City", "name": "Nepean"} ], "hasOfferCatalog": { "@type": "OfferCatalog", "name": "Plumbing Services", "itemListElement": [ {"@type": "Offer", "name": "Drain cleaning", "priceRange": "$150-$400 CAD"}, {"@type": "Offer", "name": "Water heater installation", "priceRange": "$1500-$3500 CAD"} ] }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.8", "reviewCount": "127" } }
**Why this matters:**
Google uses Service schema to populate the Knowledge Panel, Service Listings in Maps, and increasingly the AI Overview "what services does X provide" responses. Generic Product schema applied to services causes occasional misclassification (e.g., your service appearing in shopping-related surfaces where it shouldn't).
**The areaServed property is critical for service-area businesses.** Without it, Google has no structured signal for which geographic markets you actually serve, even if your website mentions city names.
**Common mistakes to avoid:**
1. **Using Product schema with category: "Service".** Schema.org parsers tolerate this but don't reward it. Use the proper Service type. 2. **Including `@type: "Offer"` with prices when you don't actually have public pricing.** Don't fabricate prices for schema; either include real ranges or omit Offer entirely. 3. **Listing every city in your province as areaServed.** This is read as spam. List the cities you genuinely serve and could deliver to within a reasonable timeframe. 4. **Combining multiple Service schemas on one page when one Service with hasOfferCatalog is cleaner.** A "plumbing services" page should have ONE Service schema describing plumbing services, with multiple Offers inside it — not 12 separate Service schemas.
**For local service businesses, layer LocalBusiness schema with Service schema** (LocalBusiness on your homepage and contact page; Service on each individual service page). Don't put both on every page — that creates duplicate signal noise.
- **Should I use JSON-LD, Microdata, or RDFa for schema markup?** — JSON-LD, period. Google has explicitly stated JSON-LD is preferred since 2017. Microdata and RDFa still parse correctly but add no benefit and complicate maintenance. Strip out any old Microdata when you migrate. - **Is FAQ schema still worth implementing in 2026?** — Yes, but with reduced expectations. Google removed FAQ rich snippets from most non-authoritative sites in August 2023 and continued tightening through 2024–2025. FAQ schema still helps with semantic understanding and AI Overview citations, even when rich snippets don't display. - **How do I add AggregateRating schema without violating Google's guidelines?** — Only mark up reviews that are genuinely visible on the page, came from real customers, and are first-party (collected by you, not aggregated from elsewhere). Google's 2019 review snippet update made fake or third-party-aggregated review markup ineligible for rich results. - **Should I add Author schema for E-E-A-T?** — Yes — Author/Person schema with sameAs links to professional profiles is one of the few concrete technical things you can do to signal E-E-A-T. Pair it with a real bio page, byline on every article, and verified author identity across platforms.