The Complete Schema Markup Guide for Service Businesses (2026)

Schema markup is a structured data layer that helps search engines and AI systems understand your business information more accurately. It tells Google, ChatGPT, Perplexity, and other tools what your business does, where you do it, what services you offer, and what customers say about you — in a machine-readable format.

Without schema, search engines and AI systems have to interpret your website's plain text and infer what your business is. Sometimes they get it right. More often they get it partially right or miss important details. Schema markup reduces that ambiguity by providing structured, verifiable facts.

This guide covers the schema types a service business may need, why each one matters, and how they work together. Schema can support eligibility for applicable search features, but it does not guarantee rankings, rich results, or AI citations. Google's documentation is clear that structured data is not a direct ranking factor — it helps search engines understand your content, which can indirectly improve visibility.

Need this implemented for you? Explore our Schema Markup Services for service businesses.

What Is Schema Markup?

Schema markup is a standardized code format — specifically JSON-LD (JavaScript Object Notation for Linked Data) — that you embed in your website's HTML to provide search engines with structured, machine-readable information about your business.

Think of it this way: your website's visible text is written for humans. Schema markup is the same information rewritten for machines. Both exist on the same page, but they serve different audiences.

When Googlebot or GPTBot crawls your site, it reads both. The visible content helps it understand context. The schema markup gives it structured facts it can use to accurately identify your business, services, and content.

Schema markup does not change how your website looks to human visitors. It is invisible code that lives in your page's HTML head or body. But it helps search engines and AI systems interpret your site more accurately and efficiently.

Schema Markup for Service Businesses

The right schema depends on the entities and content your website actually represents. A service business commonly uses Organization or LocalBusiness, Service, BreadcrumbList, and Article or BlogPosting markup. FAQPage can be appropriate when visible FAQs are present. Product, Offer, Review, and Person markup should only be used when the page genuinely contains that information.

The Essential Schema Types for Service Businesses

1. LocalBusiness Schema

This is the foundation. LocalBusiness schema tells search engines your business name, address, phone number, service area, business category, operating hours, price range, and website URL. It is your business's identity card for every search engine and AI system on the internet.

Without LocalBusiness schema, a search engine has to piece together your business information from scattered text across your pages. It might find your phone number in the footer, your address on the contact page, and your business name in the header — but it has no structured way to confirm that all of these belong to the same entity.

With LocalBusiness schema, you provide a single, structured data object that says: this is who we are, this is where we are, this is what we do, here is how to reach us. No guessing required.

Critical fields to include: name, telephone, email, address (with full postal breakdown), geo coordinates, areaServed (list every city and region you serve), priceRange, openingHoursSpecification, and sameAs (links to your social profiles and secondary domains).

2. FAQPage Schema

FAQPage schema structures your frequently asked questions and answers into a format that search engines and AI systems can read and process. It maps visible Q&A content into structured data that is easier for these systems to parse and use.

When a homeowner asks ChatGPT "how much does a new roof cost" and your roofing website has a FAQPage schema with that exact question and a clear, specific answer, the structured format makes it easier for ChatGPT to process and attribute your answer. Without FAQPage schema, your answer is plain text that ChatGPT has to interpret from the surrounding page context.

Best practices for FAQPage schema: write questions in the exact language your customers use (not industry jargon), lead every answer with the direct response before adding context, and organize questions by service category if you offer multiple services. Each FAQ section should have its own FAQPage schema, but only one FAQPage schema per page to avoid duplicate field errors.

Important update on FAQ rich results: Google discontinued FAQ rich results in 2026. FAQPage schema no longer produces the expandable FAQ snippets that previously appeared in search results. However, FAQPage structured data still has value — it provides organized question-and-answer information that search engines and AI systems can read and process, even without a visible rich result. Do not implement FAQPage schema expecting FAQ rich results to appear in Google search.

You can verify current rich result eligibility in Google's Rich Results Test and review Google Search Central documentation for the latest status of each structured data feature.

3. Service Schema

Service schema describes each individual service your business offers as a distinct structured data entry. For a general contractor who does roofing, siding, gutters, and deck building, that means four separate Service schema entries — each with its own name, description, service area, and provider reference.

Structured service descriptions help search engines and AI systems match specific service queries to specific businesses. When someone asks "who does deck building in [city]," having a Service schema entry where the serviceType matches deck building and the areaServed includes that city provides clear, structured information about your offering. Without Service schema, search engines have to infer your services from page content.

Adding Service schema does not cause AI systems to automatically recommend your business. It makes your service information more accessible and accurately structured — which can support better understanding, but is not a guarantee of citation or recommendation.

4. Contact Page and About Page Schema Considerations

Contact pages should clearly expose real contact details and connect them to the Organization or LocalBusiness entity. About pages should explain the actual business and, where a real person is represented, may use Person schema for that person. Do not add invented employees, awards, credentials, or locations.

5. Review and AggregateRating Schema

Review schema structures your customer testimonials into machine-readable review objects. Each review includes the reviewer's name, their rating, and their review text. AggregateRating schema summarizes your overall rating and total review count.

Eligibility and policy considerations: Google has specific policies for review and rating structured data. Self-serving reviews — where a business marks up reviews about itself on its own pages — are generally not eligible for rich results in Google search. Google's guidelines state that reviews must be genuine and independent. Reviews that you collect on your own website and mark up with Review schema may not produce review rich results. Reviews on third-party platforms like Google Business Profile, Yelp, or industry-specific review sites are handled differently.

AggregateRating schema is subject to similar policies. Google may disregard aggregate ratings that appear self-serving or that cannot be verified against an external source. If you implement Review or AggregateRating schema, ensure the reviews are genuine, that the rating values are accurate, and that you are following Google's current structured data policies. Review Google Search Central's documentation on review snippets for the most current eligibility requirements.

Every Review schema object should include an itemReviewed field that references back to your organization. Without this field, Google flags the review as invalid.

6. Organization Schema

Organization schema establishes your business as a recognized entity in Google's knowledge graph. It includes your business name, logo, description, founding location, contact information, and social media profiles.

For businesses operating nationally or across multiple markets, Organization schema supports entity recognition. It tells search engines that your business is a distinct, verifiable entity — not just a collection of web pages.

Include a knowsAbout field listing your areas of expertise. This provides structured information about the topics your business covers, which can support topical authority signals.

7. WebSite Schema

WebSite schema describes your website as a whole — its name, URL, publisher, and description. A SearchAction property can be included to describe site search functionality.

Update on sitelinks search box: Google discontinued the sitelinks search box feature in November 2024. Including a SearchAction property in your WebSite schema no longer produces a search box in Google search results. The SearchAction property can still describe your site's search functionality for other systems, but do not implement it expecting the sitelinks search box to appear.

This is a supporting schema type rather than a primary one, but it helps search engines understand how your individual pages relate to your overall web presence and who publishes the content.

8. BreadcrumbList Schema

BreadcrumbList schema shows the navigation hierarchy of each page on your site. For a blog post, it might show Home, Blog, Post Title. For a service page, it might show Home, Services, Roofing.

Google can use breadcrumb schema to display enhanced navigation in search results. Search engines and AI systems also use it to understand how your content is organized and how pages relate to each other. It is a small addition that improves both user experience and crawlability.

How Schema Types Work Together

Individual schema types are valuable on their own. But they are most effective when they connect. Your LocalBusiness schema identifies your business. Your Service schema describes what you do. Your FAQPage schema answers questions about those services. Your Review schema provides customer feedback data. Your Organization schema establishes you as a recognized entity. Your WebSite schema ties it all together.

Search engines and AI systems evaluate this entire web of structured data to build a more complete picture of your business. A website with multiple schema types implemented correctly gives these systems a comprehensive, machine-readable understanding of the business. A website with none of it forces the systems to infer everything from plain text — which is less reliable.

However, implementing schema does not guarantee that AI systems will cite or recommend your business. Schema makes your information more accessible and accurately structured. It is one factor among many — including content quality, backlinks, reviews, and brand authority — that influence how search engines and AI systems evaluate your business.

AreaServed and Service-Area Considerations

Use AreaServed to describe the locations your business genuinely serves. It should reflect the visible service area on your website and should not be used to imply offices or storefronts that do not exist.

Structured Data Validation and Common Schema Mistakes

Validate JSON-LD with Google's Rich Results Test and the Schema Markup Validator. Common mistakes include marking up content that is not visible on the page, using fake ratings or reviews, adding unsupported properties, creating duplicate entities, and leaving outdated business details in the markup. Schema should be updated whenever the visible page content changes.

A Simple LocalBusiness JSON-LD Example

Here is a minimal, technically valid LocalBusiness JSON-LD example for a service business. In practice, you would include additional fields like areaServed, openingHoursSpecification, and sameAs to provide a more complete picture.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business Name",
  "telephone": "+1-555-555-5555",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Hudson",
    "addressRegion": "FL",
    "postalCode": "34667",
    "addressCountry": "US"
  },
  "url": "https://www.yourbusiness.com",
  "priceRange": "$"
}
</script>

This is a starting point. A complete implementation includes Service schema for each offering, BreadcrumbList for navigation, and FAQPage for any visible question-and-answer content. Validate every implementation with the Rich Results Test before publishing.

How to Check Your Current Schema

Run your website through Google's Rich Results Test at search.google.com/test/rich-results. It will show you every schema type detected on your page, flag any errors, and tell you which rich result types your page is eligible for.

You can also view your schema directly by looking at your page's source code and searching for "application/ld+json" — every JSON-LD schema block on your page will appear in a script tag with that type.

When we run free AEO audits for service businesses, schema analysis is the first thing we check. Most service business websites have zero structured data. The ones that do often have errors that need correction — missing required fields, duplicate schema types on the same page, or references to the wrong domain.

Implementation: DIY vs Professional

Schema markup requires adding JSON-LD code directly to your website's HTML. If you are comfortable editing code or working with a developer, the schema.org documentation provides the full specification for every schema type.

However, schema implementation has several technical requirements that are easy to get wrong. Each schema type has required and recommended fields. Some fields reference other schema objects by ID. Duplicate schema types on the same page cause validation errors. And the schema must be present in the raw HTML source — not injected by JavaScript after the page loads — or crawlers cannot read it.

For service businesses that want it done right the first time, our AEO Sprint includes full schema implementation in 7 business days. For new website builds, every site in our portfolio ships with a complete schema suite from day one. See our AEO services and SEO services for the full scope of what we do.

Frequently Asked Questions About Schema Markup

Does schema markup directly improve my Google rankings?

No. Schema markup is not a direct ranking factor. Google's documentation is clear on this. However, structured data helps search engines understand your content more accurately, which can indirectly improve visibility. It can also enable certain search features when eligible. The indirect benefits are real, but schema alone does not improve rankings.

Does schema markup guarantee rich results in Google?

No. Schema markup makes your pages eligible for rich results, but Google decides whether to display them based on its own algorithms and policies. Additionally, some rich result types have been discontinued. FAQ rich results were discontinued in 2026, and the sitelinks search box was retired in November 2024. Always check Google Search Central documentation for current eligibility.

Is structured data required for Google AI Overviews?

No. Google's generative AI search features do not require structured data to appear. Pages without any schema markup can still be cited in AI Overviews. However, structured data can help Google understand your content more accurately, which may support better representation in AI-generated answers. It is a helpful factor, not a requirement.

Can I add schema markup to a WordPress site?

Yes, but with caveats. Plugins like Rank Math and Yoast can generate some schema types automatically. However, they typically only cover basic LocalBusiness and Article schema. Full implementation — including FAQPage, Service, Review, and SpeakableSpecification — usually requires custom JSON-LD code added manually or through a developer.

How many FAQs should I include in FAQPage schema?

There is no specific number that is a ranking requirement. Include as many genuine question-and-answer pairs as you have visible on the page. Each FAQ section should have its own FAQPage schema, and only one FAQPage schema per page to avoid duplicate field errors. Focus on answering real customer questions accurately rather than reaching an arbitrary count.

Will schema markup help me show up in ChatGPT?

Schema markup helps ChatGPT's crawler (GPTBot) understand your business more accurately by providing structured information. However, ChatGPT does not guarantee citation based solely on the presence of schema. The structured information schema provides — clear business identity, services, FAQs, reviews — can make your content easier to interpret, but ChatGPT's recommendations depend on many factors including content quality, web-wide citations, and brand authority.

How do I know if my schema has errors?

Use Google's Rich Results Test at search.google.com/test/rich-results. Paste your page URL and it will show all detected schema, flag errors (red), warnings (yellow), and valid items (green). You can also use the Schema Markup Validator at validator.schema.org for broader validation beyond just Google's rich result types.

What is the difference between JSON-LD and Microdata?

Both are formats for adding structured data to web pages. JSON-LD is a standalone script block you add to your HTML head — it does not mix with your visible content. Microdata adds schema attributes directly to your HTML elements. Google recommends JSON-LD as the preferred format, and it is significantly easier to implement, maintain, and debug than Microdata.

Does adding Service schema make AI engines recommend my business?

No. Service schema makes your service information more accessible and accurately structured for search engines and AI systems. It does not cause AI systems to automatically recommend your business. AI recommendations depend on many factors — content quality, web-wide authority, reviews, brand recognition, and the specific query being asked. Schema is one helpful factor, not a guarantee.