How do you run an SEO audit on a Webflow site with Claude?

Quick Answer: Connect Claude to your Webflow site via the Webflow MCP or export your site data manually, then use Claude to crawl page metadata, flag missing or weak SEO elements, and generate a prioritised fix list. The full workflow takes under an hour and replaces what would otherwise be a day of manual auditing.

Running an SEO audit on a Webflow site usually means jumping between Ahrefs, Google Search Console, and your CMS, then manually cross-referencing what you find. Claude changes that. By connecting Claude directly to Webflow, you can pull live page data, identify metadata gaps, and get structured recommendations without touching a single spreadsheet. This guide walks through the exact crawl-and-recommendations workflow that B2B SaaS teams at SaaS Hackers use to cut audit time from hours to minutes.

What You Need Before You Start

Before running the audit, get these three things in place:

• A Webflow site with CMS collections or static pages you want to audit
• Claude (Claude.ai Pro or API access with Claude Code enabled)
• Webflow API access either through the Webflow MCP (Model Context Protocol) integration or a manual data export from your Webflow dashboard

Optional but useful:

• Ahrefs or Google Search Console data exported as a CSV (adds keyword and traffic context to Claude's recommendations)
• A list of target keywords for your key pages

Step 1: Connect Claude to Your Webflow Data

You have two paths here. Choose based on your technical setup.

Option A: Use the Webflow MCP (Recommended)

The Webflow MCP lets Claude read your site structure, CMS content, and metadata directly. Webflow added native MCP support in early 2026, which means Claude Code can now call Webflow's API without custom scripting.

To set it up:

1. Open Claude Code in your terminal
2. Add the Webflow MCP server to your Claude Code config file
3. Authenticate with your Webflow API token (found in Webflow under Account Settings > API Access)
4. Run a test prompt: "List all pages on my Webflow site with their current meta titles and descriptions"

If Claude returns a structured list of pages, you are connected.

Option B: Manual Export + Paste

If you are not using Claude Code, export your Webflow CMS data as a CSV from the Designer (CMS > Collections > Export). Paste the CSV content directly into a Claude conversation and proceed from Step 2.

This path works fine for sites under 100 pages. For larger sites, the MCP route is faster and more accurate.

Step 2: Run the Initial Crawl Prompt

Once Claude has access to your Webflow data, run this audit prompt:

You are an SEO auditor. Review the following Webflow site data and identify:
1. Pages missing a meta title
2. Pages with meta titles under 30 characters or over 60 characters
3. Pages missing a meta description
4. Pages with meta descriptions under 120 characters or over 160 characters
5. Pages missing an H1 tag
6. Pages with duplicate meta titles or descriptions
7. CMS collection pages with no SEO-specific fields populated

Return results as a structured table with: Page URL, Issue Type, Current Value, Recommended Action.

Claude will return a table you can copy directly into a Notion doc, Google Sheet, or your project management tool.

Step 3: Add Keyword Context

A metadata audit tells you what is missing. Adding keyword context tells you what to fix first.

If you have Ahrefs data, export a top pages report and paste it alongside your audit results. Then run:

Here is my SEO audit output and my top pages by organic traffic. 
Cross-reference them and tell me:
1. Which high-traffic pages have the weakest metadata
2. Which pages rank for keywords that are not reflected in their meta titles
3. Which pages have strong keyword rankings but no meta description (losing click-through rate)

Prioritise fixes by traffic impact, highest first.

This gives you a prioritised fix list rather than a flat list of every issue on the site. For B2B SaaS sites where engineering time is limited, prioritisation is the difference between an audit that gets actioned and one that sits in a doc forever. If you want a broader framework for fitting this into your wider acquisition strategy, SaaS Hackers also has an ultimate guide to B2B SaaS digital marketing.

Step 4: Generate the Recommendations

Now get Claude to write the actual fixes, not just flag the problems.

Use this prompt for batch metadata generation:

For each page in the audit table marked as [missing meta description], write a new meta description that:
- Is between 140-155 characters
- Includes the primary keyword for that page (use the page title as a guide if no keyword is specified)
- Has a clear value proposition or call to action
- Matches the tone of a B2B SaaS brand: direct, specific, no hype

Return results as: Page URL | Current description | Suggested description

Run the same structure for meta titles, H1 tags, or any other element flagged in Step 2. If your audit shows repeated gaps across high-value pages, it can also be worth reviewing how specialist B2B SaaS SEO agencies structure metadata, content, and on-page optimisation workflows.

Step 5: Push Fixes Back to Webflow

This is where the MCP connection saves the most time.

With Claude Code connected to Webflow via MCP, you can approve and push metadata changes without leaving the Claude interface. The Webflow MCP supports write operations, meaning Claude can update CMS fields directly once you confirm each change.

The recommended workflow:

1. Review Claude's suggested fixes in the output table
2. Mark each one as approved, edited, or rejected
3. Ask Claude to push all approved changes: "Apply all approved metadata changes to the corresponding Webflow CMS pages"
4. Verify in Webflow Designer that changes appear correctly before publishing

If you are not using MCP, copy the approved values back into your Webflow CMS export CSV and re-import, or update them manually in the Designer. Less elegant, but it works.

Step 6: Set Up a Recurring Audit

A one-time audit decays fast. New pages get added, CMS entries get created without metadata, and rankings shift. Set a recurring prompt in Claude Code or save your audit prompt as a reusable template.

Run it monthly, or trigger it any time a new content batch goes live. The Webflow MCP makes this fast enough that a monthly metadata check takes under 10 minutes once the workflow is in place. If you are starting to measure how AI assistants influence discovery and site visits, SaaS Hackers also explains how to track traffic from AI tools.

What This Workflow Catches (and What It Does Not)

Claude is strong at structured data analysis. This workflow reliably catches:

• Missing or malformed metadata across every page
• Duplicate titles and descriptions
• H1 gaps and heading hierarchy issues
• CMS collection pages with unpopulated SEO fields
• Keyword-to-title mismatches when you supply keyword data

It does not replace tools like Ahrefs or Google Search Console for:

• Backlink analysis
• Core Web Vitals and page speed
• Index coverage and crawl errors
• Ranking trend data over time

Use Claude for the content and metadata layer. Use your existing SEO tools for the technical and authority layers. Together, they cover the full audit picture. If you need support beyond in-house workflows, you can compare vetted B2B SaaS SEO agencies or explore specialists in newer search channels like GEO and AEO agencies.

FAQs

Q: Do I need Claude Code to audit a Webflow site with Claude?

No. Claude Code with the Webflow MCP is the fastest path, but you can run the same audit by exporting your CMS data as a CSV and pasting it into Claude.ai. The manual method works well for sites under 100 pages. For larger sites, Claude Code with MCP is significantly faster and supports write-back to Webflow.

Q: How long does a Claude Webflow SEO audit take?

Once your data connection is set up, the crawl and recommendations workflow takes 30-45 minutes for a typical B2B SaaS site with 50-150 pages. Initial setup of the Webflow MCP connection adds around 20 minutes the first time. Subsequent audits run in under 10 minutes.

Q: Can Claude write and publish meta descriptions directly to Webflow?

Yes, with the Webflow MCP connected through Claude Code. Claude can read CMS fields, generate updated metadata, and push approved changes back to Webflow via the API. You review and approve each change before anything goes live. Without MCP, you update fields manually or via CSV re-import.

Q: Is this workflow suitable for Webflow sites with large CMS collections?

Yes. Claude handles large structured datasets well. For sites with hundreds of CMS items, break the audit into batches by collection type (blog posts, case studies, landing pages) and run each batch separately. The Webflow MCP also supports paginated API calls, so Claude Code can process large collections without hitting token limits.

Q: What is the best Claude prompt for a Webflow SEO audit?

The most effective starting prompt asks Claude to check six specific elements: meta title length and presence, meta description length and presence, H1 tags, and duplicate metadata. Provide the page data as structured input (CSV or MCP-connected), and ask for output as a table with the current value and a recommended action for each issue. That format makes it straightforward to prioritise and action the results directly.