Skip to content

Google Business Profile Dietary Attributes: Restaurant Playbook

Google added gluten-free, dairy-free, halal and kosher dietary badges to restaurant menus on Business Profiles. Here is how to set them up accurately.

11 Oct 202610 min read
  • Local SEO
Dish on white ceramic plate, illustrating Google Business Profile Dietary Attributes: Restaurant Playbook

Google is rolling out dietary badges for restaurant menu items in Google Business Profile: gluten-free, dairy-free, halal and kosher, joining the vegetarian and vegan badges that already existed. As reported on 13 October 2026, restaurants add them item by item through "Edit menu", so the work is a menu-data task, not a profile-settings tweak. Do it per dish, do it accurately, and keep your website menu consistent with it.

Key Takeaways

  • Four new dish-level dietary badges (gluten-free, dairy-free, halal, kosher) were announced on 13 October 2026, alongside existing vegetarian and vegan badges.
  • You set them by opening your profile, choosing "Edit menu", selecting an item and ticking the badges. They attach to dishes, not to the whole restaurant.
  • Google's developer documentation shows the API enum also carries allergen and nutrition fields, so structured menu data is clearly the direction of travel.
  • Nobody has said Google verifies these claims. A wrong "gluten-free" badge is a customer-safety and trust problem, not just an SEO one.
  • The practical job this week: audit your top 30 dishes, tag only what your kitchen can stand behind, and match your website menu.

What Google actually announced (as of 14 October 2026)

The news comes from Search Engine Roundtable, which reported on 13 October 2026 that Google is expanding dietary attributes for restaurants in Business Profiles. Barry Schwartz wrote that the new tags are gluten-free, dairy-free, halal and kosher, with vegetarian and vegan already available. The source is a LinkedIn post by Google's Lisa Landsman, who said that for millions of diners with specific dietary needs, dining out requires careful planning. The same post says tagged dishes help items "stand out right on your profile". A secondary write-up dated 14 October repeats the same details and cites no separate Google help page.

Here is what I could not confirm from those sources: which countries get the rollout, whether every account has it today, and how Google checks the claims. Treat "rolling out" literally. If you do not see the badges yet, check again in a week before assuming you did something wrong.

Where the badges live: dishes, not the profile

Google's own menu editor help page describes the editing flow: you open "Edit menu", and each item has a name, description, price and optionally a photo, grouped into sections. Changes can take 24 to 48 hours to appear on Maps and Search. The help page I read does not list the dietary badges, which suggests the documentation has not caught up with the rollout. I am therefore relying on the Search Engine Roundtable description of the flow for the badge step.

Two practical consequences follow:

  • Multi-location brands managing menus through the Business Profile API may not see the editor in the interface at all. Google's page says API-fed menus may not have the feature in Business Profile or Search.
  • Google may transcribe your website menu. The same page says Google can pull menu data from your site and lets you edit, delete, or opt out of transcription. If your site menu says "contains gluten" and your profile badge says otherwise, you have created the conflict yourself.

The API signal: this is structured data

Developers will find a clearer picture. The Business Profile API release notes have an entry dated 9 October 2026 saying the DietaryRestriction enum now supports GLUTEN_FREE and DAIRY_FREE for food menu items. The FoodMenus reference lists the enum values as DAIRY_FREE, GLUTEN_FREE, HALAL, KOSHER, ORGANIC, VEGAN and VEGETARIAN. Menu items can also carry an allergen list (dairy, egg, fish, peanut, shellfish, soy, tree nut, wheat), nutrition facts, ingredients, spiciness and portion size. Allergens, dietary restrictions and nutrition facts are marked optional but recommended.

I would not read too much into one release note, but the shape is clear. Google wants menu items as structured records. The restaurants that keep a clean, central dish database will be able to push accurate data to every surface; the ones that keep a PDF and a chalkboard will not.

Dietary filters are not new in Google's local products. Back in 2023, a DAC Group write-up described Google testing saved food preferences in Maps settings, matching the attributes businesses already supply (gluten-free, halal, kosher, kid-friendly and more). The author's point then was that Google reads manually entered attributes first, so a business cannot rely on its name or website alone. That article is from 2023 and describes a test, so I use it for context only, not as evidence of how ranking works today.

My practical reading: a "gluten-free dinner near me" query has to be answered from data Google trusts. Dish-level badges give it a cleaner source than parsing review text. I cannot tell you whether badges influence ranking, and nobody has published evidence that they do. What they plausibly do is make you eligible to show up when the query specifies a diet.

A five-step audit you can finish in a day

  1. Export your menu. One row per dish: name, section, price, ingredients, allergens, preparation notes.
  2. Mark each dietary claim with its basis. "Gluten-free" must mean the recipe has no gluten-containing ingredients and the kitchen can control cross-contact, or you should say otherwise in the description. Write the basis in a column.
  3. Tag the top 30 dishes first. Sort by orders and photo views and start there. A half-tagged long tail is fine; a wrongly tagged hero dish is not.
  4. Apply badges in Edit menu and note the date.
  5. Reconcile your website, delivery apps and printed menu within the same week.

A decision table for each dish

SituationBadge it?What to write in the description
Recipe has no gluten ingredients, shared fryer or surfacesNot gluten-free"Made without gluten ingredients; prepared in a shared kitchen"
Recipe has no gluten, dedicated prepGluten-freeOptional: name the prep method
Dish uses ghee or paneerNot dairy-freeList dairy plainly
Meat sourced from a certified supplier, certificate on fileHalalName the certifier if you can
Kosher claim without certificationDo not badgeLeave out
Vegetarian dish cooked in animal-fat oilNot vegetarianFix the recipe or the label

The table is my own working template, not Google guidance. Adapt it to your kitchen.

India notes: halal, jain, veg and the claims you can prove

Many Indian restaurants already carry veg and non-veg markings by habit and by regulation. Food-labelling rules come from FSSAI, and I have not opened the current regulation text for this post, so check the FSSAI site before you change printed menus. What I can say is practical: halal and kosher are certification-type claims. If a customer asks "who certifies this?", you want a name, not a shrug. Jain and "no onion, no garlic" are not among the badges Google listed, so put them in the item description in plain words, because the description field is free text.

A restaurant menu board with handwritten dietary labels beside a laptop showing a profile edit screen

Treat the menu board and the Business Profile as one source of truth. Disagreement between them is where trust is lost.

Risks: accuracy, allergies and liability

Schwartz's own aside in the Roundtable piece is that kosher claims probably are not checked by a rabbi, so diners are trusting the restaurant. That is his suspicion, not a Google statement. Either way, the safe assumption is that the badge is your claim and your responsibility.

  • Allergy is not preference. A diner who chooses gluten-free because of coeliac disease has a medical need. Cross-contact matters. If you cannot control it, say so in the item text.
  • Staff must know. A badge online with a kitchen that does not know about it is the worst outcome. Brief the line cook and the front of house the day you publish.
  • Review the badges monthly. Recipes change when suppliers change.

I am not a food-safety or legal adviser. For compliance questions, talk to your FSSAI consultant or local food authority.

Badges say what a dish is; photos show it. Google's help page on popular dishes says owners can add a photo and name through Maps, that customers can add too, and that names you add take priority over customer-added names. If a customer has labelled your thali "vegan" in a photo caption, you can correct it. Check the Menu tab in Maps once a month and fix mislabelled or unnamed dish photos.

Measuring whether it worked

You will not see a "dietary badge impressions" report. Use proxies and keep the experiment honest:

  • Record Business Profile performance (calls, direction requests, website clicks) for four weeks before tagging.
  • Tag once, change nothing else about the profile, and compare the next four weeks.
  • Watch search terms in the Business Profile performance view for diet words ("gluten free", "halal").
  • Ask at the table: "How did you find us?" Add "searched for a diet-friendly place" as an option.

One caveat: rank trackers and local SERP checks are unreliable at the moment. I covered that in why your rank tracker is struggling, so do your checks by hand, from a phone, near the restaurant.

What food brands without a restaurant should do

Packaged-food and D2C brands do not get menu badges. The lesson still carries over: put diet, allergen and ingredient facts in structured, plain-text form on product pages and keep them identical across your site, marketplace listings and Merchant Center feed. For local retail stockists, the Business Profile attributes section is where you state "organic" or "vegan-friendly" at store level. I wrote a related checklist for local panel changes.

A short template for your internal SOP

  • Owner: one person responsible for menu data (not "the team").
  • Source of truth: one spreadsheet with ingredients and allergens.
  • Change rule: any supplier or recipe change updates the sheet first, then the profile, website and delivery apps, within 48 hours.
  • Audit: the first Monday of each month, review ten random dishes against the kitchen.
  • Escalation: if a customer reports a wrong badge, remove the badge immediately, investigate afterwards.

Frequently Asked Questions

What are the new Google Business Profile dietary attributes?

As reported on 13 October 2026, Google added gluten-free, dairy-free, halal and kosher badges for restaurant menu items. Vegetarian and vegan badges already existed. You add them per dish through "Edit menu" in your profile.

Do dietary badges improve my local ranking?

No evidence has been published that they do. What they plausibly do is make your dishes eligible for diet-specific searches such as "gluten-free dinner near me". Treat any ranking claim from a vendor as unverified.

Does Google verify halal or kosher claims?

Google has not said so in the sources I read. A Search Engine Roundtable aside suggests kosher claims are not independently checked. Assume the claim is yours, and keep certificates on file.

Where do I add the badges?

Open your Business Profile, choose "Edit menu", select an item and tick the applicable dietary badges. If your menu comes through the Business Profile API, the editor may not be available to you, and you will need your API integration to supply the data.

How long do menu changes take to appear?

Google's help page says menu edits can take 24 to 48 hours to appear on Maps and Search. Check on a phone in a normal browsing session, not only from the dashboard.

Can I use the badges if I do not have a restaurant?

The menu editor is for food and drink businesses. A shop or packaged-food brand cannot add dish-level badges, but can state attributes in the profile and keep product-page facts consistent.

What if my website menu disagrees with my profile?

Google's help page says it may transcribe menu data from your website, and you can opt out of that. Disagreement creates confusion for diners and for Google. Fix the website and the profile at the same time.

Should I tag every dish?

Start with your top 30 dishes. A smaller set of accurate badges is worth more than a full menu tagged from memory.

Is cross-contact covered by a "gluten-free" badge?

The badge does not explain your kitchen. If you cannot guarantee separation, say what the dish is made without and state that it is prepared in a shared kitchen.

What about Jain, no-onion-no-garlic or Sattvic dishes?

These were not in the badge list I read. Use the item description in plain words, and keep the same wording across your site and delivery apps.

CTA

I am Younus Fardeen, and I have 4+ years of marketing experience across SEO, AEO and content for edtech and startup teams, including growing Masai School's social following (disclosure: that was my work, not a guarantee of anything for your business). If you run a restaurant group or a food brand and want a local-search audit that starts from your real menu data, see my work and send a message through the contact form at https://younusfardeen.in.

Want help with search and AI visibility for your own site? Get in touch through the contact form.