Local Business Schema: A Practical Guide for Small Businesses
Choose and validate LocalBusiness JSON-LD using accurate location facts, stable entity identifiers and a repeatable release checklist.

The quick read
Key questions at a glance
Where should LocalBusiness schema go?
Put it on a page that describes the real location. For several branches, maintain location-specific facts on the corresponding pages.
Should I mark up an address customers cannot visit?
Represent the actual business model and verify applicable feature requirements. Avoid inventing a public location or exposing a private address.
Does valid markup guarantee a rich result?
Google decides how results are displayed. Validation checks eligibility and errors for supported features.
Start with what a customer can verify
LocalBusiness structured data describes a real business or location in machine-readable form. Begin with the location's visible name, address where appropriate, phone, website and hours. Decide what each page represents before adding markup. A homepage might describe the company, and a location page might describe one shop with a different address and phone from other branches.
Google documents required and recommended properties for its local business feature. Schema.org vocabulary and Google's feature rules serve different purposes. The vocabulary lets you describe entities and relationships. Google's guide specifies the details its feature expects. Check the requirements that apply to your page before treating a clean syntax check as search eligibility. Google's LocalBusiness guide
Build a fact sheet first
Give the owner a small spreadsheet. Use one row per real location with the approved display name, address, public contact number, URL, regular hours, special hours and approver. Check the facts against what customers see on the page and in the booking flow. Where the directory shows different details, ask the business which information is correct before updating structured data.
For a service-area business or a team working from a private address, settle what information should be public before building the markup. Use the correct representation and current feature requirements. An unavailable requirement may mean choosing a more appropriate entity description and leaving that feature out of scope. A fabricated storefront would mislead customers as well as machines. Google Business Profile representation guidelines
Give each entity a stable identity
Choose an applicable type, using a genuinely more specific subtype when supported by the business description. Give each actual location a stable identifier, for example its canonical location URL plus a fragment such as #business. Use the same identifier when other markup refers to that location. Keep multiple branches separate. A branch-level number and opening schedule should belong to the correct branch.
Imagine a florist with a walk-in shop and a studio where staff create bouquets but do not take public visits. The location page contains the shop address, public hours and pickup instructions. The structured data can describe that shop and use a stable ID on its location page. The studio's existence does not create a second storefront. If the business later opens it to customers, review the location model and facts before creating another local page.
Add fields in order of evidence
Start with the required fields for the chosen Google feature. Then make a deliberate pass through recommended fields. The business name, canonical URL, public address, phone and approved regular hours form a practical initial set where applicable. Add details only when the team can verify and maintain them. If the page presents a special schedule around holidays, give the owner one place to approve the website and structured-data update.
Inspect existing output before adding anything. A theme may emit Organization information and a location plugin may add LocalBusiness markup. Multiple types can coexist when each has a clear purpose and IDs and facts are consistent. If two tools publish competing hours for the same branch, trace their sources and correct the shared record or disable the duplicate output through the normal configuration.
Validate what was actually published
Test the markup syntax, then test the final public URL using Google's Rich Results Test for supported result features. Compare warnings and errors against the intended feature documentation. A warning about a recommended property may be acceptable if the fact is unavailable. A required property error needs a decision about the markup or whether the feature applies.
Open the live page and inspect the visible content alongside the rendered structured data. Verify the exact location, time zone context where it matters, canonical address and customer contact route. Check another branch and a non-location page to catch accidental sitewide duplication. Google requires markup to represent the page and excludes misleading content. Its rules also limit self-serving review stars for local businesses and organizations. General structured-data guidelines and Google review snippet guidelines
Worked review: a holiday-hours correction
A hypothetical shop normally closes at six but closes at two on a holiday. The owner confirms the date and the closing time. The website editor updates the public location page, the booking owner reviews the available slots and the developer checks whether the markup draws from the same approved schedule. On release day the reviewer compares all three surfaces and records the location URL and observed result. If the storefront has a profile, the owner reviews the applicable special hours there as well.
Repeat the same review when an address changes or a branch closes. Keep a short record of the markup source, approval date and validation output. Check whether a relevant Search Console report is available after release, while recognising that Google chooses when to process the page and whether to display a feature. Google also says its AI search features require no additional schema. Google's AI search guidance
For the wider customer journey, make the location page easy to reach and keep its enquiry route current. Google Business Profile guide and Local SEO plan
Review a multi-location rollout before scaling it
Prepare a test set with two real public branches and an ordinary service page. Use branch records with different contact numbers and operating hours. Compare the stable identifier and public URL of each entity. Verify that a branch page references its own address and that the general service page does not accidentally inherit a branch's hours. If a booking panel can switch locations, confirm that the markup describes the actual page and that the initial customer journey identifies the right branch.
Ask the developer to explain which part of the system provides each fact. For example, a location collection might supply address and telephone, while opening times are manually written into a separate page block. A holiday update would need both controls unless the display and markup are connected. Identify that duplication while planning the rollout. A single approved source for shared facts makes routine edits easier to audit.
Write the acceptance criteria before duplicating a branch template. Each public page should describe the correct branch, publish internally consistent facts and expose the intended markup in the rendered output. Review one unusually formatted address and a location with a temporary schedule. Capture the evidence and the limitations of the test. Keep the inventory and approval owner current when locations merge, move or change services.
Bring an existing location page and an approved list of public details to a markup review. Contact Brands Essential
Frequently asked questions
Questions, answered
Where should LocalBusiness schema go?
Put it on a page that describes the real location. For several branches, maintain location-specific facts on the corresponding pages.
Should I mark up an address customers cannot visit?
Represent the actual business model and verify applicable feature requirements. Avoid inventing a public location or exposing a private address.
Does valid markup guarantee a rich result?
Google decides how results are displayed. Validation checks eligibility and errors for supported features.
Can I copy customer testimonials into an aggregate rating?
Google restricts self-serving review stars for LocalBusiness and Organization. Review the current rules before adding rating markup.
What if a plugin already adds schema?
Inspect the rendered page and identify the source of each block. Fix conflicting information and assign one owner per entity.
Does AI search require separate schema?
Google says its AI features have no special schema requirement. Follow standard search practices and keep markup aligned with the page.
Build a website around your customers and budget.
Tell Brands Essential what you need, what is already working and the budget you can sustain. Agree a useful first phase and the responsibilities before adding more.



