I've spoken to four destination restaurants in the last twelve months whose answer to "what's your website strategy?" was some variation of "we just use Instagram." One was a two-chef-hat regional restaurant in Tasmania. One was a degustation-only place outside Adelaide. One was a wine bar with a tasting menu in inner Sydney. One was a coastal NSW destination with a six-week waitlist.

All four had Instagram accounts that were genuinely good. Beautiful food photography. Real audience. Engaged comments. None of them had a website worth the URL.

I want to make a careful argument here, because Instagram for restaurants is not a mistake. It's an essential discovery channel. The mistake is thinking the feed is sufficient — that a Linktree link in bio and a fortnightly story update replaces a real website. It doesn't, and the gap is costing these restaurants serious money.

What Instagram does brilliantly

Let me give the platform proper credit first, because I'm not anti-Instagram and I'd never tell a chef to spend less time on it.

Instagram is the single best discovery channel for destination restaurants in Australia. A well-shot dish, posted at 6pm with a strong caption, reaches:

Existing followers immediately.
Friends-of-followers via shares and resends.
Strangers via the discovery feed and reels.
Aggregators (Broadsheet, Concrete Playground, Time Out) who source story content from social.
Visiting food writers and critics who scout Instagram for what to try.

It's earned media at a scale that almost no other channel can match for the same effort. A single great post can drive 200–600 new followers and 50–150 booking enquiries in 24 hours. That's real distribution.

The case against relying only on Instagram is not that Instagram is bad. It's that Instagram does discovery well and conversion badly. The chef's audience grows. The booking funnel leaks.

The five things Instagram structurally cannot do

These are the gaps. Each one is a leak in the funnel that a real website would close.

1. Rank for your name on Google

When someone hears about your restaurant — from a friend, from a magazine, from a critic — the first thing they do is google the name. They don't open Instagram. They type "Brae restaurant" or "Attica menu" into Google.

If your only web presence is Instagram, the page that ranks #1 for your name is almost always not yours. It's The Australian Good Food Guide listing. Or Broadsheet. Or Concrete Playground. Or an old TripAdvisor page. Those third-party properties capture the click, run their own ads on it, and feature their own affiliate booking links — which often route through OpenTable or another network that takes a cover fee or shifts the booking to a competing venue's sponsored slot.

A real website with a domain that matches your name, proper schema markup, and a clear meta description captures that search click for you. The user lands on your page. They see your menu, your booking widget, your story. The conversion happens in your ecosystem, not someone else's.

This is the single most expensive thing Instagram-only restaurants give up. It's not visible day-to-day. It compounds over years.

2. Convert at the moment of intent

Instagram's link-in-bio is famously bad. The user has to leave the post, tap the profile, tap "Link in bio," pick from a list of links on a third-party Linktree page, then arrive at the actual destination. That's four taps and three context switches. About 75% of the users who tap "Link in bio" never make it to whatever the link is supposed to point to.

A real website with proper URL structure means a post can link directly to the menu page, the booking page, the wine list, the event page — and the user is one tap from where they need to go. That's a 4x improvement in click-through, and the booking conversion compounds on top.

The CTA infrastructure of Instagram is designed for engagement, not action. The CTA infrastructure of a real website is designed for action.

3. Hold the menu, the price, the policy

A booking decision at a destination restaurant requires information. What's on the menu? How much? Is there a vegetarian option? What's the deposit policy? Can the kitchen accommodate gluten-free?

Instagram cannot hold this information. You can post a menu image once, but it's buried under twelve subsequent posts within a week. You can pin a story highlight, but the format is square-format vertical screens that are awful for reading prose. You can put it in a Notes app screenshot in a post, but it's an accessibility wreck.

Every prospective guest who needs this information opens Google. If you don't have a website, they find someone else's representation of your restaurant — and that representation is usually wrong, outdated, or stripped of context.

4. Build an email list (and a real customer database)

Instagram followers are not your customers. They're Instagram's customers. Meta can throttle reach (and has), shadow-ban accounts (and has), or change the algorithm so your posts reach 4% of followers instead of 30% (Facebook page reach is now in single digits).

An email list — built from booking confirmations, from a newsletter signup on the website, from a post-stay email asking for feedback — is yours. You can email it. You can segment it. You can re-engage lapsed guests. You own the customer relationship in a way you never will on Instagram.

A restaurant doing 14,000 covers a year should have a 10,000-name email list inside three years. Without a website, you have zero.

5. Establish authority for press, PR, and partners

When a Good Food Guide reviewer is preparing to review your restaurant, they read your website. When a wine importer is deciding whether to pitch you a new producer, they look at your wine list page. When a private dining client is shortlisting venues, they want a downloadable PDF and a price guide they can share with the CFO.

Instagram does none of this. A real website does it as a foundational layer. The press kit page. The wine list. The chef's CV. The kitchen's accolades. The private dining inquiry form with a structured intake. The press contact email that goes to a separate inbox so it isn't lost in the reservations queue.

For a destination-tier restaurant, the website is your PR infrastructure. Cutting corners on it means cutting corners on credibility with the people whose opinions matter most.

What "good enough" looks like

I want to be realistic. A destination restaurant doesn't need a $50,000 bespoke website. The chef doesn't have time to fight a CMS. The kitchen is the priority, not the digital strategy.

Here's what a minimum-viable serious website looks like:

A homepage that says what you are

Three lines of positioning above the fold. One photo of a current dish. One CTA: "Reserve a table." A second CTA: "View the current menu." That's it.

A menu page (in HTML, not PDF)

Each course in proper headings with descriptions. The pairing option. The dietary note. The deposit policy. Updated when the menu changes.

A reservations page with the actual booking widget embedded

Not a phone number alone. Not an "email us" form. A real widget from Now Book It, SevenRooms, Tock, or OpenTable — embedded on the page, not bolted in via a popup.

For Australian fine-dining restaurants, Now Book It is increasingly the default — it's built for the AU/NZ market, owns its own consumer-facing directory, and doesn't charge per-cover network fees the way OpenTable does. Tock works well for ticketed degustations and is preferred by restaurants that take prepaid bookings (it was originally built by Grant Achatz at Alinea for that exact pattern). SevenRooms is the right choice if you need real guest CRM and loyalty workflow.

A short "about" or "story" page

The chef's background. The kitchen's philosophy. The provenance of ingredients. 300–500 words. One or two portrait photos. This page does SEO, it does PR credibility, and it does the emotional work of differentiating you from "another tasting menu in Sydney."

A press / private dining page

Email contact for media. Phone for press enquiries. Downloadable press kit. Private dining capacity and pricing. This is small but it makes the restaurant legible to people who need to make decisions about it from outside.

A blog or "journal" — optional but high-leverage

If the chef writes — even occasionally — a journal of supplier visits, seasonal menu thinking, technique posts — that's organic SEO gold and reputation infrastructure. Brae's journal is a great example: not frequent, but substantial. It positions Dan Hunter as a thinker, not just a chef.

For a place where the chef's voice is part of the product, a journal is more valuable than another Instagram post.

The investment vs the return

A serious destination-restaurant website with the architecture above runs $12,000–$25,000 AUD if built properly and once. Lower if compromises are made. Higher if the design is exhaustive.

The first-year return for a restaurant doing $5m in covers:

Capture the Google clicks currently going to Broadsheet / AGFG / aggregators: 8–15% more website visits, of which maybe 25% book directly. That's 200–500 additional covers/year at, say, $180 average → $45,000–$90,000 in incremental revenue.
Convert 50% of "find me on the link in bio" Instagram clicks instead of 25%: 100–300 additional bookings → $18,000–$54,000.
Email list of 3,000 names re-engaged twice a year at a 3% booking rate per send: 180 additional covers → $32,000.

Year-one net: $95,000–$176,000 in incremental revenue. Year-one cost: $12,000–$25,000. The website pays for itself before service number twenty.

The bottom line

Instagram is essential. Instagram alone is a strategic mistake. The work isn't replacing the feed — it's adding the conversion infrastructure that the feed can't be.

If you're running a destination restaurant on Instagram with a Squarespace landing page or a Linktree as your "website," it's time to upgrade. The food deserves the architecture.

The objection: "we don't have time to maintain it"

This is the most common pushback I hear from chefs and restaurant owners. The kitchen is the priority. The day already has too many hours of admin. A website becomes another thing to update, another thing to break, another thing to ignore.

The honest answer: a properly-built restaurant website needs about 90 minutes a month to maintain. Update the seasonal menu (30 min). Refresh the homepage image to reflect a current dish (15 min). Approve any new press citations on the press page (10 min). Reply to one or two private dining enquiries that come in through the form (varies, but the volume is low). That's it.

If the maintenance feels like more, the website was built wrong. A CMS like Sanity or Payload gives a non-technical user a clean editor for the menu and the journal. The chef or maître d' can update content from their phone during a quiet moment. This is a different experience to fighting a WordPress dashboard with a page builder.

The decision isn't whether to give the website 90 minutes a month. It's whether to give the current fragmented Instagram-plus-Linktree setup the equivalent time (probably more, when you count the time spent answering DMs about menu questions that the website should have answered). For most restaurants, a real website is less total time once it's running, because the website does the answering and the social media goes back to being marketing instead of customer service.

If you've got a website that's mostly a placeholder while Instagram does the heavy lifting, run our free audit on it. You'll see what it's actually doing on mobile — load times, SEO surface, the bits that are silently broken — which is usually enough to decide whether it can be fixed in a weekend or whether the right move is a proper rebuild around a 90-minute-a-month CMS.

Why Instagram Alone Kills Restaurant Bookings (2026)