▤ COMPLETE OMEGA WEB PRO DOCUMENTATION • BUILD • LICENCE • EDIT • DEPLOY

Everything You Need to Understand, Build, Licence, Edit and Deploy with Omega Web Pro.

This is the central documentation hub for the complete Omega Web Pro platform: Universal Website Studio, website specification, AI-assisted planning, blueprints, page architecture, staged generation, Pure HTML and native WordPress production, responsive images, SEO and schema, accessibility, performance, security, Web Metrics, Builder live preview, secure Stripe purchase, monthly/annual/two-year Omega Web Pro Hosting plans, the lifetime domain licence, My Account, the private Website Editor, the Omega Web Pro Hosting Dashboard, staging, production deployment, backups, databases, SFTP, usage controls and licensed ZIP export.

Open Universal Website Studio → Lifetime Licence Guide Purchased Customer My Account

73 industry starting points 111 selectable page types Up to 120 pages per build Pure HTML + WordPress 2 live-preview workflows 14 editor validation responsibilities Lifetime same-domain editing

DOCUMENTATION • ARCHITECTURE • BUILDER • EDITOR • DEPLOYMENT

OMEGA DOCUMENTATION LIBRARY● COMPLETE PLATFORM REFERENCE

Documentation Getting Started Builder Generation Pure HTML WordPress Images SEO + Schema Website Editor My Account Billing Centre Hosting Dashboard Licensing Deployment

✓ Builder documented✓ Editor documented✓ Account workflow documented

Omega Hosting • two dedicated, protected website editors

Separate editing workspaces for Pure HTML and native WordPress websites.

Omega uses the verified website's hosting record, platform and authorised Website ID to select its editor. The Pure HTML and WordPress tools are separate OVHcloud pages, not two modes of the older combined website-editor.php. Sign in through My Account and select your purchased website; do not choose a platform by changing the URL.

Pure HTML Website Editor

dashboard.omegawebpro.com/website-editor.php

Work with the site's authorised HTML, CSS, JavaScript and supporting project files. Use the code editor with Save, Undo, Redo, Find and Replace, a desktop/tablet/mobile sandbox preview, validation, version history, updated licensed ZIP export, Builder-source adoption and guarded Deploy / Update Live Website.

The selected Pure HTML site can also access its eight applicable Omega hosted Website Plugin implementations and compatible third-party HTML add-ons through the editor's website-specific plugin panels. The embedded Omega AI Agent assists with code, validation explanations and reviewable proposed fixes; customers approve and save changes themselves.

Native WordPress Website Editor

dashboard.omegawebpro.com/website-editor-wordpress.php

Work with native WordPress Pages and Posts, their HTML/block content and responsive WordPress preview, plus the integrated WordPress Manager for supported site administration. WordPress engine dashboards, the installed-plugin repository and one-at-a-time plugin administration workspace operate within the authorised editor.

Builder-generated WordPress theme/content changes, validation and live publication follow the WordPress-specific staging and deployment process—not the Pure HTML static-file editor. Saved WordPress database content and a published WordPress theme are distinct operations. The Omega AI Agent is also embedded here for page/code guidance, validation help and controlled, reviewable repair suggestions.

Both editors retain customer/Website ID checks and protected workflows. Each paid Omega Hosting purchase covers one website; only the eight engines appropriate to that website's detected platform apply. Both pages include the floating bottom-right Omega AI Agent for public web research with sources, NativeAI knowledge and planning, six-stage Builder guidance, code explanations, error/log review, website-scoped validation help and staged repair proposals. Customer-specific account, hosting and source assistance require a verified session and authorised Editor context; suggested changes require explicit review, saving and validation before publication, never silent live edits. Lifetime licence editing and licensed ZIP rights are separate from the paid hosting entitlement required to deploy. Hosting, editing, staging and publication remain subject to the selected site's permissions, entitlements and validation checks.

New: lifetime-licensed WordPress editing without Omega Hosting

Private WordPress Website Editor — for WordPress lifetime licence holders without Omega Hosting

A customer who owns a lifetime licence for a WordPress website but does not have active Omega Hosting for that same Website ID uses the dedicated Private WordPress Website Editor. Sign in, select your authorised website in the customer Dashboard, and use its Edit Website action. This is a private project workspace, not a hosted WordPress installation.

Source-code editing: browse and search the licensed WordPress package files, edit supported text source including theme PHP, CSS and other source, save changes privately, reload files, and use code-buffer undo and redo. Binary media remains in the package.
Pages & Posts: select, load and edit the package's WordPress pages and posts as private content drafts, without requiring a hosted WordPress database.
Responsive preview: inspect package markup and theme CSS at Desktop, Tablet and Mobile widths, refresh or expand to full screen, and resolve supported images from the private package. Preview is sandboxed and does not execute WordPress PHP, database queries or plugins.
Website Builder continuation: return to the Website Builder for authorised regeneration, and load the latest Builder-generated WordPress package into the private editing workflow. Changes to a newly generated package still require review and private saving.
Validation and recovery: run offline package-source validation, capture and inspect complete private package checkpoints, review version history, and download the latest edited WordPress ZIP.
Five private Omega diagnostic dashboards: Image, Performance, Security, SEO and Web Metrics; each has independent per-website enable/disable state, an individual selectable dashboard, package reports and downloadable JSON findings. Image inventory/preview and explicit security malware scanning are available where supported. These are private-package diagnostics, not the five original live hosted WordPress plugin services or live visitor analytics.

Three distinct editing paths: website-editor.php is the Pure HTML Editor; website-editor-wordpress.php is for an authorised WordPress website with eligible active, provisioned Omega Hosting (including lifetime-licensed customers who also have that hosting); website-editor-wordpress-private.php is for lifetime-licensed WordPress customers without active Omega Hosting for that website. The Dashboard determines the correct editor from the website's platform and entitlements.

Hosting boundary: a lifetime licence allows the private WordPress project to be edited and its ZIP exported without buying Omega Hosting. It does not include live hosting, public deployment, live WordPress administration, live plugin execution, visitor-traffic metrics or server-side WordPress PHP rendering. Publishing to Omega Hosting requires a separate, eligible hosting entitlement for that same website.

Open your customer Dashboard to select the licensed website. The authorised private workspace is Private WordPress Website Editor (website selection and sign-in required).

73Industry starting points

111Selectable page types

120Maximum pages per build

2Production targets

2Live-preview workflows

14Editor validation responsibilities

Start here

The complete customer lifecycle from specification through billing, hosting, editing and export.

Omega Web Pro is a complete website lifecycle rather than a one-time AI generation screen. The Builder handles specification, generation and preview. A customer then chooses a recurring managed-hosting plan or the separate lifetime single-domain software licence. For a first-time Omega Hosting checkout, Omega saves the selected plan and pending website to one restricted checkout-bound account, sends a secure one-time account-setup email, and requires password setup and sign-in before the required purchase acknowledgements and secure Stripe Checkout; paid entitlement activates only after Stripe confirmation; for a first-time Lifetime Licence purchase, an existing account is reused where available or the account is created after Stripe confirms the purchase. My Account becomes the commercial identity, billing and entitlement centre; active hosting customers can continue into the Omega Hosting Dashboard, while eligible lifetime customers retain same-domain Builder, Website Editor and licensed export rights.

1Specify

2Generate

3Builder Preview

4Purchase Licence

5My Account

6Regenerate or Edit Code

7Validate + Export

New Visitor

Open Builder without purchasing, define the website, generate it and inspect the responsive public Builder preview.

Open Builder →

First-Time Purchaser

Choose Monthly, Annual, Two Years or the US$999 Lifetime Single Website Domain Licence. For a first-time recurring Hosting purchase, Omega first saves the selected plan to a restricted account and sends a secure one-time setup email; after password setup and sign-in, the customer reviews the required purchase acknowledgements and continues to Stripe Checkout. Verified Stripe payment establishes the paid entitlement. Lifetime purchases continue through their separate documented account-creation path.

Purchase & Licence Guide →

Purchased Customer

Use My Account to manage licences, reopen Builder, edit licensed source code, resume or delete pending checkout orders, view paid purchase history and manage account security.

Open My Account →

Two paths after preview: a managed hosting subscriber proceeds through verified billing, website provisioning, domain connection and ongoing live editing; a lifetime single-domain licensee keeps the separately purchased same-domain regeneration and portable ZIP rights. A WordPress hosting customer additionally receives a separate site-owner setup email. Follow Plans & checkout, WordPress provisioning and Live WordPress editing for the complete sequence.

Universal Website Studio documentation

The Builder creates an authoritative website specification before Omega generates the project.

The customer can begin with a short idea or provide a detailed professional specification. Explicit Builder choices are requirements; Auto choices can be resolved through the assisted planning layer.

Industry + Business

Choose from 73 current industry starting points, select multiple relevant industries where appropriate, or define a custom industry and sub-industry.

111

Page Architecture

Select from 111 selectable page types plus custom requirements across business, commercial, ecommerce, content, support, legal, campaign and utility needs.

Repeatable Page Systems

Services, locations, products, case studies, team members and articles can expand structured lists into individual generated pages.

120

Build Limit

The current browser and server generation paths enforce a maximum of 120 generated pages per website build.

50K

Professional Brief

Provide up to 50,000 characters of project requirements, background, business rules, exclusions and detailed production instructions.

🎨

Design System

Control theme, colours, typography, content width, spacing rhythm, corners, shadows, backgrounds, header, navigation, mobile menu, hero, cards, imagery, gallery, buttons and motion.

✉

Generated Features

Request secure contact forms, newsletter sections, booking/quote CTAs, search UI, galleries, testimonials, catalogues, pricing tables, analytics hooks, cookie banner shells, RTL and multilingual-ready structure.

ZIP

Supporting Material

Controlled TXT, Markdown, HTML, HTM, XML and ZIP source material can supplement—but does not silently replace—the authoritative Builder specification.

Production target rule: one shared specification feeds one renderer per build. The customer selects either Pure HTML or WordPress for that generation. The lifetime licence itself includes rights to generate either supported platform later for the same permanent domain.

Full field-by-field reference: Builder Documentation and Website Specification cover business, pages, design, content, media and advanced controls. The Blueprints guide explains design systems. Supporting documents augment the project specification; they do not silently override customer-specified choices.

ARCHITECTURE & PROJECT BRIEF

Turn your requirements into an accurate, reviewable website specification.

Use the six-stage Builder—Business, Pages, Design, Content, Media and Advanced—to record what the business does, who the audience is, what must appear on each page and which production platform to use. User-specified requirements outrank automatic suggestions. The architecture and design system should be reviewed before generation.

Business context and audience

Document the organisation, industry, location, services, products, customers, objectives, brand terminology, legal constraints and credible source facts.

Information architecture

Select page types and required sections, define menus and hierarchies, and use repeatable Services, Locations, Products, Case Studies, Team and Article systems where relevant.

Design direction

Select from the 73 industry starting points and configurable style choices; specify typography, colours, layout, navigation, hero, cards, imagery, component behavior and responsive priorities.

Content, media and source files

Provide a professional brief up to 50,000 characters and supported reference files; supply a separate logo and appropriate content images. Never submit credentials or other unnecessary secrets.

Advanced constraints

Choose Pure HTML or native WordPress, set forms, SEO, integrations, accessibility, performance, technical limitations, multilingual/RTL readiness and project exclusions.

Review before Generate

Inspect the Builder summary for factual mistakes, conflicting instructions, duplicated pages and unsupported promises. Correct the specification before production begins.

For the exact current input fields and build requirements, consult the dedicated Website Specification Guide and Builder Documentation.

Related guides: Specification Guide · Design Blueprints

AI + generation architecture

AI assists strategy. Omega remains authoritative for the production website files.

The generation system uses a verified sixteen-stage production flow: AI Orchestrator, Entity Architecture, Website Specification, Site Architecture, Design System, Semantic HTML, Content + Conversion, SEO + Schema, Image, Performance, Security, Web Metrics Readiness, Accessibility, Forms + Backend, Deployment and Final Validation. Omega-native planning remains constrained within this architecture and does not become unrestricted production code.

Normalize

Builder inputs are combined into one authoritative brief covering business identity, architecture, design, content, media, features and platform requirements.

✦

Omega-native AI knowledge planning

When configured, a compact structured strategy request can refine positioning, content emphasis, calls to action, image allocation and related planning choices.

Omega Native Planner

Deterministic planning works from the authoritative Builder specification, source evidence and canonical knowledge inside the Omega-controlled workflow.

✓

Plan Validation

Structured planning output is checked before it can influence generation. Explicit customer selections remain authoritative.

↻

Checkpointed Generation

Builds progress through initialization, media, page batches, finalization, platform packaging, validation and preview publication rather than one oversized request.

⟳

Retry + Recovery

Temporary continuation failures can be retried so a substantial build is not automatically discarded because one stage briefly fails.

GENERATE • VALIDATE • PACKAGE

Understand the checkpointed generation pipeline and its production limits.

The site distinguishes Omega-native planning from the production execution system. The generated website is built through sixteen ordered production stages with checkpointing, stage validation and recovery. A valid specification and a completed generation job do not by themselves prove that the preview or live deployment is ready.

Normalized requirements

Business facts, design rules, page contracts and selected target platform are normalised before pages are generated. Incompatible or unsupported planning data is rejected or corrected.

Page and content production

The native generation pipeline assembles per-page information architecture, original content, navigation, templates/components and relevant evidence; project size may extend to the documented 120-page limit.

Image and icon assets

Logo and content media pass through platform-aware responsive image processing. Documented output may include AVIF/WebP variants, responsive markup, favicons and device icon sets, subject to source quality and runtime support.

Platform branching

Pure HTML produces a portable static site with appropriate compatible endpoints; WordPress produces the appropriate native theme/content/installation package, not just an HTML folder renamed WordPress.

Quality and final validation

Generation checks structural contracts, page differentiation, links and supported assets, schema, accessibility readiness, relevant security constraints and publication consistency.

Preview and export boundaries

Project preview uses an isolated environment. Paid checkout/entitlement and successful preview or deployment gates are separate, validated workflow steps; export is never just a screenshot of the preview.

Specific stage names, generation checkpoints, recovery behavior and platform packaging details are maintained in the Generation Pipeline Guide.

Related guides: Generation Pipeline · AI Planning

Production targets

Pure HTML and WordPress are separate production renderers, not cosmetic export formats.

Both start from the same validated specification, then branch into platform-appropriate architecture, forms, files, validation and deployment packages.

</>

Pure HTML

Produces semantic HTML5 pages, local CSS, vanilla JavaScript, responsive images and supporting deployment/crawl files in a portable website package with no CMS or database dependency.

Semantic multi-page HTML
Local CSS + vanilla JavaScript
Responsive picture/srcset assets
sitemap.xml, robots.txt and llms.txt support
Portable compatible-hosting deployment

Pure HTML Documentation →

Native WordPress

Uses a dedicated WordPress renderer and validator. It can produce block/Site Editor or classic PHP theme architecture, generated content material and setup/import components.

style.css, functions.php and theme.json
Templates, parts, patterns and responsive assets
Generated content JSON + WXR package
Setup/installer plugin architecture
WordPress-native forms using admin_post, nonce verification and wp_mail

WordPress Documentation →

Key distinction: a Pure HTML source ZIP is a portable site tree; WordPress output includes native WordPress theme/content/setup material and its own live database and management workflow after installation. Do not treat a WordPress website as if it were merely a static HTML export.

Media + SEO + accessibility + performance + security + metrics

Omega evaluates the generated website through multiple specialist quality responsibilities.

These are build-time readiness systems. Deployed Lighthouse, Core Web Vitals, penetration testing, legal review and manual accessibility review remain separate deployment-time responsibilities where required.

◈

Responsive Image System

Uploaded media is validated and can produce AVIF, WebP, JPEG and PNG responsive derivatives without unnecessary upscaling, plus favicon and multi-resolution ICO families.

Image Engine →

↗

SEO + Schema

Checks titles, descriptions, H1 structure, canonicals, Open Graph, JSON-LD, sitemap, robots, llms.txt and utility-page indexing behavior.

SEO + Schema →

♿

Accessibility Readiness

Structural checks include landmarks, heading organization, image alternatives, skip links and accessible names. This is readiness auditing, not WCAG certification.

⚡

Performance Readiness

Checks local assets, third-party dependencies, image dimensions, payload discipline, CSS integrity and responsive media strategy.

Performance →

◆

Security Readiness

Reviews generated output for selected unsafe patterns, remote script concerns, external-target handling, private project boundaries and deployment hardening expectations.

Security →

▥

Web Metrics

Build-time diagnostics are deliberately distinguished from browser runtime metrics such as LCP, CLS and INP. Measure those on the deployed URL using appropriate browser tooling.

Web Metrics →

Two separate live-preview systems

Builder preview and Website Editor preview solve different problems.

The first is a public generation preview. The second is a private licensed-code editing preview available after purchase.

◫

1. Builder Live Preview

After generation, Builder publishes the temporary project into its controlled preview environment. The customer can inspect desktop, tablet and mobile views before purchase.

Available before purchase
Shows the generated project
Desktop / tablet / mobile controls
CSS, JavaScript and image health signals
Export/purchase workflow remains gated until required preview health succeeds

Builder Preview Documentation →

</>

2. Website Editor Live Preview

A purchased customer opens one of their own active Website IDs, selects a supported project file, edits the source and sees valid changes in the sandboxed preview beneath the editor.

Paid customer access only
Licensed project files only
Exact-line live validation feedback
Desktop / tablet / mobile preview
Customer-edited PHP is not executed in preview

Website Editor Documentation →

Before purchase: inspect the Builder preview and real asset delivery. After purchase: the authorised Website Editor sandbox displays validated source changes; separate native WordPress management edits live site content, and confirmed deployment updates the production website.

PLAN SELECTION & CHECKOUT

Select the right commercial model and complete verified checkout.

Omega offers three recurring managed-hosting plans for one hosted website per purchase and a distinct lifetime single-domain software licence. Pricing, taxes, invoices, hosting entitlement and software ownership must not be confused. The current public pricing page is the authoritative price and terms reference at checkout.

Monthly Omega Hosting

US$9.99 per month for one hosted website, including 5 GiB (5,120 MiB) of managed storage while the hosting entitlement is active.

Annual Omega Hosting

US$99 per year for one hosted website with the same 5 GiB hosting allocation and customer workflow.

Two-Year Omega Hosting

US$179 per two years for one hosted website; the published equivalent is approximately US$7.46 per month.

Lifetime software licence

US$999 paid once for one permanently licensed domain, with same-domain editing/regeneration and licensed ZIP export rights. Production hosting is not included unless separately purchased.

Account-bound checkout

For first-time hosted purchases, a restricted checkout-bound Omega account is created and verified through the account setup email before customer sign-in and Stripe Checkout. The lifetime purchase has a separately documented account-creation path.

Verified payment and billing

Only the confirmed payment/webhook and matching account, purchase, Website ID and plan establish entitlement. Pending/abandoned checkouts are not completed subscriptions; billing portal actions depend on confirmed subscription state.

Each hosting purchase covers one website. Customers can buy multiple separate hosting plans for multiple Website IDs. Domain registration is separate for all these products; taxes and current prices must be checked at checkout.

Related guides: Pricing · Checkout · Purchase & Licence

Purchase options

Use the same generation platform with either managed hosting or lifetime licensing.

After generation and preview verification, choose US$9.99 monthly, US$99 annual, US$179 for two years, or the US$999 Lifetime Single Website Domain Licence. Recurring plans include managed Omega Web Pro Hosting while active; lifetime production hosting is separate.

Compare all four plans

Purchased customer My Account

My Account is the commercial account centre; the Omega Web Pro Hosting Dashboard is the operational hosting control panel.

There is no public Create Account registration flow. A first-time recurring Hosting checkout creates a restricted checkout-bound account before payment, sends a secure one-time account-setup email, and requires password setup and sign-in before Stripe Checkout. A first-time Lifetime Licence purchase reuses an existing account where available or creates the customer account after Stripe confirms the purchase.

Lifetime Website Licences

View each licensed domain, Licence ID, Website ID, supported platforms, generation count and other permanent commercial identity information.

↻

Return to Builder

Reopen supported licensed project data and regenerate the same permanent domain without purchasing that domain licence again.

</>

Edit Website Code

Open the active licensed Website ID in the private Website Editor for direct source editing, real-time preview and validation.

⏳

Pending Checkout

View unpaid checkout orders associated with the currently authenticated customer account.

→

Proceed to Checkout

Resume the exact existing open Stripe Checkout Session rather than silently creating a duplicate pending order.

Delete Pending Checkout

Remove an abandoned unpaid pending checkout from the Omega account and expire its open Stripe Checkout Session where available. Stripe customer and historical Stripe records are retained; paid records and issued licences are protected.

US$

Purchase & renewal records

View confirmed lifetime licence purchases and the commercial records associated with recurring hosted plans. Subscription invoice and renewal history remains distinct from one-time lifetime Purchase History; future zero-dollar same-domain lifetime generations or exports are not recorded as new US$999 purchases.

👤

Profile Details

Update personal and contact information without changing the permanent licence-domain relationship.

🔐

Account Security

Change password, request a verified login-email change and use password recovery while keeping Licence IDs, Website IDs and licensed domains permanent.

Open My Account → My Account Documentation Checkout Documentation

STRIPE BILLING & RENEWALS

Manage subscriptions, invoices, renewal state and payment recovery.

The Omega Billing Centre uses authenticated customer context to reach applicable Stripe billing services. It does not replace My Account or the production Hosting Dashboard. Billing evidence, subscription lifecycle, website allocation and a separately purchased lifetime software licence have different records.

Payment methods and invoices

Use the authenticated Billing Centre/Stripe Customer Portal for eligible payment method changes, invoices, receipts and payment history.

Renewal and cancellation

Recurring subscriptions may renew according to plan terms; cancellation, payment failures and reactivation affect hosting entitlement as defined by the applicable subscription status.

Incomplete purchases

My Account identifies eligible pending checkout records and offers continuation or removal without deleting confirmed paid transactions.

Ownership separation

Cancelling a recurring hosting subscription does not erase a separately purchased lifetime single-domain licence or convert that licence into hosting.

Secure recovery

Use the established Omega account sign-in/reset and Stripe-supported billing recovery routes. Customer support cannot safely treat a screenshot as proof of purchase.

Never send payment card numbers or account passwords to customer support. Read the Billing Centre and Checkout guides for the supported workflow.

Related guides: Billing Centre · Checkout Guide

OMEGA WEB PRO HOSTING

Omega Web Pro Hosting architecture

The customer workflow now continues beyond generation and checkout into the Omega Web Pro Hosting Dashboard. My Account remains the account, billing and licence centre; the Hosting Dashboard is the operational control panel for active hosted websites.

Customer control plane

Customers on monthly, annual or two-year plans can manage project workspaces, previews, staging, production hosting, backups, databases, SFTP access and usage information through Omega Web Pro interfaces. Lifetime customers retain permanent build/edit/export rights for their licensed domain and may add Omega Web Pro Hosting separately.

Managed hosting plans

Monthly US$9.99 · Annual US$99 · Two Years US$179. Managed Omega Web Pro Hosting remains available while the recurring plan is active.

∞

Lifetime software licence

US$999 one time for permanent supported build, edit and export rights for one licensed website domain. Production hosting is separate and can be added when required.

OMEGA HOSTING • PRODUCTION WORKFLOW

From Hosting Purchase to Live Website

Omega Hosting is an optional recurring service for one hosted website and is separate from the US$999 Lifetime Single Website Domain Licence. A hosting purchase is associated with the authenticated Omega customer account and the exact Website ID, domain, project and platform selected for that website.

Purchase + provision

After a Monthly, Annual or Two-Year Omega Hosting purchase is confirmed, Omega provisions the generated website into its assigned hosting environment. The hosted website then appears in the customer's authenticated My Account and Full Hosting Dashboard.

Hosting Setup Email + DNS

Omega supplies the required DNS instructions in the Hosting Setup Email and through authenticated hosting controls. The customer applies those records with the authoritative DNS/domain provider. Existing nameservers may remain in use unless the supplied instructions specifically require otherwise.

Verification + SSL

Provisioning or file upload alone does not make the public domain live. Omega verifies the public DNS connection; once the domain resolves correctly, SSL/TLS activation and certificate automation can proceed. The domain then resolves to the Omega-hosted production website.

Edit + update the live website

An active Omega Hosting customer can open the hosted project through My Account / Full Hosting Dashboard, work in Builder and/or Website Editor / Code Editor, save the project, then use Deploy / Update Live Website to update the existing production website.

Protected deployment

Before production activation, Omega verifies the authenticated account, Website ID, hosting entitlement, hosting allocation and permanent project source. Deployment uses validated project source, private staging, a pre-deployment restore point, production activation and post-deployment validation. If activation fails after the live site changes, Omega attempts automatic rollback.

Ongoing hosting controls

The Full Hosting Dashboard provides customer-facing access to deployments and deployment history, Domains & SSL, backups and restore points, databases, SFTP/access status, resources and usage, security status, billing and subscriptions, lifetime licences, activity/audit, support and account/privacy controls.

DNS responsibility: use the exact DNS records supplied for your website. Do not copy an IP address or DNS value from another customer's setup. Where available, My Account can resend the Hosting Setup Email. Domain registration is separate unless explicitly supplied, and correct DNS configuration and propagation are required before the public domain and SSL can become active.

AUTOMATIC WORDPRESS HOSTING

How an eligible paid WordPress website is provisioned automatically on Omega Hosting.

When an authorised customer chooses WordPress as the website platform and purchases the applicable Omega Hosting service, Omega links the confirmed hosting entitlement with that specific account, Website ID, domain and project. The installed automatic WordPress lifecycle detects qualifying provisioned websites, performs eligible site-specific setup and protects already-initialised installations from unnecessary reinstallation. Provisioning and public DNS/SSL go-live are separate states.

1. Purchase and verified entitlement

Customer chooses a recurring hosting plan for the selected WordPress project. Omega verifies payment, owning customer, site ID, platform and hosting allocation before the relevant automation is eligible.

2. Provisioned server and isolated site

Omega assigns the hosted project to its customer-specific hosting context. Each website maintains separate web files, database identity, WordPress application and authorised execution context.

3. Automatic WordPress installation lifecycle

The installed background lifecycle periodically examines eligible paid WordPress hosting records and, where needed, carries out controlled WordPress core/configuration/database/site initialization. It checks installed state to avoid rewriting existing working sites.

4. Initial WordPress administrator identity

The onboarding workflow establishes the site-specific WordPress owner/admin identity through the protected installation process, instead of exposing a reusable password in a public page or welcome email.

5. Owner setup email

The site sends the owner-facing WordPress setup information to the authorised customer email address when applicable. It supplies the website URL, Omega Website Editor entry, WordPress admin entry, the assigned site-specific username and the official password setup/recovery route.

6. DNS, verification and TLS

A provisioned WordPress installation does not automatically mean the customer-owned domain is publicly connected. Follow that site’s Hosting Setup Email/Dashboard DNS records, wait for verification, and complete certificate activation.

7. Website ID, editor and plugins

The purchased website appears under Your Purchased Websites; the customer chooses it and Omega loads the matching WordPress management features, native hosted plugins and authorised third-party plugin workspace.

8. Continue live administration

Save live WordPress Pages and Posts through the embedded native editor/WordPress Manager and deploy confirmed theme/project changes through the separate protected workflow.

Two distinct messages: the Omega customer account-setup email is for Omega account login/checkout; the later WordPress site-owner email is for that particular WordPress administrator account. The automated lifecycle has been installed and tested on an example hosted site; each new purchase is still subject to successful individual provisioning, email delivery and domain readiness.

Related guides: WordPress Website Hosting · Hosting Guide · First Steps

WORDPRESS OWNER SETUP EMAIL

Set up the separate WordPress administrator account safely.

After an eligible WordPress hosting installation has been provisioned and its owner onboarding is ready, the customer receives a WordPress website setup email. The message identifies the customer’s actual domain and Website Editor link, a direct WordPress administration address, site-assigned WordPress username and a WordPress-native password setup/recovery URL. It does not include an initial password or a private reset token.

Recognise the correct message

Expect a message describing your Omega WordPress website setup details from that WordPress installation. Verify that the domain and requested site are yours before following links.

Set a personal WordPress password

Use the site-specific WordPress password setup or recovery link, normally https://your-domain.example/wp-login.php?action=lostpassword, and follow the WordPress instructions. Do not use another site’s email or username.

Keep both logins distinct

Omega account credentials control My Account, paid products and authorised Website Editor selection. The separately assigned WordPress login is for that particular WordPress installation.

Open the Omega website workspace

Sign in to Omega My Account and choose the purchased site in Website Editor; the authorised session then exposes the matching WordPress management area and supported plugin dashboards.

If the email is missing

Check spam/junk, verify your account email, site provisioning and domain status, then use the documented support pathway. Do not ask support to send a plaintext WordPress password.

Privacy: published documentation uses placeholder domains and generic steps. Actual customer domains, Website IDs, assigned WordPress usernames and password recovery links belong only in each customer’s own onboarding communications.

Related guides: Getting Started · Account Access · Troubleshooting

WordPress hosting • account to live site

New: WordPress owner email, authenticated Website Editor and live Pages/Posts management.

Provisioned Omega-hosted WordPress customers receive a site-specific WordPress setup email containing the site's WordPress administrator details and a password setup/recovery address. This is separate from their Omega customer-account credentials. They open My Account, select their paid WordPress website and enter the dedicated WordPress Editor and use the authorised native WordPress Source Code panel and embedded Manager without a second manual WordPress sign-in for supported controls.

The WordPress hosting lifecycle also includes automatic site-specific WordPress installation after eligible paid provisioning: dedicated database and core setup, owner-account initialisation and a separate owner invitation when onboarding is ready. These steps are different from DNS/SSL setup and publishing a generated theme, and direct WordPress account access stays separate from your Omega account login.

Live WordPress Pages and Posts

Select, load and edit WordPress HTML or block markup; Save to WordPress updates the selected site's live content with WordPress revisions. Preview selected WordPress content using the dedicated WordPress Editor; generated static HTML belongs to the different Pure HTML Editor.

✓

Protected WordPress deployment

Inside the dedicated WordPress Editor, authorised users work with the applicable validation, native revisions, WordPress plugin dashboards and protected deployment workflow, subject to verified staged source. A WordPress database save is not the same as a generated theme deployment. See Website Editor Documentation and Deployment Documentation for each workflow.

See the complete sequence: Automatic WordPress provisioning explains how an eligible hosted WordPress installation is prepared; WordPress owner email describes separate password setup; Live WordPress management shows how a verified site is selected and edited without leaving Omega Website Editor.

Documentation hub • practical editors

Choose an Editor by platform and follow the correct save and publish workflow.

Start from My Account and choose the purchased website. Omega checks the account, Website ID, domain, hosting eligibility and detected platform before opening the applicable editor. Do not change a URL parameter to try to open a different site or the wrong editor.

Pure HTML: website-editor.php is the source-file editor for an authorised Pure HTML project. WordPress: website-editor-wordpress.php is the separate WordPress Editor for an authorised native WordPress website. The platform should be selected from trusted website records, not by guessing which page to use.

Pure HTML workflow

In the Pure HTML Editor, select a source file; use the code editor and desktop/tablet/mobile sandbox to inspect the change; address validation feedback; Save and review Version History. The full-project Validate Licensed Website step is distinct from the preview. Generate Updated Licensed ZIP creates an eligible export; Deploy / Update Live Website requires an authorised hosted destination and completed validation.

Native WordPress workflow

The WordPress Editor contains native Page/Post source tools, a supported live WordPress-rendered preview, integrated WordPress Management and installed-plugin dashboards. Editing a live WordPress Page/Post is not the same as updating a Builder-generated WordPress theme or exporting a private source package. Use the available Load, Reload from WordPress, and explicit Save to WordPress operations for content; follow separate validated native package/deployment controls for theme and Builder changes where enabled.

Where to get specific help

Read Website Editor documentation for step-by-step editing, Hosting Dashboard documentation for entitlement, DNS and live operations, WordPress Builder for native generation and Troubleshooting for failure-specific checks.

Private Website Editor

Direct source-code editing with real-time preview, validation, revisions and licensed export.

Neither dedicated Website Editor is a public arbitrary-code upload surface. It is tied to the authenticated purchased account and verified licensed Website ID.

FILES

Purchased Website Selection

Purchased websites appear as selectable project controls. The selected project loads its own authorized filenames into the file sidebar.

Complete File Editing

Supported files load into the editor with line numbers, cursor position, Undo, Redo, Find, Replace and Replace All.

Exact-Line Blocking Issues

Newly introduced blocking issues can be shown at the responsible line with the validation area and reason.

✓

Preview + Save Gate

Blocking syntax, malformed-data, security or protected-domain issues can prevent changed content from entering Preview or Save until corrected.

≋

Version History

Accepted editor saves create versioned revisions for the licensed project.

ZIP

Updated Licensed ZIP

Whole-project validation can be run before generating an updated signed licensed website ZIP.

14 Website Editor validation responsibilities: Website Specification, Brief Normalizer, AI Planning, Plan Validation, Site Architecture, Content Conversion, Design System, Image Engine, SEO + Schema, Accessibility, Forms + Backend, Deployment, Quality / Metrics and Final Validation.

Permanent domain protection: the permanent licensed root host is protected. The home-page canonical host cannot be changed to another domain. Legitimate internal filenames and page canonical paths can still change while remaining under the same licensed host.

Hosted customer controls: Validate Licensed Website, Version History, Generate Updated Licensed ZIP and Deploy / Update Live Website operate within the authenticated entitlement and project context. The WordPress Manager is integrated for eligible WordPress sites; static snapshot editing and live database editing remain separate, as described in Live WordPress editing.

LIVE WORDPRESS EDITING

Edit WordPress content and manage the real installation in the dedicated WordPress Website Editor.

For an authorised, paid and provisioned WordPress website, Omega opens the separate website-editor-wordpress.php page using the verified hosting record and provides WordPress Management for the selected Website ID. The customer can work on native live Pages, Posts, Media and supported site settings without leaving the Omega editing experience. The live WordPress data and the protected generated static snapshot are intentionally distinct.

Securely select the live WordPress website

From My Account, open Omega Website Editor and select the verified WordPress entry under Your Purchased Websites. Do not copy another customer’s Website ID.

Native WordPress source editing

The embedded native WordPress source/content editor and WordPress Manager use the selected site’s live WordPress Pages/Posts. Changes to those native records are saved to the relevant live WordPress database through the authorised workflow.

Pages, posts and media

Create or update page/post content and work with WordPress media and relevant native settings from the integrated management area, subject to site capabilities and WordPress permissions.

Dedicated Pure HTML project editor

The dedicated Pure HTML Editor at website-editor.php remains separate from website-editor-wordpress.php. HTML source editing does not write WordPress Pages, Posts, theme files or database records.

Validation and safe preview

The original Code Editor retains supported file selection, diagnostics, line-aware validation, preview, revision history and licensed ZIP controls. Live PHP is not executed simply by putting it into the editor preview.

Deploy and update

Use the supported Deploy / Update Live Website control for validated project/theme deployments. Treat this as a confirmed, guarded action distinct from saving a native WordPress Page or Post.

Owner login and sessions

The customer’s Omega account and WordPress administrator are separate identities. Omega can establish a temporary, site-bound administrative session for supported embedded WordPress management after verifying the authorised account/site; this does not publicly reveal a WordPress password.

Domain and project protection

The site’s permanent licensed canonical root domain stays protected. Cross-website access, wrong-site updates, unsafe project identity substitutions and unauthorised deployment must be rejected.

WordPress may still expose its ordinary direct /wp-admin/ access to the site owner, but the integrated Omega editing workflow does not require leaving Website Editor for supported content and plugin management. Some native theme/database actions remain separate from static snapshot operations.

Related guides: Website Editor Guide · WordPress Guide

EIGHT OMEGA ENGINE FAMILIES

Understand all eight hosted native Omega Website Engines and their platform-specific versions.

Website Generation Engines operate during Builder generation. These hosted Website Engines are a different system: eight named engine families each have a Pure HTML implementation and a WordPress implementation (16 in total). The selected eligible hosted website gets the matching eight controls; each website and engine has its own persistent green Enable, red Disable and readable status.

Omega Image

Platform-aware image processing and responsive media operations, including supported next-generation image formats and variants. Capability depends on source media and image-library support.

Omega Performance

Protected performance configuration and diagnostics with appropriate conservative/balanced or higher-risk settings where offered; changes should be tested on the real site.

Omega Security

Supported request/site security controls, checks and website-scoped rules. Operational checks complement, rather than guarantee, comprehensive cybersecurity.

Omega SEO

Technical SEO configuration and diagnostics such as titles, metadata, canonicals, social tags, robots and schema within the applicable platform.

Omega Web Metrics

Observed build/site readiness and supported performance, image, SEO and security diagnostics; live site measurements must be distinguished from estimated build checks.

Omega Uptime & Availability

Website reachability, response timing, DNS/TLS evidence, history and outage/recovery signals for the verified hosted target.

Omega Accessibility Monitor

Automated checks of page structure, labels, accessible names, images and other supported conditions; automated scans do not certify WCAG conformance.

Omega Scheduled Task Monitor

Platform-appropriate scheduled job visibility. On WordPress this can include WP-Cron hooks, recurrence, overdue tasks and relevant configuration; it is not a general arbitrary command executor.

Native hosted plugin availability and all management operations depend on current paid hosting, the verified Website ID, its platform and supported implementation. Disabling one engine does not disable the other seven. These private managed-hosting engines are not bundled into an ordinary customer ZIP export.

Related guides: Complete Omega Plugins Guide · Website Editor

Documentation • operational Website Editor

Find the right guide for hosted Omega engines, WordPress plugins and HTML libraries.

After you generate, preview and purchase a website, the authorised Website Editor brings together source files and hosted plugin operation without turning Pure HTML into WordPress or mixing the two platforms’ runtime controls.

Eight native Omega engine families

The hosted website gets the correct eight implementations for its platform, with independent persistent enable/disable states. Native hosted plugins are separate from generation pipeline stages and from third-party repository plugins.

WordPress plugins and secure original dashboards

The WordPress Third-Party Plugins workspace searches and browses the full public WordPress.org plugin directory with live, paginated results—not only Omega’s 52 curated starting plugins. Customers explicitly choose compatible official plugins to install for their authorised hosted WordPress website. Installed supported plugins expose Open Dashboard inside the protected one-plugin-at-a-time workspace, without an additional manual WordPress dashboard sign-in for supported controls.

HTML add-ons and npm/cdnjs search

The fourteen managed Pure HTML add-ons have their own Install, Enable, Disable, Status and supported Sync controls. Separately, customers can search the public cdnjs browser-library directory or search the wider npm package registry, browsing paginated provider results for research only; arbitrary public packages are not automatically installed, executed or declared compatible. See Website Editor Documentation for both dedicated editor workflows and Omega Plugins for the eight hosted plugin families, each implemented separately for Pure HTML and WordPress.

For the full eight-plugin-family function reference and the WordPress.org, installed plugin, curated catalogue, managed HTML add-on, npm and cdnjs distinction, continue to eight hosted Omega plugins and Plugin repositories and HTML libraries. Search results are discovery, not proof of automatic installation.

THIRD-PARTY PLUGINS & LIBRARIES

Search, install, enable and manage compatible extensions for the selected site.

The Third-Party Plugins workspace is separate from the eight native Omega engines. It filters its tools by the selected hosted site’s real platform. Third-party additions are optional; they are not automatically installed just because the website was provisioned.

WordPress.org plugin directory

For WordPress websites, the live paginated repository search exposes publisher metadata and available compatible packages. The implementation also includes a curated 52-package starting catalogue. Search totals are dynamic; they are not an installed-plugin count.

Installed WordPress plugin inventory

The installed list reflects the selected site’s actual plugins. Applicable controls include installation, enable/disable, plugin status and the supported embedded management entry point.

One original WordPress dashboard at a time

Each supported installed plugin can expose Open Dashboard. Its publisher-provided WordPress administration UI is loaded within the secured Omega workspace; selecting another closes/replaces the previous one.

WooCommerce, TablePress and other extensions

The original plugin screens are site-specific and depend on actual installed plugin menus and native WordPress permissions. Omega does not fabricate substitute dashboards for unsupported plugin UI operations.

Fourteen managed Pure HTML add-ons

Back to Top, Smooth Anchor Scrolling, Table of Contents, Heading Share Links, Image Lightbox, Click-to-Load Video, Page Sharing, Print Page, Reading Progress, Code Block Copy, Accessible Tabs, FAQ Accordion, External Link Safety and Countdown Timer.

npm and cdnjs directory discovery

Pure HTML library search can surface relevant npm packages and cdnjs browser libraries, including publisher/version information. A directory result is research/discovery and is not automatic trusted installation of arbitrary remote code.

Site-specific controls and isolation

Managed add-ons support their actual installed state and available settings for the selected website. One account may own multiple sites, but one site’s plugins and enabled states must not leak or be changed on another.

Repository snapshots change: a previously observed WordPress.org query showed 71,229 results across 2,968 pages, npm 631,928 search results, and a bounded cdnjs window of 240 matches; these are not permanent catalogue-size guarantees. Installed plugins and supported dashboards are determined at runtime.

Related guides: Omega Plugins · Editor Guide

US$999 Lifetime Single Website Domain Licence

Choose managed Omega Web Pro Hosting or a permanent lifetime software licence for one normalized website domain.

The licence is a commercial identity record, not merely a download token. The customer account can hold several licences, but each website domain has its own Licence ID and Website ID.

Licence Element	How It Works
Price	US$999 one-time for one Lifetime Single Website Domain Licence.
Licensed Domain	Permanently assigned normalized domain. A different domain requires a separate licence.
Platforms	Licence rights include future Pure HTML or WordPress generation for that same domain; one production target is generated at a time.
Builder Rights	Unlimited future same-domain generations/re-edits under the existing licence.
Website Editor Rights	Private direct source editing for the active licensed Website ID, including preview, validation, version history and updated ZIP generation.
Account Ownership	Account ↔ Licence ID ↔ Website ID ↔ licensed domain relationship remains protected.
Hosting / Domain Registration	Monthly, annual and two-year plans include managed Omega Web Pro Hosting while active. The US$999 lifetime licence does not include production hosting unless separately purchased. Domain registration remains separate for all plans.
Future Same-Domain Exports	Recognized under the existing licence rather than treated as a new paid purchase.

Complete Purchase & Licence Guide → Lifetime Re-editing Documentation

The lifetime licence is permanently tied to its normalised root domain; a new domain requires a separate licence. Retain the latest licensed ZIP for portable deployment and eligible future re-edit workflows. An active monthly/annual/two-year hosting plan covers one hosted website and does not itself grant a US$999 lifetime software licence.

Export, hosting and deployment

Recurring plans deploy through Omega Web Pro Hosting; lifetime-licensed projects also retain portable ZIP deployment rights.

Temporary generation workspaces and previews are not the production website. The authoritative package comes from the generated project and the applicable licensed export workflow.

⬇

Authoritative ZIP

Download the generated source project after the required generation/preview/licence gates complete.

</>

Pure HTML Deployment

Place the generated website files in the intended hosting document root without accidentally nesting them inside an extra wrapper directory.

WordPress Deployment

Use the generated theme, setup/installer material, content JSON/WXR and installation instructions with a compatible WordPress environment.

✉

Forms + SMTP

Pure HTML server-side contact functionality requires compatible PHP/hosting and authenticated SMTP configuration. WordPress packages convert form handling to WordPress-native mechanisms.

DNS

Domain + DNS

The customer remains responsible for domain registration, DNS and hosting configuration unless separately supplied.

TEST

Post-Deployment Testing

Test navigation, responsive behavior, forms, HTTPS, redirects, canonicals, sitemap, robots, schema, Lighthouse/Core Web Vitals, accessibility and security on the final deployed URL.

Important measurement boundary: Omega build-time readiness checks are not a substitute for deployed Lighthouse, CrUX/Core Web Vitals, manual accessibility testing, penetration testing, legal review or industry-specific compliance review where those are required.

Deployment Documentation → Forms & SMTP Documentation Troubleshooting

For a hosted WordPress project, saving a WordPress Page/Post directly through native management is different from the protected Deploy / Update Live Website action for generated project/theme updates. In both platforms, check the authorised website, permanent domain and current restore points before production activation.

FULL HOSTING DASHBOARD

Operate each paid, provisioned website through its authorised hosting controls.

My Account is the commercial entry point; the Full Hosting Dashboard is the operational control surface. Its features are scoped to the selected authenticated hosted Website ID, and the available actions depend on payment state, provisioning, DNS, SSL and actual server capabilities.

Website and project inventory

View purchased hosted websites, assigned platform, canonical domain, Website ID, provisioning state and supported project access.

Deployments and recovery

View hosting deployment state and history, preview/staging where available, protected deployment operations, backups and restore points.

Domains and certificates

Read per-website DNS connection instructions, DNS status, HTTPS/certificate information and domain-connection tasks.

Databases and secure access

View available site database information, SFTP and access status under permission checks; only applicable website operations are exposed.

Resources and security

Inspect storage, usage/resource information, security status, audit/activity history and supported support diagnostics.

Payments, licences and support

Reach subscription information, billing, licence references, account/privacy operations and customer support without confusing hosting rights with software licence rights.

Operational controls cannot be inferred for a different customer or Website ID. A website may be paid but awaiting provisioning or public DNS connection.

Related guides: Full Hosting Dashboard Guide · My Account

DOMAINS • DNS • SSL

Connect the purchased site’s permanent domain to production hosting.

A software licence, a paid hosting subscription, domain registration and public DNS resolution are different parts of the lifecycle. The domain remains the website’s identity; its registrant/provider must configure the exact site-specific DNS records supplied by Omega, while the hosting service verifies public resolution and activates HTTPS where eligible.

Domain search and registration

Search available domain names using the public domain search workflow. Registration, registrar management and transfer terms are separate from the website builder and hosting plan unless expressly stated.

Site-specific DNS

Follow the per-site Hosting Setup Email or signed-in Domains & SSL dashboard instructions. Do not substitute example IP addresses or records copied from another customer.

Connected-domain verification

After the domain provider publishes the records, allow for propagation and await successful connection/verification before assuming the production site is reachable.

Certificates and HTTPS

Where the service supports it, SSL/TLS certificates are obtained/renewed once the target domain and hosting configuration satisfy issuance conditions.

Canonical hostname protection

The permanent licensed root host is validated during editor save/export and protected deployment. Internal paths can evolve without moving the licensed website to another root domain.

Live-site checks

After connection, verify redirects, HTTP/HTTPS variants, indexed canonical URLs, robots/sitemap, accessibility, performance, security and forms on the final public hostname.

If DNS, hosting or certificates are incomplete, a perfectly valid generated site may not yet be publicly available. Consult Hosting Dashboard and Troubleshooting.

Related guides: Domain Search · Hosting Guide

FORMS • EMAIL • INTEGRATIONS

Configure website contact workflows and third-party services for the chosen platform.

Generated front-end forms, subscription/booking interfaces and analytics placeholders need applicable backend services and valid owner-controlled configuration to operate in production. Pure HTML and WordPress take different implementation routes, so a successful visual preview is not equivalent to end-to-end email delivery.

Pure HTML form backend

Compatible PHP hosting, configured handler and authenticated SMTP may be required for working email delivery. Review spam protection, input validation, confirmation messages and any data handling obligations.

WordPress-native forms

The WordPress renderer uses WordPress-appropriate form mechanisms, hooks and configured mail delivery rather than copying a Pure HTML mail endpoint into WordPress.

Customer-owned credentials

Use approved secure configuration surfaces for SMTP/API keys, payment and external integrations; never publish passwords or access tokens in HTML, source previews or support messages.

Mail transport and deliverability

Verify From addresses, outbound server/SMTP settings, sender domain authentication where applicable, recipient handling, errors and actual inbox receipt.

External widgets and services

Third-party libraries, maps, analytics, commerce, booking and marketing integrations can impose provider terms, privacy and consent requirements beyond Omega’s core generation.

End-to-end test

Submit a test form on the live HTTPS website, confirm validation and error handling, verify mail receipt or external service operation, and retain no unnecessary personal data.

WordPress onboarding setup mail is a separate installation/account invitation workflow, not proof that all customer website forms are correctly configured.

Related guides: Forms & SMTP · Deployment

SEARCH • ACCESSIBILITY • QUALITY

Improve crawlability, readable content and technical readiness without making ranking guarantees.

Omega produces site-specific architecture and technical optimisation evidence, while publication quality depends on accurate content and the deployed environment. SEO tools, accessibility checks, security diagnostics and performance recommendations measure different concerns; they cannot promise rankings, compliance or immunity.

Content hierarchy and discovery

Write original, relevant page content, distinguish page intent, use a logical H1–H3 outline, descriptive text links, clean navigation and accessible page structure.

Search engine metadata

Review page titles, descriptions, canonical URLs, indexability, social metadata and supported JSON-LD. Search engines may choose different search snippets and rich-result eligibility depends on their own criteria.

Crawl and index

Confirm published robots.txt, sitemap URLs, noindex decisions, redirects and canonical consistency. A submitted URL does not guarantee crawling speed or indexing.

Responsive images and load speed

Serve appropriate image sizes/formats and assess live caching, CSS/JS, server latency and user-perceived Core Web Vitals with deployed measurement tools.

Accessibility and usability

Verify headings, keyboard access, focus states, labels, image alternatives, colour contrast and dynamic widget behavior using both automated and manual review.

Security and compliance

Use least-privilege access, HTTPS, secure updates, input handling, privacy notices and periodic operational review; specialist audits may still be necessary.

Build-time readiness reports must not be presented as live Lighthouse/CrUX measurements, WCAG certification, independent penetration testing or guaranteed Google/Bing rankings.

Related guides: SEO & Schema · Accessibility Statement · Web Metrics

OMEGA AI AGENT • ASSISTED WORKFLOWS

Understand what Omega AI can do—and which actions remain customer-controlled.

The customer-facing Omega AI Agent is distinct from the native planning knowledge stage and from deterministic production generation. It can help with questions, public research, analysis of supplied files and business specifications, while authenticated customer contexts may provide authorised website/hosting/editor assistance. Proposed changes require applicable validation and customer-controlled actions.

Public assistance and research

Ask questions, investigate website decisions and obtain practical guidance without granting a public visitor access to any customer-owned site.

Prepare a Builder specification

Provide a prompt/files; Omega AI can analyse requirements, populate the same six reviewed Builder stages, and pass the resulting specification into Omega’s normal Generate workflow.

Native planning and production separation

Omega AI Agent, Omega-native AI knowledge planning, deterministic validation and the actual generation engines have different responsibilities. Do not treat a chat answer as an automatic production deployment.

Customer-context answers

Within a signed-in authorised account/site, Omega AI can help interpret supported licence, hosting and website status without bypassing the normal website and payment permissions.

Website Editor code diagnosis

Omega AI can inspect allowed Editor context, explain validation errors, propose candidate multi-file repairs, and use supported reviewed Apply-to-Editor/save steps; unsaved customer work remains protected.

Operational safety and limits

Read-only operational assistance is separate from privileged deployments, plugin activation, billing changes, restore or security operations. The authorised control plane remains the source of truth.

AI-generated copy, code and architecture require customer review of facts, rights, legality, safety and performance before publication.

Related guides: Omega AI Features · Omega AI Agent · AI Planning

CURRENT PRODUCTION WORKFLOW

Authenticated production controls

The production system has two complementary authenticated customer surfaces. My Account is the customer-level view for profile and security, lifetime ZIP re-editing, recurring hosting websites, Website IDs, provisioning/DNS/SSL state, Builder and Website Editor entry points, Hosting Setup Email resend, Billing Centre, invoices and lifetime licences. The Full Hosting Dashboard is the operational control centre for websites/projects, hosting purchase, deployments, Domains & SSL, backups, databases, SFTP/access, resources, security, billing, licences, activity, support and account/privacy.

Controls are state-aware. A checkout-pending website can remain restricted until billing is active; a purchased hosting website can show provisioning in progress; a provisioned website can expose its exact DNS requirements; and an active connected website can be edited and deployed through the authenticated workflow. Customer-specific IDs, DNS values, payment-provider identifiers and private infrastructure are intentionally not reproduced in public documentation.

Documentation hub • safe AI assistance

Use Omega AI in both Editors while retaining customer approval.

Both dedicated Editors have the floating Omega AI Agent, supported by Omega's existing native AI and its configured research facilities. It can explain the selected workflow, help understand code or validation feedback, propose reviewable repairs, give Builder planning guidance and discuss website-scoped plugin issues. Research results and technical suggestions should be checked against their source and the actual website.

A chatbot response is not a Save or Deploy operation. Apply to Builder assists the planning/generation pathway; any Apply to Editor or Save All AI Fixes workflow requires inspection, authorisation and normal validation. Site ownership, canonical protection and available actions still come from server-side checks.

Do not confuse the two sets of sixteen

The sixteen Builder engines generate and validate websites. Separately, the eight Omega hosted Website Plugin families have two platform-specific implementations each (eight Pure HTML and eight WordPress). A hosted site only uses the eight appropriate to its platform. Neither system is the public WordPress.org, cdnjs or npm third-party repository.

WordPress.org offers a searchable, paginated full plugin directory, plus a curated starting list and authorised install controls. HTML users may search public cdnjs/npm libraries for discovery, while the fourteen managed HTML add-ons retain their own controls. Third-party discovery alone does not modify a website.

DIAGNOSE THE FAILED LAYER

Resolve problems using the exact project, platform and stage rather than guessing.

Before changing code, preserve project or deployment evidence and identify whether the problem concerns Builder inputs, generation, preview, customer identity, checkout, hosting, WordPress, plugin management, DNS, email or production deployment.

Builder and generated content

Confirm supported build limits, required inputs, planning contracts, output generation state, page uniqueness and selected platform.

Preview and editing

Distinguish the Builder preview from the licensed Editor sandbox, native WordPress Pages/Posts and actual live deployment. Read blocking errors and exact lines before saving.

Account and purchase

Check the signed-in Omega identity, paid entitlement, assigned Website ID and platform, pending checkout versus confirmed transaction, and separate site WordPress login.

WordPress onboarding

Verify provisioning status, email delivery, separate WP password setup, the actual installation URL and native WordPress Manager eligibility. Never share reset tokens.

Plugins and engines

Choose the correct website, confirm hosting entitlement/platform and installed plugin status, then distinguish native Omega Engine controls from publisher-provided WordPress dashboards or Pure HTML add-ons.

DNS and deployment

Verify the site’s DNS records, SSL, actual publicly serving document root, staging/backup/history, canonical host and post-deployment status before attempting another change.

Forms and third parties

Check mail transport, SMTP/authentication and service credentials on the actual live site, not just a rendered preview.

Escalate without exposing secrets

Provide support with the site/domain reference, Website ID through authenticated channels, operation, timestamp, exact error and safe redacted diagnostic evidence. Never disclose passwords or tokens.

First stop: Troubleshooting Guide. The Support page explains the right channel and what evidence helps.

Related guides: Troubleshooting · Support

Support, policies and customer responsibility

Documentation explains the platform. Support and legal pages govern how it is used.

Generated content, AI-assisted planning and readiness checks still require customer review before publication. Customers remain responsible for the accuracy, lawfulness and suitability of the websites they deploy.

FAQ

Quick answers about Builder use, platforms, licences, accounts and exports.

FAQ →

◉

Support

Help with Builder, generation, purchases, licences, My Account, Website Editor, export and deployment.

Support →

Terms & Conditions

Commercial and service terms governing Omega Web Pro use and purchases.

Terms →

AUP

Acceptable Use

Rules covering generated content, platform abuse, illegal/harmful use, licence abuse and customer responsibility.

Acceptable Use →

Privacy

Information about privacy and personal-data handling.

Privacy →

Copyright + IP

Intellectual-property and copyright information.

♿

Accessibility

Omega Web Pro's own accessibility information and accessibility expectations.

Accessibility →

✉

Contact

Contact Omega Web Pro for sales, customer and general enquiries.

Contact →

Begin with Troubleshooting for stage-specific checks, use the complete guide library to locate an in-depth reference, and refer to the legal and customer responsibilities overview before publishing regulated, copyrighted or third-party content.

LEGAL • PRIVACY • RESPONSIBILITIES

Understand the applicable rules and customer responsibilities.

Legal, intellectual-property, accessibility, privacy and third-party service obligations vary by the product purchased and the content published. Public documentation explains features; the governing terms and policies remain the relevant legal documents.

Terms and commercial rules

Review the Terms & Conditions for licence rights, pricing model boundaries, single-domain restrictions, account ownership, payments and service limits.

Privacy and data protection

Consult the Privacy Policy for data-handling disclosures, customer account data, retention, connected services and applicable rights and support contacts.

Acceptable use and security

The Acceptable Use Policy covers unauthorised access, spam, malware, prohibited content, fraudulent use, unsafe automation and abuse of account/editor/hosting resources.

Copyright and assets

Customers must have adequate rights to use supplied text, design material, media, fonts, trademarks, source files and generated website content.

Accessibility statement

Automated readiness does not remove the customer’s obligation to test and maintain the deployed website and meet applicable accessibility duties.

Third-party licences and warranties

Review upstream notices for AI models/libraries and any separately installed WordPress/npm/cdnjs code or other provider-dependent services.

Public documentation cannot substitute for legal, regulatory, security or professional advice for a particular customer’s website.

Related guides: Terms · Privacy · Acceptable Use · Copyright · Accessibility · Third-Party Licences

COMPLETE PUBLIC DOCUMENTATION LIBRARY

Find the dedicated page for every major Omega Web Pro topic.

This directory links to the existing specialist pages across the current published website. Use the sections above for an end-to-end explanation and these original guides for deeper, platform-specific instructions. Page availability and account-only functionality are governed by the customer’s actual purchases and permissions.

The main site navigation continues to provide the primary product, pricing, engine and support destinations. The secondary navigation on this page additionally links to documentation sections and specialised pages that are not in the main navigation.

Build • Preview • Licence • Regenerate • Edit Code • Validate • Export

Use this documentation hub throughout the complete website lifecycle.

Start in Builder, return here when you need implementation detail, then use the dedicated guides for purchased-account management, editing, licensing, export and deployment.

Start Building → How It Works Support