AIUNIFY Leads separates the underlying Website Page from the language-specific information displayed to visitors.
A page has one Page Key and one website association, while its displayed Name and Header visibility can be stored separately for each Website Language.
This structure allows one logical page to support multiple translated navigation names without creating unrelated page records for every language.
Website Pages belong to a specific website.
Before creating or editing a page:
From the Website Pages workspace, authorized users can open the page-creation interface.
Page creation is protected by the Website Pages creation permission and may also be affected by subscription-module availability.
The Page Key is the stable URL-friendly identifier used by the public website routing system.
A valid Page Key must:
Example:
about-us
If an invalid format is submitted, the confirmed validation message is:
The page key must be lowercase letters, numbers, and hyphens only (e.g., about-us).
If the Page Key already exists for that website, the confirmed validation message is:
The page key already exists for this website.
Each page translation contains its own Name.
This lets the same underlying page display a different navigation label for every Website Language.
| Example Language | Example Page Name |
| English | About Us |
| Spanish | Sobre Nosotros |
| French | À Propos |
The translated names can differ while the underlying Page Key remains about-us.
Each language-specific page translation contains its own Show in Header setting.
This allows header-navigation visibility to be managed for each language independently.
For example, a translated page can be available publicly while being excluded from the Header navigation for a particular language.
The confirmed page request structure requires page translations and associates each translation with a Website Language.
For each translation:
| Field | Requirement |
| Website Language | Identifies the language belonging to the translation. |
| Name | Required text with a maximum of 255 characters. |
| Show in Header | Optional boolean setting controlling Header inclusion. |
When AIUNIFY Leads creates a Website Page, the confirmed server workflow:
The confirmed successful server response is:
Resource created successfully
Open the page's available Action controls to edit it.
In the confirmed page-editing interface, the Page Key is disabled while editing an existing page. This helps preserve the established URL identity while allowing language-specific page information to be maintained.
During editing, review every language translation rather than changing only the first language shown.
For each configured Website Language:
If the requested Website Page no longer exists when an update is processed, the confirmed controller response is:
Resource not found
Return to Website Pages, refresh the list, and verify that you are working with the correct website.
When a new page is created, AIUNIFY Leads can synchronize existing Header and Footer sections according to the website's shared Header/Footer settings.
This helps new pages inherit the established website-wide navigation and Footer structure instead of beginning without those shared sections.