Farm and Agriculture Website Design

A farm website has to present a range that changes month by month, answer the tonnage questions of wholesalers and processors, and show exactly what each certificate covers, all at once. We wrote this guide for growers, orchards, greenhouse operations and agricultural businesses that want their site organized the way a buyer thinks.

The sections follow the order in which decisions get made on a project: who you sell to, then season data, produce pages, the enquiry form and certificates, then photography, traceability, direct sales, export buyers, search and measurement. Each section gives you something to apply today.

01Start with who actually buys from you

The structure of the site follows the type of buyer that brings in your revenue, not the list of crops you grow. A wholesale market trader, a supermarket category buyer, a processing plant, an importer and a family ordering a weekly veg box all look for the same tomatoes with very different questions. On a wholesale farm the first screen belongs to produce, season and the enquiry form; on a farm selling direct it belongs to the grower, ordering and delivery areas.

Bring answers to these questions to the first call; they decide the menu order and the default path of the form:

• Revenue split: Last season, how much of your volume went to trade buyers and how much to consumers?
• Decision maker: On the trade side, who chooses the supplier: a buyer, a quality manager or the owner?
• Paperwork: Which certificate or lab report do buyers ask for before they request a quote?
• Geography: Do you sell only in your home market, or do you work with buyers abroad or want to?
• Growth target: Which channel do you want to grow over the next two seasons? The site should serve that channel first.

Write the answer down as one sentence, for example "wholesale cherries are the core business, farm boxes are a side line". Every design and copy debate later gets settled against that sentence.

02Turn the harvest calendar into data

A harvest calendar should be a data table that feeds the whole site, not a picture. Uploaded as an image, it has to be redrawn every year, it soon contradicts the produce pages and search engines cannot read what is inside it. Kept as a table, the produce pages, the calendar page and the downloadable list all draw from one source.

We build that table with you in five steps:

1. Crop and variety: One row per variety; not "apples" but "Gala" and "Braeburn" as separate rows.
2. Harvest months: The month picking starts and ends in a normal year, plus any period of sales from cold storage.
3. Status field: Four fixed values such as available, limited, preorder and out of season, chosen from a list rather than typed freely.
4. Update owner: Who changes the status in the field and on which day, for example every Monday morning.
5. Note field: One short line for things like a weather delay.

The status field is the most frequently changed piece of information on a farm website, so it should take one tap in the admin panel and work comfortably on a phone. When harvest slips by weeks, change the status rather than the months, so buyers see the delay instead of dates that silently move.

03What every produce page should carry

A produce page should answer the questions a wholesale buyer would otherwise ask on the phone. Before asking for a price, a buyer wants to know exactly what the product is, how it is packed and how well it keeps. If that information is missing, the enquiry gets completed on the third call instead of in the first message.

• Specification: Variety, class or size grade, color and sugar level where relevant, with the way each is measured.
• Packaging: Crate, carton or sack type, net weight per unit and pallet configuration; whether you can pack to a customer's specification.
• Storage and shelf life: Recommended temperature and humidity, whether a cold chain is needed, and your own cold storage capacity if you have it.
• Origin: Region, altitude, soil or greenhouse type, the details buyers associate with quality.
• Linked certificates: The certificates that cover this crop and the date of the latest lab report.

Do not delete a page when its crop goes out of season. Keep the same address, show the status as out of season and state the next harvest window; a deleted page loses both its search visibility and the buyer's bookmark. If your range runs to hundreds of lines, a filterable catalog structure is easier for you and the buyer than managing pages by hand.

04Design the wholesale enquiry form with your sales team

A good wholesale enquiry form collects everything your sales side needs before quoting, in one go, and nothing more. The person who builds quotes on the phone should define the fields, not a designer. In the first meeting we ask that person how they completed the last ten enquiries and turn the answers into the field list.

1. Produce: Prefilled when the enquiry starts on a produce page, with the option to add a second crop.
2. Quantity and unit: A number with a choice of tonnes, cases or pallets, plus a one off or regular supply question.
3. Packaging: Your standard options in a list, special requests in a short text field.
4. Delivery: Delivery point, the date window required and who arranges transport.
5. Buyer details: Company, contact person, phone and email; billing details are not needed at this stage.

Once the form is sent, the buyer should get an automatic reply saying when you will respond, and the enquiry should land in your inbox, and on WhatsApp if you want, tagged with the page it came from. Keep required fields to five and make the rest optional; that balance keeps the data complete without people abandoning the form. A click to call button should stay visible on every produce page for buyers who prefer the phone.

05Build the certificates page around a buyer's checklist

The certificates page should answer an auditor's questions before anyone opens a PDF. A logo tells a buyer that a certificate exists, but not which crops, which fields and which period it covers. GLOBALG.A.P., Red Tractor or an organic certificate shown without its scope sends the buyer straight back to the phone.

For each certificate the page should show:

• Issuing body: The full name of the certification or control body and the certificate number.
• Scope: The crops, sites or greenhouses covered, and a clear note of what is not covered.
• Validity: Start and expiry dates, and whether a renewal is in progress.
• The document: A legible PDF copy, with any personal data redacted.
• Lab reports: If you commission residue or quality tests, the laboratory name and report date.

Enter expiry dates in the admin panel and have a reminder sent a month before each one. An expired certificate that still looks valid is a bigger trust problem than a certificate that is not shown at all. We always work from the certificate itself and never widen its scope in our own words.

Link certificates to produce pages as well. A buyer on the cherry page should see only the certificates that cover cherries, without scanning the whole list.

06The word organic and other growing claims

Use the word organic only for produce that is certified by an approved control body. In the UK, GOV.UK guidance states that using organic in the labelling or advertising of food that has not been inspected and certified is breaking the law.

In the EU, Article 30 of the EU organic regulation governs terms referring to organic production, and in Turkey, Article 8 of Law No. 5262 reserves the organic label and logo for organic products and requires promotion that does not mislead. Website copy, product names and image captions all count as promotion.

Uncertified produce grown with care still has plenty to say; it just needs methods instead of claims. We run this check at the copy stage:

• Scope match: Does every product labeled organic appear, under the same name, in the scope list on the certificates page?
• Mixed ranges: Where certified and uncertified produce share a page, are they visually separated?
• Method copy: For uncertified produce, are irrigation, feeding and pest control described concretely instead?
• Unbacked descriptors: Can words like natural, chemical free or spray free be supported by a test or a document?
• Conversion period: Have you asked your control body how produce in conversion may be described?

The final legal assessment belongs to the farm and its adviser. We prepare the copy against this checklist and flag every doubtful phrase to you before publishing.

07Photos that show the farm, sized to load fast

Real photos of fields, greenhouses and harvest answer a buyer's question about origin at the moment it comes up; stock images make every farm look the same. Treat photography as a plan that runs through the season rather than a single shoot, so each produce page opens with an image of its own harvest.

1. Early season: Blossom, seedlings or planting, and wide shots of the land.
2. Harvest: Picking, grading and close ups of the produce; the main images for produce pages come from here.
3. Packing: Crates, cartons and pallets; this is exactly the photo a wholesale buyer looks for.
4. People: Portraits and working shots, with written consent from everyone shown.

Caption photos with place and month; a short note like "May, upper orchard" turns an image into evidence. Many buyers open the site in a market hall or a packhouse on a weak mobile signal, and phone photos are often several megabytes, so run them through an image resizer before upload.

Google's Core Web Vitals give a concrete target. LCP, which measures how long the largest element takes to load, is good at 2.5 seconds or less; INP, which measures how quickly the page responds to a tap, at 200 milliseconds or less; CLS, which measures layout shifting during loading, at 0.1 or less. On produce pages led by a large photo, LCP mostly depends on that image, and fixed image dimensions prevent the shifting.

08Traceability with QR codes and batch pages

A QR code on the packaging connects the product on the shelf to your farm website when it opens the produce page or the details of that batch. For this to work, the address it opens must not change for years; thousands of printed cartons should never turn into broken links after a redesign.

The fields we suggest for a batch page:

• Batch code: Exactly as printed on the pack, and searchable on the site.
• Harvest date and site: Which orchard, field or greenhouse, and which week it was picked.
• Packing date: Where and when it was packed.
• Related documents: The certificate covering that batch and any lab report.

Start simple: one code pointing to the produce page adds value before any batch system exists. Generate the code with a QR code generator, print it at actual size on the real packaging and test it with several phones, under cold store lighting and on a curved surface. Keep the quiet zone around the code and keep it clear of seams and folds.

09Farms that sell direct to consumers

When you sell direct, the site has to answer "how does this reach me" on the first screen. Customers want to see the farm and the people behind it, but at the moment of decision they look for delivery areas, how to order and what is ready now.

• Delivery areas: Which towns or postcodes get deliveries on which days, and whether you ship further.
• How to order: A prefilled WhatsApp message with produce and quantity, or a simple box request form.
• Boxes and subscriptions: If you offer weekly or fortnightly boxes, how the contents change with the season.
• Visits and harvest days: Farm shop hours, pick your own days and how to book.

As orders grow, a WhatsApp based process stops being enough. Once stock, payment and delivery slots need to be managed together, a full e-commerce setup is worth assessing, and we plan for that from the start by building produce pages and addresses that can later turn into a shop. Every form that collects personal data needs a privacy notice, the order form included.

10Language and paperwork for buyers abroad

An overseas buyer wants to read your site in their own language and trade terms, and to see the certificates first. An English page produced by raw machine translation can mangle variety names and pack sizes, and an importer's quality team notices on the first read. We recommend a separate, carefully written version per market.

• Trade terms: Produce and variety names as that market knows them, size and class according to its standard.
• Units: Weight, pallet and container details in the units the buyer uses, both side by side if needed.
• Delivery terms: Which Incoterms you work with and which port or border crossing you load from.
• Documents: The certificates that market asks for listed first, with an explanation in that language.
• Contact: A named person who writes in that language and a reply time that allows for the time difference.

Language versions are connected with hreflang annotations; each version must reference itself and all the others, otherwise Google cannot pair them correctly. We cover the setup in detail on our multilingual website page. Keep the number of markets small, since two well maintained languages bring more enquiries than five neglected ones. Decide which language to add by looking at where your enquiries came from over the last two seasons.

11Showing up for crop and region searches

Agricultural buyers usually search for a crop together with a region, a variety or the word wholesale, and each produce page should answer one of those searches. Queries like "Kent cherries wholesale", "Turkish dried apricots supplier" or "vine tomato grower" belong to the matching produce page, not the home page.

1. Search list: Write down how buyers describe you on the phone; those phrases are the raw material for page titles.
2. Preseason updates: Refresh produce pages weeks before harvest, because that is when buyers plan supply.
3. Business Profile: Use your real world business name in the Google Business Profile; Google's guidelines do not allow added keywords in the name.
4. Structured data: Mark up business name, address, phone and opening hours so search engines can read them.

A farm that sells only wholesale and does not receive visitors can hide its address and show a service area; with a farm shop or visiting days, the address should be visible. As the number of produce pages grows, technical structure and internal links matter more, and we plan that together with the harvest calendar as part of our SEO service. Check how a busy produce page opens on a phone with the mobile friendly test; buyers usually land on that page directly, not on the home page.

12Measuring which crop brings enquiries

Visitor numbers say little to a farm; the real question is which produce page brings enquiries, in which month and in which language. Setting up measurement from day one lets you end the season with data rather than guesses.

• Conversion events: Enquiry form, click to call, WhatsApp clicks and certificate downloads counted separately.
• Source page: Every enquiry stored with the produce page and language version it came from.
• Enquiry quality: Your sales side marks each enquiry as quoted, sold or not a fit.
• Season report: When harvest ends, a one page review of enquiries and sales per crop.

Measurement tools process personal data, so a privacy notice and cookie consent belong on the site. In the EU, consent is needed before non essential tracking, and Google requires consent mode for measurement and personalized advertising features for visitors in the European Economic Area; if you sell into Europe, set this up from the start. Marking enquiry quality takes seconds, but only those marks show which page actually sold produce.

13Common mistakes on farm websites

Most of these mistakes come from treating the site as a one time job rather than bad intent. Each item includes the better alternative:

• Uploading the calendar as an image: It gets redrawn every year and contradicts the produce pages; build it as a table updated from the admin panel.
• Deleting out of season produce: Search visibility and buyers' bookmarks disappear; keep the page, set the status to out of season and show the next harvest.
• Showing certificates as logos only: Buyers cannot see the scope; list each one with issuing body, scope and expiry date.
• Using organic as a general quality word: It creates legal risk; use it only for certified produce, together with the scope.
• Asking only for name and phone: Every enquiry then needs several calls; ask for quantity, packaging, delivery point and date in the form.
• Depending on someone else for updates: In harvest week the site shows last year; insist on a panel where you change status and certificate dates yourself.

You can check your current site against this list today. If more than two items apply, the problem lies in the structure rather than the design, and planning a new structure may take less effort than patching the old one.

14Choosing a partner and the next step

Choose the team for your farm website by how quickly it understands your season and your buyers. A team that shows designs before asking about your range, harvest months and certificates is heading for a generic template. Ask these questions before you take a quote:

• Can we update season status and certificate dates ourselves, from a phone?
• Who decides the fields of the wholesale enquiry form, and based on what?
• How do you check organic and other growing claims before publishing?
• Will out of season produce pages and the QR addresses on our packaging still work years from now?
• How will we see which produce page brings enquiries, and in what report?
• Who takes the photos, and how is the shoot scheduled around our harvest?

We do not have a live client project in agriculture yet; we show our approach on a live demo site linked on this page, and the demo is not a client site. You can read about scope and process on our web design service page and see fixed packages in the pricing section. Share your produce list, harvest months and certificates through the contact form, and we will work out a page structure and a written quote with you.