Primary route
The first screen should tell a café prospect what you do, where you work, what the next step is, and why they can trust the page enough to keep reading.
Ask for a Cafés quoteA café website that shows your menu as a proper page (not a PDF), pushes your opening hours into Google's knowledge panel, and links out to Deliveroo and Uber Eats from the hero.
Start Your Cafés Site →Café websites have one job: turn a local search into a visit, order, or delivery click.
Your customer is checking whether you are open now, what is on the menu, where you are, and whether they can order before they choose the café down the road.
Every site I build for cafés is engineered around that one action — structured opening hours, HTML menus, food photography, map details, allergen information, and delivery links all working together to get the customer through the door or into checkout.
The first screen should tell a café prospect what you do, where you work, what the next step is, and why they can trust the page enough to keep reading.
Ask for a Cafés quoteI'd scope the site around four decisions: what a visitor needs to see before they trust you, the action that should be easiest on mobile, the pages that deserve to exist for search, the proof you genuinely have and the proof you still need to collect. That keeps the page practical rather than decorative.
Choose a planI can describe what a strong café site needs. I won't claim I've shipped client results in this industry unless the facts file supports it.
See capability examplesYour menu rendered as HTML, split into sections (breakfast, lunch, cakes, drinks). Prices next to each item, allergen icons where relevant. I mark it up with schema.org/Menu so Google can surface items in search. You send me a spreadsheet when the menu changes and I update it, or I give you a simple editor if you want control.
Your hours rendered in plain text on the contact page, plus schema.org/OpeningHoursSpecification in the page head. Google reads the schema and pulls 'Open now / Closes 5pm' into the knowledge panel. I also handle bank-holiday overrides so Boxing Day doesn't tell customers you're open when you're not.
A gallery of your food, shot in natural light if possible. I build a masonry grid that loads fast, with lazy loading below the fold. Each image gets alt text for accessibility and search. Customers decide whether to walk in largely on photos, so the gallery earns its space on the homepage.
Deliveroo, Uber Eats, and Just Eat links rendered as proper buttons in the hero and footer, with the right brand colours. I check each link works and tracks as an outbound conversion. If you have a direct-order page, that gets a primary button and the third-party apps sit secondary.
An embedded map, pinned to your exact door (not the middle of the street). Below it, a short paragraph on parking, the nearest tube or bus stop, and whether you're pram-friendly. These are the questions customers actually ask, and answering them upfront reduces the 'are you easy to find?' emails.
An allergen page linked from the menu, with each item tagged (vegan, vegetarian, gluten-free, contains nuts). This is a legal requirement in many contexts and a trust signal for everyone. I build it as a filterable list so a customer with a nut allergy can see at a glance what's safe.
Starter is £250 and I deliver in 10 working days. For a café that covers a homepage, a menu page, a contact page with map, and an allergen page. You send me a menu spreadsheet, photos, and opening hours. I draft the copy, you review, we go live.
I build on Next.js with the menu as structured data. Hosting is Vercel's free tier. Your site will load in under two seconds on a phone, which matters when a customer is standing on your doorstep checking whether you do oat milk before they walk in.
If you want an online ordering system, a loyalty integration, or event-booking for private hire, that's Business at £400 or Growth at £1,000.
The menu-as-PDF problem is everywhere. PDFs don't render well on phones, they're invisible to Google, and customers hate them. HTML menus cost nothing to maintain once they're built, and they do ten times the SEO work.
The other issue is opening hours copy-pasted into a paragraph. Google can't reliably parse 'We're open Mon-Fri 8-4, weekends 9-5'. Structured schema fixes it in one pass and you'll see your café's hours in the search sidebar within a few weeks.
Yes, if you want to. I can set up a simple Google Sheet that the site reads from, or a small CMS. On the Starter plan I do menu updates for you (within reason). Most café owners prefer that so they're not learning new software during service.
Instagram is great for repeat customers. A website is for new ones. Someone searching 'best flat white near Victoria' finds a website first, an Instagram much later. The two work together. I can embed your Instagram feed on the homepage so the site stays fresh.
For a simple 'email to book' flow I add a form. For proper reservations I integrate ResDiary or a similar tool (Business plan). Most small cafés don't need full reservation software, but if you take private hire for birthdays the form is worth having.
No, I'm not a photographer. If you don't have photos yet, I'll point you at a few local food photographers and I'll size and crop whatever you send. Good natural-light phone photos are genuinely fine for a café site.
Tell me about your business. I'll come back with a fixed-price proposal within 24 hours. No pitch, no pressure.
Get My Cafés Proposal →