Link-in-Bio Hub

What it is: the single page every social bio points to, with every destination the business wants a customer to reach, ordered, tracked and changeable without touching a profile bio.

Overview

Works out the smallest useful link hub for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a page. The link map - CSV, SQL DDL, JSON Schema, Notion mapping - is produced on request, from one field list so the four cannot drift apart.

Layer: Layer 3: Acquire. Fits: Starter stage. Table code: n/a.

The rule this table exists to enforce: a link hub exists because a social bio allows one link and a business needs six. That means the hub is the only page where the order and the destination are a business decision, which makes it the one place to be deliberate. It is also the cheapest tracked landing page the business will ever own, because the click lands on its own domain rather than a third party's.

When to Use This Skill

• linktree, link in bio, link hub, bio page
• "we only get one link in our Instagram bio"
• a QR code for a leaflet, a van, a reception desk, a conference stand
• one URL for WhatsApp, email signature, QR code and leaflet
• tracking which channel a click came from
• "our socials send people nowhere useful"

Do not use it for: the social account setup itself (social-media-setup), the website's page structure (business-website-setup), or a full campaign landing page with its own form and tracking - that is a website page.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" / "build" / "we need" -> artifacts wanted; go to Step 2.
• "we have one already" -> something exists; capture the current links, then Step 2.
• "which links should we even have" / "review" -> a decision question, not a build.
• "our clicks are not converting" / "fix" -> capture the numbers, then Step 2.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: What is the business called, and what is the one thing someone should do after they land on the page?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything already answered. Ask the rest one at a time, and stop as soon as the remaining answers would not change the link list.

• Action - What is the single most valuable thing - call, book, buy, book a demo, read the menu, order on WhatsApp? / Is there a second and third priority behind it?
• Destinations - Which destinations exist today - website, WhatsApp, phone, menu, form, social profiles, document, review page? / Which are essential on day one and which can wait?
• Channels - Which platforms will the hub serve? / Is the page also going on print - leaflet, business card, vehicle, QR code? / Is a custom subdomain needed?
• Tracking - Does the business want to know which channel sent the click? / Is there an analytics tool already, or would this be the first? / Any consent or privacy constraint?
• Ownership - Who can add or remove a link, and how quickly can they? / Is there a seasonal link - a festival offer, a hiring push - that needs to go up and come down?

Never invent an answer. Handles, URLs, phone numbers, offer names, dates and click counts the user has not supplied are Unknown.

Step 3 - Hold the internal context

module: linktree-link-hub
intent: null            # set up | fix | review | report | import
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Action": null
  "Destinations": null
  "Channels": null
  "Tracking": null
  "Ownership": null
requested_outputs: []
confirmed_facts: []
open_questions: []

Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: One page on the business's own domain, six links maximum, with one clear primary action at the top and every other link below it. Each link carries a UTM

…