Local Business Schema Markup: How to Help Google Understand Your Business
Local business schema markup gives search engines a clearly labeled version of your business information: what kind of business you operate, where it is located, and how customers can contact it. It sits in your website’s code, while customers read the ordinary page.
The practical approach is to get your business details consistent, choose the right business type, add the information to the appropriate page, and test the published result. For most businesses, accuracy matters more than adding every available field.
Schema can help Google interpret business details and support eligibility for certain enhanced search displays. It does not guarantee rich results, higher rankings, or more clicks. Clearer search information may help customers decide whether to visit your site, but schema alone does not explain why a competitor outranks you.
Think of it as the labeling beneath your local search presence. Your website, Google Business Profile, directory listings, and customer-facing content still need to tell the same story.
1. Get your business information consistent before adding code
The first benefit is fewer conflicting details for customers and search engines. Adding schema to an inaccurate page simply gives the wrong information another place to appear.
Start with the page that represents your location. For a single-location business, that might be the homepage or a dedicated location page. Check these details against your Google Business Profile and important directory listings:
- Business name: Use the actual customer-facing name, without extra service keywords or city names added for search.
- Address: Check the street address, suite, city, state, and ZIP code.
- Phone: Use a number that reaches the business or location described.
- Hours: Separate regular operating hours from temporary or holiday changes.
- Website address: Identify the page customers should use for that location.
These first three details are often called NAP, meaning name, address, and phone number. NAP consistency is about matching the underlying business facts, not making every punctuation mark identical.
Schema does not update your citations, which are mentions of your business on other websites. An old address in a directory needs its own correction.
2. Choose the business type that actually describes your operation
The right type helps describe your business more precisely. LocalBusiness is the broad category, while more specific types describe particular kinds of local businesses.
For example, an auto repair shop can use AutoRepair, and a restaurant can use Restaurant. Choose the most specific appropriate type rather than adding unrelated categories to cover more searches. Schema types are not a list of keywords.
Separate the business from its services
An auto repair shop offering brake repairs and oil changes is still one business. Its business type describes the operation; its service pages explain what customers can buy. Adding several unrelated business types is not a substitute for clear service content.
Also distinguish between what the Schema.org vocabulary can describe and what Google uses for particular search features. Those are not identical lists. Our explanation of which local business schema markup types Google uses covers that distinction in more detail.
3. Build a useful business record
A good record helps connect the page to the right business and location. Start with accurate identity and contact details, then add relevant supporting information.
The technical field names below are the labels used in the markup. They give you a practical checklist when reviewing a setup with a developer or entering details into your website’s structured data settings.
| Field | What it describes | What to check |
|---|---|---|
@type |
The business category | Use an appropriate specific type, such as AutoRepair. |
name |
The business name | Match the genuine name shown on the page. |
address |
The physical location | Use a PostalAddress record with separate street, locality, region, postal code, and country fields. |
telephone |
The contact number | Use the correct location’s number, including the country dialing code. |
url |
The business or location page | Point to the relevant live page, not an unrelated service or campaign page. |
openingHoursSpecification |
Regular operating hours | Enter the appropriate days and opening and closing times. |
image |
An image representing the business | Use an accessible image URL that genuinely represents the location or business. |
sameAs |
Other profiles representing the same business | Use official profile URLs, not loosely related websites. |
geo |
The location’s coordinates | Use the actual location, not the center of a nearby city. |
Keep the record aligned with the visible page
If the markup lists Saturday hours but the page says the business is closed on Saturdays, resolve that conflict. Structured data should describe the information customers can find on the page, not introduce a different version of the business.
Do not invent a storefront address to complete a field. For a service-area business that keeps its address private, avoid publishing that address in markup merely to pursue a search feature. Google’s LocalBusiness rich-result requirements include a physical address, so that particular feature may not fit the business’s public information.
Do not add ratings just to chase stars
Testimonials and review scores are not interchangeable with eligibility for review stars. Google does not award self-serving review stars to a business’s own LocalBusiness pages, including when those reviews appear through an embedded third-party widget. Keep reviews useful for visitors rather than treating rating fields as a display shortcut.
4. Choose direct HTML or Google Tag Manager
The implementation method matters because Google needs to encounter the information reliably. JSON-LD is a common format for schema: a compact block of labeled facts added to a page’s code.
Before adding anything, inspect the page with a structured data testing tool. A website theme, plugin, or existing integration may already generate business markup. Updating that record is usually cleaner than adding a competing one.
Option A: Add JSON-LD directly to the page
Direct implementation keeps the markup with the page it describes. It is generally the simpler maintenance choice when you have access to the website’s templates or structured data settings.
- Choose the page. Use the homepage or relevant location page.
- Prepare the record. Map the approved business details to the fields above.
- Add the JSON-LD. A developer can place it in the page’s HTML, in the head or body, or configure the website system to output it.
- Control its scope. Ensure a location-specific record does not appear across unrelated location pages.
- Publish and test. Check the live URL, not just the unpublished code.
If your website provides schema settings, check what they actually publish. A completed settings screen is not the same as a correct live record.
Option B: Add JSON-LD through Google Tag Manager
Google Tag Manager can deploy the markup when editing the website directly is less practical. It adds a dependency, though: the container and tag need to load correctly.
- Create a Custom HTML tag containing the JSON-LD markup for the business or location.
- Set a page-view trigger limited to the intended page, using its URL or page path.
- Use Preview mode to check that the tag fires on that page and not on unrelated pages.
- Publish the container after checking the record and trigger.
- Test the live URL to confirm Google’s testing tool can detect the generated markup.
A “tag fired” message confirms the deployment step, not the accuracy or eligibility of the business data. Validation comes next.
5. Test both the structure and the meaning
Testing prevents a technically valid record from describing the wrong thing. Use these checks for different purposes:
- Schema Markup Validator: Check whether the markup follows the Schema.org vocabulary and is structured correctly.
- Google’s Rich Results Test: Check supported Google search features and identify errors or warnings affecting those features.
- Google Search Console URL Inspection: Check whether Google can access the page and inspect its rendered version when troubleshooting.
Fix errors first. Review warnings individually: some identify useful missing information, while others concern fields that do not apply. Adding inaccurate information just to remove a warning makes the record worse.
Check what the tools cannot decide for you
Read the detected values yourself. Does the phone reach the correct branch? Do the hours match the page? Does the image represent this location? Is an old address still present in another block of markup?
If a tool cannot detect the record, check whether the page is publicly accessible, the correct template was published, and any Tag Manager trigger matches the page. A successful code-only test does not prove the live implementation works.
6. Give each location its own accurate record
Customers need branch-specific information, not a mixture of details from several offices. For a business with multiple physical locations, each location page can carry its own business record.
Keep the address, telephone, hours, and page URL specific to that branch. A stable @id, which acts as a unique identifier, can help distinguish one location record from another.
For example, two auto repair locations can share a brand name while having different addresses and opening hours. Copying the first location’s entire record onto the second page would erase that distinction.
Assign responsibility for updates. When a location moves, changes its number, or adjusts hours, update the page, schema, Google Business Profile, and important listings together. Include markup checks when changing website themes or SEO plugins.
7. Measure search performance and customer actions
The useful outcome is not simply “schema installed.” It is a clearer search presence connected to a website that helps customers take the next step.
Record the publication date and the pages changed. In Search Console, compare impressions, clicks, and click-through rate for those pages across comparable periods. Separate branded searches from service searches where practical, and account for seasonality and changes in search position.
Then examine what visitors do: calls, completed forms, bookings, or other meaningful inquiries. More clicks are less valuable if the page leaves customers unsure about the service or how to contact the business.
A change in click-through rate alone does not prove schema caused it. Titles, rankings, competition, and other page changes also influence clicks.
Keep schema connected to the bigger customer journey
At David Rivero, we treat technical search work as part of a connected business growth system. Local search and SEO help people find the website. Useful content, social media, video, and reputation help them evaluate the business. Conversion strategy, follow-up, and analytics connect that attention to business opportunities.
AI search visibility belongs in that same system, not in a separate promise of automatic growth. Discovery methods continue to change, but the objective stays consistent: get found and give customers a reason to choose you.
For schema, the next step is straightforward: correct the business facts, publish one coherent implementation, test the live page, and keep it aligned with the rest of your online presence.
