If your channel already has a verified custom domain, the community on that channel automatically gets the same domain — readers never have to leave your brand.
The URL shape
Pick whichever line matches how you reach the channel today; the community URL is in the right column.
| Channel URL | Community URL |
|---|---|
https://omnicon.cloud/en/c/your-channel |
https://omnicon.cloud/en/c/your-channel/community |
https://your-domain.com (custom) |
https://your-domain.com/community |
The same pattern extends to every sub-page:
/community/p/{post-name}— a post/community/m/{display-name}— a member's public profile/community/join,/community/profile,/community/leave— the member-side actions/community/sitemap.xml,/community/feed.xml— SEO and RSS
What you have to do
Nothing extra. Once your channel's custom domain is verified, the community is reachable at the same domain immediately. There's no second DNS record, no separate verification, no community-specific settings.
If you haven't set up a custom domain yet, see DNS setup and verifying. Same flow as for the channel site itself.
Login on a custom domain
One thing to know: web cookies don't span hosts, so a reader who's logged into omnicon.cloud arrives at your-domain.com as a visitor. To join, post, or edit their profile they'll log in on the custom host directly. Same OmniCon credentials — they just enter them once on each domain.
For most cases this is invisible: a reader who lands on your-domain.com/community for the first time hits Join → login → back to the join form. No double-jump.
SEO and the canonical URL
When a community is on a custom domain, OmniCon emits the canonical link tag pointing at that custom origin (not omnicon.cloud). Search engines see your domain as the source of truth, which is what you want.
The sitemap and RSS feed at /community/sitemap.xml and /community/feed.xml are auto-populated with every Published community post and respect the same custom-domain origin in their links.
Private communities and SEO
If your community has Posts readable without joining turned off (set during enable), the sitemap and RSS feed both 404 — we don't list URLs that visitors can't actually load. That's intentional: the privacy gate is real, not just UI.
Multiple custom domains
One channel, one domain, one community. If you need multiple branded communities (e.g. one per region), open multiple channels and verify a domain on each. The community lives wherever its parent channel does.