[01] website
Branding and ordering site
- branding, a 36-item price list, ordering by route and delivery day
- serverless site: Cloudflare Worker + storage + email delivery
- confirmation to the buyer and the farmer, every order archived
// work / wegom
Wegom
Farm-to-door beef delivery on two delivery days a week around Esztergom and the Danube Bend. In mid-September there was no website, no branding and no tracking; the ordering site went live in early October, and by early November landing pages from the weekly Marketing.OS SEO plan and the first campaigns are running.
- typewebsite · marketing
- channelsGoogle · Meta · SEO
- deliveredbranding · ordering site · landing pages
- livewegom.hu ↗
The starting point
A good product and a page mock-up built with ChatGPT whose form sent nothing anywhere. Orders came by phone and messages; products, prices and delivery routes were organised only in the owner's head. No domain strategy, logo, colours, and of course no tracking.
What we do
[02] SEO + content
Landing pages for the searches
- weekly SEO plan: delivery page, restaurant page, product pages
- knowledge base and articles, published automatically after approval
- Google Business Profile prepared as a service-area listing
[03] campaigns + monitoring
Marketing.OS
- Meta consumer campaign, Google Search for restaurants
- daily campaign watchdog, weekly decision email, monthly report
- every piece of content approved by the owner
The technical decisions that keep it cheap and stable
- No server, no monthly hosting fee. The site is static; orders land in a Cloudflare Worker that validates the town and delivery day, stores the order with a one-year retention and confirms by email. If email delivery failed, the order still would not be lost and the buyer gets a fallback.
- Publishing is git-based. Marketing.OS writes the approved landing page into the repository and GitHub Actions deploys it; every change leaves a trace, and a bad publish is reverted in one move.
- Canonical URLs from day one. www and http redirects, one address per page — nothing to fix afterwards, because it was part of the starting architecture.
- No orphan blog posts. A new article can only go live if it also lands on the index page and gets internal links; the publishing flow enforces this, not human attention.
- Machine rules for copy. The farmer takes no online payment; the system checks every generated text so it never promises it, while letting the negated sentence ("no online payment") through.
How
- Product and ordering first, marketing second. No campaign started until there was somewhere to send the traffic.
- Small budget, fast feedback. The restaurant Google campaign got no impressions in three days because of the bid; the system flagged it, we reallocated the budget, and the Budapest restaurant campaign was already running.
- The owner decides, the system executes. Article, landing page, ad: everything is approved on the dashboard and then goes live on its own.
Outcome in the first month
From nothing to a working ordering site with branding and tracking in seven weeks. In the first month ad spend was 6% of online order value, two new landing pages from the weekly SEO plan are live, and Google has started showing the site for purchase searches beyond the brand name. This is our newest project: the numbers are still building, the system is already at work.
A producer, maker or local service that wants to take orders online? Let's start with a conversation: we'll tell you what you need and what you don't.
$ lets_talk →