Curify + Webflow Programmatic SEO Integration: Per-SKU Visuals at CMS Scale

Goal: every CMS item has the fields Curify needs to fill in the template's parameter slots.

Open your Webflow Designer → Collections → the collection you're generating images for (e.g., Products). Add fields that map onto the Curify template parameters. For the lifestyle-photo-grid template, you need:

• subject (plain text) — the product or category name (e.g., "silk midi dress")

• scene_preset (option) — one of: met-gala-red-carpet, paris-fashion-week, beach-summer, autumn-park, wedding-day, city-fashion, spring-meadow

• palette_hint (plain text, optional) — hex color or named register (e.g., "vinho-do-porto red + gold")

• generated_image (image field) — leave empty; Curify writes the URL back here.

Naming convention: keep your Webflow field slugs identical to the Curify template parameter names. The integration script in step 3 uses direct slug → param mapping; mismatched names mean manual translation per row.

Goal: choose one (occasionally two) templates that match your output format requirement.

Open /nano-banana-pro-prompts and filter by template family. Your decision matrix:

• Need 9-scene grids (product across multiple use cases in one image) → lifestyle-photo-grid. 7 scene presets, plays well for DTC catalogs.

• Need single hero shots (one product, one camera angle) → product-poster. 8 example variants in the gallery.

• Need fashion / apparel (model wearing supplied outfit) → ai-outfit-try-on-poster. 5 style presets.

• Need packaging mockups → food-product-packaging-design.

• Need promotional / sale campaign visuals → product-theme-promotional-poster. 5 themed presets.

• Need before/after variant cards → fashion-before-after-outfit-annotation-card.

Each template's example URL (e.g., /nano-template/lifestyle-photo-grid/example/template-lifestyle-photo-grid-met-gala-red-carpet) is the visual reference for what your output will look like. Show this to the design team for sign-off BEFORE you wire the integration — locking the wrong template means re-running the whole batch.

Goal: produce a CSV (or JSON) where each row is a CMS item translated into Curify template parameters.

Pull your Webflow collection via the Webflow Data API:

GET https://api.webflow.com/v2/collections/{collection_id}/items
Authorization: Bearer {WEBFLOW_API_TOKEN}

Run a small mapping script (Node, Python, whatever) that reads each item's fieldData and writes a row with the template parameters. For lifestyle-photo-grid:

item_id,subject,scene_preset,palette_hint
650abc...,silk midi dress,met-gala-red-carpet,"vinho-do-porto red + gold"
650def...,linen jumpsuit,beach-summer,"sand cream + teal accent"
650ghi...,wool coat,autumn-park,"burnt sienna + mustard"

Add error handling for items missing required fields — Curify skips them rather than generating from partial data. A pre-flight report listing which items will skip lets you fix the CMS before the run. Keep item_id in the CSV so you can match generated images back to the source items in step 5.

Goal: feed the CSV to Curify, get back a folder of generated images keyed to item_id.

Three paths depending on your team's stack:

A. Direct batch upload — easiest for teams without an automation platform. Upload the CSV via the Curify dashboard (early-access workflow today). Curify runs the batch, returns a ZIP of generated images named by item_id, plus a manifest (item_id,image_url) you'll use in step 5.

B. Make.com / Zapier flow — best for ongoing operation. Trigger: "new item in Webflow collection." Action: send to Curify generation endpoint with the item's mapped params. Action: webhook Webflow Assets API to attach the resulting image back to the source item. This makes new product pages self-imaging within ~5 minutes of CMS publish.

C. Curify API direct (for engineering teams) — POST the CSV to the Curify batch endpoint, poll for completion, fetch the manifest. Same shape as the dashboard workflow but scriptable.

Throughput note: Nano Banana Pro takes ~15-45 seconds per image. A 1,000-item batch typically completes in 4-8 hours depending on concurrency tier. Plan your first run on a weekend if you're doing the whole catalog at once.

Goal: each CMS item's generated_image field now points to the matching generated visual.

Use the Webflow Assets API to upload each generated image, then patch the source CMS item to point at the new asset:

for row in manifest:
    # 1. Upload generated image to Webflow Assets
    asset = POST /v2/sites/SITE_ID/assets/...
    # 2. Patch the CMS item to point at the asset
    PATCH /v2/collections/CID/items/ROW_ITEM_ID
        body: fieldData.generated_image = asset.id

Faster path for one-shot batches: skip Webflow Assets entirely. Curify's manifest URLs are CDN-served (cdn.curify-ai.com); patch the CMS items to use the CDN URL directly. Saves the upload round-trip; tradeoff is that the image lives on Curify's CDN rather than Webflow's. For programmatic SEO pages where you don't need Webflow image optimization (responsive variants, lazy-load), the CDN-direct path is fine.

Trigger a Webflow publish after the batch lands so the live site picks up the new images. For sites with thousands of items, Webflow's publish is incremental — you don't republish the whole site.