Preview
What it is.
Ours, and we sell the service it runs inside. It takes a finished article and pushes it into the client's CMS with the headings and links intact, and it is at version 2 because the first one lost formatting on the way through.
It closes the last manual step in a content chain. Copy-pasting a formatted article into a CMS is where headings collapse and links break, and someone reformats by hand for half an hour.
What you get.
- A finished article pushed into the CMS with no copy-paste step
- Formatting preserved through the transfer
- The last manual step of a content chain closed
- A repeatable publish, so two articles arrive identically structured
How to set it up.
Build it last. Publishing only pays off once the drafting, checking and linking steps upstream are reliable.
Map your CMS fields explicitly before you build, since a field mismatch is what breaks a publish silently.
Preserve headings and links through the transfer instead of sending plain text. Ours is at v2 because that is where the first version failed.
Push as a draft in the CMS and not as a live page, so a human reviews before it publishes.
Test with your longest and most heavily formatted article, since the transfer breaks on those first.
For an installable route, the Webflow MCP connectors and CMS-focused skill sets on GitHub cover this job publicly.
Pricing Plans
Not sold as a skill.
It runs inside client engagements. The published account dates from April 2026.
Use cases
Closing the copy-paste step
Every article ends with someone reformatting headings in the CMS. Hand the finished draft to the publish step and it arrives with headings and links intact, and the reformatting session drops out of the process.
Stress test before volume
You're about to publish at volume. Push your longest, most heavily formatted article through first, since the transfer breaks on those before it breaks on anything else.
Mapping fields before building
The CMS has custom fields every article must fill. Map each field explicitly up front, because a mismatch is what breaks a publish silently.
Publishing behind a review
Nothing should go live unseen. The push lands as a CMS draft, so an editor reads the page in place before it publishes.
Best for
A content chain that ends in copy-paste
Everything upstream can be automated and the final step still eats twenty minutes per article.
Formatting that breaks on publish
Field mapping and preserved structure is the whole job, and it is why this reached v2.
Publishing at volume
Two articles arriving with identical structure matters more as the count goes up.