Linkfor vs Dub: branded short links, plus the rest of your domain
Dub is a polished link-management tool. Linkfor uses the same redirect primitive as your Notion site, so /go/* lives next to / on the same domain — and you stop paying for the parts of Dub that overlap with your CMS.
Pick Dub if branded short links are your only job, your team already uses its workspace UX, and you don't need anything else on the domain — no Notion site, no static files, no /.well-known endpoints.
Pick Linkfor if your domain is a filesystem: / renders Notion, /go/* redirects with deep links, /ads.txt serves a raw response. Same primitive, same dashboard, one subscription.
Linkfor vs Dub.co, feature by feature
| Feature | Linkfor | Dub.co |
|---|---|---|
| Entry paid tier | $1/mo | $25/mo (Pro) |
| Custom domain | ||
| Notion content rendering | ||
| Branded short links + UTM | ||
| Deep linking (iOS / Android) | AASA + assetlinks.json | Yes (UA routing) |
| File hosting (raw endpoints) | ads.txt, /.well-known/* | |
| Analytics | Pageviews + redirect counts | Strong (the marketed feature) |
| SEO control (meta, OG, sitemap) | N/A (no rendered pages) | |
| SSL | Auto, on every mount | |
| Branded short links | Native /go/* on same domain | Yes (separate domain) |
| Themes | Color + font + radius | Branded link metadata only |
| White-label (drop "Powered by") | Business plan | Higher tier |
| Scheduled publishing | ||
| Password gate | Roadmap | |
| Multi-site / org | 3 sites on Pro, 10 on Business | Workspaces with seat pricing |
The bundled subscription you're already paying for
Dub Pro is $25/mo. To match what Linkfor Pro ships at $1/mo you also need a Notion website builder (Super.so, ~$16/mo, or Potion.so, ~$12/mo) and somewhere to host raw ads.txt / /.well-known/* endpoints.
Linkfor folds all three into one subscription against one custom domain — see the home-page consolidation table.
When to pick Dub.co
- Link management is your specialty — you live in dashboards, you ship hundreds of links, and the analytics depth is the tool you reach for daily.
- You need the open-source angle. Dub is OSS-leaning; Linkfor is closed-source SaaS. If self-hosting matters, that's a real reason.
- Your team already onboarded into Dub's workspaces and the switching cost outweighs the consolidation savings.
- You want password-protected short links today; Linkfor's gate is on the roadmap.
- Your domain is doing exactly one job (redirecting), and you don't mind keeping a separate
wwwhost for the marketing site.
When to pick Linkfor
- You want
/go/demoand your Notion site at/on the same domain — no CNAME tetris, no "use a separate go.acme.com for links." - You want a Notion site included in the same plan, not a separate vendor.
- You ship a mobile app and want universal deep links (AASA + assetlinks.json) on the redirect domain — no Branch SDK to integrate.
- You need to host
ads.txt,robots.txt,/.well-known/*without a separate Vercel project. - You want a single subscription: $1/mo on Linkfor Pro against $25/mo for Dub Pro alone.
How to switch from Dub.co to Linkfor
Dub exports your link list to CSV. Linkfor takes the same shape (slug → destination, with optional UTM and deep-link config) and re-creates the cluster on your own domain.
- Export your link list from Dub as CSV (slug, destination, UTM tags, optional iOS/Android URLs).
- Sign up for Linkfor and create a site. Attach the same custom domain you used in Dub — point the CNAME at Linkfor when you're ready to cut over.
- Mount your redirect cluster (typically
/go/*or/r/*) and import the CSV. Linkfor maps each row to a redirect route with optional{ ios, android, web }deep-link fields. - Add a Notion site mount at
/if you want a landing page on the same domain. Optional but free with the same plan. - Cut over DNS, verify a few links resolve, then cancel Dub.
Also see short links Notion sites deep links pricing.