Local Business

When users search for businesses on Google Search or Maps, Search results may
display a prominent Knowledge Graph card with details about a business that matched
the query. When users query for a type of business, such as a restaurant, they
may see a carousel of listings hosted by restaurant listing providers.

We are currently piloting this feature with a small set of initial providers.
We hope to open up the feature to more providers soon.
Register your
interest in our form.

Location-based queries such as "nearby barbers" or "hair salons within 15 miles"

Business hours

The following examples demonstrate how to mark up different types of business
hours.

We accept both the official schema.org notation for indicating
dayOfWeek
(canonical URLs for Monday, Tuesday), as well as a
shorter form being discussed in the schema.org community. We expect
to update this documentation to track the
eventual outcome of those discussions, and to continue to accept both
variations for backwards compatibility.Standard hoursStandard Hours Excluding the validFrom and validThrough properties signify that the hours are valid year-round.This example defines a business that is open weekdays from 9am to 9pm, with
weekend hours from 10am until 11pm.

All-day hours
To show a business as open 24 hours a day, set the open
property to "00:00" and the closes property to "23:59".To show a business is closed
all day, set both opens and closes properties to "00:00". This example
shows a business open all day Saturday and closed all day Sunday.

Multiple departments

For a business with sub-departments, each with its own distinct properties such
as opening hours or telephone numbers, you can mark up the department property
with an element for each sub-department. Define properties that differ
from the main store individually in each respective department element.

Example

Follow these guidelines for department names in your markup:

Include the store name with the department name in the following format:
{store name} {department name}.

For example, gMart and gMart Pharmacy.

Use a department name by itself when it is explicitly branded. For example:
Best Buy and Geek Squad.

Restaurant lists

When a user searches for best dinner in NYC or provides similar list-seeking queries, your
marked up restaurant content can appear as a host-specific carousel in Search Results.
To enable host-specific lists for restaurants, build your restaurant list pages in AMP HTML with
ItemList markup and mark up individual restaurant
pages. For implementation details, see the
carousels documentation.

Example

We are currently piloting this feature with a small set of initial providers.
We hope to open up the feature to more providers soon.
Register your
interest in our form.

Order & reservation scenarios

Business markup can specify multiple Action types
and qualify the actions with other parameters. Depending upon your offering, you might mark up
your content with more than a single combination of actions and qualifying parameters.

OrderAction

parameters

potentialAction.@type

potentialAction.target.inLanguage

potentialAction.target.actionPlatform

ReserveAction

parameters

potentialAction.@type

potentialAction.target.inLanguage

potentialAction.target.actionPlatform

potentialAction.result.provider

The following examples show markup for a single action target for different businesses.

Order food delivery

Reserve fitness class

Reserve restaurant

Many other combinations of actions and parameters are possible. When developing more
complex business actions, be sure to use only a single value in either
potentialAction.target.url OR potentialAction.target.urlTemplate.

Provide only a single value in either
potentialAction.target.url OR potentialAction.target.urlTemplate.

The target web page or app must let the user complete the action online. For
example, a web page that displays the menu of a restaurant is not a valid
action page if the user must make a telephone call to place an order or reserve
a table.

Type definitions

The following tables list properties and usage for local business and business
action types, based on the full definitions at schema.org/LocalBusiness.

Local business properties

Globally unique ID of the specific business location in the form of a URL. The
ID should be stable and unchanging over time. Google Search treats the URL as
an opaque string and it does not have to be a working link. If the business has
multiple locations, make sure the @id is unique for each location.