Connecting Webflow to SKYA

The SKYA app for Webflow writes page SEO fields and blog drafts into your Webflow site after you approve them, and for a Webflow store imports your products into GPT Ads. It never publishes your site.

The SKYA app for Webflow writes the fixes you approve into your Webflow site, and nothing else. SKYA never publishes your site: publishing stays with you, in Webflow.

What the app does

• **Page SEO.** After you approve a fix, SKYA writes that page's SEO title, meta description and Open Graph fields. The change is saved in Webflow and waits for you to publish.
• **Blog drafts.** A draft you send from SKYA lands as a draft item in a blog-like CMS collection on your site. SKYA never publishes it.
• **Webflow Ecommerce stores.** On the GPT Ads page, a workspace owner or admin can import the store's products into the GPT Ads catalog, one row per product variant: its name, its options and its Description field. Archived products and drafts that were never published are left out. Prices are not imported yet, so price checks still use the catalog you upload. A variant whose SKU code matches one you uploaded stays as you uploaded it.
• **Short product descriptions.** SKYA flags imported products whose Description field is empty or under 50 words. It reads only that field, not custom fields. A workspace owner or admin can ask SKYA to draft a longer one, written only from what is already on the product (its current description, option names and variant names, never its price). When a product has too little on it, SKYA says so rather than invent details.
• **Saving a description.** Nothing is written until you review the draft, edit it if you like, and tick the approval. SKYA then saves that one Description field to Webflow as a staged change, and Webflow marks a product updated this way as the Advanced product type. If the description changed in Webflow after the draft was made, or the product has unpublished changes, SKYA writes nothing. The GPT Ads page lists each change and what happened to it, with the previous description a click away.

What it never does

• Publish your site. Publishing stays with you, in Webflow.
• Change your site settings.
• Touch your orders, customers or payments.
• Change a product's price, SKUs, stock or anything but the Description field you approved.
• Write robots.txt, the sitemap or site-wide code. Those stay copy and paste: SKYA gives you the exact text and tells you where it goes.

Each permission, and why it is asked for

• **sites:read** lists the sites you authorize, so SKYA can match the right one to your SKYA project.
• **pages:read** lists your pages, so SKYA can find the page a fix belongs on.
• **pages:write** saves the title, meta description and Open Graph fields you approved.
• **cms:read** finds a blog-like collection and its fields, so a draft lands in the right place.
• **cms:write** creates the draft item in that collection. SKYA never publishes it.
• **ecommerce:read** reads your products and their variants (names, options and the Description field) into the GPT Ads catalog. Webflow's store permission also covers orders; SKYA never reads them, and it does not import prices yet.
• **ecommerce:write** saves a product description you approved, as a staged change, and nothing else.

How to connect

• **From the Webflow Marketplace.** Click Install on the SKYA listing. You land on the SKYA install page. If you are signed out, sign in or create an account and you come straight back to it. With more than one SKYA project, pick the one this site belongs to.
• **From SKYA.** Open your project, click Connect website, and click Connect Webflow on the Webflow card.
• **From GPT Ads.** A workspace owner or admin clicks Connect Webflow on the Your Webflow store panel. A Webflow site already connected on another project in the same workspace, for the same domain, is used as it is.
• Either way, Webflow then shows its permission screen. Choose the site and approve, and you come back to SKYA with the site connected. The site must serve your SKYA project's domain: if none of the sites you chose does, or more than one does, SKYA connects nothing and names the sites it saw.

If SKYA says one more step is needed, that is deliberate. SKYA only accepts a connection it started and signed itself, so a connection that began in Webflow goes through the install page once more, and Webflow may show its permission screen again.

If you click Deny

Nothing is connected and nothing is stored. SKYA says so and takes you back to your project, or to your dashboard. You can connect again at any time.

How to disconnect

• **In SKYA:** open your project, click Connect website, and click Disconnect on the Webflow card. SKYA deletes the connection and the access token it held.
• **In Webflow:** open your site settings, go to Apps & integrations, find SKYA and uninstall it. SKYA loses access to the site straight away. Disconnect it in SKYA as well, so the Webflow card stops showing it as connected.

Changes SKYA already saved stay in your site either way, as ordinary edits you can change or remove in Webflow.