Email it to the client and ask for their logo back with
it.
Plain questions in plain language: their business, their hours, their
two brand colors, their services, their towns, three real reviews and
their story. Everything the site says comes from their answers, so a
blank here is a blank on the page. The last question asks whether they
are in a regulated industry; if they say yes, stop and check before
building, because the standard privacy policy and terms do not cover
health, lending, insurance, tax, legal, credit repair or addiction
treatment.
Drop the client’s answered questionnaire into the panel below, as a
Word document or as plain text, and Zap fills the whole sheet from it.
Four values are not part of this step and are entered in step 4
instead: the Google tag, the conversion event, the Meta pixel ID and
the lead endpoint. The pixel is the ID on its own, not the code block,
because the ads pages load it after first paint.
What lands in the box is a run of lines like BUSINESS_NAME:
Ridgeline & Cedar Homes, one per line; anything not shaped
like that is ignored. You can also paste or drop a sheet straight into
the box, which is how you reopen a site you built before.
Anything wrong with the sheet is listed under the box with a Fix button
beside it, and fixing it rewrites that line in the box, so the sheet you
export carries the correction. Two things are held separately, under
Approve before building: a value the questionnaire did not cover, which
Zap wrote and marked as invented, and a service or service area that had
to come off to fit the grid. Neither is a mistake, and neither is yours
until you have read it, so the build stays locked until you approve them.
Colors
From the questionnaire. Zap builds the rest of
the palette from these two. Change them here if the client’s colors need adjusting.
Content
Photographs
both optional
Codes
read the sheet first
https://
No build sheet loaded.
Meta Pixel
Reports visits and leads to Meta Ads.
Not set
Events
Every page reports a PageView. An event marks a page as a step toward a lead.
Tracking Codes
Scripts from Google, Meta and other services, in the order they load.
Embed Sections
A Google Map or a review widget shown as its own section.
Build
Three things come out of a build and each one is worth keeping.
The pages. One HTML file each. Create the page at the address on
its card, set the page name and the URL slug, then paste the file in as
an HTML block.
The delivery sheet. A document listing every file, the exact
address it belongs at, its page name, its URL slug, its title tag, its
meta description and whether to index it. A site builder serves those
last three from its own settings and ignores the copies inside the
file, so this is where you type them from. Four addresses cannot
change: the home page, /thank-you/,
/privacy/ and /terms/.
Every form and every footer builds its links to those from the domain
and nothing else, so a page saved elsewhere will not look broken, it
will simply send people nowhere.
The build sheet. Every value this site was built from, in the
same format step 3 reads. Save it with the client's other files. When
they change their phone number, rewrite a service or pick a new color
six months from now, open it, edit that line, paste it back into step 3
and rebuild. You never fill the questionnaire twice for the same
client, and you never go back to Claude for a change you can type
yourself.