Skip to content

SEO by platform

Publish where your site already lives

The pipeline is the same everywhere: plan on the calendar, write against the content score, link to real crawled pages, and verify every publish by fetching the public URL. What differs is the door into your platform, and each page below states how that door works, the three-step connect, and what the connector will not do.

13 platforms, one honest template

Counted from the registry these pages render from. Beta connectors are labeled beta on their own page, and a platform with no write API gets its real path documented instead of a pretend connector.

  • WordPress

    Two connectors, one pipeline. Publish with an application password, or install the plugin and paste one Integration Key. Either way the article arrives with its images uploaded into your own media library, and the publish is confirmed by fetching the public URL.

  • WordPress.com

    Sites hosted on wordpress.com cannot use the self-hosted WordPress connectors: /wp-json/ is not reachable there, and plans below Business cannot install plugins. This connection exists for exactly those sites, and you connect it with your WordPress.com account rather than a pasted credential.

  • Ghost

    Articles arrive in your Ghost site through Ghost's Admin API, with content, images and metadata ready to review in Ghost's editor. New connections publish as drafts, so nothing goes live until someone presses publish in Ghost.

  • Webflow

    Articles land as items in the CMS collection you point the connection at, your Webflow templates render them like any other item, and new connections create draft items that wait in Webflow for your publish action.

  • Shopify

    Articles publish into your store's own blog through Shopify's Admin API, where content builds authority next to the collections and products it links to. New connections publish as drafts until you switch them live.

  • BigCommerce

    Articles publish into the store's built-in blog through the BigCommerce API, with a store-level API account token and your store hash. Posts start as drafts in your control panel until you publish them or switch the connection live.

  • Wix

    Wix stores posts in Ricos, its own structured editor format, rather than HTML. So each article is converted, headings, lists, links and images, into that format before publishing, and posts open cleanly in the Wix editor as if written there.

  • GoHighLevel

    Agencies running client sites on GoHighLevel get the same pipeline as WordPress users: calendar articles flow to the client's blog inside the location, as drafts by default until the connection is switched live.

  • Duda (beta)

    Articles arrive in your Duda site's blog through the Duda Partner API, with body, description and hero image, as drafts you can open in Duda's blog editor. Duda's own import rule helps here: an imported post always lands unpublished, and going live is a separate call we make only when the connection says so.

  • Snapps

    Articles land in the Snapps blog with their structure and images mapped to Snapps' blog fields, as drafts by default until you switch the connection to publish live.

  • GitHub

    Articles commit as markdown files into the repository and path you choose, and your deploy turns each commit into a page. Built for Next.js, Astro, Hugo, Jekyll and any headless setup where a committed file becomes a page on the next build.

  • Next.js

    Two paths for a Next.js site. The blog package scaffolds list, article, tag and sitemap routes and fills them from the articles your project publishes, with nothing to host on your side. Or commit markdown into your existing content folder through the GitHub connection and leave your rendering alone.

  • Framer

    Framer does not expose a public API that lets an outside service create CMS items on any site, so there is no direct connector to pretend with. What Framer does offer is two doors we already serve: it imports a CMS collection from an RSS feed, and its official Zapier and Make integrations create CMS items from a webhook.

On something else?

Two universal paths cover platforms with no connector of their own.

A keyed RSS feed serves any builder with an RSS import, and the signed webhook hands each article as JSON to an endpoint or automation you run. Both are documented in the help centre, and the free CMS detector tells you what a site runs on in seconds.

SEO by platform

See it on your own site

A free audit grades your site A+ to F, then the calendar, the writer and your platform's connection do the week's work. No card required.