Link in Bio Page: 5 Reasons to Self-Host It

A link in bio page starts as a convenience and turns into a dependency. You sign up, fill in five links, and eighteen months later the page carries your traffic, your brand, and a subscription you cannot cancel without losing the history.

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

Hosting it yourself is not nostalgia for the static web. On a single PHP file the page loads faster than the service version, the metadata is yours, and the cost stops being monthly.

1. The page is part of your site, not a detour

A hosted page lives on someone else’s domain. Every visitor who clicks a link leaves your brand for three seconds, sees a logo that is not yours, and comes back through a redirect.

A self-hosted link in bio page sits on your domain. The analytics are the same analytics as the rest of the site, the cookie banner is the one you already wrote, and the fonts match the homepage because they are the same files.

2. You control the metadata

This is the part most people discover late. The hosted service decides which Open Graph image appears when someone shares the page, and which title a search engine indexes. Those decisions are fine until your brand changes and the preview card still shows the old one.

With the page generated by your own code, the canonical URL, the hreflang pairs, the JSON-LD profile block and the sitemap all come from the same source as the visible content. One edit updates all of them.

3. No framework is a feature

The version we run is plain PHP 8.1 and up, with one JSON file as the content store and no Composer packages at runtime. There is no build step, so a change deploys as a file copy. There is no framework upgrade path, so there is nothing to migrate every spring.

That matters when the page is one of twenty things you maintain. A dependency-free page still works after a server migration that breaks three plugins elsewhere.

4. Editing does not require a browser session

The page exposes an MCP server with twelve tools, so an AI client can add a link, reorder a section, hide an entry or rewrite a description. Every write validates the whole content tree, copies a backup, writes atomically under a lock, and appends to an audit log.

The concurrency model is a revision number. Two agents editing at once produce one clear rejection instead of one silent overwrite. For anyone who has lost a paragraph to a last-write-wins editor, that is the feature.

5. You can move it

The content is a JSON file. If the design stops working, you take the file and render it somewhere else. No export flow, no “your plan does not include data portability”.

What a self-hosted link in bio page changes in practice

It adds one job: patching PHP and renewing a certificate. That is the honest trade against a monthly fee and a service that can change its pricing.

On a small server the runtime cost is negligible. The page renders once and caches the HTML with a key built from the content revision, the template and the source files, so an edit or a deploy invalidates itself. Static-speed responses from a dynamic page.

Accessibility is the part that usually gets skipped in this category. The page targets WCAG 2.0 to 2.2 AA, keeps keyboard shortcuts from hijacking the input, respects reduced motion, and passes axe-core with no violations. A hosted template rarely gives you that control, and a bio page is exactly the kind of thing an accessibility audit checks.

When the hosted service is the better call

If you need the page this afternoon and have no server, a subscription is cheaper than a project. If you have no one to patch a PHP install, the same applies.

Self-hosting makes sense when the page carries brand traffic, when the same server already runs your site, and when you want the metadata to stop changing without notice.

If the page also needs to be indexed properly, the work overlaps with SEO. And if the links point to a store, the order of operations matters, which is covered in web development. The copy on the page deserves the same check as any other: content readability measures it before a translator or a rewrite touches the text.

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