16.1 The Main Page Editing Workspace

The Main Page is the primary visitor-facing page of an AIUNIFY Funnels Landing Page. After creating a Landing Page from a Template or cloning an existing Landing Page, the Main Page can be customized through the visual Landing Page Builder.

The Main Page and Thank You Page are stored separately. Editing the Main Page does not automatically replace the Thank You Page, and editing the Thank You Page does not automatically replace the Main Page.

16.2 Opening the Main Page Builder

You can open the Main Page Builder from the normal Landing Page workflow.

  1. Open Landing Pages → My Landing Pages.
  2. Locate the Landing Page you want to edit.
  3. Select the Landing Page Name or choose Builder from its available Action menu.
  4. Confirm that Main Page is selected in the Builder.

The normal Builder route without the Thank You Page suffix opens the Main Page editing context.

16.3 Main Page and Thank You Page Controls

The Builder provides page controls for:

Main Page Edits the primary Landing Page content shown to visitors.
Thank You Page Edits the separate page experience that can be used after supported form or payment actions.

Use the Main Page control whenever you intend to change the principal acquisition, lead-generation, offer, registration, or selling experience.

16.4 What the Main Page Saves

The Main Page has its own Builder data. AIUNIFY Funnels saves the Main Page's:

  1. Components
  2. Styles
  3. HTML
  4. CSS
  5. Main Page script information used by supported payment-button components

These fields allow the visual Builder to reload your previously saved Main Page structure and styling when you return later.

16.5 Builder Components

The visual page is composed of Builder components. A component can represent text, an image, a button, a form element, a reusable Block, a payment-related control, or another supported page element.

Select the component you intend to modify before using the available styling or Settings controls.

16.6 Using Blocks on the Main Page

The Blocks panel contains reusable page structures made available to the user Builder.

Blocks are grouped by category and can be added to the current page so that you can start from an existing content structure instead of building every section from the beginning.

After a Block is placed on the Main Page, work with the resulting components just as you would with other Builder content.

16.7 Using the Style Manager

The Builder exposes a panel identified as Style Manager.

Use the Style Manager for supported appearance adjustments on the currently selected component. Depending on the component and available controls, styling may affect properties such as spacing, sizing, typography, backgrounds, borders, positioning, or other visual presentation.

AIUNIFY Funnels saves Builder CSS separately from the page's HTML structure.

16.8 Using Layers

The Layers panel gives you a structural view of the elements contained in the page.

Layers are particularly useful when:

  1. Elements are nested inside other elements.
  2. A small component is difficult to select directly on the canvas.
  3. You need to understand the hierarchy of a section.
  4. You need to confirm which element is actually selected before applying a style change.

16.9 Component Settings and Traits

The Builder adds a Settings area for the traits or configurable properties associated with the selected component.

Available settings depend on the component being edited. Do not assume that every component exposes the same properties.

16.10 Main Page Payment Components

The Main Page Builder supports payment-related components used by supported Landing Page selling workflows.

When the Main Page contains supported PayPal or Stripe button components connected to a product, the Builder prepares Main Page script information that preserves the relationship between those payment controls and their selected Product identifiers when the page is stored.

This payment-specific Main Page behavior is not applied to the Thank You Page in the same way.

Important: A visual payment button is only one part of a working checkout. Product configuration, account-level payment settings, and the visitor checkout flow are covered later in this manual.

16.11 Saving Main Page Changes

The Builder uses remote storage to load and save Landing Page Builder data.

It is configured to save after a sequence of Builder changes rather than treating every individual click as an independent server write.

For an important editing session, use the Builder's available Save control before leaving the page. The explicit Save action requests a Builder store operation and displays the resulting success or error message.

A successful Main Page Builder update is reported by the application as:

Updated successfully

If the update cannot be saved, the Builder can return:

Updated failed

16.12 Do Not Navigate Away Too Quickly

Because the visual editor uses a remote storage cycle, avoid closing the browser tab immediately after significant changes.

Allow the save process to complete, especially after restructuring sections, changing multiple styles, uploading assets, or updating payment-related elements.

16.13 Back and Landing Page Settings

The Builder includes navigation back to your Landing Pages workspace and navigation toward the Landing Page Settings screen.

The control that leads from the Builder toward publishing configuration should not be interpreted as a one-click publish operation. In the confirmed user workflow, it takes you to the Landing Page's Settings area, where publishing and other Landing Page configuration are managed.

16.14 Editing on Mobile Devices

The current AIUNIFY Funnels Builder is not intended for Builder editing on a small mobile viewport.

When the browser width is 768 pixels or less, the current Builder displays:

Builder not work on mobile

Use a desktop or sufficiently wide device for Builder editing. Mobile presentation should still be tested as part of the public Landing Page review process.

16.15 Recommended Main Page Editing Sequence

  1. Open the correct Landing Page in Builder.
  2. Confirm Main Page is selected.
  3. Review the existing page from top to bottom before changing it.
  4. Add or adjust Blocks and components as required.
  5. Use Layers when the page hierarchy is difficult to navigate visually.
  6. Use the Style Manager and component Settings for supported presentation changes.
  7. Confirm form and payment components still contain the intended configuration.
  8. Save the Builder.
  9. Open Landing Page Settings if publishing, domain, form, SEO, payment, or custom-code configuration must also be changed.
  10. Open the public Landing Page and test the actual visitor experience.

16.16 Builder Versus Public Page

The Builder is the editing environment. It should not be treated as the final proof that the page is ready for traffic.

After meaningful Main Page changes, always review the actual public Landing Page to verify that its content, forms, buttons, images, responsive behavior, and conversion path work as intended.

Operating principle: Build the Main Page visually, save deliberately, and validate the final visitor journey on the public Landing Page.

Write Your Comment