Skip to content
← SignalSpring 2026 No. 16
Positioning3 min

Why Linktree Is the Wrong Answer to the Right Question

The brief

Linktree solved a real problem. The problem just wasn't the one we now need to solve. Why the aggregator era is closing.

The link-in-bio aggregator is what you build when you've correctly identified the problem and incorrectly identified the solution.

The problem is real. Every social platform gives you one external link, and you have more than one place worth pointing the link to. Your podcast. Your newsletter. Your shop. The article that just came out. The thing you'd want them to follow if they had to follow only one. Linktree solved that problem the most direct way anyone could solve it: a list, with a click count, served on a flat page.

For a decade, that was the answer. The answer worked because the question was small.

The question has gotten larger.


The problem with the link-in-bio aggregator is that it makes the link inventory bigger but doesn't make the routing better. A visitor lands on your Linktree and sees seven links. They have one specific reason for clicking. None of the seven labels matches their reason. They scroll. They guess. They click the wrong one. They leave.

Multiplied across the hundreds of millions of profiles using a link-in-bio aggregator today, the failure mode is the same one that's plagued every flat directory since the Yellow Pages: the visitor brought intent, the directory ignored it.

A list of links is not routing. It's a longer menu. It still asks the visitor to do the work the menu was supposed to do for them.


Consider the writer who drops her Linktree in her Substack author bio. A reader finishes a 3,000-word essay and clicks through. The reader has spent more time with her than most acquaintances will. The reader is in a specific state — they want to read more like the essay, or they want to subscribe to the newsletter, or they want to hire the writer for a piece, or they want to know what podcasts she's on.

Each of those is a different click, and the Linktree shows the reader all of them. The reader scans the list. Three of the seven links are stale. Two go to the same place under different labels. One is a podcast appearance from 2023. The reader clicks the newsletter — or doesn't, and tabs out.

The writer didn't fail. The writer's link inventory was correct. The aggregator failed.


The steel-man is real and worth saying. Linktree solved the right-now problem at a moment when nothing else did. Beacons, Bento, Magic, Stan — every aggregator that came after is a refinement of the same template, and each of them ships, and each of them has paying customers, because the underlying need is genuine. Most people who use a link-in-bio aggregator are happier with it than without it. The category exists because the problem existed.

What the category got wrong is the level of the problem. The problem isn't I have multiple things to link to. The problem is visitors arrive with different reasons and the link doesn't know. Solving the first means showing more links. Solving the second means asking, gently, what brought the visitor here, and routing the response.

Those are different problems with different solutions. The aggregator solved the wrong one with conviction.


The shift from list to host is the same shift that's already happened in every other piece of recognition infrastructure in our lives. A restaurant doesn't show every guest the entire wine list before deciding who they're seating. A hotel doesn't ask returning customers to scan the list of rooms. A doorman doesn't recite the directory to everyone who walks past. Recognition routes; lists don't.

The link in your bio has the same job as the doorman's. Recognize the visitor at the threshold, route well, get out of the way. A list of links cannot do that. A host can.


The era of the aggregator is closing not because it failed, but because it solved a smaller problem than the one we're now ready to solve. The link in your bio in 2026 has a different job than the link in your bio in 2018. Linktree was the right answer to the right question of its decade. The question changed.

You don't need more links. You need one that knows what the visitor came for.

Continue reading