Back to Help

Custom domains — Overview

April 15, 2026

Serve a channel under your own domain like blog.example.com instead of an omnicon.cloud URL.

A custom domain lets readers reach a channel at your own hostname — for example blog.example.com — instead of the default omnicon.cloud/en/c/<channelPermaName> URL.

Under the hood, OmniCon keeps serving the same channel; a middleware layer matches the incoming hostname against the channel's CustomDomain field and rewrites the path internally. Your content, editor URLs, and APIs don't change.

Setup is two steps:

  1. Prove you own the domain by adding a TXT record.
  2. Point the domain at OmniCon with a CNAME record.

Related topics: