Food Truck & Mobile Kitchen Catering Schema Markup (JSON-LD)
Structured data for gourmet food trucks, mobile pop-up kitchens, and street food vendors, modeling roaming service areas, payment options, and culinary specialties.
Displayed below main page header or above the tool container. • Zero CLS Container
Production JSON-LD Code Block
Embed this structured data block directly into your HTML <head> or framework layout template.
{
"@context": "https://schema.org",
"@type": "FastFoodRestaurant",
"@id": "https://example.com/trucks/taco-nomad#business",
"name": "Taco Nomad Artisan Street Kitchen",
"description": "Award-winning mobile food truck serving wood-smoked birria tacos, artisanal churros, and seasonal aguas frescas across the metropolitan area.",
"telephone": "+1-503-555-0144",
"priceRange": "$",
"servesCuisine": [
"Mexican Street Food",
"Tacos",
"Birria"
],
"paymentAccepted": "Cash, Credit Card, Apple Pay, Google Pay",
"areaServed": [
{
"@type": "City",
"name": "Portland"
},
{
"@type": "City",
"name": "Beaverton"
}
],
"address": {
"@type": "PostalAddress",
"streetAddress": "820 SW 3rd Avenue (Cartlandia Hub)",
"addressLocality": "Portland",
"addressRegion": "OR",
"postalCode": "97204",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Wednesday",
"Thursday",
"Friday",
"Saturday",
"Sunday"
],
"opens": "11:00",
"closes": "20:00"
}
]
}Typed Properties Specification (6 Fields)
Key Schema.org properties and sub-objects required to qualify for rich snippet treatment in Google Search.
| Property | Expected Type | Status | Description & Example |
|---|---|---|---|
| name | Text | Required | Official trading name of the food truck brand. e.g. Taco Nomad Artisan Street Kitchen |
| servesCuisine | Text | Required | Types of street food or cuisine served from the mobile truck. e.g. Mexican Street Food |
| areaServed | City | AdministrativeArea | Required | Geographic cities or postal routes where the truck operates. e.g. Portland, OR |
| paymentAccepted | Text | Required | Accepted tender formats (cashless, tap-to-pay, cards). e.g. Cash, Credit Card, Apple Pay |
| priceRange | Text | Required | Relative price indicator ($ for typical street food pricing). e.g. $ |
| openingHoursSpecification | OpeningHoursSpecification | Recommended | Weekly operating hours schedule at primary food cart pods or routes. e.g. Wed-Sun 11:00-20:00 |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying FastFoodRestaurant schema.
Static Physical Address Without areaServed Specification
Listing only a single home base or commissary kitchen address without declaring `areaServed` misrepresents mobile operations across city sectors.
Include `areaServed` specifying all municipal operating zones.
Omission of Contactless paymentAccepted
Omitting digital and mobile payment methods reduces trust for on-the-go lunchtime customers looking for mobile pay.
Explicitly declare 'Cash, Credit Card, Apple Pay, Google Pay' in `paymentAccepted`.
Invalid servesCuisine Array Structure
Concatenating cuisines into an unformatted single sentence rather than clean array items or comma-delimited strings.
Structure `servesCuisine` as an array of recognized food taxonomy strings.
Recommended Implementation Scenarios
Related Schema Blueprints
Explore complementary structured data blueprints across the Local Business cluster.
Fine Dining Tasting Menu & Michelin-Style Restaurant Schema Markup (JSON-LD)
Catering & Private Chef Service Schema Markup (JSON-LD)
Pizzeria, Wood-Fired Pizza & Delivery Schema Markup (JSON-LD)
Craft Brewery & Taproom Tasting Room Schema Markup (JSON-LD)
Displayed below main page header or above the tool container. • Zero CLS Container