Generate SEO blog posts from keywords and publish to Webflow

See What's Earning in AI Automation Freelancing.
DigiNo helps new AI automation freelancers earn faster by tracking what clients actually pay for.

Niche site owners and affiliate marketers need a constant stream of keyword-targeted content but hate the manual grind of writing, formatting, and uploading it. This AI automation handles the entire pipeline from keyword list to published Webflow draft, giving you a productised service you can sell repeatedly.

What This Automation Does

Reads a structured keyword list from Google Sheets and processes each keyword through an AI writing agent that produces 600-plus word SEO-optimised articles
Calls a separate image-generation sub-workflow using Gemini to create a relevant featured image for every article automatically
Validates each article against a minimum word count and expands any thin content before converting markdown to Webflow-ready HTML
Logs every success and every error back to Google Sheets so you and your client have a clear record of what was published and what needs attention

Tools Used

n8n
OpenAI
Google Sheets
Webflow

Where to Get Hired for This Skill

On Contra, top freelancers across this stack have earned 171 combined verified reviews from real client projects.

Source: Contra freelancer search · refreshed 30 May 2026

Start Earning as a Freelancer on Contra

Contra is a commission-free professional network for independents. Browse live AI automation work and keep what you earn.

Join Contra Free →

How To Build It

Load keywords from Google Sheets

Connect a Google Sheets source containing two columns, main keyword and URL slug, so the workflow pulls each row as a discrete job and processes them in controlled batches rather than all at once.

Generate full articles with an AI agent

Wire OpenAI into an agent configured with SEO writing instructions so it produces a structured, 600-plus word article for each keyword, following heading hierarchy and natural keyword placement without keyword stuffing.

Trigger the image generation sub-workflow

Build a separate image-generation workflow powered by Gemini and attach it as a callable tool inside the agent, so the main workflow requests a contextually relevant featured image for each article without running image logic inline.

Validate word count and convert to HTML

Add a conditional check after each article is written that measures word count, re-prompts the agent to expand content if it falls short, then converts the final markdown output to clean HTML formatted for Webflow's rich text field.

Publish drafts and log results to Sheets

Push the completed HTML and featured image to Webflow as a draft CMS item, then write the outcome back to a second Google Sheets tab recording the slug, publish status, and any errors so nothing falls through the cracks.

Pitfalls

OpenAI rate limits hit hard when processing large keyword batches back-to-back: build in a wait step between batches or your workflow will start throwing 429 errors mid-run and leave half the sheet unprocessed.
The image sub-workflow must be created and saved as a standalone workflow before it can be selected as an agent tool. Trying to embed its logic inside the main workflow breaks the tool-calling architecture and the agent will silently skip image generation.
Webflow CMS field names are case-sensitive and must match your collection schema exactly. A mismatch between the HTML field your workflow sends and the field slug in Webflow causes silent publish failures that only show up in your error log sheet, not as an obvious error.

FAQ

Can I build this without coding?

Almost entirely, yes. The workflow uses a small code block for the markdown-to-HTML conversion, but it is copy-paste logic that does not require you to write anything from scratch. Every other step is configured through visual settings and API credentials.

How long does it take to build?

Expect four to six hours for a first build including setting up both the main workflow and the image sub-workflow, testing the Webflow field mapping, and verifying the Google Sheets logging. Repeat builds for new clients go faster once you have a template.

What can I charge for this as a service?

Pricing is yours to set based on volume, niche, and client budget. Common positioning is a monthly retainer for ongoing content production or a per-article fee for one-off bulk orders, with setup billed separately.

Which tools are required versus optional?

OpenAI and Google Sheets are required as the content engine and data layer. Webflow is required as the publishing destination for this specific build. OpenRouter is listed as an alternative API gateway if you want to swap models, and Gemini for image generation can be replaced with another image API if you prefer a different provider.

This is original DigiNo analysis. The underlying automation pattern is a community workflow template – view the original on n8n.