Build a Page with Webby

Name the page and set its address

Pick a page type from the list — it tells Webby what kind of page this is, and a pricing page is planned very differently from an about page.

Page name is what the page is called. The URL slug is its address, generated from the name as you type; override it if you want something shorter.

Slugs are worth a moment. /pricing outlives /our-pricing-plans-2026, and changing an address later means setting up a redirect.

Say what the page needs to do

Six intents, each describing a job rather than a layout:

• Sell something specific — a product, service or programme page that moves the reader from interest to action
• Get a contact — one goal, a form submitted or a call booked
• Show we delivered — a case study proving outcomes with a real story
• Introduce the business — a homepage, about page or manifesto
• Speak to a specific audience — a page built around one segment's language and objections
• Make a positioning claim — a category-defining page

Choosing one sets a matching narrative structure, which you can still change.

Choose who it is for

Search and add audience segments. Leave it empty for a general audience.

This is one of the highest-leverage fields on the form. A page written for "operations directors at mid-size logistics firms" reads completely differently from the same page written for nobody in particular — different objections answered, different vocabulary, different proof.

Choose what it focuses on

Search and add the products or services this page should feature.

This pulls in what Zyntro already knows about each one — what it does, who it is for, the objections it meets — so you are not re-explaining your own offering in the instructions field.

Attach the assets it should use

Ten kinds of asset can be attached, and they will be woven into the page rather than appended: Images, Videos, Background Videos, Forms, Calendars, Artefacts, Pricing Plans, Products, Curated Resources and Testimonials.

Attaching them here is better than adding them afterwards, because Webby plans around them. A form attached up front gets a section built to lead into it; a form added later gets dropped into a page that was not expecting it.

Pick how the page should flow

Six narrative structures, each a sequence of sections:

• Pitch a Ware — hook, tension, why now, our approach, how it works, proof, offer, close. For service, product and programme pages.
• Capture a Lead — big promise, who it's for, what you get, one credibility beat, claim it. Short and single-decision.
• Prove a Result — subject, before, what they tried, what we did, outcome, how to get the same. The case study shape.
• Anchor the Brand — status quo, the shift, why we exist, what we believe, where to start. For homepages and manifestos.
• Audience Specific — recognition, their world, the gap, the shift, how we fit, proof from peers, the path forward, call to action.
• Category Launch — twelve sections for brands defining a new market.

Each card lists its sections and what it suits, so you can see the shape before committing.

Add anything else, then generate

The last field takes free instructions: specific requirements, a tone to hit, things to avoid. You can reference assets inline by typing @. Leaving it blank is a legitimate choice.

Use it for what the structured fields cannot express — "do not mention price anywhere", "the audience is sceptical of AI, so lead with the human oversight", "keep it under five sections".

Then generate. Webby plans the page and shows you the arc before writing a word of it.