Publishing Confluence pages publicly: how are you doing it, and what's painful?

[#1]

A lot of useful content already lives in Confluence:
product docs, guides, FAQs, knowledge base articles, onboarding materials.

But when this content needs to become public, things are not always simple.

Public links are helpful when you just need to share a page. But once you need SEO, branding, analytics, or a custom domain, I’m not sure public links are enough.

We recently launched Public Pages for Confluence an app that lets you publish selected Confluence pages as public, SEO-friendly pages.

We want to better understand how people make their Confluence content public today and what we should improve next.

A few questions I’d love to hear your thoughts on:

1. What do you use for public Confluence documentation today?
Native public links, Scroll Sites, Refined, a custom website, a help center tool, another CMS, or something else?

2. What is the most painful part of this process?
SEO, custom domains, keeping pages updated, branding, analytics, permissions, or something else?

3. What works well in your current setup?

4. What would you expect from a simple Confluence publishing app?