CitePilot

Help

CMS publishing guide

Connect a CMS only if you already have a real website where your CitePilot articles should go live. If you do not have one yet, skip this step and keep generating content inside the dashboard.

Do I need a CMS to use CitePilot?

No. CMS publishing is optional. You can still run audits, track citation history, generate content, and use alerts without connecting anything.

Which plan includes CMS publish?

Pilot and Fleet include publishing to connected CMS providers. Free tier covers audits and dashboard access — upgrade when you want ongoing monitoring and publish.

What if I do not have WordPress, Ghost, Shopify, Framer, or Webflow?

Skip CMS setup for now. Keep creating drafts inside CitePilot until you or a client already has a real destination site.

When should I connect a CMS?

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.

How publishing works

  1. Step 1

    Generate an article in CitePilot from the Content dashboard.

  2. Step 2

    Connect the CMS for the specific workspace if that workspace already has a site.

  3. Step 3

    Publish the article from the queue to create the first remote item.

  4. Step 4

    Publish the same article again later to update the existing remote item instead of duplicating it.

Which provider should I use?

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.

Webflow

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.

WordPress

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.

Ghost

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.

Shopify

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.

Framer

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.