acceptsReservations

acceptsReservations · Not mentioned by Google

Appears in

Restaurant

What is it?

acceptsReservations indicates whether a food establishment takes bookings. It accepts three value types: a Boolean (true or false), a URL pointing to the reservation page, or the legacy strings "Yes" and "No". The URL format does double duty: it confirms the restaurant accepts reservations and tells machines exactly where to book.

Why this matters for AEO

Reservation availability is a high intent signal. When someone asks an AI engine "Can I make a reservation at [restaurant]?" or "Book a table at [restaurant]," the AI system needs a definitive yes/no answer and ideally a booking link. Without acceptsReservations, AI assistants must guess from page content or default to suggesting the user call directly. Providing a reservation URL gives AI engines an actionable response they can present as a direct booking link.

What the specs say

Schema.org: Boolean, Text, or URL. Indicates whether a FoodEstablishment accepts reservations. Values can be Boolean, a URL at which reservations can be made, or (for backwards compatibility) the strings "Yes" or "No". schema.org/acceptsReservations

Google: Not mentioned. This field is not listed in Google's structured data documentation for Restaurant or LocalBusiness. Google LocalBusiness docs

How to find your value

• Restaurant website — A "Reservations" or "Book a Table" button in the header
• Third-party booking — OpenTable, Resy, Yelp Reservations, or TheFork profile URL
• Walk-in only — Use false or omit the property entirely
• Phone-only reservations — Use true (no URL available)

Format and code

Type: Boolean, Text, or URL

Boolean (simplest):

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Le Bernardin",
  "acceptsReservations": true
}

URL (recommended when a booking page exists):

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Le Bernardin",
  "acceptsReservations": "https://www.opentable.com/le-bernardin"
}

Legacy string (backwards compatible but not recommended):

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Le Bernardin",
  "acceptsReservations": "Yes"
}

Common mistakes:

• Using "true" (a string) instead of true (a Boolean): "acceptsReservations": "true" is technically valid as Text but ambiguous. Use the actual Boolean true.
• Providing an invalid or broken reservation URL that returns a 404
• Omitting the property for restaurants that do accept reservations, losing a useful signal for AI engines

Webflow implementation

Static pages

In Page Settings > Custom Code > Before </head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Your Restaurant",
  "acceptsReservations": "https://www.opentable.com/your-restaurant"
}
</script>

CMS template pages

If your Webflow CMS has a "Restaurants" collection with a "Reservation URL" plain text field:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "{{wf {&quot;path&quot;:&quot;name&quot;,&quot;type&quot;:&quot;PlainText&quot;} }}",
  "acceptsReservations": "{{wf {&quot;path&quot;:&quot;reservation-url&quot;,&quot;type&quot;:&quot;PlainText&quot;} }}"
}
</script>

For a Boolean approach, use a Webflow CMS switch field. Conditional visibility or custom embed logic can output true or false based on the switch state.

In Schema HQ

Your CMS URL fields to acceptsReservations as a string URL, or switch fields as a Boolean. It validates that URL values are fully qualified and reachable. is mapped automatically

Real examples

Schema.org FoodEstablishment example (schema.org):

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Example Restaurant",
  "acceptsReservations": true
}

Uses the Boolean format for a simple yes/no signal.

URL-based reservation pattern:

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Example Restaurant",
  "acceptsReservations": "https://www.example.com/reservations"
}

Points directly to the booking page, giving AI assistants an actionable link to surface in responses.

Related fields

• name — Restaurant name
• menu — Link to the restaurant menu
• servesCuisine — Cuisine type served at the restaurant
• telephone — Phone number for phone-based reservations
• url — Restaurant website URL

FAQ

Should acceptsReservations use a Boolean or a URL?

Use a URL when the restaurant has an online booking page. The URL format is more useful because it confirms the restaurant accepts reservations and provides the booking link in a single property. Use a Boolean true only when reservations are accepted by phone or in person with no online booking available.

Does Google use acceptsReservations for rich results?

No. Google does not mention acceptsReservations in its LocalBusiness structured data documentation. The property has no impact on Google rich results. It is still valuable for AI answer engines and other schema.org consumers that parse FoodEstablishment data.

Is there a difference between omitting the property and setting it to false?

Technically yes. Omitting acceptsReservations means the information is unknown. Setting it to false explicitly states the restaurant does not accept reservations. For walk-in only restaurants, false is the clearer signal.