Visibility engine
The URLs a crawler can walk from your bio
A follow link is an edge: profile to Now, to a dated launch story, to llms.txt, listed in a sitemap. Here is the mesh LinkForge publishes, and the order that makes it true.
A crawler follows edges. A screenshot of buttons has no edges it can trust. LinkForge builds a small mesh of real URLs around your public bio and marks the internal ones so they can be walked: ordinary follow links, in HTML, listed where a sitemap can announce them.
You do not draw this graph by hand. You publish a profile that says something, you add a Now line when the week has a fact, you generate a launch story when you want a dated article, and you leave llms.txt public if you want that file fetched. The mesh is the consequence. It is useless on an empty profile, which is why the order below starts with sentences.
The nodes, and the job of each one
/u/you — the profile. Title, bio, and links as HTML. This is the URL in every Website field. If this page is thin, every other node is advertising a thin page.
/u/you/now — one live line, rendered in your theme. It exists so you can change “what’s true this week” without minting a new bio link. A crawler that revisits can see a newer sentence on a stable path.
A dated launch story — an article URL associated with the profile (the public pattern is /en/launch/you). Search already understands articles. It does not have a special type for “five buttons in a webview.” The story should cite destinations you really linked, with real hrefs.
/u/you/llms.txt — markdown for anything that prefers a plain file. It restates the bio and the links. It is not a secret API and not a ranking lever you pull. It is a polite duplicate. The product-wide file at /llms.txt describes LinkForge, not you.
The sitemap. Published bios and launch URLs are listed so you are not asking a crawler to guess. Being listed is not the same as being ranked for a competitive query. It is the minimum courtesy of a site that wants to be found.
Internal links between these surfaces stay rel="follow" (or simply omit nofollow, which means follow). A bio product that nofollows its own Now page and its own launch story is hiding the graph. The point of the page is to be found and then to send a person onward to a booking or a shop you chose — those outbound links are yours, and you should only point them at places you trust.
What the structured data is doing in the same mesh
JSON-LD on the profile names the entity: Person, Organization, or LocalBusiness, plus FAQ only from real link titles. That is a description, not a widget skin. A plumber is not a “link list.” The type decision is entity pages, launch editorial, HTML. The markdown twin is llms.txt. If the JSON-LD name and the llms.txt name disagree, fix the profile. Do not maintain two biographies.
Build it in an order that does not create empty nodes
- Write the profile: name, sentence, links with specific anchors. Publish. Open the HTML logged out and confirm the sentence is in the source.
- Paste that exact profile URL into the Website fields you use. The mesh has a center. Social apps are how humans arrive; they are not nodes you control.
- Save a Now line that is true this week. Open
/u/you/nowand confirm the profile links to it and it links back in a way a person can use (a way back to the offers). - Generate a launch story only when you have something to say that the links support. Read it. If it cites a product you removed, do not leave it up as “content.” The cap is two a day so you cannot paper the sitemap with duplicates. The editorial reason for dates is launch story and Now.
- Open
llms.txtand the sitemap entry if you are checking your own work. You are looking for presence and accuracy, not for a score. - Attach a custom domain on Pro only after the mesh has content. Pro is 7€/month (domain, SSL, full SEO fields, AI insights, custom CSS, the generation tools). The free plan is the profile, five links, per-link analytics, and the public HTML. A domain on an empty mesh is a pretty hostname with nothing to walk.
Create the profile before you worry about whether a model will quote the leaf nodes.
What this is not
It is not a private web of purchased backlinks. It is not a promise that Google will treat a new profile as a newspaper. It is not a reason to generate a launch story every day to “keep the mesh fresh.” Freshness without a new fact is noise, and noise is how indexes learn to ignore a path.
Outbound links to shops, calendars, and maps are part of your usefulness. They are not the internal mesh. Do not nofollow them by habit if they are the point of the page; also do not point follow links at anything you would be ashamed to recommend. The mesh’s internal edges should stay obvious and few.
A monthly walk
Open the profile, Now, the newest launch story, and llms.txt in a private window. Click each internal link. Fix any that 404. Read the first sentence of each and ask whether a stranger could say what you do. If Now contradicts the profile (“closed” versus “book today”), fix the contradiction before you generate anything else. Crawlers will not resolve the argument for you. They may quote both.
Then look at the Website fields on your social accounts. If one of them still points at an old shortener, that account is sending humans around the mesh instead of into it. Bring it back to the profile URL.
Publish the center, link the dated pages you actually mean, leave the internal edges followable, and keep the words true. That is the whole mesh.
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.