How to connect your own channels, third-party platforms (browser extension) and AEO signal tools, how integrations are kept per project, and what Connected / Not tested / Disabled / Integration mean.

What this page is for

Connect your website, store or blog, and every article publishes in one click with the real link recorded. Integrations are saved per project, so several brands or projects never interfere with each other.

When to use it

Before publishing your first article.
When the publish dialog shows Not connected · publishing will fail for a platform (Set up in Integrations → opens the right card directly).
To get pages indexed faster by Google and Bing.

The page

The title is Publishing Integrations. The page needs Pro or higher. Configuring project at the top switches which project you are setting up.

Extension banner: the status of the browser extension Citadex Publisher — Connected (v…), Extension not detected or Browser not supported (Chrome / Edge only). If it isn’t installed, click Install from Chrome Web Store. Publishing to third-party platforms relies on it.

Three groups of cards:

Your own channels: GitHub / Static Site, WordPress, Shopify, Ghost, HubSpot, Webflow, Wix, Zapier / Automation, Hosted blog and Content API / RSS.
Third-party platforms (browser extension): Medium, Dev.to, Hashnode, Substack, LinkedIn Articles, note, Qiita, Zenn and Ameblo. They follow your markets’ languages: English platforms appear only with an English-language market, Japanese platforms only with a Japanese-language market. A note below says how many are hidden, with a link to add markets.
AEO Signal Tools: Bing IndexNow, robots.txt health check and Google Search Console.

What the statuses mean

Connected: GitHub is authorized and a repository is chosen; platforms that take credentials have passed Test Connection (test again after changing credentials).
Not tested: required fields are filled in, but the test hasn’t passed yet.
Disabled: the settings are kept, but the channel is switched off.
Integration: not set up yet; click to start.
The hosted blog can also show Waiting for DNS or Domain error. Content API / RSS shows Awaiting integration after you generate a token, and changes to Connected only once your site has actually fetched from it (within 30 days).
Third-party platform cards show Enabled / Disabled. WordPress, Ghost and HubSpot have both an extension badge and an Integration badge; a green Integration badge means direct publishing credentials passed the test.

Common tasks

Connect GitHub (static site)

On the card, Connect with GitHub to authorize → choose the repository → the framework and content folder are detected automatically (edit them if they’re wrong) → Test Connection → Save.

Connect WordPress / Ghost (direct publishing, recommended)

On the card, click Integration → Set up direct publish: enter the site URL, the WordPress username and an application password (for Ghost, the Admin API key) → Test direct publish → Done. No browser extension needed. Alternatively, use only the extension: switch it on and enter the site URL.

Connect Shopify / Webflow / Wix

Each card has a "3 steps to connect" guide: create API credentials in the platform’s admin → paste them into the form → Test Connection → Save.

A site without a CMS

Hosted blog: enter the address and name, Save, then Open blog ↗ to see it. Then Use your own domain: enter a subdomain, Bind, add the DNS record shown at your domain provider and click Check status. View illustrated walkthrough shows each step with screenshots.
Content API / RSS: Generate token and give the article list, single-article and RSS endpoints to your developer.
Zapier / Automation: follow the 5 steps in the drawer to build a Zap that forwards articles by webhook to Notion, Contentful and similar tools. Note that Zapier counts Webhooks as a paid app.

Get indexed faster

Connect Google Search Console with your Google account and every publish is submitted automatically. For Bing IndexNow, enter the key and click Test link. robots.txt health check checks whether AI crawlers are allowed and gives you a Fix snippet.

Common questions

Why can’t I switch on a third-party platform without the extension? Third-party platforms have no official publishing API, so the extension opens their editor in your browser. Switching one on first prompts you to install it.

The extension says it’s out of date. The banner or the platform group shows the minimum version needed; update the extension.

I don’t see note, Qiita and the other Japanese platforms. The project has no Japanese-language market. Add one and they appear.

The test passed, but a few days later it says Not tested. The credentials were changed. Any change to a field needs a new Test Connection.

If something goes wrong

Required fields missing: fill in the fields marked red in the drawer.
A failed test: check the credentials, permissions or site URL (without a trailing slash) as the message says.
Hosted blog Domain error: the DNS record isn’t live yet or is wrong. Compare it with the record in the drawer and click Check status.
"Publishing Integrations require Pro plan or higher": your plan doesn’t include integrations; they are available after upgrading.

Integrations: connect once, then publish every article to your own site in one click