← back to blog
    Berner SetterwallJuly 15, 20263 min read

    Webflow MCP: SEO Metadata, Page Copy, and Redirects — Now Agent-Operable

    Webflow MCP: SEO Metadata, Page Copy, and Redirects — Now Agent-Operable

    Our Webflow integration page makes a specific promise: Cogny reads your Webflow site alongside GA4 and Search Console, finds pages that leak, and — after you approve the ticket — ships the fix through the Webflow MCP: CMS field values, metadata, internal links, redirects.

    Until now the MCP server behind that promise covered the CMS half well (collections, items, publishing) but stopped short of the structural half. You could update a blog post's field data, but not a landing page's SEO title. You could publish a site, but not lay down the 301 that keeps inbound links alive after a slug change.

    That gap is now closed. The Webflow MCP at mcp.cogny.com/webflow exposes 28 tools against the Webflow Data API v2, and the newly shipped set is exactly the structural-fix toolkit:

    What's new

    Page SEO metadata — the highest-leverage fix in most audits:

    • update_page_settings — set a page's title, slug, SEO title, SEO description, and Open Graph title/description. Partial by design: only the fields you pass are touched. Passing an explicit OG value also clears Webflow's "same as SEO" copy flag so your value actually renders.

    Static page content — for copy that lives on the page, not in the CMS:

    • get_page_content — read a page's text nodes and component instances, each with a stable nodeId.
    • update_page_content — write up to 1,000 text nodes in one call. Webflow's API only allows this on secondary locales (primary-locale copy is Designer-only), so this is the tool for keeping localized pages in sync, not for rewriting your primary homepage.

    Redirects — the tool the integration page always promised:

    • list_redirects, create_redirect, update_redirect, delete_redirect — full 301 rule management with site-relative paths (/mostly-harmless → /earth). Rules take effect on the next publish_site.

    Collection schema — so an approved content-model change doesn't need a human in the Designer:

    • create_collection_field, update_collection_field, delete_collection_field — including Option fields (with choices) and Reference/MultiReference fields (pointing at another collection).

    Domains:

    • get_custom_domains — list the custom domains on a site, useful before publishing to the right host.

    The loop, end to end

    The point of these tools isn't any single call — it's that the whole structural-fix loop is now operable by an agent:

    1. Search Console shows /pricing-old bleeding impressions with a title tag from 2024.
    2. list_pages → get_page confirms the stale seo block.
    3. update_page_settings writes the new title and description.
    4. The page slug moves? create_redirect('/pricing-old', '/pricing').
    5. publish_site takes it live.

    Every write in that loop is gated: Cogny's tool-permission defaults auto-approve the reads (list_*, get_*) and hold every create_*, update_*, delete_*, and publish_* call for ask-first approval — the same review-before-live model we use everywhere. Each tool also ships full MCP behavior annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), so any MCP client — not just Cogny — can make the same safe/unsafe distinction.

    Connecting

    One token, no OAuth dance: in Webflow, go to Workspace Settings → Integrations → API access, generate a token (Site or Workspace scope), and paste it into Settings → Integrations → Webflow in Cogny. From that point the tools are live in chat, in scheduled reports, and for ticket-gated fixes.

    If you pair it with Google Search Console and GA4, the structural-fix templates can run the whole find-→ ticket → fix → publish cycle on a schedule.