Link list

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Public and deliberately small, because a list of twenty links gets none of them clicked.

Ordered by clicks, so the list arranges itself around what people want.

One shareable address that points at everything else.

How it works

1
A handful of links are published in one place, deliberately few.
2
Click counts accumulate and inform the order, so the list arranges itself around what people want.
3
Labels are phrased as actions rather than destinations.
4
One shareable address that points at everything else.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Labelrequired	text	What the link says, phrased as the action somebody wants to take.
Goes torequired	text	Where it points, internal or external.
Clicks	number	How often it is used, which is what decides the order.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Deliberately small. Twenty links gets none of them clicked, and nothing stops you adding twenty.
No scheduling — a seasonal link has to be removed by hand.
Click counts are total rather than per period, so a spike is invisible.
No custom styling per link.

Before it works

What you have to provide, if anything.

Nothing.
Reorder by clicks after a fortnight. The order you guessed is usually wrong.

In practice

A restaurant with a booking system, a menu and a shop, all on different domains.

“One link for the Instagram bio that covers everything.”

What was said to the agent

What the agent built

Four labelled links in one place, ordered by use.

What changed

Book a table took 1,840 clicks against Instagram 288. The order was changed to match, and bookings rose again.

Better with

These do a different job on the same data. An agent can have all of them.

Bookmarks / URLsLive

References accumulate from across the web and finding one again is currently a matter of luck.

BookingsLive

Customers reserve time, capacity is finite, and double-booking would be a real problem.

MenuLive

Food or drink is served, and questions about what is in it need answering accurately every time.

Questions

What data does the Link list page use?

It reads url records the agent has collected. Curated resource list. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.