Landing pages
Hosted pages to point an ad or a link at — with your forms on them, live product prices, and a report showing which traffic converted.
A landing page is a hosted page you build in Nectazo and point traffic at — an ad, a link in a bio, a QR code on a flyer, or a button in one of your own emails. It lives on a Nectazo address, it can carry one of your forms, and it counts its own visitors so you can see which of your links actually worked.
Pages are on Starter and above. See plans and limits for how many each plan includes.
Building one
- 1Go to Pages and press New page. You start with one section.
- 2Add blocks from the panel on the left. Drag one onto the page to put it exactly where you want, including inside a particular column. While you drag, every section and column is outlined: the one you are over is highlighted, and pointing at an existing block shows a line on the edge it will land on. Clicking a block instead drops it at the end of the section you are looking at.
- 3Click a block on the canvas to edit it in the panel on the right. Headings and paragraphs can be typed into directly, with a small toolbar for bold, italic, underline, links and colour on the part you have selected.
- 4Every selected block has a set of tools beside it: drag to move it, duplicate, rewrite with AI, and delete.
- 5Check it at all three widths using the screen icons at the top, then press Publish.
Building one with AI
Build with AI, at the top of the editor, writes a whole page from a sentence about what it is for. Say who it is for and what you want them to do — the more specific the brief, the less generic the page.
The AI decides which sections the page needs and what order they go in: a hero, a feature grid, text beside an image, a gallery, your products, a signup form, a closing call to action. What each of those looks like is not up to the AI — the layout is ours, so a generated page comes out looking like the rest of your pages rather than like a template.
- Images are generated for the sections that want one — the hero, anything beside text, a gallery. You set how many at most and at what quality, and the cost in tokens is shown before you start. They are drawn in your brand's colours if you have set them under Settings.
- Products are chosen by you, not by the AI. Pick them in the dialog and it writes the words around them; the prices still come from your catalogue when somebody loads the page.
- Buttons come through without links. A brief rarely says where a button should go, and an invented link is worse than an obvious blank to fill in.
What comes back is a starting point. Nothing is saved until you press Save, so you can generate, look, and try a different brief without losing anything — but applying a result replaces whatever was on the canvas.
Sections are the frame
Everything else sits inside a section, and the section is what makes a page look like a page rather than an email. It carries the background — a colour, a gradient, or a photograph with an overlay over it so text stays readable — and it can run that background to the edge of the window while the words inside stay within a comfortable measure.
- Full width paints to the edge of the screen, with the words still held inside the content width. Boxed draws the section as a card instead, with a margin around it and rounded corners you can set.
- Pattern lays a texture over the background — dots, a grid, lines, diagonals or honeycomb — with its own colour, size and strength. It sits over the background rather than replacing it, and a few percent of strength is usually all it wants. Size scales the tile without thickening the lines, so a large honeycomb stays as fine as a small one.
- Inner width is how wide the content may get inside that section. The page's own content width, under Page, is the default.
- Minimum height plus vertical position is how you get a tall hero with its words centred in it.
- Overlay strength on an image background is the control worth reaching for first. A photograph that looked fine on its own will usually swallow white text until you put something between them.
Blocks
| Block | What it does |
|---|---|
| Section | The container everything else goes in. Background, pattern, full width or boxed, height. |
| Heading | H1, H2 or H3. The size you set is the size on a wide screen — it scales down on smaller ones by itself. |
| Text | A paragraph. Select it on the canvas and type straight into it. |
| Button | A link. Colours, size, corner radius, and an option to fill the width. |
| Image | Uploaded, dragged in, chosen from your media, pasted as a link, or generated with AI — and croppable once it is there. Width as a percentage, an optional fixed shape, corner radius, and an optional link. An image narrower than the full width goes full width on a phone unless you turn that off. |
| Columns | Side-by-side content that stacks on narrow screens. One to four columns, widths as proportions rather than pixels, and a background behind the block or behind each column. |
| Gallery | A grid of images, each with its own alt text and link. Drag in several at once, pick them from your media, or generate them. Stacks on narrow screens like everything else. |
| Form | One of your published forms, placed on the page. |
| Products | Products from your catalogue, with prices read at the moment somebody looks. Columns, alignment, and control over the title, price and button. |
| Divider | A rule. Colour, thickness, and how much of the width it spans. |
| Spacer | Empty vertical space. |
Putting a form on a page
Add a Form block and choose one of your forms. Only inline and hosted forms appear in the list — a popup or a slide-in is designed to appear over somebody else's site, and does not belong inside a page.
The form is read at the moment the page loads, not copied into it. Change the fields, the button text or the colours in the form editor and every page carrying that form updates, with nothing to re-edit. Everything the form does elsewhere it does here too: double opt-in, the target list, lead magnet delivery, suppression checks and automation triggers.
After submitting, go to sends the person somewhere else instead of showing the form's success message in place. That is set on the block, not on the form, so the same form can stay put on one page and hand off to a thank-you page on another.
Build a second page, publish it, copy its address, and paste that in. You then have a funnel you can measure at both ends rather than a form that quietly succeeds.
Products on a page
The Products block works the way it does in email: you choose products, and the titles, images and prices are looked up when somebody loads the page. Change a price in your shop, re-sync, and the page already agrees — there is nothing to re-edit and no stale price to notice too late.
A page has room an inbox does not, so the grid is a real one: it can be three or four across on a laptop and stack on a phone, which the email version cannot do.
Type and colour
Page — shown in the right-hand panel when nothing is selected — sets the background, text and link colours, the content width, and the typeface. All three typefaces are ones already on the reader's device, so a page never waits on a font download. On a phone opening an ad that is the difference between the words appearing at once and appearing after a round trip.
Checking it before you publish
The three icons at the top of the editor put the canvas at a desktop, tablet and phone width. This is a real change of width rather than a preview picture, so what you see is what the layout does: columns stack, headings shrink, and a hero you thought was fine may turn out to need less padding.
Stack below, on a Columns or Products block, decides when that happens. Phone stacks only on the narrowest screens; Laptop stacks on everything smaller than a laptop.
The address
A published page lives at /p/ followed by a short code and the page's name — for example https://www.nectazo.com/p/k7m2xq9wta/spring-sale. The short code is what identifies the page; the name after it is decoration.
That is deliberate: rename the page later and the old link still works, which matters when the address is already inside an ad you have paid for.
The readable half is yours to set. With nothing selected on the canvas, the right-hand panel has an Address field, and a one-click Use the page name beside it — renaming a page does not move its address on its own, because an address that changed itself would be one you could not rely on. The same panel sets what a search result or a link preview says about the page.
A page reached at a /p/ link is for traffic you send to it, which arrives by the link rather than by searching. Nectazo tells search engines not to index those, so nothing you build here will compete with — or be mistaken for — your own website. Connect your own domain, below, and pages served there are indexable.
Your own domain
You can serve a brand's pages from a subdomain you own, so the address reads go.yourbrand.com/spring-sale instead of a Nectazo link. It is worth doing: an address on your own domain is one people recognise, and search engines credit the page to your domain rather than to ours.
- 1Go to Settings → Domains, find Landing page domain, and enter the subdomain you want to use —
go.yourbrand.com,pages.yourbrand.com, whatever suits. - 2Nectazo gives you a CNAME record. Add it wherever your domain's DNS is managed — usually your registrar, or your hosting provider.
- 3Come back and press Check status. Once DNS has propagated the badge turns to Live, and an HTTPS certificate is issued automatically.
The badge turns to Live as soon as your DNS points here, but the HTTPS certificate is issued a moment later. In the gap the browser has nothing to complete a secure connection with, so it says something like ERR_CONNECTION_CLOSED or “this site can't be reached” rather than showing an error page. Nothing is wrong and there is nothing to fix — wait a minute and reload.
From then on, every published page for that brand is served at both addresses. The Nectazo link keeps working — anything you have already shared or paid to advertise is unaffected — and the page tells search engines that the version on your domain is the real one.
Connect go.yourbrand.com, not yourbrand.com. Your root domain is where your website lives, and pointing it at Nectazo would take your website down. Nectazo refuses root domains for that reason.
One page per brand can also claim the bare domain — what somebody gets if they type go.yourbrand.com with nothing after it. Tick Use as the home page in the Address panel of the page editor; the checkbox only appears once a domain is live.
Connecting a domain does not by itself make go.yourbrand.com show anything. Until one page has Use as the home page ticked, that address answers “This page isn't available” — only the full address with a slug after it, like go.yourbrand.com/spring-sale, works. Only one page can hold it, so ticking the box on a second page takes it from the first.
Disconnecting is safe. Pages stay published and keep working at their Nectazo links; only the extra address goes away.
What the report tells you
Every page has a report covering the last 30 days.
- Visits and unique visitors. A visitor who comes back tomorrow counts twice — see the note on counting below.
- Signups, and the conversion rate against unique visitors rather than visits, so somebody who reads the page twice before signing up does not count against you.
- Where the traffic came from, with a conversion rate for each source. This is the table worth looking at — it is what tells you which ad or post is worth more money.
- A day-by-day chart, and the countries visitors came from.
Tagging your links
Nectazo reads standard UTM parameters. Add ?utm_source=instagram to a link and that traffic appears under “instagram” in the report with its own conversion rate. Without one, the source shown is the site that linked to you, or “Direct” if there was none.
Visits are counted by a small script in the visitor's browser, and visitors are identified by a value derived from their network address and browser that changes every day. Nothing is stored on their device — Nectazo sets no cookie on your landing pages, so they need no cookie banner.
The trade-off is honest: somebody returning across two days counts as two visitors, and two people on the same office network and browser count as one. These are traffic figures for deciding where to spend, not billing figures, and nothing on a page is charged by the view.
Unpublishing
Unpublish takes a page down immediately. Anyone who follows the link sees a short “this page isn't available” message rather than an error, and the report keeps everything already recorded. Publishing it again puts it back at the same address.
What pages do not do
Worth saying plainly, so you can plan around it rather than go looking:
- No custom HTML or JavaScript blocks. Pages are hosted on a shared domain that every brand's email deliverability depends on, and arbitrary code on it is not a risk worth taking.
- No custom domains yet — pages are served on a Nectazo address.
- No A/B testing yet.
- A page is a page, not a site: there is no navigation menu and no multi-page structure. Link pages to each other if you need a sequence.
Something unclear or wrong? Tell us and we'll fix it.