How to Use Webflow MCP and Claude to Write Blog Posts That Rank

If you manage a Webflow site and you're trying to produce content consistently, this workflow will save you a lot of time. I've been using a combination of the Webflow MCP and Claude to go from keyword research to a published CMS draft without switching tools, and the results have been genuinely useful.

This guide walks through the full process, including things most people don't think about until they've already made the mistakes.

What is the Webflow MCP?

MCP stands for Model Context Protocol. It's a connection layer that lets AI tools like Claude interact directly with external platforms, including Webflow.

In practice, it means Claude can:

• Read your existing CMS collections and items
• Create new resource or blog posts as drafts
• Populate fields including title, body, slug and meta data
• Save directly to Webflow without you copying and pasting anything

To set it up, go to Settings in Claude.ai, find Integrations, and connect your Webflow account. Once it's connected, Claude has read and write access to your site.

I use it alongside a dedicated Claude Project so my preferences and tone of voice are always loaded before I start writing.

Step 1: Start with keyword research, not a topic idea

The most common mistake I see with AI content is starting with a vague topic and hoping it ranks. It won't. You need to know what people are actually searching for before you write a word.

Here's what I do:

1. Open Google Search Console and look at queries that are already getting impressions but low clicks. These are quick wins.
2. Type your broad topic into Google and look at the autocomplete suggestions. These tell you what people are actually asking.
3. Scroll to the "People also ask" section and note down the questions. These become natural H2 or H3 headings.
4. If you have access to Ahrefs or Semrush, check search volume and keyword difficulty before committing.

What you're looking for is a keyword with genuine search intent behind it. "Webflow CMS tips" is too broad. "How to structure a Webflow CMS for a blog" is specific, searchable and answerable.

Once you have your primary keyword, pick two or three related terms that fit naturally. These go into your brief.

Step 2: Write a brief before you prompt Claude

Prompting Claude without a brief is like briefing a designer with "make it look good." You'll get something, but it probably won't be right.

A good brief covers:

• Your primary keyword and what someone searching for it actually wants to find
• Your target audience and how much they already know about the topic
• The angle you want to take (how-to, comparison, common mistakes, opinion)
• Any specific points, tools or examples you want included
• Words or phrases to avoid

I keep a notes document with my standard brief template so I can fill it in quickly rather than starting from scratch each time.

Step 3: Ask Claude for an outline first

I never ask Claude to write a full post in one go. I always ask for the outline first.

A prompt I use regularly:

"I'm writing a resource article for my Webflow freelance site targeting the keyword [keyword]. My audience is [describe them]. Give me an outline with H2 headings, a rough word count per section, and a note on what each section should cover."

Once I have the outline, I review it before anything gets written. This is where I:

• Reorder sections that don't flow logically
• Cut headings that don't match the search intent
• Add sections I know from experience are missing
• Check that the structure would satisfy someone who actually typed that keyword into Google

Getting the structure right first saves significantly more time than fixing a badly structured draft.

Step 4: Prompt for the full draft with clear instructions

With the outline approved, I prompt for the content. The more specific you are here, the better the output.

A prompt I use:

"Using this outline, write the full article. Keep paragraphs short. Use bullet points and numbered lists where they make the content easier to scan. Write in first person as a Webflow freelancer sharing experience from real projects. Use British English. Do not use em dashes. Do not use the words 'comprehensive', 'leverage', 'delve' or 'it's worth noting'."

The instruction to write in first person from real experience is important. It signals to Claude that this should read like genuine expertise, not a generic how-to guide. That matters for Google's helpful content guidelines, which reward content written with firsthand experience.

I also always add:

"At the end, provide a suggested meta title (max 60 characters, include the keyword) and a meta description (max 155 characters, conversational, no clickbait)."

Step 5: Create a Claude Skill to save your preferences

This is the thing most people don't know about yet.

Claude supports custom skills, which are saved sets of instructions that load automatically every time you start a conversation inside a Project. Think of it as a standing brief that's always there.

For content writing, a skill can include:

• Your tone of voice and writing style rules
• Words and phrases to always avoid
• Your standard post structure (intro, numbered steps, tips, summary)
• Notes on your audience and what they care about
• Instructions on how to format meta descriptions

‍

To create a skill, you need to be using Claude Projects (available on paid plans). Inside a Project, go to the instructions section and write your skill there.

My own content writing skill includes instructions like:

• Write short paragraphs, no more than three sentences each
• Use bullet points for lists of three or more items
• Always include at least one practical example from real Webflow project experience
• Do not use em dashes
• Use British English throughout

Once this is set up, you don't have to repeat these instructions in every prompt. Claude reads them automatically at the start of each conversation.

Step 6: Publish directly to Webflow via the MCP

Once the draft is ready, I ask Claude to push it straight to my CMS. No copying and pasting.

A prompt for this:

"Create a new draft item in my Resources CMS collection with the following. Name: [title]. Slug: [slug]. Post body: [content]. Meta title: [meta title]. Meta description: [meta description]. Read time: [X mins]. Save as a draft."

Claude will confirm when it's done. I then open Webflow, review the draft, check the formatting has come through cleanly, add any images, and publish when I'm happy.

The whole process from brief to published draft takes me around 45 minutes for a 1,000 word article. Without the MCP, the same process took twice as long.

Before you publish, do this

AI-assisted content still needs a proper read before it goes live. I check for:

• Tone: does it sound like me, or does it sound like a press release?
• Accuracy: has Claude invented any statistics or tool names that don't exist?
• Search intent: would someone who searched that keyword find a genuinely useful answer here?
• Internal links: are there existing articles or service pages worth linking to from this post?
• Formatting: do the headings, lists and paragraph lengths render correctly in Webflow?

The internal linking step is worth doing manually. It's one of the higher-impact SEO actions you can take on a page, and Claude won't know which of your other posts are worth linking to unless you tell it.

A note on Google and AI content

Google doesn't penalise content because it was written with AI assistance. What it does penalise is thin, generic content that doesn't actually help the reader.

The keyword brief, the structured prompt, the first-person framing and the human review step are all there to make sure what gets published is genuinely useful. Skip any of those steps and the content will show it.

I think of Claude as a capable writing partner, not a content machine. The better the input I give it, the better the output I get back.