Funnel and Website Builder

One page editor produces two different kinds of thing. A funnel is an ordered sequence of pages with a single job: a landing page, perhaps an order form, a thank-you or booking step, maybe an upsell. A website is a set of pages with navigation that visitors wander between. Same blocks, same styling, same hosting: different intent, and the intent should drive which you build.

The useful mental model is that a funnel is a corridor and a website is a building. In a corridor you remove every door that is not the one you want used: no navigation, one call to action, one next step. In a building you give people a map. Most client problems in this module come from building a website when the campaign needed a corridor, or putting a corridor on the home page and wondering why nobody can find the services list.

Everything built here is wired into the rest of the platform by default. Forms create contacts, order forms take payments, booking widgets consume calendars, chat widgets open conversations, and every page can carry tracking. A page built here is not a brochure; it is an entry point to the system.

Structure

• Funnels as ordered steps, each step its own page with its own URL slug
• Websites with pages, a navigation menu and a home page
• Sections, rows and columns, with desktop, tablet and mobile behavior set per element
• Global sections such as headers and footers reused across pages
• Templates: starting layouts, cloning an existing funnel, importing a shared template, and saving your own

Page elements

• Headings, text, images, galleries, video embeds, buttons, dividers and spacers
• Forms and surveys embedded inline or as a popup
• Calendar booking widgets, including a calendar group selector
• Order forms with products, quantity, order bumps and one-click upsell or downsell steps
• Countdown timers, progress bars, accordions, tabs and testimonial blocks
• Chat widget, click-to-call buttons and social links
• Custom code and custom CSS where the design demands it

Behavior and conversion mechanics

• Button actions: go to the next step, scroll to a section, open a popup, submit a form, start a payment
• Two-step opt-ins, exit-intent popups and sticky calls to action
• A/B split testing between page variants with traffic shared between them
• Thank-you behavior: a message, a redirect, a booking step or a download
• Workflow triggers on page visit, form submission, order placed and link clicked

Domains, SEO and sharing

• Custom domain and subdomain mapping, with the DNS records the platform requires
• Page-level title, meta description, slug and canonical settings
• Social share image and preview text
• Sitemap and robots behavior, favicon and tracking code placement in head or body
• Redirects for retired pages, and a 404 destination

Performance and presentation

• Image compression and alternative text
• Font selection and a global color and style palette applied site-wide
• Mobile-specific visibility, so an element can be hidden on small screens rather than squeezed
• Page load behavior for popups, embeds and third-party scripts
• Consent banner placement where tracking requires it

1. Decide funnel or website before you open the editor, and write the single job of the page. If you cannot say what one action a visitor should take, you are not ready to build.
2. Map the steps in order, including the thank-you step and whatever happens after it. The step after conversion is the one most builds forget and the one that decides whether the lead is followed up.
3. Set up the domain first. Add the DNS records, confirm the certificate is issued, and decide whether the site lives on the root domain or a subdomain before any link is shared.
4. Build the global header and footer once, with the client's real contact details, and reuse them. Scattered one-off footers are how out-of-date phone numbers survive for years.
5. Define the color palette and fonts globally rather than styling each element. A later rebrand then takes minutes rather than a day.
6. Build the desktop layout first, then go through every element in the mobile view. Most of this traffic is mobile, and the mobile layout is where unreviewed builds fall apart.
7. Place the form, booking widget or order form before you write the copy around it. The conversion element is the page; the copy supports it.
8. Wire the form to the right fields, including consent capture, and submit a real test entry to confirm the contact is created with the tags you expect.
9. Configure the thank-you step with something useful on it (a booking widget, a download, a clear next instruction) rather than a message nobody reads.
10. Attach the workflows: form submission to immediate response, order placed to fulfillment and receipt, page visit to retargeting tags where that is wanted.
11. Fill in the page title, meta description and social share image for every page. A link pasted into a message with no preview image looks broken.
12. Compress every image and add alternative text. Page weight is the most common cause of a poor conversion rate that the client blames on the copy.
13. Add the tracking and consent setup, then verify with the network's own diagnostic that events fire where they should and not before consent.
14. Test the whole path on a real phone on mobile data, not only in a desktop preview: load speed, scroll, popups, form keyboard behavior, payment step and confirmation.
15. Set up redirects from any old URLs the client already has in circulation, and check the 404 destination is a page with a route back into the site.
16. Publish, then re-test every link and every form on the live domain. Pages behave differently once they leave preview.
17. If you are split testing, change one thing at a time and leave it long enough to mean something. Two variants that differ in five ways teach you nothing.
18. Document which funnel serves which campaign, and give pages names a stranger can interpret. Unnamed clones are the reason agencies cannot find their own landing pages.

Pages are where traffic lands, so this module sits directly beneath the ad manager, the social planner and the blog, and directly above forms, calendars, payments and workflows. It is also where tracking is installed, which makes it the single point on which attribution either works or quietly does not. In a typical build it is the first module constructed and the last one to stop being edited.

Campaign landing page to booking

A single-step funnel page carries one headline, one proof section and a booking widget. There is no navigation to wander into. The booking triggers the confirmation and reminder workflows, creates the opportunity, and reports the conversion back to the ad network. The page exists to produce appointments and is judged on nothing else.

Order form with an upsell

A funnel runs landing page, order form, one-click upsell, thank-you. The order form takes payment through the connected processor, the upsell is accepted without re-entering details, and a workflow sends the receipt, grants access to the product in Memberships and creates a fulfillment task. Reporting reads the order value against the campaign that produced it.

Full website with service pages

A website holds the home page, service pages, an about page and a contact page with navigation between them, plus the blog. Each service page carries its own form and its own booking calendar for that service, so an inquiry arrives already labeled. The chat widget sits on every page and lands in the shared inbox.

• Changing a page slug breaks every link to it. Ads, printed material, social posts and email templates all keep pointing at the old URL. Add a redirect at the same time as the rename, every time.
• Global sections are global. Editing a shared header changes it everywhere, including on pages a client is currently sending paid traffic to.
• Mobile layout does not inherit as expected. Padding, font sizes and column order frequently need separate treatment, and an unreviewed mobile view is the most common defect in published builds.
• Page weight kills conversion. Uncompressed hero images, autoplaying video and several third-party scripts turn a good page into one that is abandoned before it renders on mobile data.
• Custom code is fragile. It can break the editor, conflict with the platform's own scripts, and silently stop working after a platform update. Keep it minimal and documented.
• SEO on a funnel page is usually a mistake. Thin, duplicated campaign pages indexed alongside a real website dilute it. Decide deliberately what should be indexed and exclude the rest.
• Duplicating a funnel copies its wiring. The clone can point at the original's forms, calendars, products and workflows, so a test edit reaches a live client's build. Re-check every element after cloning.
• Split tests need traffic. On a page with a handful of visits a week, a difference means nothing. Running a test on thin traffic is worse than not testing, because people act on the noise.
• Popups and exit intent behave differently on mobile. Exit intent in particular barely exists on touch devices, and an aggressive popup can make a page unusable.
• The DNS and certificate step is where go-lives slip. Propagation, an existing site on the same domain, and email records that must not be disturbed all need planning rather than discovery on launch day.
• Moving an existing website onto the platform loses what you do not migrate. Existing rankings depend on URLs, titles and content being carried across, and redirects being in place before the switch.
• Forms without consent capture create unusable contacts. The record exists but cannot lawfully be marketed to, and nobody notices until a campaign is built on the list.
• A thank-you page with nothing on it wastes the warmest moment. That is the one point at which the visitor is certain to be paying attention.
• Published is not tested. Preview rendering, tracking behavior and payment steps can all differ on the live domain. Re-test after publishing, not before.
• Accessibility is usually an afterthought. Low-contrast text, images with no alternative text and forms without labels exclude real customers and create legal exposure in some sectors.