--- service: "Publicasta" schema_version: "1.0" article_id: 569 title: "One Channel, Multiple Domains: Publish Once, Reach Different Audiences" language: "en" default_language: "en" canonical_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=en" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=en" api_url: "https://publicasta.com/api/public/v1/channels/publicasta/articles/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=en" channel_url: "https://publicasta.com/api/public/v1/channels/publicasta" channel_articles: "https://publicasta.com/api/public/v1/channels/publicasta/articles" search_url: "https://publicasta.com/api/public/v1/search" documentation_url: "https://publicasta.com/api-docs#reading-publicasta" openapi_url: "https://publicasta.com/api-docs/openapi.json" published_at: "2026-10-01T11:33:19+00:00" updated_at: "2026-10-01T11:33:19+00:00" translations: - language: "ar" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=ar" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=ar" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=ar" - language: "de" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=de" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=de" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=de" - language: "en" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=en" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=en" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=en" - language: "es" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=es" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=es" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=es" - language: "fr" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=fr" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=fr" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=fr" - language: "id" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=id" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=id" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=id" - language: "it" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=it" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=it" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=it" - language: "ja" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=ja" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=ja" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=ja" - language: "ko" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=ko" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=ko" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=ko" - language: "pl" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=pl" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=pl" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=pl" - language: "pt-br" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=pt-br" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=pt-br" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=pt-br" - language: "ru" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=ru" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=ru" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=ru" - language: "tr" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=tr" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=tr" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=tr" - language: "zh-hans" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=zh-hans" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=zh-hans" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=zh-hans" - language: "zh-hant" html_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences?lang=zh-hant" markdown_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.md?lang=zh-hant" json_url: "https://publicasta.com/publicasta/one_channel_multiple_domains_publish_once_reach_different_audiences.json?lang=zh-hant" --- # One Channel, Multiple Domains: Publish Once, Reach Different Audiences > Connect multiple custom domains to one Publicasta channel, assign a default language to each domain, and publish articles once without creating duplicate channels or copies. ![cover_en](https://publicasta.com/storage/projects/5/pages/569/2026/09/1f38deed-cd26-4491-9bb6-ffccabbd3b82.webp) A company may run several websites: an international site, a Spanish site, a German site. Separate domains may also be used for different brands, regions, or products. Sometimes the reason is simpler: the same content needs to appear under different addresses for different audiences. The articles themselves may be identical. Creating a separate channel for every domain quickly leads to duplicate content. A new article has to be published several times, corrections copied manually, translations checked separately, and someone has to remember which version was updated where. Publicasta lets you connect several domains to a single channel. Articles, translations, comments, and channel settings remain shared. The domains only determine where readers enter the channel and which language version should be shown first. ## Publish Once, Use Several Domains Suppose your articles are available in English, Spanish, and German. You could connect three domains to the same channel: - `www.example.com` - `www.example.es` - `www.example.de` There is no need to create three separate channels. You publish the article once and add English, Spanish, and German versions to that same article. They remain part of one publication and are managed inside one channel. Each domain can have its own default language. A reader visiting the Spanish domain will first be shown the Spanish version, if it exists. The German domain can prefer German, while the international domain can default to English. The channel itself remains the same. When you publish another article, you do not have to copy it to three different places. A new translation is added to the existing article rather than becoming another independent publication. ## One Main Domain — or Several Working Mirrors One connected domain is selected as the primary domain. Other domains can either redirect to it or work as mirrors. With a redirect, visitors are sent to the primary or canonical domain. A mirror behaves differently. The reader stays on the domain they originally opened. For example, someone may visit: `www.example.de/getting-started` and continue browsing articles on `www.example.de`. The same domain is also preserved in channel and article URLs, as well as RSS, JSON, and Markdown links. This makes a mirror more than another address pointing to the same destination. It becomes a separate entry point into the same channel. ## Let Each Domain Speak to Its Own Audience A domain often already tells you something about the audience. For example: `www.example.com` — English `www.example.es` — Spanish `www.example.de` — German Each mirror can have its own default language. If the URL does not specify a language explicitly, Publicasta first tries the language assigned to that domain. If that translation does not exist, the normal channel fallback languages are used. The Spanish domain can open Spanish versions by default, while the German domain opens German versions, without splitting the articles into separate channels. This works well for projects that already have regional websites and want to keep familiar local addresses without maintaining duplicate content. ## Readers Are Not Locked to the Domain Language The domain only sets the default. If the reader chooses another language or opens a URL with an explicit language parameter, that choice takes priority. All translations still belong to the same article. The domain simply helps decide which one to show first. ## Keep Internal Links on the Current Domain Articles often link to other articles in the same channel. If every link contains a full URL, those links become tied to one particular domain. For internal navigation, you can use a relative URL: `./getting-started` A reader on the Spanish mirror will open the next article on the Spanish domain. A reader on the German mirror will stay on the German domain. The same article content can therefore work across all mirrors without maintaining separate sets of links for each site. ## Where This Becomes Especially Useful: Documentation A regular blog or publication can use multiple domains to separate audiences without duplicating articles. The same setup is particularly useful for documentation, help centers, and knowledge bases. These channels usually contain many interconnected articles, and their structure often needs to stay identical across several languages or websites. For example, the same documentation channel could be available through: `docs.example.com` `ayuda.example.es` `hilfe.example.de` The articles and translations remain in one channel. The Spanish address opens Spanish versions by default, the German address opens German versions, and the documentation itself is still maintained in one place. For larger documentation channels, you can create a dedicated contents article and pin it. For example: - Getting Started - Account Settings - Working with Articles - Integrations - API - FAQ Relative links work well here too. A pinned article can also be used as the navigation structure for the whole channel. H2 and H3 headings form sections and nested items. Only published articles from that channel are included. External links, duplicates, and the pinned article itself are excluded. When a reader opens the documentation through a mirror, navigation links keep the current domain. The reader’s language is also preserved unless the source link specifies another language explicitly. Long articles can have their own table of contents based on H2 and H3 headings in the selected language version. On wide screens, navigation can move into a side panel after scrolling. On narrow screens, it appears in a compact bar at the top. If both article navigation and channel navigation are available, the reader can switch between them. ## What Search Engines See The same article appearing on several domains needs clear canonical and language signals. Publicasta assigns one canonical domain to each published language. The `canonical` URL points to the main address for that language version, while `hreflang` connects the different translations. Each mirror sitemap contains only the canonical URLs assigned to that domain. Adding several mirrors does not mean that the same article has to be indexed as several unrelated publications. For Google Search Console, each mirror should be added as a separate property and managed by the domain owner. ## One Article, Shared Reader Activity A custom domain does not create a separate copy of the channel or a separate set of reader data. Comments, reactions, favorites, and subscriptions belong to the same publication regardless of which active domain the reader used. Readers can sign in to their Publicasta account from the primary domain or any active mirror and continue using those features. The sign-in screen identifies Publicasta because reader accounts are handled by the platform. A custom domain changes the public address of the channel, but it does not turn Publicasta into a white-label service. ## See Which Domain Brings the Traffic Publicasta records the domain through which a page was opened. Analytics can therefore separate traffic from: `www.example.com` `www.example.es` `www.example.de` There is no need to create several channels just to compare traffic from different domains. ## Connecting a Custom Domain Only the channel owner can connect a domain. Enter the domain in channel settings and Publicasta will provide a TXT record to verify ownership. Once verified, point the domain with a CNAME record to: `connect.publicasta.com` For a root domain, use CNAME flattening, ALIAS, or ANAME if your DNS provider supports it. DNS changes may take some time to propagate. Publicasta automatically rechecks domains that are still pending, and you can also start a manual check from channel settings. After Cloudflare validates the hostname and issues an SSL certificate, the domain can be selected as primary or switched to mirror mode. If your DNS configuration includes CAA records, they must allow the certificate authority used by Cloudflare. If your subscription no longer includes custom domains, the interface shows a grace period before the domain is disconnected. Articles are not deleted and remain available through their Publicasta addresses. ## One Publication, Several Ways In A single channel can serve several websites, regions, or language audiences. It may be a blog, a company publication, a collection of articles, a help center, or a multilingual knowledge base. The articles and their translations stay in one place. Each domain gives readers a different way into the same channel and can open the language intended for that audience by default. A new article only needs to be published once. Its translations can be added to the same publication, while domains and languages are configured around it without creating duplicate copies of the content.