LocalBusiness Schema for a Service Business: What to Mark Up and What to Leave Out

Structured data is a way to describe information already on a page in a machine-readable format. For an eligible local business, LocalBusiness markup can help Google understand details such as its name, location and opening hours. It does not guarantee a rich result, a higher position or inclusion in an AI answer.

Start with the official LocalBusiness documentation and general structured data policies. Supported properties and feature eligibility can change.

Make a visible-facts inventory

Before writing JSON-LD, list each fact and the public page that supports it:

• Business name and website: Use the real name and canonical site URL shown to customers.
• Business type: Choose the closest applicable schema type; do not call an online-only operation a storefront.
• Address or service area: Publish only what customers should genuinely see. Do not expose a private home address just to complete a field.
• Hours and contact details: Match the site and public profile, and avoid stale holiday hours.
• Image and logo: Use assets you own and that represent the business.

If a fact cannot be verified in your own public copy, correct the visible page first. Markup is not a place to add a claim you would avoid showing a customer.

Pick the right level of detail

An Organization description may be enough for a remote service. LocalBusiness is more specific when the business genuinely has a local presence and the properties apply. Mark up a particular location only if it is real. If you serve customers at their premises and hide your address from the public profile, be careful not to publish that private address in page source.

Do not mark every generic FAQ or testimonial in hopes of a special display. Eligibility for search features has separate rules, and markup must reflect the visible page. Google's AI feature guidance says no special AI schema is required.

Validate in two passes

First, use Google's Rich Results Test to catch syntax and supported-property errors. A valid result means the code is parseable for a supported feature; it is not a promise that the feature will appear.

Second, inspect the actual deployed URL with Search Console's URL Inspection tool if you have access. Compare the rendered page, canonical URL and structured data with the page customers see. Check after deployment, not only in a local preview. If several pages carry the same organization data, keep the core facts consistent.

A practical stopping rule

If your service page does not yet explain what you do, who it is for, where you operate and how to contact you, improve that copy before spending an afternoon on nested schema properties. The website audit checklist starts with those basics. The free AI Visibility Score can flag website signals to investigate, while the Full Report adds human review across your public presence.