Skip to content
Leonidov.DEV

Linktree Alternative: 5 Simple Reasons I Moved

Engineering
Linktree Alternative: 5 Simple Reasons I Moved

My link page had a handful of links and a monthly bill. I did not notice the bill until the service raised prices, and by then the page was the second result for my own name and the first thing a conference organiser clicked.

Code: Link-in-Bio-with-MCP-Server, MIT licensed.

Moving it to my own server took an evening. The result is bio.leonidov.dev, two pages in two languages, rendered by PHP from one JSON file, with an MCP endpoint so I can edit links from a chat window.

These are the five reasons the trade was worth it, and the parts that are worse than the service I left.

1. The page loads from the same server as everything else

The site answers in roughly fifty milliseconds from the server that already hosts my other projects. There is no third-party script in the critical path, no font fetched from a CDN I do not control, and no redirect between the click and the page.

Small numbers, but the crawl budget of a link page lives or dies on how fast a stranger can read it on mobile data.

2. My metadata stopped changing without me

This was the actual reason. The hosted page decided the title and the preview image, and twice in a year a redesign changed how my page looked in a search result. I found out from a screenshot someone sent.

Now the canonical URL, the hreflang pair, the Open Graph block and the JSON-LD profile all read from the same JSON tree as the visible content. Rename a role once and the structured data follows.

3. Editing is a tool call, not a dashboard

A link hub is edited in bursts: nothing for a month, then four links after a conference. A dashboard means logging into an admin, finding the right screen, and fighting a drag handle.

The page exposes twelve MCP tools and I call one of them from the agent I already have open. A create, a move, a visibility toggle. Every write validates the tree, copies a backup, writes atomically and logs what changed.

The concurrency detail matters more than it sounds. Each write carries a revision number, so an edit from my phone and an edit from the laptop produce a rejection instead of a lost link.

4. What a linktree alternative has to do better

Cheap is not enough. The hosted product wins on three things: zero maintenance, a template that looks fine on any phone, and a sharing flow a non-technical person can finish in five minutes.

A self-hosted page has to match at least the first two and add something. Here the additions are the metadata control, the JSON-LD that a hosted profile page rarely exposes, and the fact that the whole page is a file I can read in a diff.

5. Two languages with no plugin

The page carries English and Russian from one content tree, with hreflang and canonical URLs generated per language. There is no translation plugin, no duplicated template, and no file to keep in sync by hand.

Ukrainian is not there yet, which is a real gap for a page aimed at people in Ukraine. The reason is honest: I would rather ship two versions that are correct than three where one is machine-translated.

What is worse than the service

Maintenance is mine. A PHP update, a certificate renewal, a server that has to stay up. If it breaks at the wrong moment, the page is down until I look at it.

The design is also mine to keep current, and a hosted template gets redesigned for free by someone else’s team.

For anyone without a server and without the habit of patching one, the subscription is the better answer, and I would say that to a client. Ownership pays when you already run the box.

The build details, including the twelve tools and the cache key that invalidates on deploy, are in an MCP server in PHP. If the page is the first step of a bigger site, the order of work is in developer roadmap.

Background: WCAG 2.2 quick reference and the Model Context Protocol.