How to Use Webflow to Audit SEO Metadata With an AI Agent

The short answer: if a Webflow site has grown to dozens of pages and posts with missing or duplicate meta descriptions, an AI agent connected through Webflow's MCP server can audit and rewrite them, the server is listed on every Site plan, and the blog posts themselves need the CMS, which starts on Premium at $25 a month billed yearly (pricing page, checked on 26 October 2026). The steps: export the collection as a backup, connect the MCP server as a site owner or admin, run Webflow's SEO Metadata Auditor prompt without letting it write, review its proposals page by page, let the agent save the approved changes as drafts, check them in Webflow, and publish yourself.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

Nobody schedules the work of writing meta descriptions. Each one takes a few minutes, a site has hundreds, and the ones written at launch describe a product that has since changed. An agent is good at the first draft of that work and poor at knowing which claim your legal team removed last quarter, so this guide keeps a person between the draft and the live site. For plans and add-ons, see the Webflow glossary entry.

Before the agent touches anything:

1. What the manual version costs. For example, 120 posts at 3 minutes each is 360 minutes, six hours of writing. With the agent drafting, your part is review: at 30 seconds a post, 120 x 0.5 = 60 minutes.
2. What you already have. A CSV export of the blog collection is your undo button, and Webflow's CMS update describes exporting a whole collection or a filtered selection, then reimporting it. Search Console's list of pages by impressions tells you which 20 pages to fix first.
3. The reading that says it worked. Note the click-through rate of those 20 pages in Search Console today; you will compare it with the same figure 28 days after publishing.

What you need

• A Webflow site, with the CMS on Premium if the posts live in a collection. The pricing page lists the MCP server on Starter, Basic and Premium alike.
• Owner or admin rights on the site. Only site owners and admins can authorize the MCP server; for everyone else the site shows greyed out, per the MCP FAQ.
• Claude Desktop, ChatGPT, Cursor or another MCP client.

Step 1: Export the collection

In the CMS, export the blog collection to CSV before anything changes. If the agent's work goes wrong, this file and the item IDs in it let you restore the old fields.

Step 2: Connect the MCP server

In Claude, click the + symbol, choose Add connectors, search for Webflow (under All rather than Featured), click Connect, sign in, select the sites and Workspaces to share and click Authorize App, per Webflow's Claude Desktop guide. Other clients add the remote server at https://mcp.webflow.com/mcp. Each authorization covers one Workspace; to switch, remove and reinstall the connector, per the overview.

Step 3: Write the house rules once

Each site can carry its own Agent Instructions that guide how agents work on it, per the overview. Put your rules there: brand name spelled one way, the claims you may not make, the length you want. The agent reads them on every request instead of you repeating them.

Step 4: Run the audit without writes

Webflow publishes an SEO Metadata Auditor prompt for exactly this job. It lists the pages, reads each page's title, meta description, slug and Open Graph fields, and scores them out of 100: titles between 30 and 60 characters, descriptions between 70 and 160, no duplicates across the site. It runs in what it calls safe mode by default, never publishing or changing slugs without explicit approval, and it asks for confirmation before any write. Paste the prompt, name the site, and ask for the executive summary first.

Step 5: Review the proposals

Read the summary, then ask for the proposals on your 20 priority pages. Check each one for three things the agent cannot know: a claim that is no longer true, a keyword your team has chosen not to chase, and a promise sales cannot keep. Leave slug changes off. The auditor only proposes them when you allow it, and a changed slug is a broken link until someone redirects it.

Step 6: Let the agent write drafts

Approve the batch you have read. For static pages the agent calls update_page_settings; for posts in the CMS it updates the collection items, and Webflow's tool reference states that CMS items are created and updated as drafts, with publishing as a separate action. Webflow's own example prompt in the overview does the same for collections: find items with missing descriptions or SEO metadata and fill them.

Step 7: Check in Webflow before anything goes live

Open five of the changed items in the CMS and two pages in page settings and read them as a searcher would. Then ask the agent to re-read the metadata and report any page where the saved text differs from what you approved; the auditor prompt ends with the same verification.

Step 8: Publish yourself

Publish the approved items, or the site, from Webflow. The agent can publish when told to, and the auditor offers it only on request, so keep that click with the person who reviewed the drafts.

Step 9: Read the result in 28 days

Compare the click-through rate of the 20 priority pages with the figure from before. Google sometimes uses a page's meta description for the snippet under its result, per its snippet guidance, so judge the new text on clicks per impression rather than on position.

What Webflow's MCP documentation warns about

• One Workspace per authorization. A second Workspace means reinstalling the connector, per the FAQ.
• The Designer for some tasks. Snapshots, image uploads and anything about the current page or selection need the Designer open with the MCP Bridge App connected; metadata work does not.
• Sleeping tabs. If the Designer is involved and the connection drops, the FAQ suggests keeping the webflow.com tab active.
• Localized items. The server can update existing CMS items in secondary locales but cannot create new localized ones.

The free check, and the paid one Webflow offers

Search Console's click data answers whether the new descriptions worked, and it costs nothing. The MCP server can also read traffic and goals inside Webflow, but only through Webflow Analyze, an add-on from $9 a month on yearly billing, per the overview and the pricing page: the measurement step inside Webflow comes with one more subscription attached, and for search snippets Google's free report already has the numbers.

FAQ

Does this work on the free Starter plan?

The MCP server is listed on Starter, but Starter holds 50 CMS items and two static pages on a webflow.io address, per the pricing page, so a real blog needs Premium.

Can the agent publish by itself?

Only if you ask. CMS items it writes are drafts, and the auditor prompt never publishes without explicit approval, per the prompt page.

What if the agent rewrites a page I wanted left alone?

Restore the fields from the CSV export in step 1, then add the page to your Agent Instructions as one the agent must not edit.