Documentation

How Scaup connects to your site

Each integration works differently depending on your platform. Scaup reads your existing pages and content, identifies SEO gaps, then writes changes back through your platform's API. No plugins to install on Webflow or Wix. WordPress uses Application Passwords, which are built into WordPress core since version 5.6. GitHub users connect a repository and Scaup commits changes directly to the branch you specify.

What Scaup can change depends on what each platform exposes through its API. On Webflow, that includes page titles, meta descriptions, Open Graph fields, blog post content, and image alt text. On WordPress, titles, meta descriptions, and new posts. On Wix, blog post SEO fields require the Wix Blog app to be installed. On GitHub, Scaup can edit meta tags, page copy, and create new pages as commits.

Changes go live when your platform publishes them. For Webflow and Wix that means after you publish your site. For WordPress and GitHub, changes are visible as soon as the API write completes or the commit is merged.

Common questions

Does Scaup need admin access to my site?

It depends on the platform. Webflow requires a site-level API token. WordPress uses an Application Password tied to any user account with edit permissions. Wix uses OAuth. GitHub needs a personal access token or GitHub App with write access to the target repository.

Will Scaup overwrite content I've already written?

Scaup only writes fields you've approved. You review suggested changes before anything goes live, so existing content isn't touched unless you confirm the update.

Which platform should I connect first?

Start with wherever your main site lives. If you run a blog on WordPress and a marketing site on Webflow, connect the one with the most pages first - that's where Scaup will find the most to improve.

Questions? Email [email protected].