Post by account_disabled on Feb 26, 2024 22:55:43 GMT -5
The way of truly marking up individual menu items and their prices let alone specifying different types of menus such as breakfast lunch dinner and so on. menupagemockup.jpg Well restaurant owners and tse w do SEO for restaurants rejoice With their latest release Schema.org has added several new properties and types that will allow markedup menus to truly be structured data. And while this article is addressed particularly to restaurants any business that serves food or drinks such as coffee sps bakeries cafes bars and so on can use these new properties and types to mark up their menus.
The new menu properties types The first thing youll notice when you visit the schema.orgRestaurant page is that the Kazakhstan Pne Number List menu property has been replaced with the hasMenu property. But if your current markups are still using the old menu property dont worry everything will still work until you get around to updating things. Heres what else has been added for restaurant menus A new menu type. Menus officially become entities in Schema.org with their own properties and subtypes. The new Menu type includes a hasMenuItem property.
This property would be used to point to the also new MenuItem schema type which is what would be used to mark up individual menu items. Since most restaurants feature a few menus such as one for breakfast one for lunch and one for dinner there is a new hasMenuSection property and a MenuSection type that can be used to mark up the various menus. the different sections of each particular menu such as the appetizers salads main courses and desserts on a dinner menu. For each MenuItem were able to mark up the name description price and nutritional information. And while its not new to schema you can also use the suitableForDiet property to denote if the menu item is low calorie low fat low salt vegan glutenfree or suitable for various.
The new menu properties types The first thing youll notice when you visit the schema.orgRestaurant page is that the Kazakhstan Pne Number List menu property has been replaced with the hasMenu property. But if your current markups are still using the old menu property dont worry everything will still work until you get around to updating things. Heres what else has been added for restaurant menus A new menu type. Menus officially become entities in Schema.org with their own properties and subtypes. The new Menu type includes a hasMenuItem property.
This property would be used to point to the also new MenuItem schema type which is what would be used to mark up individual menu items. Since most restaurants feature a few menus such as one for breakfast one for lunch and one for dinner there is a new hasMenuSection property and a MenuSection type that can be used to mark up the various menus. the different sections of each particular menu such as the appetizers salads main courses and desserts on a dinner menu. For each MenuItem were able to mark up the name description price and nutritional information. And while its not new to schema you can also use the suitableForDiet property to denote if the menu item is low calorie low fat low salt vegan glutenfree or suitable for various.