LocalBusiness schema is a small block of code that tells search engines who you are, where you are and when you are open, in a format they read without guessing. Most sites I audit either skip it or fill it with fields that do nothing. This guide covers the fields Google actually documents, the ones worth your time, a clean example you can adapt and the mistakes that make markup useless.
What LocalBusiness Schema Does, and What It Does Not
The markup sits in your page code as JSON-LD and describes your business: name, address, phone, hours, location on the map and the type of business. It helps Google connect your website with your business and read details such as hours correctly.
It is not a ranking switch. Adding schema will not move you into the map pack on its own, because the map pack depends mostly on your Google Business Profile, your reviews and how relevant and close you are to the searcher. Think of schema as one more place where your details are stated clearly and consistently, which supports everything else. It is one of the technical pieces I set up in every local SEO project.
The Two Required Fields: name and address
Google’s local business structured data documentation lists only two required properties: name and address. Everything else is recommended.
- name should match your sign and your Google Business Profile exactly. No extra keywords, no city name added for SEO.
- address is a PostalAddress with separate parts: streetAddress, addressLocality (the city), addressRegion, postalCode and addressCountry. Write it the same way it appears on your profile and your contact page.
Getting these two right, and identical everywhere, matters more than any optional field.
Recommended Fields Worth Filling In
These are the fields from Google’s recommended list that apply to most local businesses, with what to put in each and the mistake I see most often.
| Field | What to put in it | Common mistake |
|---|---|---|
| @type | The most specific subtype, such as Dentist, Plumber, AutoRepair or VeterinaryCare | Plain LocalBusiness when a better subtype exists |
| telephone | The main local number, with country code | A tracking number that changes every few months |
| url | The page about this location | The homepage for every location |
| geo | Latitude and longitude with at least five decimal places | Rounded coordinates that land on the wrong street |
| openingHoursSpecification | Opening hours for each day, plus special hours with start and end dates | Hours that differ from the Business Profile |
| priceRange | A short range or currency signs such as $$ | A sentence of marketing copy |
| department | Separate departments with their own hours, such as a pharmacy inside a store | Listing every service as a department |
| image | A real photo of the location | Only the logo |
| aggregateRating and review | Leave them out on your own site | Marking up your own testimonials |
Two notes on the last rows. Google’s review snippet guidelines say pages using LocalBusiness markup are not eligible for review stars when the business controls the reviews about itself, so marking up testimonials on your own site gains nothing. And for hours, Google’s documentation shows a 24-hour day as opening at 00:00 and closing at 23:59, and a closed day as both times set to 00:00.
A Clean Example You Can Adapt
Here is a complete block for a fictional single-location dental office. Swap in your own details, keep the structure and place it inside a script tag of type application/ld+json on the page about that location.
{
"@context": "https://schema.org",
"@type": "Dentist",
"name": "Example Family Dental",
"url": "https://www.example.com/locations/springfield/",
"telephone": "+1-555-010-0199",
"image": "https://www.example.com/images/springfield-office.jpg",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main Street, Suite 2",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 39.80172,
"longitude": -89.64371
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "09:00",
"closes": "13:00"
}
]
}Every value here should match what a visitor sees on the page itself. Markup that describes hours or an address not shown on the page is the kind of mismatch that makes search engines trust the data less.
Multi-Location and Service-Area Businesses
For several locations, give each one its own page and its own LocalBusiness block with that location’s name, address, phone, coordinates and hours. The url field points to that location page, not the homepage. On the homepage, describe the brand as an Organization rather than squeezing every location into one block.
Service-area businesses that hide their address on Google need more care. In my practice, I do not publish a street address in schema that the business keeps hidden everywhere else. Instead, I keep the name, phone and url consistent and list the towns covered with the schema.org areaServed property. The goal is the same as everywhere in local SEO: one consistent story about the business.
Adding It in WordPress
On WordPress, you rarely need to write the code by hand. Rank Math’s local SEO settings can output LocalBusiness markup from the details you enter once, and my guide to Rank Math settings covers where they sit. Whatever tool you use, check that only one plugin outputs business schema. Two plugins each adding their own block, with slightly different hours or names, is one of the most common problems I find in a technical SEO audit.
Testing and Monitoring
Run the page through Google’s Rich Results Test to confirm the markup is read without errors, and through the Schema Markup Validator for a full view of every property. After launch, check the enhancements reports in Search Console from time to time.
Then compare the markup against your Business Profile line by line. If the profile lists different hours or a different phone number, fix whichever one is wrong. My Google Business Profile checklist covers the profile side. Re-test after theme changes, plugin updates and any change to hours, phone or address.
LocalBusiness Schema FAQ
Does LocalBusiness schema improve map pack rankings?
Not directly. The map pack depends mostly on your Business Profile, reviews, relevance and distance. Schema helps search engines read your details correctly and confirms that your site and your profile describe the same business. It is worth doing well, but it will not make up for a weak profile or thin pages.
Should my homepage use LocalBusiness or Organization?
For a single location that serves customers at its address, a LocalBusiness subtype on the homepage or contact page works well. For a brand with several locations, use Organization on the homepage and a LocalBusiness block on each location page, so every location has its own accurate details.
Can I add my Google reviews to the markup?
You can show reviews on your site for visitors, but marking them up as review or aggregateRating on your own site will not earn review stars, because Google treats reviews a business controls about itself as ineligible. Your review stars in local results come from your Business Profile instead.
How often should I update the markup?
Whenever a detail changes: new hours, a new phone number, a move or a new location. Add special hours before holidays if you use them, and re-test the page after any site update. A quick check every quarter catches the changes that slip through.
Final Word
LocalBusiness schema rewards accuracy over volume. Get the name and address right, fill the recommended fields that apply to you, skip the self-serving review markup and keep every detail identical to your Business Profile. To check whether your current markup and local setup are holding you back, send your site for a free mini audit and get three quick wins within 48 hours.