Back to the journal

Visibility

Google and answer engines do not click your widget. They read the HTML at /u/slug

In 2026 a link page only exists for search if the HTTP response is already a document: title, canonical, anchors, schema. Here is what LinkForge actually sends.

November 5, 20268 minLinkForge Editorial

When someone searches your name in 2026, two machines can answer before a person does. Google, which stores documents. And an answer engine — ChatGPT, Claude, Gemini, Perplexity — which does not “visit” your page the way a reader does. It requests the URL, reads what the server returned, and quotes a sentence if it finds one. A widget painted in the browser after several round trips is not a document. It is an application. The two are not ranked the same way, and they are not quoted the same way.

LinkForge publishes a page at https://linkforge.me/u/{slug}. The response already carries the title, the description, the canonical URL, the index permission, a JSON-LD block, and the text of the page: the name, the bio, the links as real anchors. The interactive layer hydrates for a person with a browser. The document left with the first response. That is the whole difference with the category of JavaScript link-in-bio widgets, where the button list exists only after the script runs.

Two objects people have mixed up for a decade

A first-generation link-in-bio is a widget. The URL often belongs to the tool. The body is an application: the buttons live in JavaScript state, sometimes after a call that fetches the list. Turn the script off and a shell remains — a logo, a spinner, an empty region. Google can run JavaScript. It does so in a queue, with a render budget, and it is more willing to spend that budget on a page it already has a reason to keep. Many agents that answer questions in 2026 render nothing. They read the HTML. If there is no sentence, they do not invent yours. They quote someone else, or they stay quiet.

A presence page is the other object. The human use is the same: a place to land from Instagram, a QR code on a card, a line in an email signature. The contract with machines is different. The page is the document. The title says who you are. The bio is a paragraph, not a picture of typography. Every link has an href and a readable label. None of that waits for a visitor’s click before it exists in the source.

Taste is not the distinction. One of these is a program. The other is a page. A program can look sharp on a phone and be unreadable to a robot that never starts it.

What the HTTP response actually contains

Open your public URL and look at the source, not at the tab after it has been painted. Four things should be there without you having to imagine the application loading.

The canonical points at https://linkforge.me/u/{slug}. That is the address the page declares as its own. A social preview, a shortener, a domain that leads here should not become a second page in the engine’s eyes. One address, one document. If you later add a domain in your own name, the page still emits this canonical on linkforge.me. The domain is a door. The document stays this one. Inspect this URL, not a screenshot of the profile.

Indexing is open on a published page: index and follow. A handful of reserved slugs stay noindex. Yours, once published, is not hidden by a tool-wide noindex. Many widgets are, because their publisher does not want a directory of thin pages competing on its domain.

The JSON-LD is in the response, as application/ld+json, not injected when a component mounts in the browser. For a person, the page type is a ProfilePage: the name, the description, the image, and sameAs — the profiles you actually linked. A local business does not have to describe itself as a person. The type follows what you declared. The block does not create a knowledge panel. It stops the engine from guessing who is tied to what. You change it by editing the profile, not by pasting a script by hand.

The text meant for an agent that does not run JavaScript is a semantic article in the document: a level-one heading, the bio, the Now line with a date if you wrote one, the link list as <a> tags, the profiles. When the Business plan assembles the vitrine, the modules — portfolio, services, testimonials, questions, contact — are HTML too: headings, paragraphs, quotations, a FAQ whose answer sits in the page rather than behind another request. How that assembly works is in from a bio link to a vitrine.

The useful test takes a minute. Disable JavaScript, reload /u/your-slug. If the name and the destinations are still there, you have a page. If only a frame remains, you had a widget.

Why 2026 is no longer only a Google problem

Google is still the patient reader. It can render a widget later, if the page deserves the budget. Answer engines extract. A citation needs a stable sentence at a stable URL. A button labelled “Shop” is not a sentence. A bio that says “ceramicist in Limoges, pieces to order, lead times posted for November” can be one, with the page address beside it.

LinkForge keeps two layers from contradicting each other. The HTML page is what a person and a robot can keep. The llms.txt file, on Pro, is the markdown of the same week: /u/{slug}/llms.txt, linked from the page when you leave it public. It is not a manifesto you paste into a form “for AIs”. It is a view of the profile. If the bio changes, the file changes. If it still describes the old practice, turn it off rather than let a false citation carry your name. Silence is cleaner than a lead time that no longer exists.

Schema and prose do not replace each other. A perfect ProfilePage on a page with no sentence will not get you quoted. Both come from the same profile fields. You do not keep a second site “for SEO” next to the page people see.

What Free already publishes, and what the plans add

The free plan publishes the page. Up to five links, three social profiles, click stats without a vanity counter, a standard theme, basic SEO, JSON-LD, a fast mobile page, a JSON export if you leave. The LinkForge badge stays. That is enough to exist as a document. It is not the tier for a domain in your name, for links without that cap, or for the text file meant for tools that quote.

Pro, at €7 a month, does not buy indexation. Indexation is a property of the published page. Pro takes the brakes off around it: links, pages and socials without the free cap, themes, CSS, a domain, the badge removed, Studio to publish to eight networks, and the visibility pack — a dated story, the Now line, llms.txt, a title and meta you can fill. The domain matters when the address has to sit on a card or in a signature. The canonical the page emits remains linkforge.me/u/{slug}. That is the URL to give Search Console. How the connection reads is described in Search Console and the public page.

Business, at €26 a month, adds the modules that lengthen the document — the vitrine — and the tools around it: lead capture, Search Console, conversions, a social inbox, calendar intelligence, an advanced copilot. It does not replace the page with another technology. It thickens it, on the same URL. The Agency offer is a notice of what comes later. It is not a plan you can subscribe to today.

Prices are on the pricing page. The page is filled from the dashboard.

What no tag can repair

An empty page with clean schema does not rank. The engine needs a reason: a name, a craft, a place if the place matters, an offer the text is willing to stand behind. Five buttons titled “Link 1”, “Link 2” are a thin document. Google can see that. So can an answer model. There is nothing to extract that is not already said better somewhere else.

Write the sentence you would accept quoted without your photo next to it. Put it in the bio, not only in a story that expires in a day. Match the spelling of the name on YouTube and Instagram, because sameAs links URLs, not nicknames that contradict each other. If you share a common name, the city and the craft in the text do more than a plugin. A ceramicist in Limoges whose stage name and legal name differ picks the one she wants quoted, and puts it in the title, the bio and the linked profiles. The script does not referee two identities.

The Now line needs the same care. If it says “books open” while you are full until March, quoting tools repeat a false fact with your name on it. Change the line when the fact changes, then reopen the URL. A story does not update the document. Only the profile does. You fill the fields. The page assembles them. Robots read the assembly.

FAQ

Is a LinkForge page indexable without Pro?

Yes. A page published on the free plan is already an HTML document, with a title, a canonical and JSON-LD. Pro at €7 a month adds the domain, links without the free cap, themes, llms.txt and the full SEO fields. It does not buy the right to be read.

Does Google run the JavaScript of link-in-bio widgets?

It can render them, in a queue, if the page deserves the budget. That is neither immediate nor guaranteed. Answer agents that quote a page in 2026 mostly read the HTML they received. A widget whose text exists only after execution leaves them a shell.

Where is the ProfilePage JSON-LD?

In the response from https://linkforge.me/u/{slug}, as application/ld+json. It repeats the name, the bio, the image and the linked profiles. You change it by editing the profile in the dashboard.

Does llms.txt replace the HTML page?

No. On Pro it sits beside the page at /u/{slug}/llms.txt, when you leave it public. It is the same profile in markdown. An empty page produces a file with nothing worth quoting.

Do I need a custom domain to have a canonical URL?

No. The canonical the page emits is https://linkforge.me/u/{slug}. The domain, included in Pro, is another door to the same page. Give Search Console the canonical URL.

Create my page — Pro is 7€/month (~$7)

Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.