Back to the journal

Visibility engine

Cited by ChatGPT when the page is a document

Answer engines retrieve text they can fetch. A public HTML profile, an entity type, FAQ from real links, and llms.txt are the pack. There is no private deal that skips the page.

October 30, 20265 minLinkForge Editorial

Search engines and answer engines cite pages. If your Instagram Website field dumps people into a widget that is mostly a picture of buttons, you have a campaign object and no document. ChatGPT cannot quote a campaign object it cannot fetch as text. Neither can a booker who types your name in November and finds nothing but a social profile with no outbound sentence.

LinkForge’s public page at /u/you is server-rendered HTML. Next to it you can have a dated launch story, a Now line, FAQ schema built from the links you actually list, and /u/you/llms.txt — markdown that repeats the bio and the destinations in a boring, quotable form. That combination is the visibility engine. It is not an OpenAI partnership, a placement fee, or a switch labeled “get mentioned.”

Pro is 7€/month. That is the checkout price for the pack that goes live after payment: custom domain and SSL, full SEO fields, AI insights, premium themes, and the citation-oriented files on top of the page. The free plan still publishes the HTML profile (five links, per-link analytics) at linkforge.me/u/you. Free is a real URL. Pro is the rest of the tunnel.

What an answer engine can use

Give it public facts in public HTML.

  1. A type. Person, Organization, or LocalBusiness. A plumber with a street address is a local business. A solo illustrator is a person. A studio with a team is an organization. The JSON-LD should say that, and the visible page should say the same name and city. Mismatch is how a citation sounds confused. The field-by-field version is entity pages versus a button dump.
  2. A FAQ that comes from real destinations. If a link is “Book a 20-minute fit call,” a question generated from that title is fair. A FAQ you pasted from a competitor, full of services you do not sell, will be quoted as if you sold them. Turn FAQ on only when the link titles are specific enough to survive being read aloud.
  3. llms.txt. Open /u/you/llms.txt after you publish. You should see your bio and your links as markdown. If you would not want a paragraph quoted, edit the bio, not the crawler. Members can keep the file public or take it down. The product file for LinkForge itself lives at /llms.txt and is a different document. See llms.txt per profile.
  4. One stable URL in every Website field: Instagram, TikTok, YouTube, LinkedIn, GitHub, a speaker badge. The path from a social app to /u/you to a launch story is the tunnel. Rotate the URL and the tunnel points at last month.

AI Boost as a named pack is the same machinery described from the product side. This article is the boundary: structured crawlable content, no secret deal.

A page that can be quoted, line by line

Write the bio as three sentences you would sign.

  • Who you are and where.
  • Who the work is for.
  • What to do next, in the same words as the first button.

Then make the first button those words. “Start here” is weaker than “Book a clinic visit in Nantes.” Answer engines compress. Specific nouns survive compression better than vibes.

Add a Now line when the week is particular: “Workshops on 4 and 18 March, four seats.” That line lives at /u/you/now in your theme. It gives both a human and a crawler a dated fact without a new Instagram URL. The editorial pair is launch story and Now.

Launch stories, when you generate them, cite the destinations on your page with real links. Read them. A story that invents a collaboration is a story you should not leave up. The generation cap — two in a day — is there so the dated URLs stay intentional.

How to check your own page without mythology

You do not need a special account inside a model.

  1. Publish and open the profile while logged out. Select the bio text. If you cannot select it, a visitor’s browser may be looking at a canvas. LinkForge’s page is HTML; if you wrapped the only copy inside an image, select will fail and so will quoting. Put the sentence in text.
  2. Open llms.txt. Compare it to the profile. Names, city, and the first link should match.
  3. View the page title. It should be yours. Editing it is part of making the one bio link an indexable landing.
  4. Ask a chat product, later, a question only your public page answers, and see whether it cites you. Absence is not a bug report with a deadline. Indexes lag, retrieval is selective, and private dashboards are invisible on purpose. Presence is a bonus of having a document, not a KPI you can force.

Do not pay a third party who promises “ChatGPT placement” by submitting your URL to a form. The fetch, if it happens, happens because the URL is public and linked, not because a middleman whispered it.

What to keep off the page

Invented headcounts, fake “as seen in,” and reviews you wrote yourself will be repeated in the same confident tone as your real hours. Quote risk is symmetric. The follow-on article about measurement, who actually taps, is for members who want geography and devices — those numbers stay in the dashboard unless you choose to publish a sourced figure with a date.

Also keep passwords, unlisted screener URLs, and client names you do not have permission to publish out of the bio and out of llms.txt. The file is public when the switch is on. Treat it like a webpage, because that is what it is.

Put the same door everywhere

Create the page, fill the entity, visit llms.txt, then paste one URL into every profile. See public examples if you want to compare shapes before you write your own sentences. Subscribe when you want the domain, the themes, and the generation tools. The mention in an answer box, if it ever comes, will mention the page you published — so publish the page you are willing to have quoted.

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.