SEO
Schema Markup for Local Service Websites: The Five Types That Drive SEO and AI Citations
A practical structured data guide for contractors and local service businesses — which schema types matter, how to fill areaServed correctly, the mistakes that void your markup, and how to validate it.
Structured data is the least glamorous and most reliably underused lever in local search. It does not write your content, earn your links, or answer your phone. What it does is remove ambiguity — and ambiguity is the reason a search engine shows a competitor's rich result instead of yours, and the reason an AI assistant names a directory instead of your business.
This guide covers the five schema types that carry nearly all the value for a local service business, how to populate the fields that actually get read, the errors that quietly void otherwise correct markup, and how to validate the result. It assumes no prior JSON-LD experience.
If you have not yet handled the fundamentals this sits on top of, start with the local SEO playbook and the guide to AI search optimization for local services.
What schema does and does not do
Schema markup is machine-readable metadata describing what a page is about. It is not a ranking factor in the way a backlink is. It is an eligibility and clarity mechanism: it makes you eligible for rich results, and it lets a parser extract your facts without inference.
That second function is why structured data has become disproportionately valuable in the AI era. A retrieval system deciding whether to name your business needs to know your service area, your services, your hours, and your rating with confidence. Schema hands it those fields directly instead of asking it to guess from prose and a footer.
Use JSON-LD in a script tag rather than microdata; it is what Google recommends and it is far easier to maintain because it lives in one block instead of being woven through your HTML.
The five types that matter
Ignore the long tail of schema types. For a local service business, five carry the load, and each maps to a specific page role.
Effort vs. payoff by schema type
Our internal prioritization for a local service site with no existing markup. Payoff blends rich-result eligibility and observed AI extraction quality.
- LocalBusiness subtype10score (0-10) · Low effort, foundational
- FAQPage9score (0-10) · Low effort, high AI citation value
- Service (per page)8score (0-10)
- BlogPosting6score (0-10) · Usually automated by the template
- HowTo5score (0-10) · Narrower fit, still useful
- Review / AggregateRating4score (0-10) · Constrained by policy — see below
1. LocalBusiness (use the specific subtype)
This is your identity block, placed on the homepage and your contact or about page. Prefer the narrowest subtype that fits — RoofingContractor, HVACBusiness, Plumber, Electrician, MortgageLoanCompany, LandscapingBusiness — falling back to LocalBusiness only when nothing fits. Populate name, url, telephone, address, geo, openingHoursSpecification, priceRange, image, sameAs (your Google Business Profile, social, and directory URLs), and areaServed. The sameAs array is how you tell a machine that all those scattered listings are the same entity as you.
2. Service (one per offering)
On each service page, describe the offering itself: serviceType, provider pointing back to your LocalBusiness, areaServed with named cities, and an offers block with an aggregate price range where you can state one honestly. This is the markup that makes a page about roof leak repair legible as a service and not just an article.
3. FAQPage (on every service and cost page)
The highest-ROI markup for AI citation, because it pairs an explicit question with a bounded answer. Rules: the questions and answers must be visibly present on the page, each answer should be self-contained in roughly 40–80 words, and you should not mark up a page as an FAQPage when the content is really a product listing with a couple of questions bolted on.
4. HowTo (on process and DIY-adjacent content)
For process explanations — what happens during an inspection, how an insurance claim proceeds, how to shut off water before a plumber arrives — HowTo with named steps gives a parser a clean sequence to reuse. Keep steps in the same order as the visible content and name each one plainly.
5. BlogPosting / Article (on every post)
Include headline, description, datePublished, dateModified, author, publisher, and image. dateModified matters more than most people realize: recency weighting is real for cost and regulation topics, and an honest dateModified after a substantive revision is the correct way to signal it.
areaServed: the field local businesses get wrong
Most implementations either omit areaServed or fill it with a vague radius like "50 mile service area." Both are wasted opportunities, because location-scoped queries match against named places.
List explicit cities as an array of City objects — the suburbs and towns you genuinely serve, with correct spellings and no aspirational padding. If you serve a whole county, name the county and the principal cities inside it. If your coverage genuinely differs by service (emergency work within 20 miles, replacements metro-wide), reflect that in each Service block rather than flattening it into one claim.
Two guardrails. Do not claim a city you cannot dispatch to; the mismatch surfaces in reviews and erodes the corroboration you are trying to build. And do not list cities in schema that have no corresponding visible content — the markup should describe the page, not invent coverage.
The mistakes that void otherwise correct markup
Contradicting the visible page. If schema says you open at 7am and the page says 8am, you have introduced exactly the ambiguity you were trying to remove. Generate schema from the same source of truth that renders the page whenever possible.
Marking up content that is not there. Invisible FAQ answers, HowTo steps that appear nowhere, or reviews that no user can read are policy violations and can cost you rich-result eligibility entirely.
Self-serving AggregateRating. Marking up ratings you collected yourself and display on your own site is restricted; ratings on third-party platforms are theirs to expose, not yours to re-mark. Get the reviews on the platforms that count instead of trying to inject stars into your own SERP snippet.
Duplicate LocalBusiness blocks. One canonical identity block, referenced by @id from your Service blocks. Multiple conflicting definitions across pages fragment the entity.
Set-and-forget. Phone numbers change, service areas expand, hours shift seasonally. Stale schema is misinformation with extra steps. Review it twice a year.
Validating and maintaining it
Run every template through Google's Rich Results Test and the Schema.org validator — the first tells you what Google will act on, the second catches structural errors Google silently tolerates. Then check the Enhancements reports in Search Console over the following weeks, since real-world crawling surfaces problems no test harness does.
For AI extraction, add a manual check: paste your page URL into an assistant and ask it to summarize your service area, pricing, and hours. If it gets any of them wrong or hedges, your markup and your visible content are not aligned yet.
Build schema from data, not by hand. Keep your business facts and service definitions in one structured place and render both the page and the JSON-LD from it. That is the only way markup stays accurate as the business changes, and it is how we implement it as part of our SEO and AI optimization work.
A one-afternoon implementation order
Start with a single LocalBusiness subtype block on the homepage with complete NAP, sameAs, hours, and named areaServed. That alone resolves the most common identity ambiguity.
Next, add Service schema to your top revenue pages, each pointing at the LocalBusiness @id. Then add visible FAQ sections with FAQPage markup to those same pages — write the answers first, mark them up second.
Finish by confirming your blog template emits BlogPosting with dateModified, then validate everything and schedule a calendar reminder to re-check in six months. That sequence takes a focused afternoon and captures most of the available value.
Frequently Asked
Questions & answers
Which schema type should a contractor use?
The narrowest LocalBusiness subtype that fits — RoofingContractor, HVACBusiness, Plumber, Electrician, LandscapingBusiness — plus Service schema on each service page and FAQPage on pages with visible question-and-answer content.
Does schema markup improve rankings?
Not directly. It makes you eligible for rich results and lets search and AI systems extract your facts without guessing, which improves visibility and citation rates rather than raw position.
How should I fill in areaServed?
As an array of named City (and where relevant County) objects covering places you genuinely dispatch to. Named places match location-scoped queries; a mileage radius does not.
Can I add star ratings to my own site with schema?
Self-serving AggregateRating on your own business is restricted and generally will not produce stars in search results. Collect reviews on third-party platforms instead.
Do FAQ answers have to be visible on the page?
Yes. Marking up content users cannot see violates structured data policy and risks losing rich-result eligibility across the site.
How often should schema be reviewed?
At least twice a year, and immediately after any change to hours, phone number, address, service list, or service area.
Put this into practice
Check your market for exclusive leads
See whether your service area and category are still open for exclusive representation.
Check availability