A Different Kind of SEO Workflow

Most SEO advice assumes a fairly fixed division of labour: a strategist produces a keyword brief, a writer produces content, a developer handles technical implementation, and someone periodically runs an audit to see what's broken. That model works, but it's expensive and slow. For a small studio or in-house team, it often means SEO gets done in bursts when there's budget and neglected the rest of the time.

What's changed is that AI tools connected directly to your Webflow site via the Webflow MCP can now handle significant parts of all four of those stages from a single interface. Not as a replacement for thinking and editorial judgement, but as a way to compress the time between deciding to do something and having it done.

This article covers how that workflow actually operates in practice: from keyword planning and content writing through to CMS population, site auditing, and what becomes possible when you connect external data sources like Google Analytics and SEMrush into the same loop.

What the Webflow MCP Actually Is

MCP stands for Model Context Protocol, a standard developed by Anthropic that allows AI models like Claude to connect to external tools and services via structured integrations. The Webflow MCP is a direct, authenticated connection between Claude and your Webflow site. Once configured, Claude can read your site's page structure, metadata, CMS collections and items, and make changes to all of them via the Webflow API, without you needing to touch Webflow directly.

In practice, this means you can have a conversation with Claude that both discusses your SEO strategy and executes against it. You can ask Claude to audit your site's metadata, identify gaps, write content to fill those gaps, and push it directly into Webflow as a CMS draft, all within the same session. The round-trip from brief to draft CMS item, including researching the topic, writing a full article, and populating every field, typically takes a few minutes.

Planning: Keyword Research and Content Strategy

Claude's web search capability allows it to research a topic before writing about it: checking what's currently ranking, understanding the search intent behind a keyword, reviewing what competitors are covering, and identifying gaps in the existing content landscape. This is useful both for one-off article briefs and for building out a coherent content strategy over time.

A practical planning session might start with a target keyword or topic cluster and ask Claude to map out a set of articles that would collectively build topical authority in that area. Claude can assess which terms have clear informational intent (good for top-of-funnel content), which have commercial intent (better suited to landing pages or comparison articles), and how they relate to each other structurally. The output is a prioritised content plan that can be worked through systematically over weeks or months.

For healthcare, MedTech, or life sciences brands, this kind of planning is particularly valuable. The intersection of technical subject matter and regulatory sensitivities means content needs to be accurate, appropriately caveated, and written with a specific audience in mind. Claude can hold that context across an entire planning session and apply it consistently when writing.

Writing: From Brief to Publish-Ready Draft

Once a content plan exists, executing it is where the workflow becomes most tangible. A well-briefed Claude session can produce a full SEO article of 1,200 to 2,000 words: correct heading structure, proper internal linking to existing pages, a meta title and description calibrated to the target keyword, Open Graph fields, a focus keyword, read time estimate, schema type, and article tags. Everything that would normally require either a content management system form to be filled in manually or a separate briefing process for a writer.

The quality of what comes out depends heavily on what goes in. Claude writes better articles when it has context: who the audience is, what the brand's positioning is, what tone is appropriate, and what the article is trying to achieve in the context of the broader site. That context can be established once and applied consistently across every article in a series, which is where a regular cadence (publishing every two weeks, for example) becomes particularly efficient.

Importantly, the writing is not the whole task. The article also needs to be pushed into the CMS. With the Webflow MCP active, Claude can create the CMS item directly, with every field populated, as a draft ready for review. The only step that remains manual is adding a thumbnail image and hitting publish. That step stays manual intentionally: human review before content goes live is worth keeping.

Auditing: What Claude Can See Across Your Site

SEO auditing is one of the highest-value applications of the Claude and Webflow MCP combination, partly because it's the kind of work that's easy to keep postponing. Audits feel like large tasks. With Claude connected to your Webflow site, many of the most common audit checks are quick to run.

Claude can pull all pages from the Webflow API and check each one for missing or duplicate title tags, missing meta descriptions, Open Graph fields that haven't been populated, pages that are indexed but have no meaningful SEO metadata, and CMS collection items where fields like focus keyword or schema type have been left empty. It can flag pages with slugs that don't match the target keyword, identify pages that were updated a long time ago and may need refreshing, and spot structural inconsistencies in how content types are being used.

This kind of audit, done manually, might take half a day. Done via Claude and the Webflow MCP, it takes a few minutes to retrieve the data and a few more to review the output. Identified issues can be fixed in the same session: Claude can update page metadata, correct slugs, and fill in missing fields directly via the API without requiring you to navigate to each page in the Webflow Designer individually.

Connecting Google Analytics Data

Auditing metadata is a technical exercise. Connecting it to performance data is where strategy enters. Google Analytics provides the behavioural context that metadata audits lack: which pages are actually receiving traffic, which pages have high bounce rates, which landing pages are converting, and which organic search queries are bringing people in.

With GA4 data in hand, either exported and pasted into the conversation or accessible via a connector, Claude can cross-reference audit findings with performance data. A page with poor metadata might also be your second-highest organic traffic source, which changes how urgently it needs attention. A page with perfect metadata might be receiving zero traffic, which suggests either the keyword has no search volume or the content isn't satisfying the intent behind it.

This kind of synthesis is where AI assistance goes beyond task automation. Claude can look at a set of pages, their traffic trends, their metadata completeness, and their keyword rankings, and surface a prioritised action list: fix these three pages first because they're getting traffic but have no meta descriptions; these five pages need content refreshes because traffic has dropped over the past six months; this cluster of articles is building topical authority and should be expanded.

Connecting SEMrush Data

SEMrush adds the competitive and keyword dimension that Google Analytics alone doesn't provide. Where GA4 tells you how your existing pages are performing, SEMrush tells you what keywords you're not ranking for yet, how difficult they are to target, what your competitors are covering that you aren't, and where your domain has backlink gaps relative to the sites you're competing against.

Brought into a Claude conversation, SEMrush data can feed directly into content planning. Export a keyword gap report or a competitor content analysis and Claude can interpret it: which keywords align with your service offering, which represent quick wins given your current domain authority, and which should be targeted with new content versus optimisation of existing pages. The output is a brief that connects directly to the content creation workflow described above.

The combination of SEMrush data for planning, GA4 data for performance review, and Claude plus Webflow MCP for execution means the full SEO loop, from identifying an opportunity to having content live on the site, can be completed in a single working session rather than across multiple tools, multiple team members, and multiple weeks.

What This Workflow Looks Like for a Typical Client

To make this concrete: a healthcare brand with a Webflow site and an existing blog wants to build organic visibility for a cluster of keywords related to their product area. They have some existing content but no coherent strategy, and their metadata is inconsistently filled in across the site.

A single Claude session with Webflow MCP access can audit the entire site for metadata completeness and produce a prioritised fix list. A second session, with a SEMrush keyword gap export and GA4 traffic data, can produce a 20-article content plan ordered by priority. Each subsequent fortnightly session produces one article: researched, written, all CMS fields populated, pushed to Webflow as a draft ready to review. Six months later, the site has a coherent topical structure, consistent metadata, and a growing body of content. That's a realistic outcome for a small team that previously couldn't maintain the pace.

The Honest Limitations

Claude is not a replacement for SEO expertise and it's not a replacement for editorial judgement. The workflow described here produces excellent first drafts and comprehensive audits, but someone with domain knowledge still needs to review content before it goes live, especially for regulated sectors where accuracy matters. The planning outputs are a starting point for strategy, not a substitute for understanding your audience and market deeply.

The Webflow MCP integration is also genuinely powerful, but it operates within what the Webflow API exposes. There are things the API can't do: it can't add thumbnail images to CMS items, can't manage complex page interactions, and can't make changes that require working inside the Webflow Designer directly. The workflow is a complement to the Designer, not a replacement for it.

These are real constraints, but they're constraints that leave the highest-value work, the creative and strategic decisions, firmly with the people who understand the business. What gets automated is the execution layer: the repetitive, time-consuming tasks that were always the bottleneck between having a good idea and having it implemented.

How wat.studio Offers This as a Service

We use this workflow on wat.studio's own site. The content you're reading right now was researched, written, and pushed to Webflow via this exact process. We also offer it to clients as part of ongoing retainer work: monthly or fortnightly content sessions, regular metadata audits, and SEO reporting that connects GA4 and SEMrush data to actionable priorities in Webflow.

If you're a healthcare brand, MedTech company, or B2B SaaS business with a Webflow site and an SEO gap you need to close, this is what a practical, consistent approach to closing it looks like.

Find out more on our Webflow development page, or get in touch to discuss your project.