15.1 Website Pages

Website Pages define the public page structure for a selected website in AIUNIFY Leads.

Examples can include Home, About, Services, Contact, or other pages required by the website.

Each Website Page belongs to a specific website and can contain separate translated page names for the website's configured languages.

15.2 Confirm the Selected Website

The Website Pages screen includes the selected website in its breadcrumb.

Always confirm the selected website before adding, editing, reordering, or deleting pages.

15.3 Website Pages List

The confirmed Website Pages table contains:

Column Purpose
Drag Provides the ordering handle used by the page-reordering interface.
Name Displays the page name resolved from its language translation.
Page Key Stores the URL-friendly identifier used for the website page.
Action Contains page-management actions available to the current user.

15.4 Filtering Website Pages

The Website Pages workspace supports filtering by Page Key.

15.5 Adding Pages

Users with the website_pages_create permission or administrative access can use the standard Add Page action.

The same permission area also exposes the AI-assisted page-generation control. AI-assisted page generation is covered later in this manual.

15.6 Page Name and Default Language

The page editor presents the website's Default language first.

The page name entered for the Default language serves as the primary page-name entry during creation.

Each additional Website Language can have its own page name translation.

15.7 Page Key

Every Website Page has a Page Key. This is the URL-friendly identifier used by public website routing.

During standard page creation, entering the Default language page name can generate the Page Key automatically.

The confirmed server validation requires a Page Key to:

  1. Be present.
  2. Be text.
  3. Contain no more than 255 characters.
  4. Use lowercase letters, numbers, and hyphens.
  5. Be unique within the selected website.

A valid example is:

about-us

The confirmed validation message for an invalid format is:

The page key must be lowercase letters, numbers, and hyphens only (e.g., about-us).

15.8 Page Key Uniqueness

Two pages inside the same website cannot use the same Page Key.

If the Page Key already exists for that website, the application returns:

The page key already exists for this website.

15.9 Page Key During Editing

In the confirmed Website Page editor, the Page Key field is disabled when editing an existing page.

This helps preserve the established URL identity of the page while allowing the page's translated names and header visibility to be updated.

15.10 Page Translations

At least one page translation is required when a Website Page is created.

For each translation, the request contains:

Translation Field Requirement
Website Language Required.
Name Required text, maximum 255 characters.
Show in Header Optional boolean setting controlling header-navigation inclusion for that translation.

15.11 Show in Header

Each language-specific page translation contains its own Show in Header switch.

This means header-navigation visibility can be stored with the translated page entry rather than being only a single global property on the page.

15.12 New Page Ordering

When a new Website Page is created, AIUNIFY Leads finds the current highest page sort order for the selected website and places the new page after it.

The Website Pages screen then provides drag-based reordering functionality for adjusting page order.

The detailed reordering procedure is covered later in this manual.

15.13 Home Page Protection

The page whose Page Key is home is protected from deletion by the Website Page controller.

If a deletion request is made for the Home page, the confirmed server response is:

Home page cannot be deleted

15.14 Shared Header and Footer on New Pages

When new pages are created, AIUNIFY Leads checks the website's shared-header and shared-footer configuration.

If the website is configured to use the same header or footer across all pages, the system can copy the applicable Header or Footer section structure to the newly created page.

The system prefers the Home page as the source when locating an existing shared Header or Footer.

15.15 Public Website Routing

Public website routing verifies that the requested Page Key exists for the specified website before displaying the page.

This keeps each website's page structure isolated from pages belonging to other websites.

15.16 Page Creation Subscription Check

Website Page creation includes a subscription-module availability check.

If the Website Pages feature is not available under the current subscription configuration, the confirmed response is:

This feature is not available in your current subscription plan.

15.17 Recommended Page Planning

  1. Confirm the selected website.
  2. Confirm all required Website Languages.
  3. List the public pages the website requires.
  4. Use clear page names and stable Page Keys.
  5. Complete page names for each language.
  6. Choose which translated pages should appear in the header.
  7. Create the pages.
  8. Arrange them into the intended order.
  9. Build the page content in Website Builder.
Write Your Comment