Skip to content
    ZentryTechnology

    Link-in-bio research changelog

    Platforms change their pricing and documentation, and we get things wrong. When the source record changes, we correct the corpus and record the change here — the old value, the new value, the reason and the evidence. Corpus last updated 2026-09-18.

    Only material factual changes appear here. Wording edits and new pages do not.

    1. 2026-09-18

      Linklay: Server-rendered profile HTML

      Previous value
      unverified — a raw request for a profile path returned the shared marketing shell rather than profile-specific HTML
      Current value
      Verified: a raw request for a public profile returns profile-specific HTML, including display name, bio text, link labels, page title, OpenGraph tags and two JSON-LD blocks
      Why it changed
      Re-tested directly. The earlier check used a browser user agent and received a Cloudflare challenge shell, which we mistook for the application shell. Repeating the request as Googlebot, Bingbot and GPTBot returns a 5.6 KB document containing the profile's own content. Because search and answer engines crawl with those agents, the crawler-facing response is the one that determines indexability.

    2. 2026-09-18

      Linktree: Custom domain

      Previous value
      Paid plans
      Current value
      Not offered on any plan
      Why it changed
      Our previous value was wrong. Linktree's help centre states directly that it does not offer the option to use a custom domain to replace the linktr.ee URL, and does not provide domain forwarding tools. A redirect link to your own site is the documented alternative. This was corrected on the platform profile, the buyer guide, every comparison, the capability grid and the machine-readable files.

    3. 2026-09-18

      Carrd: Custom domain

      Previous value
      Any Pro tier
      Current value
      Pro Standard or higher ($19/year)
      Why it changed
      Carrd's documentation for using a custom domain is labelled 'Requires Pro Standard or higher', so the $9/year Pro Lite tier does not include one. The buyer guide's 'cheapest custom domain' framing was corrected to name the $19/year tier.

    4. 2026-09-18

      Beacons: Monthly and annual price

      Previous value
      unverified — Beacons' own pricing pages render tier prices inconsistently
      Current value
      $10/month or $100/year (Creator); $30/month or $300/year (Creator Plus); $90/month or $900/year (Creator Max)
      Why it changed
      The plan-comparison article in Beacons' help centre now states each tier's monthly and annual price, so the field moves from unverified to verified.

    5. 2026-09-18

      Stan Store: Custom domain

      Previous value
      unverified
      Current value
      Not available on any plan
      Why it changed
      Stan's help centre states there is no way to connect a custom domain yet and suggests domain forwarding instead. This is a documented absence, so it is now recorded as a verified 'no' rather than a gap.

    6. 2026-09-18

      Campsite: Pixels, analytics history and custom domain

      Previous value
      unverified — the help centre describes tracking pixels as a paid 'premium integration' without naming tiers
      Current value
      Meta pixel, TikTok pixel, Google Analytics, UTM parameters, custom domain and branding removal are all Pro-plan features; analytics history is 14 days on Free, 60 days on Pro and lifetime on Pro+ with CSV export
      Why it changed
      Campsite's plan-features article and the individual pixel setup guides state the Pro requirement explicitly, which resolves several fields we had recorded as unverified.

    7. 2026-09-18

      Corpus: Fact model

      Previous value
      One source list per platform record
      Current value
      Per-assertion provenance: every field carries its own verification status, source references and check date
      Why it changed
      Readers and answer engines could previously see which sources a record used, but not which source supported which claim. Each field now names its own evidence, and the JSON and CSV datasets expose the same structure. A field that cannot name a source fails the build.

    Related research

    Machine-readable version: Markdown