CitadexDocs

Integrations: manage every data and publishing connection in one place

How the Integrations page works: Configuring project, search and Suggested / All / Connected / Not finished, Suggested for you, cards by group and the one connection dialog; how to connect publishing channels (your own channels, third-party platforms through the browser extension, search-engine signals), how connections are kept per project, and what + / ✓ / Continue on a card mean.

Product Manuals7 min read

What this page is for

Every connection of a project is managed on this page: Google (Search Console and GA4), the site tracking snippet and AI crawler logs, revenue sources (stores, CRMs, payments), publishing channels, alerts and AI tools, and your own AI model keys. Once connected, AI Traffic, Revenue Attribution, publishing and the AI Assistant use the data straight away, and every article publishes in one click with the real link recorded. Connections are saved per project, so several brands or projects never interfere with each other.

When to use it

  • Right after creating a project, to get data into AI Traffic and Revenue Attribution: start with Suggested for you.
  • 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).
  • When the Data from line on AI Traffic or the Revenue from line on Revenue Attribution shows one step left or a grey not connected (clicking that chip opens the same dialog on that page).
  • To get pages indexed faster by Google and Bing.

The page

Configuring project at the top switches which project you are setting up (each project is saved on its own). Below it are a search box (for example Shopify or Cloudflare) and four filters: Suggested, All, Connected and Not finished. Every plan can open the page; publishing channels need a plan with one-click publishing.

  • Suggested: it starts with Suggested for you, up to 3 items: first connections you started that are one step short; then what your own site points to (Citadex reads your homepage to see what it runs on: "Your site runs on Cloudflare" suggests Cloudflare, a Shopify store suggests Shopify, a WordPress site suggests the WordPress crawler plugin); then the site tracking snippet and Google if they are missing. Below are the groups: Search and analytics, AI traffic, Revenue attribution, Publishing, Alerts and AI tools, AI models, 6 cards each with See all N.
  • Cards: logo, name and one line; on the right + (not connected), a green ✓ (connected) or an amber Continue (one step left).
  • The connection dialog: every card opens the same centered dialog: on the left, an overview and where it is used; on the right, its own settings and steps. Steps it depends on are listed in the same dialog and open there too; for example HubSpot needs the site tracking snippet and Auto-capture form emails first.
  • robots.txt check: whether your robots.txt lets each AI crawler in.

Publishing channels come in three kinds:

  1. Your own channels: GitHub / Static Site, WordPress, Shopify blog, Ghost, HubSpot CMS, Webflow, Wix, Zapier · Make · n8n, Hosted blog and Content API / RSS.
  2. Third-party platforms (browser extension): Medium, Dev.to, Hashnode, Substack, LinkedIn Articles, note, Qiita, Zenn and Ameblo, switched on in the Citadex Publisher extension card. The extension shows Connected (v…), Extension not detected or Browser not supported (Chrome / Edge only); if it isn’t installed, click Install from Chrome Web Store. The platforms follow your markets’ languages: English platforms appear only with an English-language market, Japanese platforms only with a Japanese-language market.
  3. Search-engine signals: Bing IndexNow and Google Search Console (both under Search and analytics).
Integrations · Suggested for you
Google
✓
Cloudflare
Continue
Shopify orders
+
WordPress
+
👆 Only a green ✓ means it is connected

What the marks mean

  • Green ✓ (Connected): GitHub is authorized and a repository is chosen; platforms that take credentials have passed Test Connection (test again after changing credentials).
  • Amber Continue (Not finished): filled in but not tested yet, still waiting for its first data, or its domain is still verifying. Open it to pick up where you left off.
  • + (Not connected): not set up yet; open it to start.
  • Inside a publishing channel's dialog you may also see Disabled (the settings are kept, but the channel is switched off); the hosted blog's Waiting for DNS or Domain error; and for Content API / RSS Awaiting integration after you generate a token, which changes to Connected only once your site has actually fetched from it (within 30 days). WordPress, Ghost and HubSpot can publish through the extension or directly; direct publishing counts as connected once its credentials pass the test.

Common tasks

Connect AI traffic and revenue data

Open a card under Suggested for you, or pick yours in the AI traffic and Revenue attribution groups: Site tracking snippet, Cloudflare, Vercel, WordPress crawler plugin, Next.js · Netlify · other servers; HubSpot CRM, Salesforce, Stripe, Shopify orders, WooCommerce, Webhook / API. Each dialog has the exact steps. Install the site tracking snippet before a revenue source, so revenue can be tied to AI.

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.

Open the card and, in the dialog, 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 dialog 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 · Make · n8n: follow the 5 steps in the dialog 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 with your Google account and every publish is submitted to Search Console automatically. For Bing IndexNow, enter the key and click Test link. robots.txt 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 Citadex Publisher extension dialog 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 Continue. The credentials were changed. Any change to a field needs a new Test Connection.

Troubleshooting

  • Required fields missing: fill in the fields marked red in the dialog.
  • 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 dialog and click Check status.
  • A publishing channel's dialog says "Publishing channels need a plan with one-click publishing.": click See plans to upgrade; every other connection works on every plan.

Was this article helpful?