Linkfor vs Potion.so

Linkfor vs Potion: which Notion website builder is right for you?

Both turn Notion into a website on a real domain. Linkfor adds branded short links, iOS / Android deep links, and raw file hosting on the same mount tree — so a single subscription covers what Potion plus a separate Bitly plus a separate Branch normally would.

tl;dr

Pick Potion if you specifically want its SEO performance tooling and have no plans for redirects, deep links, or raw file hosting on the same domain.

Pick Linkfor if you want one domain doing four jobs at once — Notion site, branded redirects under /go/*, universal deep links, and static endpoints like ads.txt — without bolting three other vendors onto the same DNS.

At a glance

Linkfor vs Potion.so, feature by feature

FeatureLinkforPotion.so
Entry paid tier$1/mo$12/mo (1 site)
Custom domain
Notion content renderingreact-notion-x, fullProprietary, full
Branded short links + UTMNative /go/* redirects
Deep linking (iOS / Android)AASA + assetlinks.json
File hosting (raw endpoints)ads.txt, /.well-known/*
AnalyticsPageviews + redirect counts
SEO control (meta, OG, sitemap)Strong, the marketed feature
SSLAuto, on every mount
ThemesColor + font + radiusTheme presets + CSS
White-label (drop "Powered by")Business plan
Scheduled publishing
Password gateRoadmap
Multi-site / org3 sites on Pro, 10 on BusinessPer-site pricing
API / programmatic configDashboard-driven, JSON configLimited

Prices captured from each vendor’s public pricing page on 2026-04-21. Potion bills per site; check the live page if you need more than one.

Price delta

The bundled subscription you're already paying for

Potion.so (1 site)$12/mo
Linkfor Pro$1/mo

Potion is $12/mo per site. Linkfor Pro is $1/mo for 3sites — and that subscription also covers branded short links, deep links, and the raw-file routes you'd otherwise pay Bitly (~$29/mo) and Branch (~$59/mo) for separately.

The home-page consolidation table has the bundled total when you actually run the math.

When to pick Potion.so

  • SEO performance is the single most important thing for you, you've seen Potion's benchmark numbers, and the competitive feature is the one that closes the deal.
  • You want password-gated pages today; Linkfor's password gate is on the roadmap and Potion ships it.
  • You only ever plan to run one Notion site, never want a redirect cluster, never want deep links — your domain has one job.
  • You're committed to Potion's theme conventions and prefer its CSS-injection model to Linkfor's design-token approach.
  • You don't mind paying separately for short links and deep links if you ever need them later.

When to pick Linkfor

  • Your domain hosts more than just a Notion site — you also want /go/* redirects with UTM passthrough and /.well-known/* JSON endpoints under the same mount tree.
  • You ship a mobile app and want universal deep links (AASA + assetlinks.json) on the same domain — Linkfor generates them per tenant when you add bundle IDs.
  • You ship multiple Notion sites — Pro covers 3 sites and Business 10, no per-site upcharge.
  • You like scheduled publishing and want a route to flip from a draft Notion page to the live one at a chosen time.
  • You're budget-sensitive: $1/mo against Potion's $12/mo per site is hard to beat, especially with the redirect + deep-link primitives included.
Migration

How to switch from Potion.so to Linkfor

Your content lives in Notion already, so the migration is mostly DNS and re-creating any theme overrides.

  1. 1Note your Potion site's public Notion page IDs and any URL-mapped subpaths (Potion calls these "pretty URLs"). You'll re-map them as Linkfor routes.
  2. 2Sign up for Linkfor and create a site. Paste the same Notion root page URL into the dashboard.
  3. 3Re-create your subpath routing in the route tree. If you used custom CSS in Potion, port the parts you care about into Linkfor theme tokens (color, font, radius).
  4. 4Repoint your CNAME from Potion to Linkfor. SSL provisions automatically; verify the green padlock and run Lighthouse.
  5. 5Cancel Potion. If you've been paying separately for short links or deep links, those folds into Linkfor too — see /short-links and /deep-links.