Schema Subtype Selection

Choosing the Right
LocalBusiness Schema Subtype

The difference between LocalBusiness and Dentist matters more than you think.

Where to find it: schema.org/LocalBusiness > subtype hierarchy | Rich Results Test > @type field

What It Is

Schema.org has 100+ LocalBusiness subtypes organized in a hierarchy. Using a specific subtype (Dentist, Restaurant, LegalService, AutoRepair) sends more precise categorization signals to Google than the generic LocalBusiness parent. Key subtypes span Healthcare (Dentist, Physician, MedicalClinic), Food (Restaurant, Bakery, CafeOrCoffeeShop), Legal and Financial (LegalService, Attorney, Accountant), Home Services (Plumber, Electrician, HVACBusiness, Locksmith), Professional (RealEstateAgent, InsuranceAgency), and Retail (ClothingStore, ElectronicsStore, GroceryStore).

Why It Matters

Google uses the @type value as a primary categorization signal for local queries. A dental practice using '@type: LocalBusiness' is telling Google only that it's a local business — not a dentist. A dental practice using '@type: Dentist' sends a specific, unambiguous categorization signal that aligns with the 'dentist near me' query category. The more precisely the schema type matches the actual business category, the stronger the relevance signal for category-specific local queries.

Root Diagnostics

Common Causes

Understanding why this failure occurs is the first step to fixing it permanently.

Generic Type Usage

Using '@type: LocalBusiness' instead of a specific subtype because the developer didn't know the full subtype hierarchy existed — the most common subtype error.

Wrong Hierarchy Level

Choosing a mid-level type like 'MedicalOrganization' when a more specific type like 'Dentist' or 'Physician' is available and appropriate for the specific practice.

No Array Type Declaration

Setting @type as a single string instead of an array, which prevents the schema from benefiting from both the specific subtype signals and the general LocalBusiness fallback recognition.

Unverified Google Support

Using schema.org subtypes that are not explicitly supported in Google's Rich Results documentation — which may reduce the practical SEO value even if technically valid schema.

Interactive Standard Operating Procedure

The Fix Blueprint (Interactive SOP)

Check off each step to monitor your implementation progress live!

Implementation Progress: 0% Completed (0/7)

1. Browse the Full LocalBusiness Subtype Hierarchy

Go to schema.org/LocalBusiness and review the complete list of subtypes in the 'More specific Types' section. Follow the subtype tree until you find the most specific type that accurately describes the business.

2. Select the Most Specific Applicable Subtype

Choose the most specific type that accurately describes the business — Dentist, not HealthAndBeautyBusiness. Specificity improves categorization precision without any downside risk.

3. Confirm Google Support in Rich Results Documentation

Check developers.google.com/search/docs/appearance/structured-data/local-business to confirm Google explicitly supports the subtype. Supported types are more likely to generate Knowledge Panel features.

4. Set @type as an Array With Both Specific and Parent Types

Use '@type': ['Dentist', 'LocalBusiness'] — the array format ensures the schema benefits from specific subtype categorization while maintaining compatibility with systems that only recognize the parent type.

5. Check for Subtype-Specific Recommended Fields

Some specific subtypes have additional recommended properties. A Restaurant benefits from hasMenu and servesCuisine. A Hotel benefits from checkinTime and checkoutTime. Review the subtype's schema.org page for these extras.

6. Use Closest Parent if No Specific Type Matches

If no exact subtype exists, use the nearest parent in the hierarchy combined with a detailed description field. '@type': ['LocalBusiness', 'ProfessionalService'] with a clear description provides more signal than LocalBusiness alone.

7. Validate Subtype Resolution in Rich Results Test

Run the page through Rich Results Test and confirm the @type resolves correctly. Check that no type-related errors appear and that Google recognizes the specific subtype.

Tools

schema.org/LocalBusiness
Free | The complete official subtype hierarchy — the definitive reference for identifying the correct @type value
Google Rich Results Test
Free | Confirms @type resolution and flags any type-related validation errors before deployment
Google Search Central Documentation
Free | developers.google.com/search — lists which schema types Google explicitly supports for rich results and Knowledge Panel features

Time to Fix

30–60 minutes

Research & Selection

30 minutes

Implementation & Validation

Pro Tip

When no exact subtype exists, combine LocalBusiness with ProfessionalService.

Using '@type': ['LocalBusiness', 'ProfessionalService'] with a clear, specific description field describing the exact business type provides more categorical clarity than @type: LocalBusiness alone. Google uses the description field as additional categorical context when the @type doesn't fully specify the business category. A well-written one-sentence description of what the business does — in plain language — complements the type signal effectively.

Ep 1: LocalBusiness Schema Foundations Ep 3: NAP Consistency and Schema Alignment

Choosing the RightLocalBusiness Schema Subtype