Meal prep service website content checklist
A meal prep site sells a weekly habit, so it needs clear plans, honest portion and nutrition details and a delivery area people can check. The slow parts are nutrition data, delivery zones and consent for customer photos.
Where to start
- Brand and legal. Registration and terms of sale come from outside the kitchen and take time to track down.
- Menu and plans. Plan names and pricing set the structure for the ordering flow and the home page.
- Nutrition and dietary. Nutrition data is the slowest to get right and has to be settled before any dish page is built.
- Delivery and pickup. Zones feed the address checker, so they need confirming before the checkout is tested.
- About. The story and photos take a week to gather, so start them while the plans are being built.
The checklist
Home
Visitors are comparing you with cooking at home and with two other services, so the first screen has to say what arrives, when and for how much.
- Service name as it should appear Short text, requiredUse the name on your containers and invoices. If customers know a short version, give both and say which leads.
- One-line description of the service Short text, requiredWho it is for and what arrives, in under 16 words. For example: 'Chef-cooked high-protein lunches and dinners, delivered every Sunday across Austin.'
- Hero photo of the meals Image upload, requiredA landscape photo of five or six real containers as customers receive them, in good light. At least 2400 pixels wide, with no stock food.
- Main call to action Single choice, requiredPick the first step you want visitors to take. The home page and the header button are built around it.Choose a planSee this week's menuCheck delivery to my addressOrder a trial box
- Who the service is for Multiple choice, requiredTick the customer groups you can serve well today. Each one can get its own landing page.Busy professionalsAthletes and gym membersWeight managementFamiliesOlder adultsPost-surgery recoverySpecial diets
Menu and plans
People decide on the plan after reading what a week of food looks like, and most meal prep sites hide that behind a login.
- This week's menu File upload, requiredThe menu you send to customers now, with every dish name and description. A document or spreadsheet is better than a screenshot.
- Plan names, meals per week and prices Long text, requiredFor each plan list meals per week, price per meal or per week and any discount for a longer commitment.
- Portion sizes Long text, requiredWeight or volume per container, by plan. 'Large' means little until it is in grams or cups.
- How often the menu changes Single choice, requiredChoose the real cycle. Customers who expect weekly variety and get a fixed list cancel quickly.Every weekEvery two weeksMonthlyFixed core menu with rotating extras
- Order cut-off Short text, requiredThe day and time after which a customer can no longer change next week's order, for example 'Wednesday 6 pm'.
- Ordering system or link LinkThe platform where customers pick meals and pay, if you already have one. Leave empty and the designer will ask about options.
- Meal photos Image upload, requiredOne photo per core dish, in a container, on a consistent background and in the same light. At least 1800 pixels wide.
Nutrition and dietary
Customers choose meal prep to hit a target, so calories and ingredients have to be right, and wrong numbers lose trust fast.
- Nutrition information per dish File upload, requiredCalories, protein, carbohydrate and fat per container, from a spreadsheet or the software you use. Note who calculated them and when.
- Method used to calculate nutrition Short text, requiredName the tool or database, such as a recipe software or a dietitian's sheet. The page will say numbers are estimates if that is the case.
- Dietary labels you use Multiple choice, requiredTick labels you apply only after checking every ingredient, including sauces and oils.VegetarianVeganGluten freeDairy freeNut freeLow carbHigh protein
- Allergen and cross-contact statement Long text, requiredHow the kitchen handles allergens and whether dishes share equipment. Rules on written allergen information vary, so check them where you operate.
- Health claims check Yes or no, requiredConfirm no one will write claims about treating or curing a condition on the site, and say who approves wording about weight or health.
- Dietitian or nutritionist involved Short textIf a qualified person designs or reviews the plans, give their name and credentials as they should appear, and confirm they agree to be named.
Delivery and pickup
A customer's first question is whether you reach their address, and unclear zones create refunds and bad reviews.
- Areas you deliver to Long text, requiredList the postcodes, zip codes or neighbourhoods you cover. The site will use this for an address checker, so spell each one out.
- Delivery days and time windows Long text, requiredWhich days you deliver, the window for each area and what happens if nobody is home.
- Delivery fee and free delivery threshold Short text, requiredThe fee by area and the order value above which it is free. Customers compare this across services.
- Pickup points Long textAddresses, collection hours and any rule about unattended pickup. Leave empty if you only deliver.
- Storage and reheating instructions Long text, requiredHow many days meals keep in the fridge, whether they can be frozen and the reheating steps by dish type.
- Container return or recycling scheme Yes or noSay whether customers return containers or recycle them, and give the steps if there is a scheme.
About
Customers trust a person with their meals, and a short story with a real kitchen photo beats any claim about quality.
- How the service started Long text, requiredWhen it began, who cooks and what problem you set out to solve. Two short paragraphs with facts, not adjectives.
- Chef name, role and photo Image upload, requiredA photo of the chef in the working kitchen, with name and role in the file name. At least 1500 pixels on the short side.
- Kitchen photos Image uploadThe prep line, the packing table and the delivery van, in daylight. Avoid anything showing staff who have not agreed to appear.
- Customer reviews with permission Long textTwo to four short reviews with first name and neighbourhood. Copy them word for word and confirm each person agreed.
- Before and after photos permitted Yes or noConfirm whether any customer transformation photos have written consent, and who holds it. Without consent, the designer leaves them out.
Brand and legal
Terms of sale and food registration are the content that arrives last, so ask for it while the menu is still being sorted.
- Logo files File upload, requiredSVG, EPS or PDF vector files in colour and one colour, plus a square version that fits a social profile or a container lid sticker.
- Brand colours ColourThe main colour from your containers or stickers as a hex code. Add one accent colour if you use it on the menu.
- Brand fonts FontThe typeface on your menu cards and container labels. If a designer made them, ask for the name and licence.
- Food business registration confirmed Yes or no, requiredConfirm the kitchen is registered with the food authority where you operate, and say who holds the certificate.
- Terms of sale File upload, requiredYour current terms covering cancellations, missed deliveries and refunds. The designer will summarise them and link the full file.
- Privacy and cookie policy approved Yes or no, requiredCustomers hand over addresses, diets and payment details. Say whether a policy exists or a template should be drafted for review.
What clients get stuck on
Macros typed by hand into a spreadsheet
Ask who calculated the calories and protein and with what tool. A hand-typed sheet drifts from the recipe within weeks, and customers who track macros will notice before you do.
Delivery zones drawn from memory
Get a list of postcodes or a map from the driver who runs the route. The owner's idea of the area usually includes streets the van does not reach in a delivery window.
Menus finished the night before they go live
Agree a weekly deadline with the chef and put it in writing. If the menu arrives on Saturday for a Sunday launch, the site will show last week's dishes.
Reheating steps for every dish
Ask the chef to write them once for each dish type, with microwave and oven times. Customers who reheat wrong blame the food, and the site is where this is meant to be fixed.
Customer photos with no written consent
Transformation shots and testimonials need a clear yes from the person. Ask where the consent is held, and if there is none, leave the photo out.
Copy the checklist
Plain Markdown you can paste into a doc or an email.
# Meal prep service website content checklist
## Home
- [ ] Service name as it should appear (Short text, required)
- [ ] One-line description of the service (Short text, required)
- [ ] Hero photo of the meals (Image upload, required)
- [ ] Main call to action (Single choice, required)
- [ ] Who the service is for (Multiple choice, required)
## Menu and plans
- [ ] This week's menu (File upload, required)
- [ ] Plan names, meals per week and prices (Long text, required)
- [ ] Portion sizes (Long text, required)
- [ ] How often the menu changes (Single choice, required)
- [ ] Order cut-off (Short text, required)
- [ ] Ordering system or link (Link)
- [ ] Meal photos (Image upload, required)
## Nutrition and dietary
- [ ] Nutrition information per dish (File upload, required)
- [ ] Method used to calculate nutrition (Short text, required)
- [ ] Dietary labels you use (Multiple choice, required)
- [ ] Allergen and cross-contact statement (Long text, required)
- [ ] Health claims check (Yes or no, required)
- [ ] Dietitian or nutritionist involved (Short text)
## Delivery and pickup
- [ ] Areas you deliver to (Long text, required)
- [ ] Delivery days and time windows (Long text, required)
- [ ] Delivery fee and free delivery threshold (Short text, required)
- [ ] Pickup points (Long text)
- [ ] Storage and reheating instructions (Long text, required)
- [ ] Container return or recycling scheme (Yes or no)
## About
- [ ] How the service started (Long text, required)
- [ ] Chef name, role and photo (Image upload, required)
- [ ] Kitchen photos (Image upload)
- [ ] Customer reviews with permission (Long text)
- [ ] Before and after photos permitted (Yes or no)
## Brand and legal
- [ ] Logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Food business registration confirmed (Yes or no, required)
- [ ] Terms of sale (File upload, required)
- [ ] Privacy and cookie policy approved (Yes or no, required)
Questions about this checklist
Should meal prep prices be shown per meal or per week?
Show both. Customers compare per-meal cost across services, but they pay per week. Lead with the figure that makes the comparison fair and give the weekly total next to the plan.
Do meal prep sites need nutrition panels on every dish?
Rules on nutrition and allergen labelling vary, so check them where the client operates. Even where it is not required, calories and protein per container are what customers look for, so ask the chef for reliable numbers.
Related checklists
Catering company
A catering site has to show what the kitchen can serve, for how many guests and at roughly what price per head, then make an enquiry easy. The slow parts are sample menus, event photos with permission and an honest delivery area.
Restaurant
A restaurant site needs a current menu, real photos of the room and the food, opening hours that match Google, and a clear way to book. Most delays come from menu PDFs and photos.
Nutritionist
A nutritionist's site has to say who you help, what a programme looks like and what it costs, without health claims that overreach. The usual delays are credential wording, programme pricing and a lead magnet nobody has made yet.