Blanc Run free audit

Home / Guides

Guide

LocalBusiness schema for AI answers: hours, prices, payment and amenities

By Jeron Clemente · Published

People ask AI assistants practical questions about local businesses: are you open on Sunday, how much does it cost, can I pay with GCash, is there parking. Most local business schema only states a name, address and phone number, which answers none of them. Add opening hours, a price range, payment methods and amenities, and the assistant has the facts it needs.

The facts, in order of importance

  1. Opening hours (openingHoursSpecification): the most asked question of all.
  2. Price range, or free entry (priceRange, or isAccessibleForFree for free venues).
  3. Payment methods (paymentAccepted): cash, cards and e-wallets such as GCash and Maya.
  4. Amenities (amenityFeature): parking, wheelchair access, Wi-Fi, a kids’ area, walk-ins.
  5. Address (address), with street, city and postal code.
  6. Phone and map coordinates (telephone, geo).
  7. Name, website and image (name, url, image).

Our audit weighs them in roughly this order. Name and address matter, but an assistant rarely needs schema to find them; it needs schema for the details people are unsure about.

A complete example

Here is the JSON-LD for a café in Pasig. Swap in your own details, and only include facts that are true and visible on your page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "CafeOrCoffeeShop",
  "name": "Kape Bahay",
  "url": "https://kapebahay.example/",
  "image": "https://kapebahay.example/img/shop.jpg",
  "telephone": "+63 917 123 4567",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Kapitolyo Street",
    "addressLocality": "Pasig",
    "addressRegion": "Metro Manila",
    "postalCode": "1603",
    "addressCountry": "PH"
  },
  "geo": { "@type": "GeoCoordinates", "latitude": 14.5701, "longitude": 121.0614 },
  "openingHoursSpecification": [
    { "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"], "opens": "07:00", "closes": "21:00" },
    { "@type": "OpeningHoursSpecification", "dayOfWeek": ["Saturday", "Sunday"], "opens": "08:00", "closes": "22:00" }
  ],
  "priceRange": "₱120–₱350",
  "paymentAccepted": "Cash, GCash, Maya, Credit Card",
  "amenityFeature": [
    { "@type": "LocationFeatureSpecification", "name": "Parking", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Wi-Fi", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Wheelchair accessible", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Walk-ins accepted", "value": true }
  ]
}
</script>

Paste it inside the <head> of the page, or use your site builder’s custom code or schema setting.

Details that make the difference

Use the most specific type. CafeOrCoffeeShop, Restaurant, Dentist, ExerciseGym and ChildCare all inherit from LocalBusiness, and say more about you than the general type does.

Write hours per group of days. One OpeningHoursSpecification for weekdays and another for weekends is clearer than a single loose string. For holidays, add an entry with validFrom and validThrough dates.

State a real range. priceRange accepts symbols such as ₱₱, but an actual range like ₱120–₱350 answers the question people ask. For free venues, use "isAccessibleForFree": true.

Keep payment methods plain. paymentAccepted is a simple text list. Name the e-wallets your customers use.

Use amenityFeature for yes-or-no facts. Each one is a LocationFeatureSpecification with a name and "value": true. Schema.org has no dedicated property for walk-ins, so an amenity named Walk-ins accepted is the closest valid option.

Three rules to follow

  1. Mark up only what the page shows. Google’s guidelines require structured data to match visible content. Put the hours, prices and amenities on the page first.
  2. Keep it consistent everywhere. The hours in your schema should match your Google Business Profile and your social pages. Conflicting details make every source less trustworthy.
  3. Validate before publishing. Paste the page URL into the Schema.org validator to catch syntax errors, which make engines skip the whole block.

A note on Google: its guide to AI search says no special schema is needed for its AI features, and it recommends a Google Business Profile for local visibility in AI responses. So keep your profile complete, and treat schema as a way to state your facts without ambiguity, not as a ranking trick. It does not guarantee rich results or AI citations, which also depend on reviews, listings and what other sites say about you.

Schema only helps if crawlers can reach the page in the first place. If you are not sure they can, start with what blocks AI crawlers from your site.

Check your page

Run a free audit to see which of these facts your schema already has. On the Solo plan, the audit builds the JSON-LD from the facts it finds on your page, payment methods and amenities included, and lists what is missing for you to add by hand.

Related guides

Questions

Which schema type should a local business use?

The most specific type that fits, such as Restaurant, CafeOrCoffeeShop, Dentist, ExerciseGym or ChildCare. All of them are kinds of LocalBusiness, so they inherit the same properties.

Can I add facts to schema that are not on my page?

No. Google’s guidelines say structured data must describe content that is visible on the page. Put the facts on the page first, then mark them up.

Is there a schema property for walk-ins?

Not a dedicated one. A LocationFeatureSpecification inside amenityFeature, named for example Walk-ins accepted, is the closest valid way to state it.

Sources

Checked November 1, 2026. Tell us at hello@heyblanc.com if something has changed.