integrations // webflow
supereo tracks how six AI engines answer the questions your buyers ask, finds what keeps your site out of those answers, and on the Autopilot plan makes the fixes on your Webflow site itself. This guide is everything the connection does.
With your Webflow site connected, supereo can change:
Titles and meta descriptions go on your static pages' SEO fields, with their Open Graph title and description. New pages go in as items of a CMS collection you allow, such as comparison pages and answers to the questions buyers ask. Structured data goes only on CMS pages whose template prints a CMS field inside a JSON-LD script.
Each change is checked on the live page the way AI crawlers fetch it (GPTBot, ClaudeBot, PerplexityBot), with no JavaScript, and supereo then measures whether it moved your answers, with 10 target questions against 10 control questions.
If you press Deny instead, nothing is connected and nothing on your site changes: supereo keeps sending you recommendations, and you can connect any time later.
Before it writes anything, supereo reads your site and proposes a site plan: the pages it may edit, the collections it may add pages to, and whether supereo or your team publishes. You approve it, or decline it, in supereo. Nothing is written until you approve, and you can change the plan any time in Settings. Every change supereo makes is checked against the plan you approved.
A Webflow publish carries every pending edit on the site, not just supereo's. So supereo never publishes while anyone else has unpublished changes: it waits, and the change says so in your dashboard until the site is clear. If your plan says your team publishes, supereo writes the change and leaves the publish to you.
Undo, on every change in your dashboard, writes the saved values back and publishes again.
Disconnect, in Settings, Website builder, revokes supereo's access in Webflow and deletes the stored access token. Changes already made stay on your site, so undo any you want gone first.
Revoking supereo's access inside Webflow stops it at once: Webflow refuses its next call, nothing more is written or published, and Settings shows that Webflow refused the connection. Press Disconnect there to delete the stored token, or connect again.
Your access token is encrypted at rest, stored only on supereo's servers and never sent to your browser. Our privacy policy and terms cover the rest.
supereo asks Webflow for these permissions, and nothing else:
sites:read: lists the sites you can pick, and reads their domains and publish state.sites:write: publishes your site, to its webflow.io address first and then to your own domain.pages:read: reads your static pages' titles, meta descriptions and Open Graph fields.pages:write: changes those fields on the pages your site plan allows.cms:read: reads your collections and their items, to know which collections new pages can go in.cms:write: adds and updates items in the collections your site plan allows.Questions, or something that didn't work: email support@supereo.app.