Publishing — Own Channels, the Browser Extension and Daily Limits
How publishing works channel by channel: native channels that return a URL, the Citadex Publisher extension for twelve third-party platforms, language-based visibility, daily caps, minimum extension versions and what "processing" means.
Two kinds of channel
- Own channels publish through the platform's own API and return the live URL: GitHub / static site, WordPress and Ghost (direct credentials), Shopify, Webflow, Wix, Zapier, the Citadex hosted blog and the read-only Content API / RSS.
- Third-party platforms have no usable publishing API, so the Citadex Publisher browser extension (Chrome and Edge) opens the platform's editor in a new tab with the article filled in; you press that platform's Publish button. Until you do, the record stays "processing".
The twelve extension platforms
Medium, Dev.to, Hashnode, Substack, LinkedIn Articles, note, Qiita, Zenn, Ameblo, plus WordPress, Ghost and HubSpot in extension mode. Platforms are shown according to your markets' languages: the English platforms appear when you have an English market, the Japanese ones when you have a Japanese market; LinkedIn, WordPress, Ghost and HubSpot always appear.
Daily caps
Third-party platforms moderate promotional posting, so Citadex caps publishes per UTC day:
| Platform | Per day |
|---|---|
| Dev.to, Hashnode, Medium, note, Qiita, Zenn | 2 |
| 1 | |
| Substack | 3 |
| Own channels, Ameblo | No cap |
Only records that reached "publishing" or "published" count; an editor tab you opened but never submitted does not.
Minimum extension version
note, Qiita and Zenn need extension 1.2.6 or newer; Ameblo needs 1.3.0. The Integrations page shows an update notice when your build is too old; publishing to those platforms with an old build opens no page and stays stuck.
Before a third-party publish
The publish dialog counts brand mentions and warns when the article reads like advertising for strict platforms (Dev.to, Hashnode, Medium, LinkedIn). An AI pre-publish review runs for every third-party platform; see Pre-publish review. Own channels skip both.
Publish records
Every channel gets its own record with status and URL. Manual posts can be logged from the Content list ("Log a post") so all channels are in one place. Freshly published URLs typically take about a minute to open.
Frequently asked questions
Why can I not enable Medium? The extension is not detected. Install it from the Chrome Web Store link on the Integrations page, or use a browser that supports it.
Do WordPress and Ghost need the extension? No. Use the Integration button on their cards and enter an application password (WordPress) or Admin API key (Ghost) to publish directly.
Was this article helpful?