small medium large

Page Builder

Turn Google Docs into complete Webflow pages using your project's existing closed Section and Item components.

Page Builder reads your content, selects suitable components, and assembles a page directly in Webflow. It can also decide to edit the content to better fit the available components, while preserving the original message.

How it works

Step

What happens

1. Initialize

The agent inspects your project's closed components and creates a Page Builder registry.

2. Prepare your content

Create a Google Doc containing your page information and content.

3. Build

The agent selects suitable components, populates their properties, and assembles the page in Webflow.

4. Review changes

The agent reports editorial adjustments, component choices, and any limitations encountered.

5. Refine

Review the draft in Webflow and adjust content or layouts where needed.

Before you start

Page Builder requires:

  • An SML Webflow project with closed Section and Item components prepared for marketers.
  • Webflow MCP connected to your AI agent.
  • The SML Page Builder skill installed in your AI agent.
  • Browser access for your AI agent to inspect the available components.
  • A components overview at /stylesheet/components, displaying all available closed Section and Item components as visual references.
  • A Google Doc containing the content for your page.

Page Builder generates a project-specific registry containing the available closed components and their properties, variants, and configurations. Combined with the visual references on the components page, this allows the skill to select suitable layouts based on both their structure and appearance.

1. Initialize the registry

Before building your first page, the agent needs to understand which closed components are available in your Webflow project.

Ask your AI agent:
‍

Initialize the SML Page Builder registry for Webflow site ID [SITE ID].


The agent inspects the available Section and Item components and records their properties, variants, slots, and identifiers.

The registry can be reused for subsequent page builds. If components are added or significantly changed, regenerate the registry to reflect the latest configuration.

2. Prepare your Google Doc

Page Builder uses a Google Doc as the source for your page content.

Start with the following information:
‍

Field

Purpose

Page name

Required. Used as the Webflow page name and to generate the URL slug.

SEO title

The page title used for search engines.

SEO description

The page description used for search engines.


Below these fields, add your page content using headings, paragraphs, lists, and links.

You don't need to specify which Webflow components to use or describe how the page should be laid out. Page Builder determines a suitable structure based on your content and the components available in the project.

Editorial adjustments

Content written in a document doesn't always fit directly into a website layout.

Page Builder can make editorial adjustments where needed, including:

  • Shortening headings that would otherwise span too many lines.
  • Condensing introductory paragraphs.
  • Adjusting button labels to make them shorter and clearer.
  • Combining or reorganizing content to fit available layouts.
  • Creating short introductory labels where they improve the structure.

The agent preserves the meaning of your content rather than rewriting it unnecessarily.

All editorial changes are reported after the build, so you can review what was changed and why.

3. Build your page

Once your Google Doc is ready, provide it to your AI agent and ask:
‍

Build a new page in Webflow site ID [SITE ID] using the SML Page Builder skill and this Google Doc: [SHARE LINK].


The agent reads the document, identifies the content structure, and selects suitable Section and Item components from the registry.

It can also inspect the project's component catalogue at /stylesheet/components to understand the available layouts.

Page Builder then creates the page in Webflow and populates the component properties with your content.

Component selection

Page Builder works exclusively with existing closed Section and Item components.

It can select between available layouts, configure their properties, and combine them to build a complete page.

If the content requires something that isn't supported by the available components, the agent asks for an alternative component mapping or reports the limitation.

It doesn't create new components or introduce custom styling to reproduce a missing layout.

4. Review the build report

After building, Page Builder provides a report describing what it created.

This includes:

  • The new page and its URL slug.
  • The components used to assemble the page.
  • Editorial changes made to the original document.
  • Content that was combined, shortened, or reorganized.
  • Any limitations or items requiring manual attention.

This allows you to review the agent's decisions without comparing every sentence against the original document.

The page remains a draft and is not published automatically.

5. Review and refine

Open the draft page in Webflow and review the result.

Check that the selected layouts suit the content, the text reads naturally, and the images and links are correct.

Page Builder will use existing placeholder images. These should be replaced before publishing.

You can make adjustments directly in Webflow Build Mode. Because Page Builder uses closed components, marketers can edit the exposed content and properties without changing the underlying layout structure.

Once you're satisfied with the result, the page can be published through Webflow.

Working within SML

Page Builder uses the closed components already defined in your project.

It doesn't create layouts from development components or generate new design rules. The available Section and Item components determine which layouts the agent can use.

This keeps AI-generated pages consistent with the site's established design, while allowing marketers to create and manage pages without rebuilding layouts manually.