Help
No. CMS publishing is optional. You can still run audits, track citation history, generate content, and use alerts without connecting anything.
Pilot and Fleet include publishing to connected CMS providers. Free tier covers audits and dashboard access — upgrade when you want ongoing monitoring and publish.
Use Signal Desk as the connected GEO publish desk, or skip CMS setup and keep drafting inside CitePilot until you have a destination site.
Connect one only when you have an actual site where the generated articles should go live. The CMS panel is there when you need it, not as a launch blocker.
Step 1
Generate an article in CitePilot from the Content dashboard.
Step 2
Connect the CMS for the specific workspace if that workspace already has a site.
Step 3
Publish the article from the queue to create the first remote item.
Step 4
Publish the same article again later to update the existing remote item instead of duplicating it.
Use the CMS your real site already runs on. If you do not have any of these platforms yet, there is nothing to connect today.
What you need: Site URL (e.g. https://www.signaldeskblog.com) and a Bearer API key from Studio → Settings
Best for: GEO / citation-ready publishing for CitePilot and Cadence articles.
Preferred connected publish desk beside the Growth Stack. Paste site URL + API key under Integrations → Signal Desk; optional publish webhook syncs status back to CitePilot.
What you need: Site API token, site ID, and collection ID
Best for: Teams already publishing the main marketing site from Webflow.
Webflow uses shared env vars today rather than per-workspace credentials.
What you need: Site URL, WordPress username, and an Application Password
Best for: Blogs or marketing sites already running on WordPress.
Best first choice if you already have a WordPress blog because setup is straightforward.
What you need: Site URL and a Ghost Admin API key in id:secret format
Best for: Publisher-style blogs already using Ghost as their CMS.
Good fit when the blog is separate from the main app and editorial workflow already lives in Ghost.
What you need: Personal access token and publication ID
Best for: Dev-friendly blogs when you have Hashnode Pro for API access.
Hashnode retired free API access in 2026 — upgrade to Pro (Dashboard → Billing) to publish from CitePilot. Paste your dashboard URL or publication ID.
What you need: Shop domain and an Admin access token with blog/article write access
Best for: Commerce brands publishing content inside a Shopify store blog.
CitePilot will publish into a Shopify blog so content and store live together.
What you need: Project URL, API key, collection ID, and target field IDs
Best for: Teams using Framer CMS collections for site content.
Framer setup is the most technical because you must supply the right collection and field IDs.
