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.
- Add structured data (JSON-LD) to your site's head. This is schema markup that helps search engines and AI tools understand what your business is. See the "Structured data" section below for how it is delivered.
- 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, or modify your sitemap directly.
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. If you have unpublished changes staged in the Webflow Designer when Scaup runs, those changes will go live at the same time as Scaup's changes. Scaup has no visibility into your draft work and cannot selectively hold it back.
- 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.
Structured data
Scaup adds Schema.org JSON-LD markup to your site's head using Webflow's Custom Code API. Because Webflow serves all registered scripts as JavaScript files (with a text/javascript type), there is no way to inject a static <script type="application/ld+json"> block directly. Instead, Scaup registers a small inline script called scaupStructuredData that creates the JSON-LD node and appends it to the page head at render time.
Google reads JSON-LD that is added this way. The script carries no tracking, no third-party network calls, and no advertising. Its only job is to add the structured data Scaup generates from your site's own published content.
When Scaup re-applies structured data, it replaces the existing script in place. It never stacks duplicates and never removes scripts you added yourself.
Permissions Scaup requests
Scaup requests the following Webflow OAuth scopes. Each one maps to a specific feature. No scope is requested that is not used.
| Scope | Why we need it | API call |
|---|---|---|
| sites:read | List your Webflow sites at connect time; read pages and collections for the growth plan | GET /sites, GET /sites/{id}/pages, GET /sites/{id}/collections |
| 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 before writing | GET /sites/{id}/pages |
| pages:write | Write SEO title and meta description on static pages | PUT /pages/{id} |
| cms:read | Resolve which CMS collection to publish blog posts into | GET /sites/{id}/collections |
| cms:write | Create and publish new blog posts | POST /collections/{id}/items |
| custom_code:read | Read existing registered scripts before writing, so Scaup's script replaces itself and never removes scripts you added | GET /sites/{id}/registered_scripts, GET /sites/{id}/custom_code |
| custom_code:write | Register the scaupStructuredData JSON-LD inline script | POST /sites/{id}/registered_scripts/inline, PUT /sites/{id}/custom_code |
| assets:read | Find images on your site that are missing alt text | GET /sites/{id}/assets |
| 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).
- Structured data and image alt text require the
custom_codeandassetsscopes, which are granted during the initial OAuth connection. Sites connected before these scopes were added 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).
- 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.