How Scaup Works on Webflow
Last updated: August 2026
What Scaup does on your Webflow site
After you connect your Webflow site, Scaup builds a monthly growth plan and runs improvements on a daily schedule. On Webflow, it can do the following:
- Update page titles and meta descriptions on your static pages, so they are more descriptive for people searching on Google.
- Publish new blog posts into your CMS collection. Scaup creates the post, writes the content, and publishes it live. This requires a Webflow plan that includes CMS Hosting and at least one CMS collection on your site.
- Write alt text for images that are missing descriptions. Scaup reads each uncaptioned image and generates a short, accurate description.
Scaup cannot edit page body content (that requires Webflow Designer), create 301 redirects, modify your sitemap, or add structured data. It also cannot write files like robots.txt or llms.txt, because Webflow has no way for an app to do it. When Scaup makes one of those files, it writes the text for you and shows it in your dashboard to paste into Webflow's own settings.
How changes go live
Scaup makes changes through the official Webflow Data API, then calls Webflow's publish API to push them to your live domain. A few things to know:
- One publish per run. Scaup publishes your site once per session, after all changes for that run are applied. It does not publish if no changes were made.
- Full site publish. Webflow's API does not support publishing individual pages. When Scaup publishes, the entire site goes live, including any changes Scaup made.
- Your draft work. Because a publish is site-wide, it would carry anything you have staged in the Designer. So before publishing, Scaup checks whether the site has unpublished work. If it does, or if Scaup cannot read the site's state, it does not publish: the changes stay staged next to yours and your Scaup site page shows a note with a Publish now button, so the decision is yours.
- Auto-apply mode. By default, Scaup applies changes to your live site without asking for approval first. You can switch to preview mode in your Scaup settings to review each change before it goes live.
Permissions Scaup requests
Scaup requests nine Webflow OAuth scopes. Each one maps to a specific feature. No scope is requested that is not used. Scaup does not request access to your site's custom code.
| Scope | Why we need it | API call |
|---|---|---|
| sites:read | List your Webflow sites at connect time, and read a site's publish state before we publish | GET /sites, GET /sites/{id}, GET /sites/{id}/custom_domains |
| sites:write | Publish your site after changes so they go live on your domain | POST /sites/{id}/publish |
| pages:read | Match each plan item's target URL to a Webflow page ID, and read the page content we work from | GET /sites/{id}/pages, GET /pages/{id}/dom |
| pages:write | Write the SEO title, meta description and Open Graph title and description on static pages | PUT /pages/{id} |
| cms:read | Resolve which CMS collection to publish blog posts into, and which fields it has | GET /sites/{id}/collections, GET /collections/{id} |
| cms:write | Create new blog posts and update existing collection items | POST /collections/{id}/items, PATCH /collections/{id}/items/{itemId} |
| assets:read | Find images missing alt text, and re-read one before writing so we never overwrite alt text you wrote | GET /sites/{id}/assets, GET /assets/{id} |
| assets:write | Write the AI-generated alt text description to each image asset | PATCH /assets/{id} |
| components:read | Read component definitions so content inside shared components is visible when building the growth plan | GET /sites/{id}/components/{id}/dom |
Requirements
- A paid Scaup subscription is required to use the improvement engine.
- Publishing new blog posts requires at least one CMS collection on your Webflow site and a Webflow plan that includes CMS Hosting (Basic plan does not include CMS).
- Image alt text requires the
assetsscopes, which are granted during the initial connection. Sites connected before those scopes existed will see a reconnect prompt in the Scaup dashboard.
What Scaup does not do
- Edit page body content — Webflow Designer is the only way to change a page's body HTML.
- Create or manage 301 redirects.
- Modify your sitemap (Webflow generates it automatically).
- Add structured data (JSON-LD). Scaup no longer does this on Webflow.
- Write robots.txt or llms.txt. Webflow has no API for these, so Scaup writes the file for you and you paste it into your Webflow site settings.
- Delete, archive, or bulk-modify any content.
- Inject any tracking scripts, advertising code, or third-party services.
Disconnecting Scaup
To revoke Scaup's access to your Webflow site, go to your Webflow account settings, open the Integrations or Apps section, and remove Scaup. You can also disconnect from within the Scaup dashboard under Site Settings.
Revoking access stops all future changes. It does not undo changes that have already been published to your site.
Questions or issues
Email [email protected] and we'll get back to you within one business day.