Inferensys

Glossary

LocalBusiness

A Schema.org structured data type used to markup a physical business location, providing critical local SEO signals like address, geo-coordinates, opening hours, and accepted payment types to appear in Google Maps and local pack results.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
SCHEMA.ORG TYPE

What is LocalBusiness?

A foundational structured data type for defining a physical business location to search engines.

LocalBusiness is a Schema.org type used to markup a specific, physical business location or a branch of an organization that serves customers at a dedicated premises. It provides critical local SEO signals—including a physical address, geo-coordinates, opening hours, and accepted payment methods—to enable visibility in Google Maps and local pack results.

As a subtype of both Organization and Place, it inherits properties for entity identity and spatial location. Implementing LocalBusiness with precise NAP consistency (Name, Address, Phone) and a linked geo property is a deterministic signal for search engines to associate a web entity with its real-world footprint, directly influencing local search ranking and knowledge graph grounding.

STRUCTURED DATA ANATOMY

Key Properties of LocalBusiness

The LocalBusiness schema type extends Organization with critical physical-world attributes that power local pack rankings, Google Maps visibility, and voice search responses for 'near me' queries.

01

GeoCoordinates & Spatial Anchoring

The latitude and longitude properties embedded within a GeoCoordinates node provide the definitive spatial signal for local search. Unlike address text alone, precise coordinates eliminate geocoding ambiguity and directly inform proximity-based ranking algorithms.

  • Use decimal degree format (e.g., 40.7128, -74.0060) with at least 6 decimal places
  • Nest within the geo property of LocalBusiness
  • Mismatched coordinates and street addresses trigger spam flags in Google's validation
  • Essential for Google Maps pin accuracy and voice search responses
6+
Decimal Places Required
02

OpeningHoursSpecification

The openingHoursSpecification property structures business hours as an array of OpeningHoursSpecification objects, each defining a day-of-week and time window. This granular markup outperforms a simple text string by enabling search engines to display current open/closed status dynamically.

  • Use ISO 8601 time format (HH:MM:SS) for opens and closes entries
  • Define validFrom and validThrough dates for seasonal or holiday hours
  • Multiple time windows per day (e.g., lunch closure) require separate specification objects
  • Directly powers the 'Open Now' filter in local search results
03

PostalAddress & Physical Location

The address property accepts a PostalAddress type, providing structured fields for streetAddress, addressLocality, addressRegion, postalCode, and addressCountry. This structured decomposition enables accurate entity reconciliation with Google's database of physical places.

  • streetAddress must contain the full street-level detail including suite numbers
  • addressLocality maps to the city, addressRegion to the state/province (use ISO 3166-2 codes)
  • Consistency with Google Business Profile address data is non-negotiable for verification
  • Missing or mismatched postal codes are a leading cause of local pack exclusion
04

AggregateRating & Social Proof

The aggregateRating property embeds an AggregateRating node containing ratingValue (numeric score) and reviewCount (total reviews). This structured data triggers star-rich results in local packs, directly influencing click-through rates and consumer trust signals.

  • ratingValue must be on a scale consistent with bestRating (typically 1-5)
  • reviewCount should reflect the total number of reviews aggregated, not a subset
  • Google may ignore markup that doesn't match visible on-page review content
  • Star ratings in local results can increase CTR by up to 35% according to industry studies
35%
Potential CTR Increase
05

PriceRange & Payment Accepted

The priceRange property uses a standardized shorthand (e.g., $$ or $$$) to signal cost tier, while paymentAccepted lists accepted methods as text strings. These attributes help search engines filter results for users with specific budget or payment constraints.

  • priceRange follows the convention: $ (inexpensive) through $$$$ (ultra high-end)
  • paymentAccepted should enumerate specific methods: 'Cash', 'Credit Card', 'Cryptocurrency'
  • currenciesAccepted uses ISO 4217 codes (e.g., 'USD', 'EUR') for multi-currency businesses
  • These properties feed into local search filters on mobile and voice interfaces
06

SameAs & Entity Reconciliation

The sameAs property accepts an array of canonical URLs pointing to the business's authoritative profiles on external platforms. This explicit entity linking is the most powerful signal for consolidating a business's identity across the web and resolving duplicate listings.

  • Include Google Business Profile URL, Wikipedia entry, Wikidata Q-ID, and major directory listings
  • Each URL must represent the identical real-world entity, not a parent corporation or franchise
  • Reconciliation via sameAs directly strengthens Knowledge Graph confidence
  • Inconsistent sameAs links across pages create entity fragmentation and dilute authority
LOCAL BUSINESS SCHEMA

Frequently Asked Questions

Essential questions about implementing LocalBusiness structured data to enhance local SEO, Google Maps visibility, and local pack rankings.

LocalBusiness is a Schema.org structured data type used to markup a physical business location on a webpage, providing search engines with explicit, machine-readable details about the entity. It works by embedding JSON-LD code containing critical local SEO signals—such as the business's legal name, physical address, geo-coordinates, telephone number, and opening hours—directly into the HTML of a page. When Google's crawler parses this markup, it reconciles the data with its Knowledge Graph and Google Business Profile, using the verified information to populate the local pack, Google Maps, and knowledge panels. This explicit communication eliminates ambiguity, ensuring the search engine understands exactly which physical location the page represents, its service area, and its relationship to other entities like parent organizations or departments.

SCHEMA TYPE COMPARISON

LocalBusiness vs. Organization vs. Place

Structural and functional distinctions between the three primary Schema.org entity types used to describe business entities and physical locations.

FeatureLocalBusinessOrganizationPlace

Parent type

Organization & Place

Thing

Thing

Physical address required

Geo-coordinates property

Opening hours specification

Accepts payments property

Price range property

Serves local area

Google Maps eligibility

Logo property

Founder property

Sub-organization nesting

Review eligibility

ContainsPlace property

GeoShape property

Telephone property

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.