Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.siftly.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Why integrate your CMS?

Siftly generates GEO-optimized content — but that content only works when it’s published. CMS integrations close the gap between analysis and execution, letting you push content from Siftly directly to your website without copying, pasting, or switching tabs.
Supported CMS platforms — WordPress, Ghost, Webflow, Strapi, Sanity, and Framer

​
Supported platforms

WordPress

Publish posts directly to your WordPress.com blog using secure OAuth2. No API keys required.

Ghost

Publish posts live to your Ghost blog instantly using the Ghost Admin API with JWT auth.

Webflow

Create CMS items in any Webflow collection via the Webflow Data API v2.

Strapi

Push content into Strapi 5 collections via the REST API with full Draft & Publish support.

Sanity

Create and update documents in Sanity Studio with structured content and rich text blocks.

Wix

Publish articles directly to Wix blog and pages via Wix’s Headless CMS API.

Framer

Push pages and blog posts to Framer sites with full CMS collection support.

Duda

Publish blog posts to Duda websites via Make.com webhook automation.

​
Platform comparison

PlatformDifficultyImage UploadJSON-LD SupportMeta FieldsSiftly Push MethodGuide
WordPress✅ Easy✅ Media libraryVia Yoast/Rank Math plugin or Custom HTML blockVia SEO plugin fieldsREST API + Application Passwords / OAuthGuide →
Ghost✅ Easy✅ Media libraryAuto-generated Article; Siftly pushes supplemental schema to codeinjection_headBuilt-in meta_title, custom_excerptAdmin API + JWTGuide →
Webflow⚠️ Medium✅ Assets CDNManual Embed element with {{wf ...}} syntaxCMS field bindings in Page SettingsData API v2 + tokenGuide →
Strapi⚠️ Medium✅ Media libraryStored in schema; frontend renders@strapi/plugin-seo component or custom fieldsREST API + tokenGuide →
Sanity❌ Developer✅ Assets APIStored in schema; frontend rendersCustom seo object type; frontend rendersContent Lake API + tokenGuide →
Wix✅ Easy✅ Media (URL import)SEO → Advanced (paid plan only)Built-in SEO panel per postContent Manager API + keyGuide →
Framer⚠️ Medium❌ No upload APIStatic in Head code; dynamic requires code component (JS)CMS field bound to page SEO settingsCMS API + tokenGuide →
Duda✅ Easy❌ No upload APINot supported via automationDescription field onlyMake.com webhookGuide →
Not sure which CMS to use? Read our guide to choosing a CMS for AI visibility — it compares platforms through the lens of GEO optimization.

​
How integrations work

All CMS integrations follow the same basic flow:
1

Enter credentials

In Siftly’s Settings -> Integrations, provide your CMS credentials (API key, token, project ID). Siftly validates the connection and discovers available collections.
2

Select collection and map fields

Choose which collection or document type to publish to (shown as a dropdown of discovered types). Siftly discovers all fields — including nested ones — and suggests mappings via AI. Edit or add custom fields as needed.
3

Publish from the content editor

In the Siftly content editor, click Publish -> [Your CMS] and choose whether to publish live or save as a draft. Fields with “Use Existing” sources are auto-filled.
4

Review in your CMS

Depending on your chosen status, content either goes live immediately or lands as a draft in your CMS for review.

​
Unified Field Mapping

Every CMS integration (except Wix, which uses fixed API fields) shares the same 3-tier field mapping system. This gives you a consistent experience regardless of which CMS you use.

​
Tier 1 — Required Fields

These three fields must be mapped during setup. They define where Siftly writes the core content.
Siftly FieldDescription
TitleThe article or page title
SlugURL-friendly identifier
BodyFull HTML or rich-text content

​
Tier 2 — Optional Fields

Optional fields are auto-populated from your content data when mapped. Leave any field unmapped to skip it.
Siftly FieldDescription
Meta TitleSEO page title
Meta DescriptionSEO description / excerpt
KeywordsList of target keywords
CategoriesContent categories
JSON-LDStructured data markup (with text/json type toggle)
Word CountTotal word count of the content
Hero ImageFeatured/banner image

​
Tier 3 — Custom Fields

Add any extra fields your CMS schema requires that aren’t part of Siftly’s standard content model. Custom fields support five types:
TypeDescription
StringPlain text value
NumberNumeric value
BooleanTrue or false
JSONStructured object or array
SelectPick from a predefined list of options
Each custom field can have a default value that pre-fills at publish time, or it can be linked to an existing content source using Use Existing Field — so you can reuse the same data in multiple CMS fields without entering it twice. Available sources: Title, Slug, Meta Title, Meta Description, Excerpt, Keywords, Categories, JSON-LD, Word Count, Hero Image, Date Published, Date Modified. Custom fields are editable after creation — click the pencil icon to change any field’s configuration.
For example, if your CMS has a nested seo.metaDescription field AND a top-level excerpt field that should both contain the same text, map one as the optional Meta Description field and add the other as a custom field with source linked to Meta Description.

​
Draft vs Published

When publishing to any CMS, you can choose between:
  • Draft — content is pushed to your CMS as a draft for review before going live
  • Published — content goes live immediately
This toggle appears in the publish dialog for every CMS integration.
Some CMS platforms (like Wix) always create content as drafts regardless of the status you select. Check the individual CMS integration page for platform-specific behavior.