The confirmed AIUNIFY Leads source does not expose a separate website-wide Publish button or a website-level Draft/Published field in the normal Website management structure.
Website content becomes part of the configured public website experience as its Website, Pages, Settings, Languages, and Website Builder sections are saved and made available through the application's public website routes.
Important distinction: Do not wait for a website-wide Publish button that is not present in this deployment. Save the required website components and verify the actual public URL instead.
The Websites workspace exposes a Landing Page URL for each Website.
This is the primary confirmed public destination to use when reviewing the finished Website experience.
When multiple Websites exist in the same workspace, verify that you are opening the Landing Page URL belonging to the intended Website.
Do not rely only on the selected Website name in the administrative workspace. Open the public URL and confirm the content itself.
Website Builder includes a dedicated Section Layout Preview interface.
That preview is designed to help select section layouts. It should not be treated as the final public-site validation.
After selecting a layout, open the Website's actual Landing Page URL and review the complete page.
Website Legal Pages provide a Page URL with controls to copy the URL or open it in a new browser tab.
Use that public Page URL after:
Before reviewing the public Website, save the changes made in the applicable workspace.
This can include:
Before distributing the Website URL publicly, review the complete configuration.
| Area | What to Verify |
| Website | Name, Slug, Category, Theme, Theme Mode, colors, and intended Website selection. |
| Languages | Enabled languages, Default language, translation quality, and RTL behavior where applicable. |
| Website Pages | Page Names, Page Keys, page order, and Show in Header settings. |
| Website Settings | Business identity, contact information, social information, logos, favicon, and SEO fields for each language. |
| Website Builder | Section content, layouts, order, responsive appearance, shared Header, and shared Footer behavior. |
| Legal Pages | Content, Slugs, metadata, Status, Show in Footer, order, and public Page URLs. |
| Custom Code | Custom CSS and Custom JavaScript should be tested for unintended display or behavior changes. |
Do not validate only the Home page.
Open each important Website Page and confirm:
For a multilingual Website, repeat the public review for every language you intend visitors to use.
Check:
The Section Layout selector provides Desktop and Mobile previews, but the completed public Website should also be tested directly at different browser sizes or on representative devices.
Verify navigation, headings, images, buttons, section spacing, and long translated text.
The current deployed routing contains a Primary Website concept, but the confirmed root URL behavior redirects the root request to the administrative login page.
Therefore, do not assume that setting a Website as Primary automatically makes the bare application domain display that Website's Home page in this deployment.
Use the Website's generated Landing Page URL as the authoritative public Website destination unless the deployment's routing is intentionally changed.
The Website Slug participates in the public Website URL.
Changing it after the URL has been distributed can require updating links, campaigns, bookmarks, or other references.
The Website Slug also participates in the Website-specific public language-cookie naming pattern.