Topic decisions are guesswork
Keyword demand, search intent, and business fit are scattered across tabs, so the next article is chosen by opinion instead of evidence.
Webflow + AymarTech
Publish AI-generated blog articles to your live Webflow CMS collection automatically or after approval, with mapped title, slug, rich text, summary, and cover image fields.
The Webflow integration connects through Webflow OAuth, lets you choose a site and CMS Collection, and publishes CMS items automatically or after approval.
Problems
Why SEO publishing keeps getting stuck
Most teams do not fail because they lack ideas. They fail because every article has too many tiny manual decisions before it can go live.
Every article turns into an ops checklist
Briefs, drafts, images, metadata, internal links, and QA bounce between tools until the process becomes slow and inconsistent.
Publishing stalls at the last mile
Finished drafts wait on slugs, formatting, platform fields, and someone with enough time to push everything live.
What you get
From real search demand to index-ready articles
Keywords people already search for
AymarTech finds search queries with real demand, clear intent, and a realistic chance to bring qualified traffic.
Deep research from many sources
Each article is built from broad source research, so the draft covers the topic with substance instead of generic filler.
Google-friendly publishing
Clean structure, metadata, slugs, internal links, and direct publishing help Google discover and index new articles faster.
Content workflow
From keyword to finished article
01
Find demand
AymarTech identifies low-competition topics your customers are already searching for.
02
Write and optimize
The article is written, fact-checked, formatted, enriched with images, and prepared with SEO details.
03
Approve or publish in Webflow
AymarTech prepares the finished article in Webflow with content, image, slug, metadata, and internal links, then publishes automatically or waits for your approval.
Who this is for
Use this when your Webflow site already has a CMS-powered blog or when you can create a blog Collection and Collection Page before publishing, with either auto-publish or approval before CMS items go live.
Fields and payload
| AymarTech field | Destination field | Notes |
|---|---|---|
| title | name or required PlainText field | AymarTech maps title to the name field when present, otherwise to the required plain text title field. |
| slug | slug | Used when the Collection exposes a slug field. |
| htmlContent | first RichText field | The article body is mapped to the first Rich Text field in the Collection. |
| imageUrl | Image field matching main image / cover / thumbnail / featured | AymarTech looks for common cover image field names and sends the image URL. |
| metaDescription | PlainText field matching summary / excerpt / description / intro | Summary text is truncated to the Webflow field max length when needed. |
| selected site | siteId | Chosen after OAuth from the list of authorized Webflow sites. |
| selected collection | collectionId | Saved as the publish target for live CMS item creation. |
How to connect in the dashboard
All connection forms, OAuth buttons, target pickers, publish-mode settings, and test actions are inside the AymarTech dashboard. Choose automatic publishing or require confirmation before go-live.
Open dashboard integrations →- Open Integrations in AymarTech and choose Webflow.
- Click Connect Webflow, sign in, and approve access for the intended workspace and site.
- Make sure the Webflow site has a blog CMS Collection with a title/name field, slug, Rich Text body, and image field.
- Make sure the live Webflow site has a Collection List or Collection Page that renders that Collection.
- Return to AymarTech and select the exact Webflow site and CMS Collection.
- Run the Webflow test connection, then auto-publish or approve an article; AymarTech creates a live CMS item according to your publish mode.
How article publishing or delivery works
- AymarTech requests Webflow scopes for sites:read, cms:read, and cms:write.
- The OAuth token is stored encrypted and used to list authorized sites and Collections.
- AymarTech reads the selected Collection schema and maps fields by type and common slug patterns.
- When auto-publish is enabled or you approve an article, publishing uses Webflow's live CMS endpoint and creates published CMS items.
- Validation errors usually come from required fields or Collection schema requirements in Webflow.
Troubleshooting
- No site listed: reconnect Webflow and approve access to the intended site.
- No Collection listed: create or publish a Webflow CMS Collection for blog posts.
- Body missing: confirm the Collection has a Rich Text field.
- Image missing: add an Image field with a slug like main-image, cover, thumbnail, or featured-image.
- Item publishes but is not visible: publish the Webflow site and confirm the Collection List/Page is connected to the chosen Collection.
Frequently asked
Does AymarTech automate the Webflow Designer?
No. It publishes CMS items through the Webflow API. Your Webflow pages must already render the chosen Collection.
Can Webflow publishing wait for approval?
Yes. You can require confirmation first, or let AymarTech create published Webflow CMS items automatically.
Can AymarTech choose custom Webflow fields?
It automatically maps common blog fields by type and slug. Collection requirements should be kept compatible with the article fields AymarTech sends.
Where do I pick the Collection?
After OAuth, the dashboard target picker lists authorized Webflow sites and Collections.
Why does my live site not show the post?
The CMS item can be created successfully while the Webflow page template or Collection List still needs to be published or connected.
Related
Control SEO publishing
Start free, connect Webflow, and choose auto-publish or approval before optimized articles go live.