Skip to Content
SettingsConnectionsWebflow

Webflow Integration

Connect your Webflow account to publish content generated in Asky directly to your Webflow CMS collections.

What You Get

Connecting Webflow enables:

FeatureDescription
Content PublishingPublish articles and posts to Webflow CMS
Collection MappingMap Asky content to Webflow collection fields
Status TrackingMonitor publishing status in Asky
Site SelectionChoose which Webflow site to publish to

Prerequisites

Before connecting, ensure you have:

  • A Webflow account
  • At least one site with CMS capability (not on free plan)
  • A CMS collection set up for blog posts or articles
  • Editor or Admin access to the site
  • (Recommended) A plain-text field named Asky Schema on your target collection. See Schema.org Structured Data Setup below.

Webflow’s free plan doesn’t include CMS. You’ll need a CMS Site Plan or higher to use this integration.

Connecting Webflow

Go to Settings → Connections in Asky.

Find Webflow

Locate the Webflow card.

Click Connect

Click the Connect button.

Authorize with Webflow

You’ll be redirected to Webflow:

  1. Sign in to your Webflow account (if not already)
  2. Review the permissions requested
  3. Click Authorize

Select Your Site

If you have multiple Webflow sites:

  1. You’ll see a list of available sites
  2. Select the site you want to publish to
  3. Click Confirm

Choose Your Collection

Select the CMS collection where content will be published:

  1. You’ll see available collections
  2. Choose the appropriate collection (e.g., “Blog Posts”, “Articles”)
  3. Map Asky fields to collection fields (if needed)

Complete Setup

You’ll be redirected back to Asky with Webflow connected.

Schema.org Structured Data Setup

Asky generates JSON-LD structured data for every draft and sends it to a CMS field called asky-schema on publish. For this schema to actually render as a <script type="application/ld+json"> tag on your live page, Webflow needs two things: a plain-text field to store the JSON, and an Embed element on the Collection Template that reads that field.

This is a one-time setup per collection. After completing it, every future publish from Asky automatically includes structured data on the live page.

Structured data helps AI search engines (ChatGPT, Perplexity, Gemini, Claude) understand and cite your page correctly, Asky ensures your articles are optimally prepared. Without this setup, content publishing still works, but your pages render no JSON-LD and miss the added AEO benefit.

Open your collection’s settings

  1. In the Webflow Designer, open the CMS panel (database icon in the left sidebar)
  2. Click the collection that holds your blog posts or articles (the same collection you selected when connecting Asky)
  3. Click the Settings gear to edit the collection structure

Webflow CMS panel with the collection settings gear highlighted

Add a Plain Text (multi-line) field

  1. Click Add Field
  2. Select field type: Plain Text
  3. Select Multiple line
  4. Field label: Asky Schema (Webflow will auto-generate the slug asky-schema)
  5. Leave Required off. If a draft has no schema, the publish still succeeds.
  6. Click Save Field

Webflow "Add Field" dialog with Plain Text (multi-line) selected and label "Asky Schema" Webflow field settings showing the auto-generated slug asky-schema

The slug must be exactly asky-schema. Webflow generates the slug automatically from the label “Asky Schema”, so typing the label that way gives you the right slug. Before continuing, open the field’s settings and double-check that the slug reads asky-schema.

Open the Collection Template page

  1. In the Designer, open the Pages panel (left sidebar)
  2. Under CMS Collection Pages, open the template for your collection (for example Blog Post Template)

Webflow Pages panel with the Collection Template highlighted

Add an Embed element

  1. Click “Add Elements” in the top left of the page
  2. Drag a Code Embed (HTML Embed) element into the template. Placement doesn’t affect rendering, so anywhere inside the body is fine.
  3. The HTML editor opens automatically.

Webflow Designer with the Embed element being dragged onto the Collection Template

Paste the embed wrapper

Paste exactly this into the Embed editor:

<script type="application/ld+json">
</script>

Then place your cursor on the empty line between the opening and closing <script> tags.

Bind the Asky Schema field

  1. With your cursor between the tags, click + Add Field in the Embed editor toolbar
  2. Select the Asky Schema field from the dropdown
  3. Webflow inserts a placeholder that pulls in each article’s schema automatically when the page loads.
  4. Click Save & Close

"Add Field" dropdown showing "Asky Schema" being selected, with the resulting placeholder inserted between the script tags

(Optional) Add conditional visibility

  1. With the Embed still selected, open the Element Settings panel (right sidebar)
  2. Under Conditional Visibility, add a condition: Asky Schema → is set
  3. This hides the Embed entirely on pages where the schema field is empty, preventing an empty <script> tag from rendering.

This is not required and will not punish visibility if set.

Conditional Visibility panel configured with "Asky Schema" "is set

Publish your Webflow site

  1. Click Publish in the top-right of the Designer
  2. Publish to your staging subdomain and/or your live domain
  3. This step makes both the new CMS field and the Embed live on the site

Verify it’s working

  1. Publish any content draft from Asky to this collection
  2. Open the published article’s live URL in a browser
  3. View the page source (Ctrl/Cmd + U) and search for application/ld+json
  4. You should see a populated <script type="application/ld+json"> block containing the article’s JSON-LD

Paste the live URL into Google’s Rich Results Test  to confirm the schema parses cleanly and Google recognizes the types.

Troubleshooting

The <script> tag doesn’t appear on the live page:

  1. Open the field settings in Webflow and confirm the slug reads exactly asky-schema
  2. Re-publish your Webflow site after adding the field and the Embed. CMS fields and template changes only go live on publish.
  3. Publish a fresh draft from Asky to this collection, then reload the live page.

The <script> tag is there but empty:

  1. The draft you published didn’t have schema attached. Open the draft in Asky and review the Schema.org preview before publishing again.
  2. If you added conditional visibility, the empty tag is hidden automatically. No action needed.

Articles published before this setup don’t have schema:

  1. Complete the setup, then republish those drafts from the Content Library. New publishes include structured data automatically.

Publishing Content

From Content Library

To publish content to Webflow:

Select Content

  1. Go to Content Library in the sidebar
  2. Click on the content you want to publish

Verify Content Status

Ensure content is in “Ready” status. Edit if needed.

Click Publish

Click the Publish button.

Select Destination

Choose Webflow as the destination.

Configure Options

Set publishing options:

  • Collection: Which collection to add to
  • Status: Draft or Published
  • Slug: URL slug for the item
  • Additional fields: Map any custom fields

Confirm and Publish

Click Publish to send content to Webflow.

Tracking Status

After publishing:

  • Content status changes to “Publishing”
  • Status updates to “Published” when complete
  • Any errors are displayed with details

Viewing on Webflow

Published content appears in your Webflow CMS:

  1. Log in to Webflow
  2. Go to your site’s CMS
  3. Find the content in the selected collection

Remember to publish your Webflow site after adding new CMS items to make them live.

Field Mapping

Default Mapping

Asky maps content fields to standard Webflow collection fields:

Asky FieldWebflow Field
TitleName
BodyRich Text / Post Body
SlugSlug
SummaryExcerpt / Summary
Schema.org JSON-LDasky-schema (plain text, multi-line)

Custom Fields

If your collection has custom fields:

  1. Configure mapping in connection settings
  2. Map Asky fields to your custom fields
  3. Save mapping configuration

Required Fields

Ensure your collection has required fields mapped:

  • Name (title) is always required
  • Slug is auto-generated if not provided

Managing the Connection

Viewing Status

The connection card shows:

  • Connection status
  • Connected Webflow account
  • Selected site and collection
  • Last publish time

Switching Sites

To publish to a different site:

  1. Go to Settings → Connections
  2. Find Webflow
  3. Click Change Site
  4. Select new site and collection

Switching Collections

To use a different collection:

  1. Access Webflow connection settings
  2. Update collection selection
  3. Re-map fields if needed

Disconnecting

To disconnect Webflow:

  1. Go to Settings → Connections
  2. Find Webflow
  3. Click Disconnect
  4. Confirm

Disconnecting:

  • Stops ability to publish new content
  • Does not delete content already in Webflow
  • Can be reconnected anytime

Revoking Access

You can also revoke access from Webflow:

  1. Log in to Webflow
  2. Go to Account Settings → Integrations
  3. Find Asky and click Revoke Access

Troubleshooting

Connection Failed

“Authorization Failed”:

  1. Verify you’re logging into the correct Webflow account
  2. Check you have Editor or Admin access
  3. Try disconnecting and reconnecting

“No Sites Found”:

  1. Verify you have at least one site in Webflow
  2. Check that you have access to the site
  3. Ensure the site has CMS enabled

Publishing Fails

“Collection Not Found”:

  1. Verify collection still exists in Webflow
  2. Check collection hasn’t been renamed
  3. Reconnect and re-select collection

“Field Mapping Error”:

  1. Check required fields are mapped
  2. Verify field types match
  3. Update field mapping in settings

“Rate Limited”:

  1. Wait a few minutes and retry
  2. Avoid publishing many items rapidly
  3. Contact support if persistent

Content Issues

“Content Appears in CMS but Not Live”:

  1. Publish your Webflow site after adding CMS items
  2. CMS items need site publish to go live

“Formatting Lost”:

  1. Check Webflow collection field type (use Rich Text)
  2. Some complex formatting may need adjustment
  3. Review content in Webflow editor

Token Expired

If connection shows “Expired”:

  1. Click Reconnect
  2. Re-authorize with Webflow
  3. Re-select site and collection if prompted

Security & Privacy

Permissions Requested

Asky requests:

  • Read site list
  • Read CMS collections
  • Write to CMS collections

We do not access:

  • Your Webflow account settings
  • Billing information
  • Site code or design
  • Assets beyond what we publish

Data Flow

  • Content flows one direction: Asky → Webflow
  • We don’t import Webflow content
  • Published content exists independently in Webflow

Best Practices

  1. Test with draft: Publish as draft first to verify formatting
  2. Use appropriate collection: Match content type to collection
  3. Review in Webflow: Check published items before making live
  4. Map custom fields: Utilize Webflow’s custom fields for rich content
  5. Regular checks: Verify connection status periodically

Limitations

AspectLimitation
Content typesText and basic formatting
ImagesNot automatically uploaded (manual add in Webflow)
ReferencesCollection references not auto-linked
Bulk publishOne item at a time

Next Steps

  • Connect WordPress for additional publishing
Last updated on
WordPressBing Webmaster