Shopify SEO for Australian Food and Drink Brands

Quick answer: For a Shopify food or drink store, the SEO work that is specific to your category starts with the label. Put each product’s ingredients, allergen declaration and dietary tags on the page as real text that matches the pack, not only in a photo of the label, and make sure any Product schema repeats what the visible page says. Google’s guidance on its AI features says to keep important content available as text, and its structured data policy says markup must be a true representation of the page. This is general information, not legal advice: the Food Standards Code, not an SEO article, decides what your label must say.

Generic Shopify SEO advice tells you to write better titles, build links and fix speed. It does not deal with what makes a food product page different: much of its useful content is regulated label information, and on many stores that information lives inside a photo of the pack.

This guide covers what the regulator says about label content, what it does not say about selling online, and how to put ingredients, allergens and dietary tags on your product pages as text. It also covers Product schema, dietary-tag collections and filters, and the claims to be careful with.

I used the Food Standards Australia New Zealand (FSANZ) and Food Regulation websites, the ACCC, and Google and Shopify documentation for this, not blogs. Everything dated is “as at 31 October 2026”. I am not a lawyer or a food technologist, and your label wording is a job for you and a food-safety adviser, not for an SEO.

Why label data belongs in your SEO

A shopper with a food allergy or a dietary need reads the ingredients before anything else. A search engine, or a tool that answers “does this contain nuts?”, can only use the text it can read on your page. If the answer sits in a pack photo, the page does not contain it as far as that tool is concerned. Two statements from Google’s documentation make the point:

• Google’s page on AI features in Search (last updated 10 December 2025) says there are no extra requirements to appear in AI Overviews or AI Mode beyond being indexed and eligible to show with a snippet, and no special schema or new files are needed. Its listed best practices include keeping important content available as text and making sure structured data matches the visible text.
• Google’s structured data policies say your markup must be a true representation of the page content and must not describe content readers cannot see.

Neither says label text earns rankings. They say the foundations are ordinary: crawlable text, an indexed page, and markup that tells the truth.

What the rules say about label content (and what they do not)

FSANZ sets the labelling standards in the Food Standards Code. Chapter 1 covers general labelling and information requirements for all foods, and Chapter 2 covers product-specific rules. In Australia the states and territories enforce them. FSANZ also notes that fair trading and food laws prohibit false, misleading or deceptive representations (FSANZ, “Labelling”). The label is regulated, and so is what you say about the food elsewhere.

Allergen declarations

FSANZ’s allergen labelling page for businesses says Standard 1.2.3 and Schedule 9 of the Code set the allergen labelling requirements, which took effect on 25 February 2024. Key points from that page:

• What must be declared. The list includes wheat, fish, crustacean, mollusc, egg, milk, lupin, peanut, soy, sesame, sulphites, and a set of tree nuts (almond, Brazil nut, cashew, hazelnut, macadamia, pecan, pistachio, pine nut, walnut). Barley, oats and rye must be declared where they contain gluten. Sulphites must be declared when added at 10 milligrams per kilogram of food or more.
• How. Declarations go in the statement of ingredients in bold, at a font size no smaller than the other ingredients, and there must also be a separate summary statement in bold starting with the word “contains”, in the same field of view and next to the ingredients.
• Required names. Wheat must be declared as “wheat”, and if gluten is present the summary statement must include “gluten”.
• Transition. Food packaged and labelled before 25 February 2024 that met the old rules could be sold until 25 February 2026. As at 31 October 2026 that window has closed.
• “May contain” statements. FSANZ says voluntary precautionary allergen labelling is not regulated by the Code.

Ingredient lists

FSANZ’s consumer page on ingredients says they are listed in descending order by ingoing weight. The ingredients of a compound ingredient must be declared unless it is under 5% of the final food, but a known allergen in it must be declared however little is used. Standard 1.2.4 covers the statement of ingredients.

What the Code does not say about selling online

This is the part to be careful with, because it is easy to assume a rule exists. The Food Regulation website’s consultation page on prepackaged food sold online (last updated 16 December 2025) says the Code requires most prepackaged food to bear a label, but there is currently “no guidance or explicit requirements in the Code” on what information must be given to shoppers when food is sold online. The Food Regulation Standing Committee consulted on a draft policy guideline from 3 November to 12 December 2025, and ministers decide whether to adopt it. The activity page for that work (last updated 23 March 2026) says analysis of the submissions is underway. I could not find a ministers’ decision as at 31 October 2026, so check foodregulation.gov.au.

So I will not tell you that Australian law requires a particular set of fields on a Shopify product page. On the sources I read, it does not say that. My argument is practical: your label is already regulated, shoppers need the same information to decide, and the page is where search engines and other tools read it.

Claims and origin

Two more areas where product-page words matter:

• Claims about the food. Standard 1.2.7 (Nutrition, health and related claims) defines a claim as an “express or implied statement, representation, design or information in relation to a food”, and goes on to cover a property of food that is not mandatory in the Code. The definition does not mention the pack, so I treat product-page wording as capable of being a claim. Section 1.2.7-12(7) limits nutrition content claims about gluten to a set descriptor from the Standard’s table or a statement that the food contains or is high in gluten. I am not reproducing the descriptors or their conditions. I read the 13 August 2025 compilation, so check for a later one before you paraphrase anything on a page.
• Where it comes from. The ACCC says country of origin claims must be true, accurate and based on reasonable grounds, that “grown in”, “produced in”, “made in” and “packed in” have defined meanings under the Australian Consumer Law, and that the Country of Origin Food Labelling Information Standard 2016 requires most food for retail sale in Australia to carry origin information. A claim that technically fits can still mislead if extra words or images create the wrong overall impression.

The practical rule for your product pages: the page must say what the pack says, and anything the page says that the pack does not say is a claim you need to be able to stand behind.

The label fields to publish as text

These are the fields I would put on every food and drink product page as real text. The “where” column is a suggestion.

Not in the table: nutrition panels and health or nutrition claims, which I have not covered here. If you publish a nutrition panel, publish it exactly as printed on the pack. I am not giving examples of claim wording, because that is where a stray adjective turns into a legal problem.

Why an image-only label costs you

Pack photos are fine. Pack photos that are the only place the ingredients and allergens appear are the problem. Three reasons:

1. Google tells you to keep important content as text. That is in the AI features guidance quoted above. Google’s image guidance, last updated 2 March 2026, calls alt text the most important attribute for giving an image context, but it does not say Google reads the words printed inside an image, and I would not rely on it doing so.
2. Accessibility. WCAG success criterion 1.4.5 (Level AA) says that if the technology can achieve the visual presentation, text should be used to convey information instead of images of text. Someone using a screen reader, or someone who needs bigger text, cannot adjust a photo.
3. Mistakes hide in images. When a recipe changes, someone updates the pack artwork and forgets the gallery photo. One text field is easier to keep right.

The fix is not to remove the label photo. Keep it as a gallery image with a plain description in the alt text, and put the same information in text next to it.

Build it in Shopify: metafields, then the theme

Shopify’s own metafield tools can do this without an app.

1. Create metafield definitions for the label fields. Shopify’s help centre says metafields extend products with your own data, and that definitions add fields to the admin and enforce validation rules so values stay consistent. Create a text field for ingredients, a text field for the allergen declaration and, if you will use them for filters or collections, a true/false field for each dietary tag.
2. Fill them from one source. Pick whoever owns the label (you, your manufacturer or your food-safety adviser) and have the metafield copied from the approved label text. Do not retype it from memory.
3. Show them on the product page. If your theme supports dynamic sources, Shopify says you can connect most metafields to the theme in the theme editor. On older themes, or for metafield types the theme does not support, you edit theme code.
4. Make the text load with the page. Google’s mobile-first guidance suggests accordions or tabs to save space, as long as the mobile content matches desktop, and says Google won’t load content that requires user interactions. So keep the ingredients text in the page when it loads, not fetched when the shopper taps. View the page source (or Search Console’s URL Inspection) and look for the ingredients text.
5. Keep a log, not a page date. Record when each product’s label text was last checked against the pack, and re-check whenever a recipe, supplier or pack changes.

This is one more block on the page covered by our product page SEO checklist, not a new project.

Product schema: what to add and what to leave out

Shopify’s structured_data Liquid filter converts a product into schema.org structured data: a Product if it has no variants, a ProductGroup if it has variants. What Google asks for, from its merchant listing documentation:

• Required: name, image, and an offer with a price (greater than zero) and currency.
• Recommended: availability, brand, description, GTIN, SKU and others. Google says it is strongly recommended to give a product description.
• Certifications: hasCertification is a recommended property that accepts up to 10, but Google’s examples are a vehicle emissions class and an energy efficiency label. If you use it for a genuine certification you can show on the page, fine. Do not add one you cannot show.

What Google’s pages do not list is a property for ingredients, allergens or nutrition. I checked the Product page, the merchant listing page and the schema.org Product page, and none of them lists one. Schema.org does provide additionalProperty, a general property-value pair for extra characteristics, but nothing I read says Google uses it for food.

So here is how I would think about it:

• Visible text does the heavy lifting.
• Repeat the ingredients and allergen line in the description markup, because description is a property Google recommends and it keeps the markup a true match for the page.
• Never add markup for something the page does not show. Google’s policy says markup must not describe content readers cannot see, and a structured data issue can lead to a manual action that removes rich result eligibility.

Here is an illustrative example. The product, the price and the barcode are made up, and this is not checked against the Food Standards Code:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Smoked Almond Mix 200 g",
  "description": "A savoury almond and seed mix. Ingredients: almonds, pepitas, sunflower seeds, sea salt, smoked paprika. Contains: almond.",
  "image": "https://example.com.au/images/smoked-almond-mix.webp",
  "brand": { "@type": "Brand", "name": "Example Pantry Co" },
  "gtin13": "0000000000000",
  "offers": {
    "@type": "Offer",
    "price": "9.95",
    "priceCurrency": "AUD",
    "availability": "https://schema.org/InStock"
  }
}

Every word in the description should appear on the visible page, worded as on the pack. If your theme and an app both output Product markup you may get two versions that disagree. Our guide to Product schema and merchant listing errors covers how to find and fix them, and schema markup and AI citations covers what markup can and cannot do for AI search.

Google’s merchant listing page also says dynamically generated markup can make shopping crawls less frequent and less reliable, and recommends Product structured data in the initial HTML. Markup injected later by an app script is the case to check.

Dietary tags: filter, tag or collection?

Decide each dietary tag with the same test.

Make it a real collection page when shoppers search for it as a category, you have enough distinct products to make a useful page, and you can substantiate the tag for every product in it. That page then follows the usual collection page SEO rules: a unique title, an introduction that says what the range is and how you decide what goes in it, and internal links from the menu and related collections.

Keep it as a filter when it is a way to narrow a larger collection. Shopify’s Search & Discovery documentation allows up to 25 filters per store, and collections with more than 5,000 products do not display filters. Filter combinations can create many URLs, which our guide to filter URLs and index bloat covers.

Three Shopify details that bite on food stores:

• Tags are forgiving in a way you may not want. Shopify’s help says special characters in tags are either ignored or treated as the same, so a condition on one hyphenated tag also matches the same tag written with an underscore or a plus sign. Pick one spelling and keep to it.
• Tag filters have language limits. The tag filter only shows in the store’s default language, and tag values cannot be translated.
• Metafield conditions are limited. For smart collections, the metafield definition needs the collections setting switched on (up to 128 definitions), and single-line text and true/false metafields support “equals” only.

My rule for data design, which is a recommendation and not a Shopify requirement: store what the pack contains (the allergen declaration) separately from what you claim (a dietary tag). The first comes straight from the label. The second is a claim, and it should only be switched on for a product after someone has checked it.

Other food-specific page checks

• Flavours and sizes. Decide whether each flavour is a variant or its own product, and keep each one’s ingredients and allergens separate, because they can differ.
• Discontinued lines. If a flavour is gone for good, handle the page properly instead of leaving a dead end.
• Bundles and gift packs. Give each component’s ingredients and allergens in the bundle page text, not just the headline.

Supplements and baby or kids products fall under different rules: see our guides on supplements and TGA claims and baby and kids brands and product safety. This post covers ordinary food and drink; I have not covered alcohol sales.

An 8-point check for an afternoon

1. Open five product pages logged out. Can you read the full ingredients and allergen line as text, in the HTML on load, including inside any accordion?
2. Compare each to the current pack: same wording, same order?
3. List every dietary tag on the store. Who confirmed each one, and when?
4. Check origin wording against the pack and the ACCC’s definitions.
5. Run one product through a structured data tester. One Product block or two?
6. Compare the markup with the visible page: description, price, currency and availability. Anything in the markup that the page does not show?
7. Check which dietary-tag pages are collections, which are filters, and which are in the sitemap.
8. Write down who owns label changes and how the page is updated when a recipe changes.

Want a second pair of eyes on your product pages? Tell us about your store.

Key takeaways

• Put ingredients, allergens and dietary tags on the page as real text that matches the pack. Keep the label photo as a gallery image.
• As at 31 October 2026, the Food Regulation website says the Code has no explicit requirement for what information appears when food is sold online. A guideline was consulted on in late 2025, analysis of submissions was underway in March 2026, and I found no ministers’ decision.
• The Standard 1.2.3 and Schedule 9 allergen rules took effect on 25 February 2024; the transition for older stock ended on 25 February 2026.
• Google lists no ingredient or allergen property for Product markup. Use markup to describe the page truthfully, never to add content the page does not show.
• Claims on the page (gluten, origin, anything about the food) need the same care as claims on the pack. Keep “contains” data separate from claims.
• Decide each dietary tag: real collection, filter, or neither.

FAQs

Do Australian food brands have to list ingredients and allergens on a Shopify product page?

As at 31 October 2026, the Food Regulation website says the Food Standards Code has no explicit requirement on what information must be given when food is sold online, and a policy guideline was consulted on in late 2025 with no ministers’ decision found. Your label is regulated, though, and shoppers need the same information. Check foodregulation.gov.au and your state or territory regulator. This is not legal advice.

Does Google read the text on a photo of my label?

Google’s image guidance does not say it reads words printed inside images, and its AI features guidance says to keep important content available as text. Put ingredients and allergens in the page as text and keep the photo as an extra.

Is there a schema property for allergens or ingredients?

Not one that Google lists. None of Google’s Product pages or the schema.org Product page that I read lists a property for ingredients, allergens or nutrition. Put the information in the visible page and in the markup description, and keep the two matching.

Can I tag a product “gluten free” or “vegan”?

Treat any dietary tag as a claim. Standard 1.2.7 defines a claim as an “express or implied statement, representation, design or information in relation to a food”, and limits gluten claims to set descriptors with conditions. Fair trading and food laws also prohibit false, misleading or deceptive representations (FSANZ). Have someone with the right expertise confirm each tag, and the wording you use for it, before it goes live. This is not legal advice.

Should I create a collection for each dietary tag?

Only for tags shoppers search for as a category, where you have enough distinct products for a useful page and can substantiate the tag for each one. Otherwise use a filter.

Do “may contain” statements have to be on the page?

FSANZ says voluntary precautionary allergen labelling is not regulated by the Code and points to the Allergen Bureau. If your pack carries one, keep your page consistent with it and ask your adviser how to handle it.

Want a second look at your food and drink product pages?

Our Shopify SEO service covers a technical SEO audit that includes schema markup, on-page optimisation and e-commerce SEO for product and collection pages. We do not review labels or give regulatory advice: whether your label and claims meet FSANZ and the Australian Consumer Law is a question for your adviser, not for us. If you want to start with a conversation, tell us about your store or book a free 30-minute diagnostic. We look at your store before we recommend anything, and we tell you honestly if SEO isn’t the right move. No pitch.