Local Business Schema: Page-by-Page Templates and Implementation
Schema markup gives search engines explicit clues about a business and its pages.
For a local site, the practical question is not whether to use schema, but which type belongs on each page and how to produce valid JSON-LD without overstating what it will achieve. This guide maps page types to schema types, walks through generation and validation, and explains the fields to fill in for location, service-area, team, contact and blog pages. The page includes a set of customizable JSON-LD schema templates for key local business pages, covering Organization, AboutPage, FAQPage, Person, ContactPage, Service, LocalBusiness and Article. Each one is a starting point only and must be tailored to your own business details before use.
What schema markup and structured data do
Schema markup is code added to a page to describe a business and its content in a standardized way. Structured data is the broader category: any data organized in a standard format so search engines can read and interpret it. Schema is a specific vocabulary, usually Schema.org, used inside that structured data to label what the data means.
When structured data is implemented correctly, it can make a page eligible for rich results: enhanced search listings that show extra details such as ratings, prices or event dates. Eligibility is not a guarantee. Some schema types can influence how a result appears; others mainly help machines interpret the page.
LocalBusiness Schema is the local-business type within Schema.org. It describes details such as name, address, phone number, opening hours and services, and is designed to clarify location-based information for search engines.
Why local businesses use schema
The case for schema rests on clarity and consistency rather than a guaranteed ranking lift. Well-implemented markup can:
- Help search engines understand business details such as name, address, phone, hours and services, which supports relevance for local queries.
- Make a page eligible for richer result treatments that show contact information, reviews, ratings or location details.
- Improve the chance that users click a listing when useful information is visible at a glance.
- Keep business information consistent across search engines and third-party services.
- Help voice assistants and assistive technologies interpret key details such as contact information and opening hours.
Treat each benefit as conditional. Schema types differ in what they can affect, and no markup should describe information that is not visible on the page.
Before you implement: a short checklist
Use this checklist before editing any template:
- Confirm the page type. A home page, location page and blog article need different schema types.
- Match visible content. The structured data should align with what a visitor can see on the page.
- Remove misleading details. Do not use schema to present false or unrelated information.
- Check Google's structured data guidelines. Compliance comes before clever markup.
- Choose a format. Microdata, JSON-LD and RDFa are all formats; Google prefers JSON-LD.
- Expect to customize. A template is a starting point, not a finished implementation.
- Check review eligibility. Review-rich results are not displayed for LocalBusiness and Organization schema because they are treated as self-serving.
A useful failure distinction: a validation error means the code is malformed or uses an unknown property; a rich-result ineligibility means the code may be valid but the type or context does not qualify for an enhanced result. Fix the first before worrying about the second.
Which schema type belongs on which page
The table below is the original page-type guide. Use it to choose a starting type, then adapt the template to the page's actual content. The notes column matters: for example, Person markup is intended to work alongside Organization, and Service markup can carry review and aggregateRating fields that you may remove.
{{TABLE_MODULE:table0001}}
Generate, validate and place the markup
A schema generator can produce the initial code. The workflow below follows the steps demonstrated with Instant Schema, but the same sequence applies to other generators.
- Open the generator and start a new schema.
- Select the schema type, such as LocalBusiness for a local business site.
- Choose the most specific business type available. Common categories include AnimalShelter, AutomotiveBusiness, ChildCare, Dentist, DryCleaningOrLaundry, EmergencyService, EmploymentAgency, EntertainmentBusiness, FinancialService, FoodEstablishment, HealthAndBeautyBusiness, LodgingBusiness, MedicalBusiness, RealEstateAgent, SelfStorage, Store and TravelAgency. If none fits, use LocalBusiness.
- Complete the form. The generated code updates as each detail is added.
- Copy the finished code.
To find an image URL, open the page, right-click the image, choose Inspect, and copy the highlighted URL into the generator.
Validation:
- Paste the code into a validator such as the Schema.org validator.
- Correct errors shown in red in the editing window, then run the check again.
- Once no errors or warnings remain, copy the code.
- Test it in Google's Rich Results Test to see whether the markup is eligible for the intended result.
For WordPress sites, plugins such as Yoast SEO, Rank Math and Schema Pro can reduce manual code insertion. JSON-LD can be placed in the head, body or footer; search engines can still read it. Placing it in the footer can keep more critical head scripts, such as analytics and pixel tags, loading without interference.
Template field map: what each page type needs
Use this field map to decide what to fill in before copying one of the JSON-LD templates below.
- Home page (Organization): business name, location and what the business does. The home page usually carries the most SEO weight, so make the Organization description accurate and complete.
- About Us page (AboutPage): company background and trust-building details. The page should help a visitor understand who the business is.
- FAQ page (FAQPage): question-and-answer pairs that are visible on the page. FAQPage can also be used on any page that contains FAQs.
- Team pages (Person): individual profiles for founders and key management. A parent page can list multiple people; child pages can carry individual Person markup. Person is intended for use with Organization.
- Contact Us page (ContactPage): the correct contact information for the business. Use it with Organization or LocalBusiness.
- Service pages (Service): the service offered. A parent page can list multiple services and link to child pages that describe each service in detail. The supplied Service template includes review and aggregateRating fields that can be removed.
- Location pages (LocalBusiness): the location represented by the page. A more specific type such as Dentist or AccountingService can replace LocalBusiness. The hasMap property can link to the matching Google Business Profile; a Place ID Finder can supply the CID (Ludocid) for that profile.
- Service-area pages (LocalBusiness): the area served rather than a physical address. The areaServed value can be a City, State or Country, each with a name and a sameAs link to a reference page such as Wikipedia.
- Blog articles (Article): topic, author, word count and publication date. BlogPosting or NewsArticle can be used instead of Article for greater specificity.
Each template below is a JSON-LD starting point. Replace the placeholder values with the real details for the page, remove any properties you do not need, and validate the result before publishing.
Worked example: a parent and child service structure
Consider an HVAC business. Its parent service page lists HVAC Services and links to three child pages: A/C Repair, A/C Installation and A/C Maintenance. The parent page can use the multiple-service template to describe the service list; each child page can use the single-service template to describe one offering in detail. If the business does not want review stars attached to the Service markup, remove the review and aggregateRating fields from the child template.
For a service-area page, the same LocalBusiness structure applies, but the address is replaced by an areaServed value. A city-level example uses a City type with a name and a sameAs link; a state or country version changes the type accordingly. The comparison table shows the before-and-after values for City, State and Country.
Schema and AI-driven search
Schema markup is increasingly discussed as a foundation for AI-driven search, where semantic understanding of page content matters. The practical implication is not a new set of magic fields; it is that accurate, well-structured descriptions of a business and its pages become more useful as search systems interpret meaning rather than matching strings. Keep the markup aligned with visible content and avoid adding types solely because they sound advanced.
Conclusion
Schema is a clarity tool. Choose the type that matches the page, fill it with real business details, validate the code, and test eligibility for rich results. The templates on this page speed up the first draft, but the value comes from accurate customization and ongoing consistency with the visible page.
Schema templates for local SEOs
The templates below are customizable JSON-LD starting points for key local business pages. Each one must be tailored to your business before use, and you can add or remove schema types as needed. Google also publishes a gallery of schema templates you can draw on.
Home page (Organization). The home page usually carries the most SEO weight, so search engines need to know the business name, where it is located and what the business does. Organization schema teaches them that.
About Us page (AboutPage). Visitors use this page to get to know the company and build trust in it, so the AboutPage template should reflect the company background accurately.
FAQ page (FAQPage). A FAQ page educates users and reduces support inquiries. Use the FAQPage template on FAQ pages, or on any page that contains FAQs.
Team pages (Person). A parent page can list all team members with multiple Person markup, while individual child pages carry a single Person profile. At a minimum, highlight founders and key management to establish credibility and transparency.
Contact Us page (ContactPage). ContactPage schema tells search engines the correct contact information for the business.
Service pages (Service). A parent service page lists all services and links to child pages that detail each one. The child Service template includes review and aggregateRating fields, which you can remove if you prefer.
Location pages (LocalBusiness). LocalBusiness schema tells search engines which pages represent which locations. You can link each location page to its matching Google Business Profile through the hasMap property, using a Place ID Finder to get the CID (Ludocid). A more specific type such as Dentist or AccountingService can replace LocalBusiness.
Service-area pages (LocalBusiness). These use the same structure as location pages, but list an areaServed value instead of a business address, because the business travels to the area without having a physical office there.
Blog articles (Article). Article schema tells search engines about the topic, author, word count and publication date. BlogPosting or NewsArticle can be used instead of Article for greater specificity.
| Page Type | Recommended Schema Type | Notes |
|---|---|---|
| Home Page | Organization | |
| About Us Page | AboutPage | |
| FAQ Page | FAQPage | |
| Our Team Pages | Person | Use with "Organization" |
| Contact Us Page | ContactPage | Use with "Organization" or "LocalBusiness" |
| Service Pages | Service | Use with "review" and "aggregateRating" |
| Location Pages | LocalBusiness | |
| Service-Area Pages | LocalBusiness | |
| Blog Articles | Article | Can use "BlogPosting" or "NewsArticle" instead |
This is the original page-type guide. The notes column is part of the guidance, not decoration; for example, Person is intended for use with Organization, and Service can carry review and aggregateRating fields that may be removed.
Frequently asked questions
Is schema the same as structured data?
No. Structured data is any data organized in a standardized format. Schema is a specific vocabulary, usually Schema.org, used inside structured data to label what the data means. Correctly implemented structured data can make a page eligible for rich results, but eligibility is not guaranteed.
Which schema type should a local business home page use?
Organization is the recommended starting type for a home page. It tells search engines the business name, location and what the business does. A location page, by contrast, is better suited to LocalBusiness or a more specific subtype such as Dentist.
Can a local business get review stars from LocalBusiness schema?
Review-rich results are not displayed for LocalBusiness and Organization schema because they are treated as self-serving. The Service template includes review and aggregateRating fields, but you can remove them if they do not fit your page or eligibility.
How does service-area schema differ from location schema?
Both use a LocalBusiness structure. A location page lists a business address; a service-area page lists an areaServed value instead, because the business travels to the area but does not have a physical office there. The areaServed value can be a City, State or Country with a name and a sameAs reference link.
Where should JSON-LD be placed on a page?
JSON-LD can go in the head, body or footer; search engines can read it in any of those positions. Placing it in the footer can keep more critical head scripts, such as analytics and pixel tags, loading without interference.