How to generate a page with AI and keep your brand

Ask most AI builders for a landing page and you get a finished website: someone else's sections, someone else's spacing, a palette that is nearly your blue. Changing it means fighting it, so the page either ships slightly wrong or gets rebuilt by hand — which is the work you were trying to skip.

Aglyn AI starts from the other end. It builds a draft, from your own theme, your own layout and the components your site already has, and it hands that draft to you. It never publishes, never changes a live page in place, never registers an address on your live site, never touches your navigation and never sends anything. You publish, with the same button you always use.

Rolling out — Aglyn AI is a release-flagged feature, currently being rolled out — generative building does not appear in every workspace yet. Aglyn Assist, the assistant that answers questions about the product, is available today.

Why prompt-built pages drift off-brand

A generator drifts when it has nothing of yours to build from. Given only a sentence, it invents: a color close to your primary, a card it wrote itself rather than the card you already use, a heading that reads like every other page it has produced. None of that is a model failing to try — it is a model with no material.

So the material is the whole design. Before it generates anything, an Aglyn AI build job proposes a plan: what it will reuse from your site — components, layouts, templates, forms, datasets and collections — what it will create and why nothing you already have will do, and the sections of the page in order. You read the plan and confirm it, or cancel. Nothing is generated until you do.

Seventeen building rules hold the draft to your site rather than to a house style, and they are checked rather than suggested: every plan and every generated document is held to them before you see it. The ones that keep a page on-brand are worth knowing by name.

• Colors, spacing and type come from your theme — never a fixed color value. A color your theme lacks comes back as a proposed theme change for you to review, not as a hex code baked into a section.
• Repeats become one reusable component. A block that appears three or more times is built once and placed as instances, and the job looks for a component you already have before it makes one.
• Site-wide regions live in the layout. A generated page sits in your header, navigation and footer. It never carries its own copy of them.
• Start from a duplicate of the nearest thing. Where your site has a similar screen, the job starts from a copy of it, which keeps its bindings and its SEO.

An answer that breaks a rule is not used. The job asks once more, naming the rules that were broken; if the second answer still breaks one it stops and shows you which.

The brief that works

A good brief is four things, and it is shorter than you think.

Who it is for. Not "customers" — "facilities managers at mid-size warehouses who have just had a compliance failure."

The offer, and the one thing to do next. One call to action beats three. A page that asks a reader to book, subscribe and download is a page that gets none of them.

Tone, in a comparison. "Plain and unhurried, like a good instruction manual" gives more than "professional." The copy follows the tone of what is already on your site and the brief you gave, and it never ships lorem ipsum or a sentence cut off partway.

Three facts you actually have. A price, a turnaround time, a place, a guarantee. This is the part people skip, and it is the part that decides how much of the page you rewrite afterward: where the brief leaves a fact out, the draft marks the gap in square brackets rather than inventing one. That is the correct behavior, and it is also a list of holes. AI jobs lists those gaps beside the draft so you can fill them before you publish.

Book demos from facilities managers who have just failed an inspection. Plain and unhurried. We audit in 48 hours, we have done 400 warehouses in Texas, and the first audit is free. One action: book a walkthrough.

You can also pick a page type — Landing, About, Pricing, Contact, Blog index, Product, Service or Event — so the job knows what shape of page it is writing.

Generate the draft

Open Screens for the site and choose Describe it, beside Templates and Create New Screen; you can also start one from Describe a page in AI jobs in the Assist panel. Write the brief in the one box and choose Plan the page.

Read the plan. It names the layout the page will render in, the components and forms it places, anything it needs to create first, the page's address and search title, and its sections top to bottom — with what the whole job is estimated to use beside the button that confirms it. If the plan is wrong, this is the cheap moment: cancel and rewrite the brief rather than editing a finished page into shape.

Confirm, and the job builds anything the plan creates first — a layout, a form, a reusable component, each as its own draft — then builds the page one section at a time in the background. You can leave the Screens page while it works.

What comes back is a new screen with no address on your site. It is not in your navigation, your sitemap or your site search, and visitors cannot reach it. It does have a layout, an address ready to take, a search title and a search description written from the page's own text. Pictures arrive as image slots with a description of what belongs there, for you to fill from your media library — generated pages never link an image from another website, and every image it does place has alt text or is marked decorative.

Edit it on the canvas

The draft opens in the Besigner like any other screen, because it is one. There is no separate AI editor to learn and nothing about the page is locked.

• Text. Select any text element and use Rewrite with AI under the field in the Attributes panel — a headline, body copy, a button label, a caption. What you apply is an unsaved change on the version you have open, exactly like typing it yourself, and one undo takes it back.
• Components. A section the job built inline that you would rather reuse can be promoted to a reusable component and placed as instances.
• Theme. If the draft made you notice the palette, the theme assistant on Setup → Theme proposes values for the theme editor's own controls — colors, font, corner radius, spacing, navigation heights, dark scheme. A hex color you name is used exactly as written, and it reads the colors of your site logo when the logo comes from your media library. Nothing changes until you save.

On the version your live site is already showing, the Besigner asks you to make a new version before it lets you edit. Take it — that is the habit that makes all of this safe.

Write the search listing

A page nobody finds is a page that did not ship. The screen's detail page has an SEO card with a Write with AI section: add target keywords if you have them, press Write SEO, and read the proposal.

Each value shows its length against the field's limit. The listing is written from the version you are looking at, in the language of its text; it does not invent a fact, a price or a claim the page does not make, and it does not reuse a title another page of your site already uses. Press Put in the fields, check them, press Save SEO.

Alt text is a separate thing and it is already handled: every image the job places carries alt text or is marked decorative, by rule. The image slots you fill yourself are the ones to check.

When the page is live, Setup → SEO has an SEO audit that runs over the published pages your sitemap lists and returns a finding with a proposed fix for each — missing or duplicate titles, a description over the limit, a thin or repeated `h1`. See AI SEO for your website for what it checks.

Publish, then measure

Publish the draft from the Besigner, the same way you publish anything. Add the navigation entry the job suggested, once you want the page found. Then give it a couple of weeks and read it: the audit for what is structurally wrong, your analytics for whether the one action you asked for is the one people take.

The checklist

• The brief names an audience, one offer, a tone and three facts you have.
• The plan reuses your layout and your existing components — read it before confirming.
• Every square-bracket gap in AI jobs is filled.
• Every image slot is filled from the media library, with alt text.
• No fixed color values. The page uses theme tokens, and any new color went through the theme editor.
• The search listing is under 60 and 155 characters, and neither value duplicates another page.
• One `h1`, with headings stepping down in order.
• Checked at phone and tablet width.
• The navigation entry added, once you want the page found.

Aglyn AI is an add-on on any paid plan, metered in credits — see Aglyn AI for how credits, caps and allotments work, and how we compare to Webflow if you are deciding between builders.