The My Landing Pages table presents several pieces of information that describe different aspects of the Landing Page.
It is important not to treat Publish, Domain, and Template as the same type of status.
| Information | What It Describes |
| Publish | Whether the Landing Page's saved publishing state is enabled or disabled. |
| Domain | Which public domain value is associated with the Landing Page's current domain mode. |
| Template | The starting Template relationship associated with the Landing Page when that Template can be resolved. |
The Landing Page model stores publishing state in the is_publish value.
When that value is enabled, My Landing Pages displays:
Published
This indicates that the Landing Page's saved publishing state is enabled.
When the saved publishing value is disabled, the My Landing Pages interface displays:
Not publish
This is the application's current user-interface wording for a Landing Page whose saved publish flag is not enabled.
A Landing Page can have a domain value while its publishing state is still a separate setting.
Seeing a generated subdomain or custom domain in the table does not by itself tell you that every publishing-related requirement has been completed.
Always review the Publish indicator independently from the Domain column.
New Landing Pages receive a generated subdomain during creation.
When the Landing Page uses the application's subdomain mode, My Landing Pages displays that generated subdomain in the Domain column.
The initial generated value is created from a random string combined with the application's configured domain.
AIUNIFY Funnels also supports a custom-domain mode.
When that mode is selected and a custom domain has been configured, the My Landing Pages Domain column displays the custom-domain value instead of the generated subdomain.
Custom-domain configuration and required DNS information are covered in Chapter 22.
Changing the domain mode does not mean that you should stop checking publishing state.
Before distributing a public Landing Page address, confirm both:
Landing Pages created through the standard template workflow store the selected Template identifier.
When the associated Template relationship can be resolved, the My Landing Pages table displays the Template's saved Name.
If the Template relationship does not provide a Template Name, AIUNIFY Funnels displays:
None
This does not automatically mean that the Landing Page has no page content.
During normal creation, template HTML and CSS are copied into the user's Landing Page record. The Landing Page can therefore retain its saved Main Page and Thank You Page content independently of whether the Template column can currently display a Template Name.
The system Template is the starting source used when the Landing Page is created.
After creation, your Landing Page has its own saved page-content fields and can be edited through its own Builder.
Do not assume that later changes to a system Template automatically rewrite an existing Landing Page.
Before using a Landing Page publicly, review the table from left to right:
| Incorrect Assumption | Correct Interpretation |
| A Domain value means the page is automatically Published. | Domain and Publish are separate Landing Page values. |
| Published means the custom domain is configured correctly. | Publishing state does not verify external DNS or custom-domain configuration. |
| Template = None means all page content is empty. | The Landing Page can contain its own copied and edited page content even if the Template relationship is unavailable. |
| The Template remains the live editable page. | Your user Landing Page is a separate saved record that is edited through its own Builder. |
Operating principle: Treat Publish, Domain, and Template as three separate pieces of information. Verify each one for the purpose it actually represents.