Local business schema is structured data used to describe a business that serves customers from a physical location or within a defined service area.
It can communicate information such as the business name, address, telephone number, opening hours, location type, and website.
Google may use structured data to understand business information and support enhanced appearances in Search. When users search for businesses or places, Google Search and Maps may also show business details through local results and knowledge panels.
Local business schema can be useful, but it is only one part of local visibility.
It does not replace an accurate Google Business Profile, strong customer reviews, a relevant website, or genuine local prominence.
What is LocalBusiness structured data?
LocalBusiness is a schema.org type used to describe a local organization or physical business.
It includes more specific subtypes for different business categories.
Examples include restaurants, medical businesses, professional services, stores, health clubs, and many other location based organizations.
Google recommends choosing the most specific subtype that accurately describes the business. A restaurant should generally use Restaurant, while a dentist should use an appropriate medical or dental subtype rather than relying only on the general LocalBusiness label.
The markup should describe the business represented on the page.
It should not be used to create fictional branches, duplicate locations, or service areas that do not exist.
What information can local schema contain?
A local business markup block may include the official business name, address, telephone number, website, opening hours, logo, images, geographic coordinates, price range, and business category.
The exact properties depend on the subtype and Google’s current documentation.
Some properties are required for eligibility, while others are recommended because they provide richer information.
Businesses should follow Google’s documentation for the specific type rather than copying a generic code example from an old article.
Structured data requirements can change, and a valid schema.org property may not necessarily be used by Google for a particular search feature.
Put the markup on a relevant page
Google allows LocalBusiness structured data on any suitable page, although it generally makes sense to place it on a page containing information about the business.
For a single location business, the homepage, contact page, or dedicated location page may be appropriate.
For a company with several branches, each location should normally have its own page.
That page should include information specific to the branch, such as its address, telephone number, opening hours, directions, services, and local contact details.
The structured data on that page should describe that location rather than the company’s entire network.
Use one clear record for each location
Businesses with multiple locations often create inconsistent markup.
A page may contain the address of one branch, the telephone number of another, and general opening hours that apply to neither.
Each location should be represented as one coherent entity.
The visible page and markup should agree on:
The business name
The street address
The city and postal code
The telephone number
The opening hours
The location URL
The relevant business type
When departments have distinct public identities, telephone numbers, or operating hours, Google’s local business documentation allows businesses to describe different departments appropriately.
The structure should reflect how the organization operates in reality.
Keep the business name accurate
The structured data should use the real business name.
Do not add keywords, cities, service descriptions, or promotional phrases that are not part of the recognized name.
For example, a company called “Green Garden” should not identify itself as “Green Garden Best Landscaping Company Warsaw” unless that is genuinely how the business is named and represented.
Google Business Profile guidelines also require businesses to represent themselves consistently with their real world branding.
Consistency between the website, business profile, signage, stationery, and directories reduces confusion.
Make addresses precise
The address in the markup should match the location shown to customers.
Use the correct street, building number, locality, postal code, region where relevant, and country.
Businesses should not use a virtual address or shared office as a customer location when customers cannot genuinely visit or receive service there.
Eligibility for a Google Business Profile generally depends on making in person contact with customers during stated hours, although Google documents certain exceptions.
Schema implementation does not change those eligibility requirements.
A website can describe an organization’s registered office, but that does not automatically make it a valid public storefront or local customer location.
Add accurate opening hours
Opening hours are among the most useful pieces of local information.
They should reflect when customers can contact or visit the specific location.
Businesses with different hours on different days should describe them accurately.
Seasonal changes, public holidays, temporary closures, and special opening periods require maintenance across the website and business profile.
Schema should not continue showing regular hours after the visible page has been updated for a closure.
Local information becomes less trustworthy when different platforms display different times.
Include the correct telephone number
The telephone number should connect customers to the relevant location or service.
A central company number may be appropriate for all branches when calls are handled centrally.
A branch number may be more useful when customers need location specific assistance.
Avoid using temporary tracking numbers in a way that creates inconsistency across important business records.
The goal is to help customers reach the business and help systems understand which number belongs to which location.
Connect local schema with organization information
A local branch is often part of a wider organization.
The website may use organization structured data to describe the main company and local business markup to describe individual branches.
Google recommends that sites representing physical local businesses use the most specific LocalBusiness subtype while also providing appropriate administrative organization details.
The implementation should avoid creating several unrelated records for what is actually one company.
Consistent identifiers, names, and URLs can help clarify the relationship.
Local schema does not replace Google Business Profile
A Google Business Profile allows an eligible business to manage how information appears in Google Maps and local Search experiences.
Businesses can maintain their location, hours, telephone number, website, photographs, service area, products, and customer interactions through the profile.
Local business schema exists on the company’s website.
The two systems serve related but different roles.
A business should maintain both where eligible.
Accurate schema cannot correct an unverified, suspended, duplicated, or outdated Business Profile. Similarly, a strong Business Profile does not excuse inaccurate information on the website.
Schema alone does not determine local rankings
Google states that local results are mainly based on relevance, distance, and prominence.
Business information, reviews, links, location, and the relationship between the company and the search can all influence visibility. There is no method to request or pay Google directly for a better local ranking.
Adding LocalBusiness markup does not remove these competitive factors.
A company far from the searcher may not appear above a closer and equally relevant competitor.
A business with weak customer feedback and limited local recognition may not gain strong visibility through schema alone.
Structured data helps describe the entity. It does not manufacture local prominence.
Be careful with review markup
Businesses often want star ratings to appear beside their listings.
Google’s review snippet policies limit how reviews can be used for local businesses and organizations.
Self serving reviews, where a business marks up reviews about itself on its own website, are not eligible for review rich results in the same way as independent review content. Google’s current documentation states that local business review markup is supported when a site captures reviews about other local businesses, subject to the applicable guidelines.
Businesses should not copy ratings from Google or another platform and place them into schema without understanding the rules and licensing conditions.
Fake or misleading review markup creates serious risk.
Validate the markup
After implementation, use Google’s Rich Results Test to check the structured data.
Fix critical errors and review warnings.
Then use URL Inspection in Search Console to confirm that Google can access the location page and see the rendered markup.
Google recommends deploying structured data on a limited number of pages first, testing the implementation, and expanding it once the setup is reliable.
Technical validation confirms that the code is readable.
It does not guarantee that Google will display a rich result or knowledge panel.
Monitor consistency across the web
Local businesses should regularly compare their website, schema, Business Profile, social profiles, important directories, and industry listings.
Check the name, address, telephone number, hours, category, and website.
Google gathers business information from multiple sources and may update profile information when other evidence suggests that existing details are inaccurate or outdated.
Consistent public information reduces the chance of confusion.
When the business moves or changes its telephone number, update the website and major profiles promptly.
Common local schema mistakes
Typical errors include using the wrong subtype, publishing an incomplete address, mixing details from several branches, adding opening hours that do not match the page, and generating multiple conflicting markup blocks.
Other mistakes include creating schema for locations that do not exist, adding unsupported ratings, or using the registered legal address as a public storefront when customers cannot visit.
Businesses may also install several plugins that each generate organization or local business markup.
The result can be duplicate and contradictory information.
A single accurate implementation is better than several uncontrolled ones.
Local schema should reflect the real business
The best local business schema implementation is not the most complicated.
It is the one that clearly describes a genuine location and remains accurate over time.
Choose the correct business subtype. Use precise location information. Connect each branch to a dedicated page. Maintain consistent hours and contact details. Validate the code and monitor the results.
Then support the markup with the elements that truly drive local trust:
A complete Business Profile
Useful location pages
Genuine customer reviews
Relevant local links
Accurate business information
A strong customer experience
Schema can help search systems interpret a local business.
The business itself must still earn visibility and trust.