LocalBusiness schema is the structured data layer that tells Google exactly what your business is, where it operates, when it's open, and what services it offers. Get it right and your business shows up better in classic search results, Maps, and AI search features. Get it wrong and it does nothing, or it throws warnings. Here's the practical implementation guide for the three business categories that benefit most: restaurants, salons, and fitness studios.
LocalBusiness schema is one of the most under-used pieces of structured data in local SEO. Most Toronto small business websites have either no schema at all, or generic Organization schema that tells Google nothing specific. The fix is a 30 to 90 minute job that locks in long-term local visibility.
This is the practical version. No theory, just what to add, where to put it, and how to confirm it worked.
1. What is LocalBusiness schema and why does it matter?
LocalBusiness is a schema.org type built for businesses with a physical location and customer-facing operations. It tells Google:
- The exact name, address, phone, and website
- The category and subcategory
- The hours by day of week, including special hours
- The price range
- The geographic coordinates
- The available payment methods, accessibility features, and services
Done right, this data feeds knowledge panels, local pack listings, voice assistant responses, and AI search citations. Skip it, and Google has to guess from your unstructured page content, which is less accurate and carries less authority.
The lift on local visibility from adding LocalBusiness schema is real. You're usually looking at a 15% to 30% improvement in click-through from local search results.
2. What's the most specific schema type I should use?
Schema.org has dozens of LocalBusiness subtypes. The rule is simple: pick the most specific type that fits your business.
Common Toronto business mappings:
- Restaurants → `Restaurant` (or `FastFoodRestaurant`, `BarOrPub`, `CafeOrCoffeeShop`)
- Hair salons → `HairSalon`
- Beauty / nail salons → `BeautySalon` or `NailSalon`
- Fitness studios → `HealthClub` or `SportsActivityLocation`
- Yoga / Pilates → `YogaStudio`
- Boutique retail → `Store` (or `ClothingStore`, `JewelryStore`)
- Professional services → `ProfessionalService` (or `AccountingService`, `LegalService`)
If no subtype fits perfectly, use `LocalBusiness` directly. Don't invent a subtype that doesn't exist on schema.org.
3. What's the minimum required JSON-LD?
Here's the minimum viable LocalBusiness schema:
{
"@context": "https://schema.org",
"@type": "Restaurant",
"name": "Jasmine Cafe",
"image": "https://example.com/cafe-storefront.jpg",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Queen Street West",
"addressLocality": "Toronto",
"addressRegion": "ON",
"postalCode": "M5H 2M9",
"addressCountry": "CA"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 43.6502,
"longitude": -79.3811
},
"telephone": "+14165551234",
"url": "https://jasminecafe.example.com",
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday"],
"opens": "07:00",
"closes": "21:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Friday", "Saturday"],
"opens": "07:00",
"closes": "23:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Sunday",
"opens": "08:00",
"closes": "20:00"
}
],
"priceRange": "$$",
"servesCuisine": "Italian"
}Embed this as a `<script type="application/ld+json">` block in the `<head>` or just before `</body>` on every page that represents the business.
4. What recommended properties add the most value?
Beyond the minimum, these are the additions worth your time:
- `menu` (URL of your menu) for restaurants
- `acceptsReservations` (true/false) for restaurants
- `servesCuisine` for restaurants
- `paymentAccepted` (e.g., "Cash, Credit Card, Interac") for all
- `hasMap` (URL to Google Maps listing)
- `sameAs` (array of social media profile URLs)
- `aggregateRating` (if you have public reviews to surface)
- `amenityFeature` for fitness studios and salons
- `isAccessibleForFree` and `accessibilityFeature` for inclusive marketing
Each property hands Google more context, and each is optional. Once the minimum is in place, adding the recommended ones takes about 15 minutes.
5. How do I handle a business with multiple locations?
There are two valid approaches.
Approach A: one schema block per location page. Each location's URL gets its own LocalBusiness JSON-LD. This is the most common and the most reliable.
Approach B: department schema. A parent business with `subOrganization` properties pointing to child LocalBusiness entities. Handy for franchises or large businesses, but more work to maintain.
For most Toronto multi-location SMBs (2 to 10 storefronts), go with Approach A. Build a per-location landing page, embed the schema specific to that location, and link them all from a "Locations" page.
6. How do I validate my schema?
Three tools, all free.
One: Google's Rich Results Test. Paste the URL or the JSON-LD directly. It tells you whether Google can read the schema and which rich result types you're eligible for.
Two: Schema Markup Validator (validator.schema.org). This runs a more detailed check against the full schema.org spec and catches issues Google's tester misses.
Three: Google Search Console. Once the page is indexed with schema, Search Console reports any structured data warnings or errors. Check it monthly.
Watch for these common errors:
- Wrong country code (use ISO codes: "CA" not "Canada")
- Phone number with letters or formatting that looks human-friendly but parses oddly
- Hours in the wrong format (use ISO 8601 24-hour: "14:30")
- Duplicate schema blocks on the same page
Fix them before they pile up.
7. Will adding schema improve my ranking?
Schema doesn't directly improve ranking. It improves how Google understands your business, and that shapes what ranks where.
Here's what it actually does:
- Better local-pack appearance in classic search
- Better knowledge panels in branded searches
- Better voice assistant responses
- Better AI search citations
- More accurate Maps presence
The cumulative effect on traffic and conversion is real. Just don't treat schema as a "rank higher" hack. Think of it as a "get understood correctly" hack, and the rankings follow.
Implement once, benefit for years
The schema you write today keeps paying off for as long as your business operates. When your hours, services, or location change, updating it takes about 10 minutes.
