# Your link hub

> The page at the top of your address — one screen holding every way a guest can reach you, and the click counts that tell you which ones they use.

_Canonical: https://seatsat.com/help/your-link-hub_

---

Your link hub is the page a guest lands on when they type your address with nothing after it. It is the one link worth putting in an Instagram bio: reserve, menu, directions, phone, WhatsApp, all on one screen, and it tells you afterwards which of them anyone pressed.

## Destinations

The hub is a stack of destinations you turn on, order and label. The built-in set covers the things a guest actually wants: **Reserve a table**, **View menu**, **WhatsApp**, **Tap to call**, **Find us**, **Order / delivery**, **Events**. Below them sit your own **custom links**.

Only one of each built-in type is allowed — the editor will tell you _"Only one destination of each type is allowed (except custom)"_ — because two "View menu" buttons is a worse page, not a fuller one.

A destination that can't work yet says so on its own row rather than shipping broken: **Needs address**, **Needs menu**, **Needs number**, **Needs phone**, **Needs link**, **Needs a published event**. That badge is a to-do list, and it's the fastest way to find why your hub looks thin.

> Some destinations are wired to your settings rather than typed here. **Find us** builds its link from your venue address — _"This destination's link is managed automatically"_ — so if it reads **Needs address**, the fix is in Settings, not on this page. One address, one source of truth, no second copy to go stale.

## Reserve is pinned, and can still be switched off

**Reserve a table** sits at the top marked **PRIMARY · LOCKED**. It cannot be removed and nothing can be moved above it — we are a booking product, and a hub that buried the booking link would be working against you.

It _can_ be hidden, and the distinction matters because the editor treats the two differently. Hide it and you get a plain warning:

> The Reserve link is hidden — guests can't book a table from your hub. Show it again unless you take reservations another way.

That is a nudge, not a block: publishing still works. Which is correct — a venue that takes bookings only by phone has a real reason to hide it. Just make sure the reason is yours and not a mis-click.

## Custom links have a ceiling

You can add your own — a supper club, a gift voucher, a press piece. There's a cap, and reaching it reads plainly: _"3 of 3 custom links used — remove one to add another."_

A limit on this page is a feature. The value of a link hub is that a guest's eye finds the right button in one second; the failure mode is a page of fourteen links where nothing stands out.

## Identity

The masthead is three fields, all optional and all worth filling.

> **One-liner**: Cucina di stagione · Milano · 28 coperti

The placeholder is doing teaching work: what kind of food, where, how big. A stranger who reads that knows whether to press Reserve.

> **Established**: 1962
>
> _Year the restaurant opened. Rendered as \`Est. 1962\` on the public link-hub masthead when set._

## Live status

Two switches put current information on the page instead of a static list.

**Show 'open now'** reads your opening hours and renders _Open until 23:00_ or _Closed_, so a guest at 22:40 knows before they walk. It's configured in Settings — the hub only decides whether to display it.

**Show 'next available'** pulls the first free slot from your calendar. It is the strongest thing on the page for a guest deciding tonight, and it costs you nothing to keep true because it isn't typed.

## Editing, then publishing

Like the menu, the hub is a draft until you publish. A banner appears while you have unsaved work — _"You have unpublished draft changes"_ — with **Discard** and **Keep editing** beside it, and **Publish changes** commits the lot.

The one exception is the **Theme**, and it says so: _"Applies across all your public pages — booking, menu, link hub. Clicks save immediately."_ A theme click is live at once and lands on all three pages, not just this one.

## What the clicks tell you

Every destination shows a seven-day count on its row — `48 · 7d`.

This is the most useful number on the page and the easiest to skip past. It answers the question every venue guesses at: whether guests are reserving, reading the menu, or calling. A **Tap to call** count far above **Reserve** on a hub that has both is telling you something concrete about your guests, and it's the kind of thing worth checking once a month rather than never.

## Languages, and who can edit

Fields with a translation control mark your own copy as **Editing the primary copy**, and an empty translation falls back to it rather than rendering blank.

Finally: **owners and admins can edit**, members read. Same posture as the menu, same reason — this is your shopfront.
