You're here because a Notion page is doing real work for you—an investor memo, a public changelog, docs for customers—and you want it to live at your domain, not a generic notion.site URL. That instinct is right. The most common problems aren't "hacks"; they're hygiene issues: public links quietly spreading in chats, slugs getting changed and breaking bookmarks, guest access lingering after people leave, and presentation gaps that dilute trust (no brand, messy URLs, weak SEO). When the doc matters, brand control and link stability matter, too. Notion now offers "Notion Sites" with first-party custom domain support, but it's easy to ship something that's on-brand in name only if you don't set it up thoughtfully.

1) Why you need this (how errors actually happen)

Link sprawl & resharing. A "share to web" URL ends up in Slack/Telegram and keeps traveling long after context is gone. If you later change page structure or slug, you 404 existing shares. Notion's slug behavior is specific and can surprise people (e.g., home pages, slug limits).
Guest creep. Over time, you invite external collaborators and forget to prune them. Access persists even when roles change. (This is a people problem, not a software problem.)
Brand dilution. notion.site/your-page looks unpolished in sales or investor workflows. You lose the trust and SEO equity of yourdomain.com.
Mixed audiences. Some content should be public, some semi-private, some fully gated. A single public link can't represent all these states cleanly.

A custom domain (and a tidy process behind it) solves most of this: clean URLs, consistent metadata, and a single address you control.

2) What "custom-domain Notion" has to do in 2025

For founder-grade results, don't chase one setting—chase a bundle:

Own the URL. Serve pages at your domain or subdomain (e.g., docs.yourdomain.com) so you control branding, redirects, and link lifetime. First-party Notion Sites now support connecting custom domains via a paid add-on.
Stable navigation & slugs. Avoid breaking links when you reorganize; plan the top-level nav and slugs before you promote URLs.
SEO & share cards. Set titles/descriptions and preview images so your links look intentional in search and social. Notion Sites exposes basic SEO fields.
Performance & uptime. Use a delivery path that's fast and cache-friendly; third-party Notion site tools emphasize this, as does Notion Sites.
Governance. Decide what's public vs. private. Public marketing? Fine. Anything sensitive? Don't rely on public Notion links—front it with a controlled viewer and identity gate. See access control best practices and confidential documents guide for secure sharing.

3) How to accomplish the goal using Peony (step by step)

Peony provides enterprise-grade secure document sharing with AES-256 encryption, dynamic watermarks, granular access controls, and complete audit trails.

If your Notion content is sensitive (pricing details, investor notes, customer lists) or you simply need a branded, controlled front door with revocation and analytics, treat Notion as the authoring surface and Peony as the distribution surface.

Step 1 — Pick the artifact you'll share

You can directly add Notion pages to Peony without exporting—simply connect your Notion workspace and select the pages you want to share. Alternatively, export the relevant Notion page (PDF/HTML where appropriate) or create a polished viewer version (deck, PDF, doc). The audience sees this artifact—not your raw workspace.

Step 2 — Upload to a Peony "room"

Create a room named by context (e.g., "Investor Update – Jan 2025," "Docs – Pricing Preview"). Upload your exported content and supporting files (appendices, FAQs). See confidential documents guide for organized, controlled sharing.

Step 3 — Set identity-based access

Grant specific emails (or approved domains). No open public links for sensitive content. This is the effective "gate" most people wish Notion had for public pages. See password protection options for additional layers.

Step 4 — Ship with protection by default

Enable view-only for externals; disable downloads unless needed; set expiry for time-boxed campaigns. Turn on dynamic watermarking so screenshots are attributable and casual resharing is risky—not invisible. See watermarking and screenshot protection for comprehensive protection.

Step 5 — Brand the entry point

Share a single Peony link everywhere (site, email, social). If you want it strictly under your domain, create a branded redirect such as go.yourdomain.com/brief → Peony link via your DNS/edge or your CMS/redirects. (This preserves your brand while you keep Peony's control.) See secure file sharing best practices and custom branding options for more.

Step 6 — Update, monitor, revoke

Replace files behind the same link as facts change; see access activity (light analytics); revoke an individual, a whole domain, or the room when the campaign/round ends. You keep the power—no broken public URLs, no link rot.

This hybrid model lets you keep using Notion to write while Peony handles gating, analytics, watermarking, and revocation—the parts public Notion links don't solve.

4) Other methods if you can't use Peony

A) Notion Sites (first-party)

On paid workspaces, you can connect a custom domain to Notion Sites via an add-on (priced per domain; up to 25 domains per workspace). You'll configure DNS (typically CNAME) and manage basic SEO, branding, and navigation right in Notion. This is the cleanest "official" path for public pages.

Notion's documentation covers the full setup process.

B) Super / Potion (third-party site layers)

Both take your Notion page and publish it at your domain with better performance, clean URLs, and styling controls. They provide step-by-step DNS guidance to connect your domain. Great for marketing sites, docs, and blogs where you want more design control.

C) DIY Cloudflare worker / Fruition approach

Free or low-cost and flexible, but technical and maintenance-prone as platforms evolve. Community threads note that older tutorials can go stale as Cloudflare changes its UI and features. Use only if you're comfortable owning breakage.

D) Keep it private inside Notion

If the audience is internal, skip public links: invite named users and rely on SSO/domain controls on Business/Enterprise tiers. This is governance-friendly, not a public website replacement.

5) Practical setup tips (tiny habits, big brand lift)

Draw the line: Public marketing/handbooks → Notion Sites or Super/Potion at your domain. Sensitive docs → Peony link with identity gate and deterrence. See confidential documents guide for secure sharing.
Ship real previews. Set titles/descriptions and social images so links look intentional in DMs and on social.
Own the redirect layer. Even if you publish at notion.site, map memorable redirects (/brief, /roadmap) from your domain; you can rotate destinations without changing the public URL.
Audit quarterly. Prune Notion guests, review what's still public, and rotate any temporary promo pages. See secure file sharing guide for access controls.
Don't gate with hope. If a page is sensitive, don't rely on "please don't reshare." Use Peony's identity-based access, watermarking, and revocation. See PDF forwarding prevention for comprehensive protection.

Bottom line

In 2025 you have three clean paths: (1) Notion Sites with a first-party custom domain for straightforward public pages, (2) Super/Potion when you want more design/performance control, and (3) Peony as the front door when the content is sensitive or you need analytics, watermarking, and revocation. Pick the lane based on audience and risk, and your Notion content will look—and behave—like it belongs to a serious brand.

Share Files Securely

How to Share Notion Pages with Custom Domain in 2025: Complete Branding & Security Guide