Quick Summary
Local schema markup is structured data that describes your business’s name, address, phone number and hours to search engines in a format they can read. It helps search engines understand who you are and where you operate, but it does not guarantee rankings or replace a complete Google Business Profile.
- Choose the most specific schema.org subtype that accurately fits your business.
- Include core properties: name, address, telephone, url, openingHoursSpecification and geo.
- Use JSON-LD, the format Google recommends, in a single script block.
- Replace every placeholder value with verified business information before publishing.
- Validate with the Rich Results Test, then monitor Search Console Enhancements reports.
Table of Contents
- What Local Business Schema Markup Is and What It Does
- Choosing the Right Schema.org Type for Your Business
- Required and Recommended Properties to Include
- Writing a Local Business Schema Example in JSON-LD
- Using a LocalBusiness Schema Generator and a Reusable Template
- Adding Markup to Your Website, CMS, and Tag Manager
- Validating Your Markup with a Local Business Schema Checker
- Your Next Step: Put Your Markup Live and Monitor It
- Frequently Asked Questions
9 Local SEO Schema Markup Mistakes to Avoid
Last Updated: November 10, 2026
What Local Business Schema Markup Is and What It Does
Local SEO schema markup is structured data, written in a vocabulary Google and other search engines can read, that describes your business’s name, address, phone number, hours and other facts directly to search engines, and proper local schema markup helps those engines understand who you are. Local businesses with clean, accurate markup give search engines fewer guesses to make about who they are and where they operate.
Google’s documentation describes local business structured data as a way to help its systems understand a business entity (Local Business (LocalBusiness) Structured Data | Google Search Central | Documentation). The markup itself does not guarantee rankings, and it does not replace a complete Google Business Profile or consistent citations across the web. Treat it as one piece of a larger local search strategy.
Google-Supported Properties, Schema.org Vocabulary, and Ranking Impact
Three things often get blended together, and separating them clears up most of the confusion. Schema.org is the shared vocabulary, a catalog of types such as LocalBusiness and Restaurant and the properties that describe them (Schemas). Google supports a subset of that vocabulary for specific result features. Ranking impact is a separate question entirely.
The practical takeaway: schema.org defines what you can say, Google decides which of it to use for rich results, and markup helps eligibility and accuracy rather than guaranteeing position. Measure outcomes in Google Search Console instead of assuming the markup alone moved your rankings.
Choosing the Right Schema.org Type for Your Business
Start with the most specific type that accurately fits your business. LocalBusiness is the broad parent type, but subtypes such as Restaurant, LegalService, HomeAndConstructionBusiness and ProfessionalService describe many local businesses more precisely. Use the subtype only when it genuinely matches what you do.
A common mistake is choosing a generic type for every location. If you run a landscaping company that also sells outdoor furniture, pick the type that matches the revenue-driving service, then describe the secondary offering in your page content, since well-chosen local schema markup keeps the primary service clear.
Required and Recommended Properties to Include
Google’s documentation lists properties it requires for specific rich results and others it recommends (Organization Schema Markup | Google Search Central | Documentation). For most local business markup, the core set is:
name: your exact business name as customers see itaddress: aPostalAddresswith street, city, state and ZIP codetelephone: a phone number in a consistent formaturl: the canonical homepage URLopeningHoursSpecification: hours for each day, including closuresgeo: latitude and longitude, where you want location precision
Recommended properties add context, such as image, priceRange, sameAs links to your social and directory profiles, and areaServed for service area businesses. The most damaging error here is inconsistency: the name, address and phone in your markup should match your Google Business Profile and website footer exactly.
Writing a Local Business Schema Example in JSON-LD
JSON-LD is the format Google recommends, because it sits in a single script block instead of being woven through your HTML. Here is a simplified example for a fictional neighborhood cafe:
{
“@context”: “https://schema.org”,
“@type”: “CafeOrCoffeeShop”,
“name”: “Maple Street Coffee”,
“url”: “https://www.example.com”,
“telephone”: “+1-419-555-0142”,
“address”: {
“@type”: “PostalAddress”,
“streetAddress”: “120 Maple Street”,
“addressLocality”: “Toledo”,
“addressRegion”: “OH”,
“postalCode”: “43604”,
“addressCountry”: “US”
},
“geo”: {
“@type”: “GeoCoordinates”,
“latitude”: 41.6639,
“longitude”: -83.5552
},
“openingHoursSpecification”: [
{
“@type”: “OpeningHoursSpecification”,
“dayOfWeek”: [“Monday”, “Tuesday”, “Wednesday”, “Thursday”, “Friday”],
“opens”: “07:00”,
“closes”: “17:00”
}
]
}
Replace every value with your verified information. Placeholder values left in production are one of the most common errors we encounter.
The table below lists the facts used in the sample markup and what each one needs.
| Property | Example value | What to check |
|---|---|---|
| name | Maple Street Coffee | Exact business name as customers see it |
| telephone | +1-419-555-0142 | Consistent format |
| streetAddress | 120 Maple Street | Matches Google Business Profile |
| postalCode | 43604 | Required in PostalAddress |
| opens / closes | 07:00 / 17:00 | Hours for each day, including closures |
| Placeholder values | Not allowed | Replace every value with verified information |
Using a LocalBusiness Schema Generator and a Reusable Template
A schema generator is a useful starting point, but treat its output as a draft. Generators often default to vague types, omit hours or insert placeholder text. Build a reusable template once, with your verified business facts stored in a single source document, then paste from that source every time you update a location.
For multi-location businesses, a template with one JSON block per location, each with its own @id and address, prevents the common mistake of blending several branches into one entity.
Adding Markup to Your Website, CMS, and Tag Manager
Where the JSON-LD lives depends on how your site is built, and the wrong placement is the most common reason markup validates in a test tool but never appears in Search Console. The rule of thumb: put one JSON-LD block on the page that represents the business entity, and let the platform render it in the <head> or just before </body>.
WordPress. Most SEO plugins (Yoast SEO, Rank Math, All in One SEO) ship a Local SEO or Organization module that outputs LocalBusiness markup from settings fields. Populate the business name, address, phone, logo, and social profiles there first. If you need a subtype the plugin does not expose, add a small custom JSON-LD block through a code-snippets plugin or your child theme’s functions.php using wp_head. Watch out: running two plugins that both output LocalBusiness markup produces duplicate entities and conflicting @id values, so disable the local module in one of them.
Shopify. Shopify’s theme outputs Organization and WebSite markup automatically. For a physical store or service business, add a LocalBusiness block through the theme’s theme.liquid before </head>, or use a structured-data app. Keep the store address in the block identical to the address in your Shopify settings and your Google Business Profile.
Squarespace and Wix. Both have built-in business information fields under site settings that feed structured data. Fill those in before adding custom code, and only inject a manual JSON-LD block through the platform’s code-injection area if the native output is missing a property you need.
Custom sites and static generators. Place the JSON-LD in the base template so it renders on every page that represents the entity, or scope it to the homepage and each location page. For multi-location sites, generate one block per location page from a data file rather than hand-editing HTML.
Google Tag Manager. You can inject JSON-LD with a Custom HTML tag triggered on specific page paths. This is useful when you cannot edit the site directly, but it has trade-offs: the markup is added client-side after the container loads, it is harder to audit in page source, and a misconfigured trigger can fire the same block on every URL. Use a page-path trigger that matches only the intended pages, and verify the rendered output with the Rich Results Test rather than trusting the tag preview alone.
A short pre-publish checklist keeps deployment clean:
- Confirm whether the platform already outputs LocalBusiness or Organization markup
- Disable duplicate modules before adding custom JSON-LD
- Place the block on the homepage or the correct location page, not sitewide
- Give each location its own
@idand address - Remove placeholder values and test the live URL, not just a pasted snippet

Validating Your Markup with a Local Business Schema Checker
Before you publish, test the page with Google’s Rich Results Test and the Schema Markup Validator at validator.schema.org. Look for both errors, which block eligibility, and warnings, which flag missing recommended properties. After publishing, check the Enhancements reports in Google Search Console to see whether Google is reading the markup on live pages.
Validation confirms syntax and eligibility. It does not confirm that your facts are accurate, so compare the output against your business records manually.
Your Next Step: Put Your Markup Live and Monitor It
Publishing valid markup is the midpoint, not the finish line. Business details change, themes get updated, and plugins get swapped, and any of those can silently break structured data. A lightweight monitoring loop catches problems before they cost you visibility.
Week one after launch. Run every marked-up URL through the Rich Results Test and the Schema Markup Validator at validator.schema.org. Confirm the live page source contains the block, not just the tag manager preview. In Google Search Console, open the Enhancements section and check that the relevant report (Local businesses, Merchants, or the generic structured data report) lists your URLs as valid.
Ongoing checks. Review the Enhancements reports monthly for new errors or warnings. A spike in invalid items usually traces to a theme update, a plugin conflict, or a page migration. When you change hours, phone numbers, or addresses, update the source-of-truth document first, then the markup, then the Google Business Profile, so the three never drift apart.
Measuring outcomes without overstating causality. Schema markup does not guarantee rankings or rich results. Track realistic indicators instead: the count of valid items in Search Console, rich-result impressions where a feature applies, and organic clicks to location pages over time. Compare against a baseline period and note other changes (content updates, review growth, profile edits) that could explain movement. A common pattern is that markup improves how accurately search engines understand a page long before any visible result changes.
Governance for multi-location businesses. Keep a single location data sheet with legal name, display name, address, phone, hours, and URL for each branch. Generate markup from that sheet, map each location to one canonical URL, and audit quarterly for inconsistent NAP, shared addresses across branches, and location-specific hours that were never updated. This is the difference between markup that scales and markup that quietly rots.
If you want help with that work, get started with Easy Street Social to review your local presence and fix the gaps that matter most.
Frequently Asked Questions
What is local business schema markup?
Local business schema markup is structured data added to a web page that describes a business in a standard, machine-readable format. It uses vocabulary from Schema.org, usually written as JSON-LD, to state your business name, address, phone number, opening hours, and service area. Search engines use this information to better understand your business and its location. Markup does not guarantee rankings or rich results, but it makes your business details clearer and easier to verify.
How do I add LocalBusiness schema to my website?
Write a JSON-LD block with the @type set to LocalBusiness or a more specific subtype, then fill in properties such as name, address, telephone, and openingHours. Place the script in the head or body of the page that describes your business, usually your homepage or location page. Many content management systems let you paste custom code into a header or footer field, and tag managers can also deploy it. After publishing, test the page with Google’s Rich Results Test to confirm the markup is read correctly.
Can I use LocalBusiness schema for multiple locations?
Yes. Create a separate LocalBusiness block for each location, placed on that location’s own page, with a unique address, telephone number, and geo coordinates. Keep the business name consistent with how it appears in your Google Business Profile so the details match across sources. Avoid putting every location into one block on a single page, since search engines associate the markup with the page it lives on.
How do I test local business schema markup?
Run the live page URL through Google’s Rich Results Test to see whether the markup is eligible for rich results and whether errors appear. Use the Schema Markup Validator to check that the code follows Schema.org vocabulary. Then review the Enhancements reports in Google Search Console after the page is crawled. Retest after every change to your template, since a small edit can break the JSON syntax.
