📌 How to Publish Confluence Pages on a Custom Domain

[#1]

Most teams spend months building solid documentation in Confluence, then share it via a link that looks like this:

yourteam.atlassian.net/wiki/spaces/DOC/pages/123456789.

That URL looks unprofessional, it confuses visitors, and it tells search engines nothing useful about your content.

Here's how to fix it.

Why the default Confluence URL is a problem

When you share documentation publicly from Confluence without any setup, a few things happen:

Your URL contains atlassian.net. Visitors see it and wonder if they've landed somewhere official or just a random team workspace.

For product documentation, help centers, or terms of service pages, this matters, it affects whether people trust what they're reading.

The URL structure is long and unmemorable. /wiki/spaces/PROJ/pages/98374651/Getting+Started is not something a user types, bookmarks, or shares. It breaks easily when pages are renamed or moved.

Google treats the content as part of Atlassian's domain, not yours. That means any SEO value from your documentation goes toward atlassian.net, not toward your own site. You're building someone else's domain authority.

What you actually want

The goal is simple: your Confluence content, accessible at something like docs.yourcompany.com or help.yourproduct.com, with clean URLs like docs.yourcompany.com/getting-started.

This means visitors see your brand. Search engines index your domain. Links you share don't break. And you control the experience.

The native Confluence option and its limits

Confluence Cloud does allow anonymous access you can make a space public so anyone on the internet can view it. But it still serves content from atlassian.net, still shows the full Confluence interface with the Create button and navigation menus, and gives you no control over the URL structure.

There's no built-in way in Confluence to serve your content from your own domain.

How to set up a custom domain for Confluence pages

The practical solution is to use an app that sits between Confluence and your visitors, serving your content from your domain. Public Pages for Confluence is built specifically for this.

Here's how the setup works:

Step 1 — Install the app from the Atlassian Marketplace

Install for Public Pages for Confluence and start a free trial. No technical setup required at this point.

Step 2 — Add your domain in Site Settings

Inside the app's settings panel, go to the Custom Domain tab. Enter the domain you want to use for example yourcompany.com.

Step 3 — Add two DNS records

The app will show you exactly which records to add at your DNS provider:

• A CNAME record pointing docs to the app's hosting address
• A TXT record for domain verification

Add records at your DNS provider (Cloudflare, Route 53, Namecheap, wherever you manage your domain). This takes about two minutes.

Step 4 — Verify the domain

Wait 5-15 minutes for DNS to propagate, then click Verify domain in the app. The status changes from "Pending verification" to "Active."

Step 5 — Publish your first page

Open any Confluence page, click the Public Page Settings button in the byline area, set a slug like getting-started, add an SEO title and meta description, and click Publish. Your page is now live at yourcompany.com/getting-started.

The result

Visitors land on a clean page that shows your logo and site name. The Confluence interface is completely hidden no Create button, no internal navigation, no Atlassian branding. Just your content, on your domain.

Your Confluence documentation or articles appear to the outside world as a proper, branded website on your own domain.

Clean URLs. Your branding. Google indexing your domain, not Atlassian's.