Page Builder

A page is usually the slowest part of a campaign: someone has to design it, write it, build it, and put it somewhere. Here you describe the page in plain language and it builds itself in front of you – already looking like your site, already wired to your customer list.

Find it at Studios → Pages. (Until September 2026 it was called the Landing Page Builder; old links still open it.)

What it builds

Say what the page is for and it builds for that job:

A landing page – an offer, a launch, a demo or call request, a lead magnet. One goal, one call to action repeated where it counts, a lead form.
A hub – a proof hub, a resource centre, a trust page: somewhere buyers come to inspect. The material is grouped under plain headings, each item labelled with what kind of thing it is. Anything you say is not ready yet shows as a marked placeholder, never as made-up content.
A comparison – you against a named alternative, or the old way against the new. The criteria come from what you and your site say; nothing is claimed about a competitor that the material does not support.
An explainer – a methodology, a process, how something works.
An event page – a webinar or a workshop, with its registration form.

When your description names the sections, those are the page, in your order.

From a task. A task whose deliverable is a page has Build the page on its The work panel. It opens the Page Builder with the task's brief already in the description and the kind of page picked from the task's words (a "proof hub" starts as a Hub). The project's own brief rides along as background the page never quotes. Nothing is written until you press Write the page. The page saves to the task as its draft – the task then shows Open the draft – and the back arrow returns you to the task. Work it in Chat is still there if you would rather build it in a conversation.

Building one

Type what the page is for – "a page for our spring collection launch, one clear call to action to the shop", or "a proof hub where buyers can check our approval process" – and it builds section by section. Under the description, Kind of page lets you say which job it is (landing page, hub, comparison, explainer, event); leave it on Any and the description decides.

The page is written in your brand's language (Brand → Profile → Market), so a Czech brand gets a Czech page, form labels and thank-you line included.

Before it writes a word, it reads your website the way a designer and a copywriter would:

How it looks. Your homepage is photographed top to bottom and read for what is actually on screen – background, text and accent colours, the heading face and how big it runs, button shape, how sections are laid out, what kind of pictures you use. The page follows that look, not a template. Exact font names come from your site's own code.
What it says. The whole homepage and the pages your menu leads to (pricing, product, enterprise and so on), the same way Chat reads a site, plus one web search for the page you asked for – so the copy argues from the real thing rather than from a blank prompt.
Your header and footer. Built once from your site – your logo or wordmark, your menu, your footer columns and legal line – and placed around the page. Under Kind of page you choose Your site's, Logo only (nothing leads a visitor away – the default for a landing page) or None.

This is read once per brand and kept for a day, so only the first page waits for it (about a minute). Page → Your site, as pages read it shows what was read – a picture of your first screen, the colours, a line on the look – with Read it again after you change your site, and switches the header and footer on any page, including one made in chat.

Your brand profile needs a website address for any of that to happen. With no site to read, you still get a page – it just arrives in neutral styling. A page asked for in chat reads your site the same way.

The page belongs to the brand it was made for. Switching brands in the header later never moves it; its colours, language and journeys stay that brand's.

Changing it

The page sits in the middle; the panel on the right has six tabs.

Chat – say what should be different ("make the hero shorter and lead with the guarantee") and the page comes back rewritten. Click a section first to rewrite only that one.
Section – every section in order. Open one to edit its words, choose where each button goes (a part of this page, such as the form, or a web address), and replace its images: generate one again, pick one from your library, or upload your own. Move, copy or delete it from the same place.
Page – the address, your own domain, the title and description for search results and shared links, the image shared links show, whether search engines may list it, where leads go, and tracking.
Quality, Review and Results – below.

Add a section above the canvas adds a layout to fill in by hand. Every word in it is a [bracketed] note saying what belongs there; nothing in it pretends to be a real quote, price or number. Undo (⌘Z) steps back through your changes; inside a text field it undoes your typing.

Images: up to three per page, drawn for your brand and placed where the layout reserved room for them, with no words painted into the picture (the page's own copy does the talking). Each one is made at exactly the size its place shows at – twice that, for sharp screens – and the page loads small web copies of it (WebP, in a few widths), not the original; the original stays in your Library. In Section, each picture has a size you can change – what fits its place, a common size, or your own width × height – before you generate it again. A picture from your Library or an upload gets its web copies too. Each generation is billed as an image generation, exactly as anywhere else in the platform. A page from chat keeps its image spots empty until you click Generate images above the canvas; a page made earlier, with pictures shown at full size, gets Make pictures web-sized there – nothing is generated or billed for that.

Saving and going live

A draft saves itself a moment after each change – the header says when. Once a page is live, your edits wait as a draft: the live page changes only when you choose Update live page. More → Take it offline stops the address showing it; the page stays here and keeps its address.

Before it goes live

Quality lists what still needs you: [bracketed] notes left to fill in, buttons that go nowhere or point at something that is not on the page, image spots never generated, a form that would not reach your contacts, a missing description. It advises and never locks – Publish tells you what is open and lets you decide.

Review holds the page's status and comments, the same review your e-mails and texts go through. When your brand approves content before it ships (Brand → Messaging), a page goes live only once it is approved; reviewers are told through the bell and can open the page straight on the Review tab. More → Copy a link for teammates gives your colleagues the page with Review open. Every page also appears in your Library.

Results

Views, visitors, leads and the lead rate for the last 7, 30 or 90 days, where the visits came from (the utm_source of the link, otherwise the site that sent them), what people clicked, and the latest form sends. Looking at a page inside the app – the canvas, the Pages list, a preview – never counts as a visit.

Visitors are counted without cookies and without storing anything in the visitor's browser: a key that changes every day, which cannot be turned back into an address. Visitors are counted from 26 September 2026.

The form is a real form

The lead form is not decoration. A submission goes straight into your customer list, can enrol that person into a journey, and lands as a lead event in your warehouse – so the follow-up email can fire the moment someone fills it in, and the page appears in the same funnel and attribution as the rest of your marketing.

Page views, call-to-action clicks and form submissions are tracked with their UTM parameters and referrer, so you can see which source actually converted. That holds wherever the page lives – on our hosting, on your domain, or as a file on your own site.

Only a live journey of the page's own brand can be chosen under Page → Leads, and a form only ever enrols people into that brand's journey.

A consent box on the form is yours to switch on, and off until you do. You write its words; each lead keeps their answer and the exact text they saw. With the box on, only people who tick it join the journey – everyone still lands in your contacts.

What a new lead's answer does. A new lead who ticks your box is recorded as giving e-mail marketing consent, with the page and the words they saw, on their consent history. A new lead who leaves it unticked – and every new lead of a page without a box – starts as "Not granted": service e-mails (a journey set to Service) reach them, marketing e-mails do not until they give consent. Someone already in your contacts keeps what they had: ticking the box records their consent, leaving it empty changes nothing. The box speaks for e-mail: a phone number a new lead leaves on the form starts "Not granted" for marketing texts. A lead is matched to your brand's existing contact, whoever on your team added it, so the same person is never created twice.

Google Analytics 4 and the Meta Pixel are optional. Under Page → Tracking you can have the page ask visitors before they load, with a notice you write; they then load only after a visitor accepts. Pixels need your own domain: at our theaicmo.com address the page runs isolated from the app, where pixels cannot set their cookies.

Three ways to put it live

Publish puts the page live on our hosting. To serve it on a domain of yours, add the domain in the builder's Page tab and create one DNS record:

a subdomain (offer.yourbrand.com) – a CNAME to cname.vercel-dns.com
your apex domain (yourbrand.com) – an A record to 76.76.21.21

Verification and the SSL certificate happen on their own; the builder shows the domain as pending until DNS resolves, then as active. Nothing here needs anyone at our end to switch it on.

Download (More → Download HTML, or Export on the Pages list) gives you the page as one HTML file to host yourself. Its forms, tracking and your consent settings are built in.

Send to developer is for when someone else runs your website. Enter their e-mail and, if you like, a note – where the page goes, by when. They get one e-mail from The AI CMO with a private link, no account needed. The link opens the page with a preview, the HTML file, and both ways to put it live: on your own site, or on a subdomain pointed at us – with the exact DNS record when you have already connected a domain. Their replies come to you.

The link works for 30 days and always shows your latest save, so a fix you make after sending reaches them. Send it again once it lapses.
Under the form you see every send: who got it, when, and whether they have opened it yet.
When the page was made for a task, the task shows the send too – on its The work panel and in its activity.
You can send up to 20 hand-offs a day.

When your own team builds the page

Some teams build their pages themselves. A task whose deliverable is a page – one a plan made for the Page Builder, or a landing page by its type – has Send the brief to your developer beside Build the page on its The work panel. They get one e-mail with a private link to the brief: what the page is for, what goes on it, the project behind it, the due date and the task's reference links, with Copy the brief to take it into their own tools. Nothing is generated and no credits are used.

The link shows the task as it reads now, so an edit to the task reaches them, and it asks them to reply with the page's address once it is live. The panel shows the send – who got it, when, whether they opened it – and the task's activity records it. A page the Page Builder made for a task travels with the brief it was built from.

Worth knowing

The copy is machine-written. Read it before you point paid traffic at it.
Prices, guarantees and testimonials appear only if they came from you or from what the research found on your own site. Nothing is invented to fill a section.
A page asked for in chat is written from the same reading of your site as one built here, and opens here for editing.
Pages on our theaicmo.com address run isolated from the app, so a page's own code can never reach anyone's signed-in session.