1. Install in Webflow
Install Rover from your Webflow workspace or the Marketplace. Webflow handles site selection and OAuth, and Rover provisions the mapped Rover site automatically.
Rover x Webflow
Install in Webflow. Finish setup in Rover Workspace. Go live when it feels right.
Rover is a site-level Webflow app. Webflow handles site selection, managed publish, and Designer context; Rover Workspace handles the defaults-first setup, guardrails, brand, journeys, AI launch, Cloud sandboxes, and Agent analytics configuration before you publish. Rover Agent is the recommended package here and already includes Agent analytics by default.
2. Finish setup in Rover Workspace
Guided onboarding opens directly inside Rover Workspace with the Webflow site already scoped. It writes the same Rover site-config contract as direct installs, keeps the launch path defaults-first, and uses a dedicated Execution step for Cloud sandboxes, automatic scrolling, and key expiry. Automatic page scrolling starts off by default; turn it on only when Rover should scroll to inspect below-the-fold content. The Agent step also exposes the Experience preset, voice narration, Action Spotlight default, and spotlight color so the managed deploy can read short guide-flow steps aloud and highlight clicks, typing, selects, and scroll targets in the site’s own brand palette. Domain scope stays owner-configurable, external pages open in a new tab with notice, and Rover chooses the right tab automatically for allowed-host hops. Runtime defaults still own the seed/presence CTA, centered stage, transparent live-action mode, and step stream unless you explicitly change them. Journeys use the same builder-first editor as direct Rover setup, with raw JSON kept as an opt-in expert mode. The final review step is a check-and-change surface, so each summary row can send you back to the right section and then return you to review.
Custom mascots can use a static image on its own or pair that image with MP4/WebM for animation. Mascot sound uses the same site-owned appearance controls as direct Workspace: off unless explicitly enabled, with a separate start-muted default once enabled, and image-only mascots stay silent. Voice dictation remains a separate input setting and still defaults on for new sites.
3. Go live on Webflow
Clicking Go live deploys Rover through Webflow Custom Code and publishes the site. The managed publish path writes the runtime bundle, and that runtime injects the inline marker, page manifest, rover-site, agent-card, service-desc/service-doc links, and A2W cloud GET resolver hints from the saved Rover site config. Static well-known files, `llms.txt`, and HTTP headers still remain origin-controlled extras. After launch, use the Designer Extension for operational actions and Rover Workspace for tuning.
Managed AI-ready defaults
Rover Agent includes Agent analytics. Choose Agent Analytics when you explicitly want visits, runs, outcomes, and feedback without the full action-taking runtime.
Managed Webflow installs now default new site keys to No expiry unless you intentionally choose a TTL.
Cloud sandboxes is the single owner-facing switch for cloud execution plus approved third-party browsing.
Webflow onboarding now persists Rover's managed baseline instead of treating discovery as an implicit side effect.
The production cue is the minimized Rover seed/presence itself. Machine-readable discovery stays published in source, and the separate floating cue stays reserved for debug flows.
If you later need discovery overrides like a custom presence CTA label, host-surface selector, or published well-known URL changes, open Rover Workspace Settings for that site. Webflow onboarding stays curated on purpose.
Shortcut behavior in Webflow onboarding
Workspace saves the same shortcut schema used everywhere else in Rover: exact IDs, labels, prompts, optional descriptions, routing, and enabled state.
Builder mode is the default. Advanced JSON is available, but invalid JSON stays local until it becomes valid and is applied back into the builder.
Exact shortcut IDs matter for deep links like ?rover_shortcut=get_started, chatbot executor links with rover_exec, and A2W run payloads like { "url": "https://example.com", "shortcutId": "get_started" }.
Webflow onboarding now uses the same shortcut flow as regular Rover Workspace. Add explicit shortcuts when you want them; otherwise Rover does not invent a Webflow-only fallback shortcut.
Marketplace positioning
Short description: Install an AI website agent on your Webflow site in one click.
Primary message: Manage deployment in Webflow. Configure behavior and brand in Rover Workspace. Rover publishes the same canonical discovery + runtime bundle that direct installs use.
Avoid marketplace copy about raw public keys, script IDs, or custom code internals. The app should feel builder-first, not API-first.
Shortcuts, prompt behavior, and AI access stay aligned with the regular Rover Workspace experience instead of adding Webflow-only shortcut fallbacks.
Submission checklist
Privacy policy, support page, and billing explanation should ship alongside the Marketplace listing.
Capture screenshots or GIFs of the install flow, Rover Workspace onboarding, and the live extension state.