Skip to content
SEOPulser

Visual CMS

Webflow integration

Webflow will not accept a field it does not have. Most of a Webflow integration is agreeing on the Collection schema first, and the rest is understanding that creating an item and publishing it are two different events.

Start publishing to WebflowHow it works

No card · 30 credits on signup

Published to WebflowLive
  • Body, headings and internal links
  • Meta title & description
  • JSON-LD structured data
  • Canonical URL & a named author
  • Featured image with alt text

Every article, formatted for Webflow — nothing to paste.

Connecting Webflow

Live in a few minutes.

  1. Step 1

    Design or audit the target Collection

    Open the Collection you want articles to land in and list its fields and their types.

  2. Step 2

    Add a field for the structured data

    Create a plain text field on the Collection dedicated to the JSON-LD payload, then bind an HTML Embed element on the Collection page template to that field.

  3. Step 3

    Generate an API token with CMS access

    In the site's settings, create an API token scoped to the site you are connecting and to CMS read and write operations.

  4. Step 4

    Connect the project and select the Collection

    In the project's integration settings, choose Webflow and paste the token.

  5. Step 5

    Map each SEOPulser field to a Collection field

    Bind title, slug, body, meta description, featured image, author and tags to their counterparts, and leave anything without a match unmapped rather than forcing it somewhere approximate.

  6. Step 6

    Push one article, then publish and inspect

    Run a single article with the project in draft-first mode so the item is created without going live.

What lands where

Every field maps cleanly.

SEOPulserWebflow
  • Title and slugCollection item name and slug fields
  • Article body (Markdown)Rich Text field
  • Meta descriptionPlain text field bound to the page's meta description
  • Featured image and alt textImage field
  • Author entityReference to an Authors collection, or a plain text field
  • Tags or categoriesMulti-reference field, option field, or plain text
  • Publish stateItem staged in the CMS, then published
  • JSON-LD graphPlain text field rendered through an HTML Embed

Worth knowing first

The honest limitations.

Every destination constrains something. These are the ones worth knowing before you commit a content program to Webflow.

  • The API cannot create or alter Collection fields, so anything you have not built in the designer is unreachable.
  • Rich text fields accept a constrained subset of HTML and normalize what they are given.
  • Creating an item and publishing it are separate events, and the publish step is the one with side effects.
  • Reference and multi-reference fields require the referenced items to exist already.
  • Webflow plans cap the number of CMS items a site can hold, and a long-running publishing program will eventually meet that ceiling.

From content chaos to search results

Without a system

  • Content takes forever, or costs a fortune
  • Generic AI drafts never rank
  • No schema, no author, no canonical
  • Publishing is a manual copy-paste chore
  • Scaling too fast gets you flagged

With SEOPulser

  • Research to publish, fully on autopilot
  • Your answers make every draft original
  • JSON-LD and a named author on each
  • One-click publishing to your CMS
  • Cadence ramped to your site's age

What's different

Built to rank, not just to publish.

Structured data on every article

Article, FAQ, HowTo and Breadcrumb JSON-LD are generated inside the pipeline and stored with the piece, so they travel to whatever you publish to.

Real named authors

Every article is bylined to a named person with a bio and a profile page — not the brand as a schema.org Person, which Google advises against.

Your first-hand experience

Before drafting, you answer a few questions only you can, and the answers go into the piece as material a model could never have inferred.

An MCP server for the loop

Claude, Codex or your own agent reads the calendar, answers questions, queues generation and controls autopilot — over the same API the dashboard uses.

Pace matched to site age

Publishing cadence ramps against when your site was first seen, so a young domain never ships at a volume that reads as scaled content abuse.

Search Console improvements

Connect GSC and it finds near-miss rankings, CTR gaps and thin pages, then rewrites them as accept-or-reject hunks — on posts we didn't write, too.

Pricing

Start free. Pay when it’s working.

Thirty credits on signup — three full articles, published to your own site. No card.

Start freeSee all plans

Professional

Most popular

$69/mo

Billed annually

  • 100 articles a month
  • 3 projects
  • Search Console improvement loop
  • MCP server and REST API keys
  • Article, FAQPage, HowTo and BreadcrumbList JSON-LD on every piece

Questions people actually ask

Do I have to build the Collection myself?

Yes. The API can create and update items inside a Collection but it cannot create fields or change field types, so the schema has to exist in the designer first. At minimum that means a name, a slug, a rich text body, a plain text meta description and an image field, plus a plain text field for the structured data. It is a one-time setup measured in minutes.

Why is my article in the CMS but not on the site?

Because creating an item and publishing it are separate events on Webflow. The item exists in the Collection, but your live domain serves static output that has not been regenerated yet. In draft-first mode this is intentional and the item is waiting for review. If the project is in full auto and the item is still unpublished, check the publish step's result on the article's record.

Can the JSON-LD go in the rich text body?

No, and it is worth being blunt about it. Rich text fields sanitize their input against a limited element set, so a script tag either disappears or renders as visible escaped text on the page. The working approach is a dedicated plain text field holding the payload plus an HTML Embed element on the Collection page template bound to that field.

Will publishing an article push my unpublished design changes?

It can, depending on how the publish is performed, because Webflow regenerates the site from its current staged state. Anything sitting unpublished in the designer is part of that state. If your team works directly in the production site, coordinate before enabling full auto, or keep in-progress design work on a separate staging site until it is ready.

How do tags work if my Collection uses references?

A multi-reference field stores links to items in another Collection, so the tag item has to exist before an article can point at it. We resolve tags against the existing items and do not create new ones, since adding rows to your content model is your decision rather than ours. Option fields behave similarly: values outside the predefined list are rejected.

What happens if I rename or move a field later?

The mapping breaks and writes to that field start failing, usually with a clear error rather than a silent skip. Re-open the integration settings, let the field list refresh, and rebind. It is a small job, but it is worth doing immediately, because an unattended project will otherwise keep generating articles that cannot be delivered.

Other destinations

Connect in minutes

Publish to Webflow without touching a draft.

Connect once, confirm the brief, and articles arrive on your Webflow site with structured data and a real author attached. Keep the review gate on until you trust it.

Start freeSee the pipeline

3

Free articles on signup

  • No credit card
  • Published to your own site
  • JSON-LD and a named author
  • Cancel anytime