# Link-in-Bio Research Changelog

Material factual corrections and verification changes to Zentry Technology's link-in-bio corpus. Platform documentation changes; when the source record changes, the corpus is corrected and the change is recorded here.

Canonical page: https://zentry.technology/creator-tech/link-in-bio-tools/changelog/

## 2026-09-18 — Linklay: Server-rendered profile HTML

- **From:** unverified — a raw request for a profile path returned the shared marketing shell rather than profile-specific HTML
- **To:** 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
- **Reason:** 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.
- **Source:** Observed response for linklay.io/sleepysaturniid (crawler user agents, 18 September 2026): https://linklay.io/sleepysaturniid
- **Source:** About Linklay: https://linklay.io/about

## 2026-09-18 — Linktree: Custom domain

- **From:** Paid plans
- **To:** Not offered on any plan
- **Reason:** 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.
- **Source:** Can I change the Linktree URL to a custom domain?: https://help.linktr.ee/en/articles/6571689-can-i-change-the-linktree-url-to-a-custom-domain

## 2026-09-18 — Carrd: Custom domain

- **From:** Any Pro tier
- **To:** Pro Standard or higher ($19/year)
- **Reason:** 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.
- **Source:** Using a custom domain: https://carrd.co/docs/sites/using-a-custom-domain
- **Source:** Carrd Pro plans: https://carrd.co/docs/pro/plans

## 2026-09-18 — Beacons: Monthly and annual price

- **From:** unverified — Beacons' own pricing pages render tier prices inconsistently
- **To:** $10/month or $100/year (Creator); $30/month or $300/year (Creator Plus); $90/month or $900/year (Creator Max)
- **Reason:** 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.
- **Source:** Beacons pricing plans: https://help.beacons.ai/en/articles/4695681

## 2026-09-18 — Stan Store: Custom domain

- **From:** unverified
- **To:** Not available on any plan
- **Reason:** 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.
- **Source:** Common feature requests: https://help.stan.store/article/149-common-feature-requests

## 2026-09-18 — Campsite: Pixels, analytics history and custom domain

- **From:** unverified — the help centre describes tracking pixels as a paid 'premium integration' without naming tiers
- **To:** 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
- **Reason:** 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.
- **Source:** Plan features: https://support.campsite.bio/en/articles/7922505-plan-features
- **Source:** Adding a Facebook pixel: https://support.campsite.bio/en/articles/6848828-adding-a-facebook-pixel
- **Source:** Adding a TikTok tracking pixel: https://support.campsite.bio/en/articles/6849950-adding-a-tiktok-tracking-pixel

## 2026-09-18 — Corpus: Fact model

- **From:** One source list per platform record
- **To:** Per-assertion provenance: every field carries its own verification status, source references and check date
- **Reason:** 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.
- **Source:** How we evaluate link-in-bio tools: https://zentry.technology/creator-tech/how-we-evaluate-link-in-bio-tools/