The generate-from-brand-DNA flow - a client intake questionnaire, a brand and keyword-grounded page plan, copy written in the client's voice, honesty gates, and the review checkpoints before you deploy.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Generating is one of the three ways to fill a new client site. Instead of porting an existing site or cloning a live one, you build a fresh site from the client's brand inputs. This is how you deliver a site to a client who has no website worth keeping, or none at all.
The output is a set of draft pages built from real builder sections, written in the client's voice, structurally unique to that client, and checked for honesty as it is saved, with anything unsupported flagged for your review. You review the draft and finish it in the builder, then deploy.
You invite the client, they receive a link to a guided intake questionnaire, and they fill it in themselves: their business details, brand, proof points, and the voice inputs that make the copy sound like them. Their answers drive the generated site directly.
Start one from Intake in the operator sidebar: enter the business name, press Start intake, then Send intake link. The link is emailed to the client when a contact email is on file and your mailer is set up, and it is always shown on the board so you can copy it and send it yourself.
It works both ways. The client can complete the questionnaire on their own, or you can walk them through it on a call or fill it in on their behalf when that is easier. Either way the answers feed the same brand-and-plan pipeline, the client only ever supplies inputs and approves a couple of checkpoints, and they never touch the live site.
Operators also have a shortcut. Generate in a site's sidebar opens the Generate from brand DNA form, where you type the business details in yourself. It drafts a starting Home, About, Services and Contact page, a page for each service, and a local page per area for a multi-location business, and flags any page with content-check errors for review. It skips the client checkpoints, the voice profile, the honesty gates, and the variance engine described below, so use the intake when the client should approve the brand and the plan.
A generate run moves through the same stages, whether the client filled the questionnaire themselves or you completed it with them:
The client fills in the raw material a good site is built from:
Those last "How you talk" inputs are what let the platform write the copy in the client's voice rather than a generic template register. See Copy in the Client's Voice.
Generated copy is written to sound like the client, from the voice inputs above and, optionally, from the tone of the writing already on their own site and in their Google reviews. Harvested writing only ever informs tone; it never becomes a quoted phrase or a stated fact. The full mechanics are on Copy in the Client's Voice.
Two clients in the same trade on the same template pack would otherwise receive a recognizably identical site. The variance engine gives each site built through the intake its own structure - column sides, band colors, spacing, typography scale, grids, image treatment, and photo selection - within brand-safe, accessibility-checked bounds, and re-rolls any build that comes out too close to one you already made. See Never the Same Site Twice.
Generated copy is checked before the draft is handed to you. A claim the client did not actually give you does not stop the build: the pages are still saved as drafts, and each finding is listed on your review board with the page and block it sits in, so you fix it before publishing rather than discover the fiction on the live site.
Flagged unless the client supplied it:
| Claim type | Examples | Rule |
|---|---|---|
| Fabricated stats | "17+ years", "since 1998", "over 500 homes served" | A number-shaped claim must trace to a real fact the client provided, or it is flagged |
| Rating and award proof | "5-star rated", "top rated", "award winning", "A+ BBB rating" | A rating or accreditation claim must be a proof point the client actually supplied |
| Superlatives | "the best plumber in town", "unbeatable", "#1 in the area" | A market-superiority boast is allowed only when the client typed it themselves; any other is flagged |
Also enforced on the built-in template packs:
seedly template-qa) look for this in every pack, including one you add yourself, so a generated site does not route a client's leads to someone else's inbox or quote a stranger as a happy customer.Advisory checks (never block, always surface):
You decide what to do with an advisory at the review board; the hard gates decide themselves.
Beyond writing copy, the build makes structural decisions that keep a generated site coherent, especially a multi-location one:
{{location.*}} token on it resolves correctly from the first render.These rules are ordinary code in the platform you own, not fixed behavior behind an API. They reflect one opinionated way of building local-service sites: locally scoped cross-links, per-city bindings, a services grid that grows. If the sites you build want different wiring, say a portfolio agency that wants global cross-links, or single-location builds where the binding logic is irrelevant, the build pipeline is in your source to adjust, the same way you would adjust anything else you own. Change it in the source with your own development workflow; the AI agent API edits page content, not the build pipeline.
Like every content flow, generation never publishes and never deploys. The finished site lands as drafts on your operator review board, honesty-gated and variance-checked, waiting for you to review, finish in the builder, and deploy. A generated site cannot reach a visitor without an operator pressing Deploy.
| Question | Answer |
|---|---|
| Input | An intake questionnaire the client fills in, or that you complete with them |
| Output | Draft pages in the client's brand and voice, unique to that client |
| Copy | Written in the client's voice, honesty-gated against fabricated claims |
| Uniqueness | Structurally varied per client and re-rolled if too close to a prior build |
| Publishes anything? | Never - drafts only, you review and deploy |
| When to use it | A new client with no site worth porting |