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.
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 some placements constrain the number of links 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 a potentially simple owned-domain landing page, with hosting/domain/analytics costs to confirm, because the click
lands on its own domain rather than a third party's.
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.
Follow these local instructions; the shared execution runtime is not bundled. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.
Read the request and pick the intent before asking anything.
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?
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.
the menu, order on WhatsApp? / Is there a second and third priority behind it?
social profiles, document, review page? / Which are essential on day one and which can
wait?
leaflet, business card, vehicle, QR code? / Is a custom subdomain needed?
analytics tool already, or would this be the first? / Any consent or privacy constraint?
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.
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: []
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
source so the channel is visible in analytics, each link has an owner and a review date,
and any seasonal link gets a start and end date so the owner can remove it under a confirmed scheduling process. Print gets a
QR code to the same URL, not a different one.
Why this one: Six links is a starting design hypothesis, not a proven ceiling; prioritize the actual user tasks and test the result. Owning the domain means the domain affords more control, but hosting, DNS, renewals and redirects can still fail, and the clicks land somewhere the
business controls.
Workflow: Primary action chosen → Destination list agreed → Hosted on own domain with a
short URL → Links ordered, primary first → UTM source set per channel → QR code generated for
print → Analytics and consent checked → Page published → Clicks reviewed and links reordered
Once the user asks for it, derive the fields from the confirmed context and emit the
requested artifacts. For machine-readable text, keep prose outside the data; for files,
provide a usable link. Report material validation failures or limitations separately.
**A selected Notion output is rendered by notion-manual-import, so route the
Notion step there.** When the user selects Notion, hand that step to
@notion-manual-import: it holds the CSV, the property
mapping, the import steps and the verification checklist, and it renders the Field
Reference below instead of defining a table of its own. Do not restate the mapping
here and do not improvise the import steps. Manual CSV and mapping outputs need no
connection. For requested workspace changes, follow the shared contract: verify actual
tool access and the target before writing. A user saying "connected" is not tool evidence.
Never ask for a Notion password or token.
Link ID,Link Label,Destination URL,Link Type,Priority Order,Audience,Track Clicks,UTM Source,Enabled On,Thumbnail,Opens In,Schedule,Review Date,Click Count,Status,Notes
,Book a free 15-minute call,https://example.com/book,Conversion action,1,Prospective customer,true,social-bio,"LinkedIn bio, Facebook bio, WhatsApp status, print QR",None,Same tab,Always on,2026-10-27,0,Draft,Example row - replace every value before use.
-- Engine assumption: PostgreSQL. For another engine use the engine's auto-increment
-- equivalent and keep the rest portable.
CREATE TABLE link_hub_link (
link_id BIGINT PRIMARY KEY,
link_label VARCHAR(255) NOT NULL,
destination_url TEXT NOT NULL,
link_type VARCHAR(100) NOT NULL,
priority_order INTEGER NOT NULL,
audience VARCHAR(100) NOT NULL,
track_clicks BOOLEAN NOT NULL,
utm_source VARCHAR(255),
enabled_on TEXT NOT NULL,
thumbnail VARCHAR(255),
opens_in VARCHAR(20) NOT NULL,
schedule VARCHAR(50) NOT NULL,
review_date DATE,
click_count INTEGER,
status VARCHAR(50) NOT NULL,
notes TEXT,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP DEFAULT NOW(),
CONSTRAINT link_hub_priority_positive CHECK (priority_order > 0),
CONSTRAINT link_hub_clicks_non_negative CHECK (click_count IS NULL OR click_count >= 0),
CONSTRAINT link_hub_opens_in CHECK (opens_in IN ('Same tab','New tab','App','Direct action'))
);
CREATE INDEX idx_link_hub_status ON link_hub_link (status);
CREATE INDEX idx_link_hub_priority ON link_hub_link (priority_order);
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Link-in-Bio Hub",
"type": "object",
"additionalProperties": false,
"properties": {
"Link ID": { "type": "integer" },
"Link Label": { "type": "string" },
"Destination URL": { "type": "string", "format": "uri" },
"Link Type": { "type": "string" },
"Priority Order": { "type": "integer", "minimum": 1 },
"Audience": { "type": "string" },
"Track Clicks": { "type": "boolean" },
"UTM Source": { "type": "string" },
"Enabled On": { "type": "string" },
"Thumbnail": { "type": "string" },
"Opens In": { "type": "string", "enum": ["Same tab", "New tab", "App", "Direct action"] },
"Schedule": { "type": "string" },
"Review Date": { "type": "string", "format": "date" },
"Click Count": { "type": "integer", "minimum": 0 },
"Status": { "type": "string" },
"Notes": { "type": "string" }
},
"required": [
"Link Label",
"Destination URL",
"Link Type",
"Priority Order",
"Audience",
"Track Clicks",
"Enabled On",
"Opens In",
"Schedule",
"Status"
]
}
| CSV column | Notion property | Set after import |
|---|---|---|
| Link ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Link Label | Title | Use as the database title; the visible link label |
| Destination URL | URL | Convert to URL. No tracking parameters - they live in the UTM columns |
| Link Type | Select (add options after import) | Convert to Select, add options: "Conversion action", "Contact", "WhatsApp", "Phone", "Menu or price list", "Document", "Social profile", "Review request", "Booking", "Map", "Newsletter signup", "Seasonal offer" |
| Priority Order | Number | Convert to Number, digits only. 1 is the top link and must be the primary action |
| Audience | Select (add options after import) | Convert to Select, add options: "Prospective customer", "Existing customer", "Partner", "Job candidate", "Press", "Public" |
| Track Clicks | Checkbox | Convert to Checkbox. Enable only when needed and legally approved; UTM support does not require tracking |
| UTM Source | Text | Leave as Text. The channel name, not the whole URL |
| Enabled On | Text | Leave as Text. Which bios, cards and leaflets carry this link |
| Thumbnail | Text | Leave as Text. Filename or asset reference, not a pasted image |
| Opens In | Select (add options after import) | Convert to Select, add options: "Same tab", "New tab", "App", "Direct action" |
| Schedule | Select (add options after import) | Convert to Select, add options: "Always on", "Start and end date", "Manual toggle" |
| Review Date | Date | Convert to Date. The next date this link is checked |
| Click Count | Number | Convert to Number, digits only. Leave blank until measured - never seed it with a guess |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "Live", "Paused", "Retired" |
| Notes | Text | Leave as optional Text |
The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Click Count is 0 in the example and blank in
the field reference - a click count is a measurement, never an estimate.
| # | Field | Type | SQL | JSON Schema | Notion | CSV example |
|---|---|---|---|---|---|---|
| 1 | Link ID | id | BIGINT PRIMARY KEY | integer | Text or Notion auto-ID | (blank) |
| 2 | Link Label | text | VARCHAR(255) | string | Text | (blank) |
| 3 | Destination URL | url | TEXT | string, format: uri | URL | (blank) |
| 4 | Link Type | select | VARCHAR(100) | string | Select | Conversion action |
| 5 | Priority Order | number | INTEGER | integer | Number | 1 |
| 6 | Audience | select | VARCHAR(100) | string | Select | Prospective customer |
| 7 | Track Clicks | boolean | BOOLEAN | boolean | Checkbox | true |
| 8 | UTM Source | text | VARCHAR(255) | string | Text | (blank) |
| 9 | Enabled On | long_text | TEXT | string | Text | (blank) |
| 10 | Thumbnail | text | VARCHAR(255) | string | Text | (blank) |
| 11 | Opens In | select | VARCHAR(20) | string | Select | Same tab |
| 12 | Schedule | select | VARCHAR(50) | string | Select | Always on |
| 13 | Review Date | date | DATE | string, format: date | Date | (blank) |
| 14 | Click Count | number | INTEGER | integer | Number | 0 |
| 15 | Status | select | VARCHAR(50) | string | Select | Draft |
| 16 | Notes | long_text | TEXT | string | Text | (blank) |
Link Type - a starting set. Conversion action is the one that must be Priority Order
Conversion action | Contact | WhatsApp | Phone | Menu or price list | Document | Social profile | Review request | Booking | Map | Newsletter signup | Seasonal offer
Audience - a starting set. A link that serves two audiences should be two links.
Prospective customer | Existing customer | Partner | Job candidate | Press | Public
Opens In - Direct action means the link fires an app or a dialler rather than
navigating, and it behaves differently on every platform. Test it.
Same tab | New tab | App | Direct action
Schedule - three values, because a seasonal link with no end date stays up forever.
Always on | Start and end date | Manual toggle
Status
Draft | Live | Paused | Retired
None. This table is standalone. Where the destination is a page on the business website,Destination URL holds the path and the join to the page map in business-website-setup
is on that path text, not a database relation across packs.
Prompt
We have a Linktree with eleven links on it and nobody clicks any of them. Our Instagram
bio points to it and our visiting cards point to the website homepage.
Context first - one question per message, nothing already answered:
Q: What is the business called, and what is the one thing someone should do after
they land on the page?
A: Example Retail. Book a table, or order on WhatsApp.
Q: Which platforms does the page have to serve?
A: Instagram, WhatsApp status, and the visiting cards.
Q: Do you want to know which channel a click came from?
A: That would be useful, yes.
Q: Is there a seasonal link - a festival offer, a hiring push - that needs to go up
and come down?
A: A Diwali offer in October.
Q: Who can add or remove a link?
A: The founder.
Recommended next step - offered, not built:
One page on your own domain with six links, not eleven. Book a table at the top, WhatsApp
second, then the menu, the location, and two social profiles. The October offer gets a
start and end date so it can be removed by an implemented scheduler or the owner. Each link carries a UTM source so the cards
and the Instagram bio are visible separately in analytics, and the same URL goes on the
cards as a QR code.
Workflow: Primary action chosen → Destination list agreed → Hosted on own domain →
Links ordered, primary first → UTM source set per channel → QR code generated for print →
Page published → Clicks reviewed and links reordered
Want the CSV, SQL DDL, JSON Schema and Notion mapping for this?
important, so nothing is.
should not have to choose between three equal buttons.
de-indexed, or start charging, and the QR code on 500 printed cards then points at
nothing.
add up instead of fragmenting across four destinations.
UTM columns, not baked into Destination URL.
still live in December.
tel:, WhatsApp, maps - on a real phone, not in abrowser preview. A QR code that does not scan from a leaflet is worse than no QR code.
on a phone held at an angle.
hub should be a fast page on the same domain, not a script from a platform.
was assumed.
confirmed across print.
fetch them and must never estimate them.
tracking plan needs checking per channel, not once.
a newsletter signup or analytics that sets cookies changes that answer. Confirm with the
business.
consent before non-essential storage.
Unknown and blank are correct.
link sends customers somewhere else for years; check the destination before printing.
forwards to a parameter-controlled destination.
and it will be crawled.
rule apply. Flag it; refer it to data-privacy-controls.
External writes, messages, provisioning, and publication require authorization for that
action and target; existing explicit authorization does not need to be repeated.
Solution: deliver manual mappings without a connection; claim a live change only
after the authorized tool operation succeeds.
Solution: ask one, wait, and drop any the first answer already covered.
Solution: that is the ceiling, not the content. Cut to six, order them, and make one
of them obviously primary.
Solution: size, contrast and quiet zone. Below about 2cm on a card it will not
reliably scan.
Solution: Schedule = Start and end date, with the date in the row, not in
someone's head.
on the card, one in the email signature, one in the leaflet.
Solution: one stable hub path with distinct authorized channel parameters or redirects when source attribution is needed.
Solution: a script-heavy hub page costs more in lost clicks than the tracking is
worth. Keep it a fast page on the same domain.
Solution: derive all four from the field list in this file, never by hand.
Solution: that is expected. Apply the property mapping table once, after import.
they must match.
names them.
data-privacy-controls (operational pack) - lawful basis if the hub ever collects data.I want one link-in-bio page that every social bio, card, QR code and email signature
points to, with the links tracked and a seasonal link that comes down on its own date.
Ask me one short question at a time, and only about what I have not already told you.
Never invent a URL, a phone number or a click count. Then recommend the smallest link
set that fits on our own domain, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema and a Notion property mapping. Data only.
This is a manually validated register, not a page builder, analytics collector or scheduler. Schedule is only a label: the illustrated schema lacks start/end timestamps, timezone and execution status. Use Manual toggle until an explicit scheduling schema/runtime is implemented consistently in every format; do not claim automatic expiry. Identical untagged inbound URLs/QR codes cannot identify whether a visit came from print or a specific bio. Use one stable hub path with source-specific inbound parameters/redirects, and distinguish incoming attribution from outgoing destination UTMs; do not expose personal data in query strings. UTM parameters alone do not count clicks. Define event, date window, bot filtering and duplicate handling before comparing counts, and keep unknown counts blank rather than zero. Validate URL scheme/host and redirect chains against approved destinations; JSON URI format alone permits unsafe schemes and needs validator support. SQL IDs are supplied explicitly here (no automatic identity), timestamp defaults do not update automatically, and status/date/priority uniqueness need confirmed enforcement. QR scanning depends on data density, printing, quiet zone, contrast and device distance, not a universal 2cm cutoff. Own-domain hosting does not remove privacy/consent obligations or availability risk; assess actual data processing rather than assuming the absence of a banner is sufficient.