beehiivYou published a post on Webflow this morning. Now you want to know if anyone’s reading it, which means Webflow in one tab, your analytics in another, Search Console in a third.
Three tabs for one question. And tomorrow you’ll open all three again.
What the board shows
Your newest collection items: the latest posts, case studies or changelog entries from any CMS collection, as a list on your board. Your blog and your changelog can each have a widget of their own.
Your sites: every site your Webflow sign-in covers, on one widget.
Beside it: what the pages bring in. Visitors from Plausible or Google Analytics, clicks and top queries from Search Console, signups from your database. The post and its traffic, one glance apart.
Where the data comes from
Webflow runs its own MCP server, the one AI apps sign in to when they read your sites. The board signs in to it through Webflow’s own sign-in page. That sign-in is sealed on the board’s server and never sent back to your browser.
Then the board runs the reads you chose, on a schedule, while the board is open. Only reads. Webflow’s server can publish and edit too, and the board never does.
You pick what to show in Connect. Choose one of Webflow’s reads, try it, and the form shows what the widget will say before anything lands on the board. Or ask your agent in a sentence. “Show my Webflow site’s newest collection items on the board” works from Claude, Codex, Cursor or any app that speaks MCP.
If a read fails, the widget keeps the last rows it got and says what went wrong and when. It never fills the gap with a guess.
Start from a blank canvas, put the Webflow list on it first, then ask your agent to add the traffic beside it.