In the threads here about AEO, schema and llms.txt, one problem keeps coming up: you find out a page is weak for AI search in one tool, then switch to Webflow to fix it and lose the context.
So we're building the Ocli Webflow Extension: a panel inside the Designer that shows, for the page you have open:
an AI readiness score (a diagnostic, not a promise of rankings or citations) and the checks behind it
suggested fixes for the title, meta description, a short answer block, structured data and internal links
approve, edit or reject each one, then apply it as a Webflow draft. Nothing goes live until you publish.
It works on static pages and CMS items, in every language version of your site.
We're starting with a small group of sites (agencies, freelancers and in-house teams), and I'd really value input from people who'd use it:
Which fixes would you trust a tool to draft, and which would you always write yourself?
On CMS-heavy sites, would you work item by item or want bulk changes?
What would make this a no-go for client sites?
If you'd like to try it early, the waitlist is here: https://ocli.io/webflow-extension
I'm happy to answer anything about how the scoring works.