Local Business Schema Examples

Most local businesses either have no schema or have plugin-generated schema that does not match the page. This pack helps you create cleaner JSON-LD you can edit, validate, and hand to a developer or add through your website platform.

Use it to:

• Add LocalBusiness JSON-LD to a homepage or contact page.
• Mark up accurate name, address, phone, website, hours, service area, map URL, and social profiles.
• Create schema for storefronts and for service-area businesses without fake public addresses.
• Create schema for restaurants, clinics, dentists, contractors, auto shops, retail stores, legal offices, real estate offices, and professional services.
• Add service-related schema to service pages and multi-location schema for real staffed locations.
• Avoid common mistakes that can make structured data misleading or invalid.

Structured data helps search engines understand the business details already visible on the page. It does not guarantee rich results or specific rankings — Google decides what is eligible to display.

This schema pack is for small business owners, office managers, marketers, web designers, freelancers, agencies, and local SEO beginners who need practical examples instead of abstract schema theory. It is especially useful for:

• Local contractors and home service companies
• Service-area businesses that travel to customers
• Restaurants, cafes, caterers, and food businesses
• Clinics, dentists, medspas, wellness offices, and appointment businesses
• Retail shops, boutiques, showrooms, and local product sellers
• Auto repair, towing, mobile detailing, and transportation businesses
• Lawyers, accountants, consultants, insurance agents, and professional services
• Real estate professionals and local offices
• Multi-location businesses with real staffed locations
• Website builders that need clean starter JSON-LD

• A LocalBusiness schema planning worksheet
• JSON-LD implementation rules and a fields guide
• 16 ready-to-edit examples: storefront, service-area, restaurant, dental, contractor, professional service, retail, auto repair, legal, real estate, multi-location, department, service page, contact page, BreadcrumbList, and FAQPage
• A review-and-rating warning so you handle stars safely
• A common-mistakes guide and a validation workflow
• 10 AI prompts for drafting, auditing, and cleaning up schema

Fill this out once before you edit any example, then reuse it everywhere so the markup describes the real business:

• Business name, type, and best Schema.org subtype — for example LocalBusiness, ProfessionalService, HomeAndConstructionBusiness, Restaurant, Dentist, MedicalBusiness, Store, AutoRepair, LegalService, or RealEstateAgent
• URLs — website, homepage, and contact page
• Phone and email — primary phone, secondary phone, and a public email only if it is shown on the page
• Address — public street address, suite, city, state, ZIP, country, and a note on whether the address should be public and why
• Service area — whether the business is service-area only, and the real areas served
• Location data — latitude, longitude, and Google Maps URL
• Media — logo URL and primary image URL
• Social profiles — only official, verified profiles
• Hours — business hours and any holiday-hours page
• Services and departments — real services, real departments, and booking, menu, order, or appointment URLs
• Commerce details — price range and accepted payment methods
• What not to mark up — anything not visible or not supportable on the page

• Use JSON-LD when possible.
• Put schema on the page it describes.
• Make sure the schema matches visible page content.
• Use the most specific accurate Schema.org type you can confidently support.
• Use absolute URLs for pages, images, logos, maps, and sameAs profiles.
• Use a stable @id for the business entity, and one clear business entity on the homepage or contact page.
• Use page-specific schema on service pages, location pages, blog posts, FAQs, and breadcrumbs.
• Remove placeholders before publishing, validate before publishing, and retest after publishing.

Core fields

• @context, @type, @id, name, url, telephone
• address if public and applicable
• areaServed if service-area or hybrid
• openingHoursSpecification if hours are public
• image, logo, and sameAs

Useful optional fields

• description, priceRange, geo, hasMap, email
• paymentAccepted, currenciesAccepted, makesOffer
• department, parentOrganization, branchOf, contactPoint, foundingDate

Use carefully

• aggregateRating, review, award, knowsAbout, slogan, serviceArea, department

Only use the "use carefully" fields when the page supports the claim and the markup follows Google and Schema.org guidance.

Local businesses often want star ratings in search results. Be careful. Do not add review or aggregate-rating markup unless all of the following are true:

• The reviews are visible on the page.
• The reviews follow applicable platform and legal rules.
• The markup follows Google's review snippet guidance.
• You understand that self-serving LocalBusiness review stars may not be eligible for rich-result display.
• The markup does not quote third-party reviews without permission.
• The markup does not invent ratings or reviews.

Safer local trust options: show real testimonials visibly, link to review profiles, add review excerpts only with permission, use Google Business Profile reviews according to platform rules, and avoid promising rich-result stars.

• Marking up a fake address or a hidden home address.
• Using a city keyword in the business name when it is not the real name.
• Adding services not shown on the page, or service areas the business does not serve.
• Copying competitor schema.
• Using invalid JSON or forgetting commas.
• Using relative image URLs.
• Using social profiles that are not official.
• Marking up reviews that are not visible or permitted.
• Adding awards, licenses, or certifications that are not visible and true.
• Using Organization and LocalBusiness with conflicting names, URLs, or phone numbers.
• Creating schema for fake locations or leaving placeholder text in live schema.

1. Replace all placeholders.
2. Remove unused fields.
3. Confirm every marked-up detail is visible or supported.
4. Check the JSON formatting.
5. Test in Google's Rich Results Test.
6. Test in the Schema.org validator.
7. Fix errors.
8. Review warnings.
9. Publish to the correct page.
10. Test the live URL.
11. Recheck after platform or plugin updates.