Publish reviewed articles to Webflow CMS
Connect a Webflow CMS collection, map article fields, save reviewed CMS drafts or confirm item publication, and check the public page.
On this page
Connection and account access
Reviewed article publishing is available on current Starter, Growth, Pro plans. Effective trial, legacy and custom access can differ; check current plans and your account’s limits.
Configured CMS collection, credentials and field mapping. Publishes the supported CMS item; does not establish whole-site editing or publishing.
This guide is public. Sign in to connect Webflow in PB; credentials, workspace articles and publishing controls stay inside your account.
What PB sends to Webflow
Prerender Buddy delivers a reviewed article to the Webflow CMS collection you select. It can save a staged CMS draft or publish the supported item after explicit confirmation.
The connection maps the title and slug, article body, optional excerpt and configured default values. It does not edit the site's design or publish unrelated site changes.
Prepare the collection and token
Use a dedicated Webflow site API token with Sites read and CMS read/write access for the intended site. Review Webflow's site-token instructions and scope reference.
The collection needs an editable rich-text field for the article body. An optional excerpt must use a separate editable plain-text field. Other required collection fields need suitable default values before the connection can be saved.
For author or category reference fields, use existing collection items. PB does not create a new author or infer the complete structure of your collection.
Connect and map fields in PB
- Open your website in PB Sites, open Publishing and select Webflow.
- Enter the dedicated site API token.
- Choose Load Webflow sites and fields, then select the intended site and article collection.
- Map the article body and optional excerpt. Supply defaults for any additional required fields.
- Choose Save destination and Check connection.
Keep the token in the authenticated connection form. Saving this destination replaces another active publishing destination for the same PB website.
Review and deliver the article
Start with a full article from Article Generation, or open an existing PB draft. Review the title, text, claims and links, then approve the article version.
Sending a draft saves the CMS item for review without making the publication call. Confirmed publication saves the item and requests publication of that item.
PB uses a stable article identifier in the generated slug to associate subsequent deliveries with the same item. Check the resulting slug and collection template before relying on the public URL.
Distinguish saved from published
Webflow can save the item successfully while the publication step fails. In that case, inspect the staged item and PB's delivery message before retrying. The draft may already exist.
Check the chosen collection's public template and the final page. Item publication does not establish that unrelated design changes have been published or that every field is displayed by the template.
PB's publication schedule is separate from editorial planning dates. A schedule must be explicitly confirmed for an approved article and its configured destination.
Diagnose mapping or access failures
A rejected body mapping usually requires checking that the selected field is editable rich text. Check missing required fields and valid reference values when Webflow rejects other field values.
For authentication or permission failures, verify that the token still has access to this exact site and the required scopes. Changing the collection means reviewing its mapping again.
Disconnecting PB does not remove existing CMS items. Revoke the dedicated Webflow token separately when needed.
Verify and monitor the result
After confirmed publication, open the final public URL without signing in. Check the expected article, title, links and canonical URL. A saved CMS draft is not public, and a connection check does not prove that an article is live.
Use Health and Monitoring to inspect the published response. Connect rendering only if checks establish a missing or incomplete crawler-readable response. CMS publishing does not require a DNS change by itself.
Revisit the relevant AI Visibility questions under comparable collection settings. Later mentions or citations do not establish that an article caused the change, and publication does not guarantee indexing or AI recommendations.
Read the article and publication workflow or how PB connects the steps. Compare other destinations in Integrations.