How to add a new landing page to your Webflow site with AI

Yes. You can build a landing page on your Webflow site with AI in two ways: with Webflow's AI Assistant inside the Designer, or with an AI marketer that works on your site through Webflow's connection and does the whole job, from the brief to the publish.

Doing it by hand in Webflow follows a familiar path. You add a page in the Pages panel, either blank or as a duplicate of an existing page, and give it a slug, which is the part of the address after your domain, such as /webinar. You build the sections from your site's classes and components, or from a template, and add a form with its fields and a submit button. Then you open the page settings to write the SEO title, the meta description, and the Open Graph title and description that control how the link looks when someone shares it. Finally, you publish to Webflow's staging address to check it, and then to your custom domain.

Webflow's AI Assistant speeds up the building part. You describe a section, and it generates one styled with your site's classes. That still leaves the parts that decide whether the page works: knowing which campaign the page serves, writing copy that matches the ad or email in the visitor's last click, settling the one action the page asks for, filling in the page settings, deciding whether the page should show up in search, and publishing without shipping someone else's half-finished edits.

That's the real work in this job. A good result is a page that a visitor from the campaign recognizes within a couple of seconds, that looks like it belongs on your site, that asks for one thing, and whose conversions you can trace back to the campaign.

Kite does that work for you. It writes the page from your campaign and your brand, builds it directly in your Webflow site, and publishes it once you've seen it.

Start by telling Kite in Slack what the page is for. A request can be as short as this:

"Build a landing page on our Webflow site for the LinkedIn ads promoting our pricing webinar. The goal is registrations."

Kite is an AI marketer in your Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time you ask for a page, it already knows your positioning, your brand voice, your customers, and what has converted on your site before, because that research lives in your team's knowledge base. So it can propose the headline, the offer, the form, and the address without a long brief. If you've already written the ad or the email, share it in the thread so Kite can match it word for word.

A Webflow workspace owner or admin connects Webflow to Kite through OAuth and approves access on Webflow's own consent screen. Once your site is connected, it appears in Kite's list of your websites next to any sites Kite has built for you.

Kite asks before it publishes a page. You can review the page first and reply in the thread to send it live.

Kite settles what the page has to do before it designs anything, because a landing page is only as good as its match to the campaign behind it. It works out four things from your request and its research:

• The source message. This is the exact ad, email, social post, or event invitation that sends visitors to the page. The page's headline repeats that message's promise in the same words.
• The audience. Kite writes for the people that campaign reaches and handles the objections they're likely to have, not every visitor's.
• The offer. This includes what the visitor gets and any deadline.
• The one conversion. This is the single action the page asks for, such as a registration, a signup, a booked call, or a purchase.

Kite also reads your brand voice, your positioning, and your past conversion findings from the knowledge base. If you haven't said which campaign the page serves, Kite asks, because a page written for nobody in particular converts nobody in particular. When two campaigns make different promises to different audiences, Kite builds one page for each.

Kite reads your Webflow site before it adds anything to it, so the new page fits the site's structure. It reads the site's details, including its custom domains, its webflow.io staging address, and when each one was last published. It also reads the list of pages already on the site.

From there, it chooses the page's title and slug. A slug another page already holds is refused, so Kite picks an address that's free and easy to type into an ad, such as /pricing-webinar. It can also place the page inside one of your site's folders.

Kite then decides whether to start from a blank page or from a copy of an existing one. Copying a page brings across every element exactly as it was, with the same styles, settings, and text. That's a fast start when the site already has a page with the right bones. A blank page is the better start when nothing on the site resembles a focused campaign page.

Kite makes the page look like the rest of your site, because visitors trust a page that's clearly part of the site they meant to visit. In Webflow, every element points to a named style, and that style is shared by every page that uses it. When Kite reuses your site's existing styles, the new page inherits your fonts, colors, spacing, and buttons. It adds its own styling only for parts your site has no style for.

When you want the page to stand apart, such as for an event or a launch, Kite can choose a fresh visual direction from a gallery of strong pages in the same category and record which one it used. Either way, it applies your brand's colors, type, and logo from the design rules in your knowledge base.

Kite creates the page in your Webflow site and builds its content directly, so there's nothing for you to paste in. It creates the page with its title and slug, and it can keep the page as a draft until you're ready. It then builds the page's elements, which include:

• Sections and containers that hold the layout
• Headings, paragraphs, and rich text
• Buttons and links
• Images
• A form with its labels, input fields, and submit button

Kite writes the page in the order a campaign visitor needs it. The promise, who it's for, and the call to action sit at the top. Proof, what happens after the visitor converts, and answers to that audience's main objections follow. The call to action repeats down the page, and Kite keeps the exits to that one action and the links you're required to show, so the page doesn't send visitors wandering. The form asks only for what you need right away, such as a name and a work email, because every extra field costs registrations.

Kite only uses proof you actually have. Customer names, logos, quotes, and certifications come from your own materials, never from invention.

Kite writes the page's SEO title, meta description, and Open Graph title and description, so the page reads well in search results and when someone shares its link. This matters most for a copied page. A Webflow page copy brings no metadata with it, so without this step it would show your site's default title, with no description and no link preview.

Kite also decides whether the page should be found in search. A page made only for one campaign usually shouldn't compete with your main pages for search traffic, so Kite plans to keep it out of search and out of the sitemap, and its report says which of those settings it applied. A page meant to last, such as one for a product or a use case, stays indexable instead.

Webflow doesn't link to a new page automatically. That suits most campaign pages, whose visitors arrive from the ad or email. When a page should also be reachable from your site, Kite can add a link to it from another page, such as your navigation or a related page.

Kite sets up the page so you can tell which campaign brought each conversion. It writes tracking parameters for every link that points to the page, using your team's existing naming when you have one. These are the tags added to the end of a link, such as the source, the medium, the campaign name, and the version of the ad or email. If you don't have a naming convention yet, Kite proposes one and saves it in your knowledge base so the next campaign uses the same names.

It also confirms where the form's submissions go and how the conversion will be counted, such as through your connected analytics product. If nobody has decided where registrations should land, Kite raises it before the page goes live, because a page whose results can't be measured isn't finished.

Kite publishes only when you approve, and it checks what else is waiting on the site first, because a Webflow publish sends every unpublished change live, no matter who made it. If a teammate has half-finished edits open in the Designer, Kite tells you before it publishes rather than shipping their work along with the new page.

A page kept as a draft in Webflow has no web address anyone can visit, so you review it in the Webflow Designer. Kite can also publish to your site's webflow.io staging address on its own, which lets you check the finished page in a browser while your custom domain keeps serving what it served before. Once you approve, Kite publishes to your custom domain.

A Webflow publish is confirmed when it's queued, not when it's done. Kite waits until the domain's own last-published time moves before it tells you the page is live, and it tells you clearly whether the page is staged or live.

When the page is up, Kite posts a summary in the Slack thread where you asked. The summary includes:

• The page's live URL, or where to review it if it's still staged
• The ad, email, or post the page was written to match
• The tracking link to use in each channel
• How the conversion will be measured
• The visual direction the page was built from

From there, Kite can keep working on the campaign. It can write the ads or emails that point to the page, watch how the page converts through your connected analytics, and propose a change to test when visitors arrive but don't convert.

When Kite finishes, your Webflow site holds a new page built for one campaign, and your Slack thread holds everything you need to send traffic to it and measure the result.