Visibility engine
Entity pages: a person, a studio, or a shop with an address
Search can keep a document with a type. Pick Person, Organization, or LocalBusiness, publish dated editorial next to the bio, and stop expecting a widget screenshot to be quoted.
Most link-in-bio products ship a widget: buttons drawn by JavaScript, a title that belongs to the tool, and a crawler that sees a shell. LinkForge ships a page. The public profile is HTML with a title you edit, links in the document, and a type — Person, Organization, or LocalBusiness — so the page is not filed as “a list of links” with no subject.
That type is not an advanced trick. It is the thing the category forgot. A photographer is a person. A label with several artists is an organization. A plumber in Lyon with a street, a phone, and opening hours is a local business. Using the SaaS-shaped defaults for the plumber, or the shop-shaped defaults for the photographer, is how structured data and the visible page start to disagree.
Choose the type from the noun in your title
Write the title first. The type should match the noun.
Person. The title is your name plus the work: “Mina Cole — editor and newsletter, Glasgow.” JSON-LD and the on-page heading use that name. Your clients can be companies; the entity is still you if the page is your professional home. SameAs-style links (social profiles, a publisher page) belong here when they are actually you.
Organization. The title is the studio, the band, the product, the collective. Do not stuff the founder’s biography into the organization name field. The founder can have a Person page later if both need to be found. One page that says it is both, with two addresses, helps nobody.
LocalBusiness. The title includes the trade and the place: “Atelier Nord — bike repair, Lille.” Fill name, address, and phone only with facts you will put on the door. Hours belong in visible text as well as in any structured field. If you travel to clients and have no public counter, do not invent a storefront. Say you are mobile and name the area you cover. Empty is more honest than a fake NAP block, and Start SEO with AI is built to leave a field empty when the links do not contain the fact. That behavior is described in titles and meta filled from your links.
FAQ schema, if you turn it on, should come from the real link titles on the page. “Book a repair” can support a question about booking. It cannot support a question about a service you do not offer. How citation uses the same fields is the answer-engine side.
Launch editorial is a dated URL, not a mood
A button list has no publication date. Search already knows what to do with an article. When you generate a launch story, LinkForge writes toward your profile and keeps a dated URL (the pattern used across the product is /en/launch/your-name). The story can cite the destinations on your page because it fetched them. Two generations a day is the cap, so the dates stay meaningful.
Now is the short sibling: one line at /u/your-name/now, in your theme, about the current offer. Together they are dated signals next to the bio. They do not replace the entity. A launch story about a plumber who has no address in the profile is a press release for a business search cannot place.
Internal links among the profile, Now, the launch story, and llms.txt stay follow links. The map of those URLs is the follow-link mesh. A nofollow maze would hide the very graph you are trying to make walkable.
HTML versus a widget, as a checklist
You can audit this without a specialist.
- Load the public URL logged out. View the HTML source. Your name and the first sentence should appear as text, not only inside a script bundle.
- The
<title>is the one you saved. Change it, reload, confirm. - Each outbound offer is an ordinary link with a readable anchor.
- The sitemap includes the published profile. LinkForge lists published bios and launch URLs there.
- The Instagram Website field is this URL. A perfect entity page that no profile points at still matters for search, and it matters more when your bios agree.
llms.txtrepeats the same entity facts. If the markdown says “Organization” and the footer says “a personal blog,” edit until they match.
A widget can still be pretty in a Story. It is a weak thing to hand someone who types your name. A bio page Google can read is the plain-language version of the same audit.
What Pro changes, and what it does not
The public page, the links, and a theme you can ship on the free plan exist on day one (five links, per-link analytics). Launch-story generation, the fuller SEO fields, custom CSS, AI insights, and a custom domain with SSL are Pro at 7€/month. Paying does not invent an entity you did not describe. It unlocks the tools around a description you still have to write. Pricing lives on the pricing page.
Do not buy a domain and point it at an untitled widget elsewhere, then expect the entity work to transfer. The structured data has to be on the URL you ask people to trust.
A small example
A salon owner sets LocalBusiness, writes “Shear House — cuts and color, Bordeaux,” pastes the street and the phone that is on the window, and links booking, the map, and a reviews URL. The Now line says “Closed 12–18 August.” The launch story, if they generate one, cites the booking page and the map because those links are real. A Person-typed page called “Welcome to my links” with no city would waste the same effort.
Set the type, write the title in the words a stranger would search, publish the HTML, and link Now and the launch story from that page. The widget era was a convenience. The document is what remains quotable.
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.