Answers to the Questions People Ask Before, During and After Building with Omega Web Pro.
This FAQ covers the complete current Omega Web Pro lifecycle: Universal Website Studio, AI-assisted planning, industry blueprints, page architecture, Pure HTML and WordPress generation, the public Builder preview, secure Stripe purchase, the NZ$999 lifetime single-domain licence, purchase-created My Account, pending checkout, purchase history, lifetime Builder regeneration, the private Website Editor, second real-time preview, validation, version history, licensed ZIP export, hosting, forms, privacy, security and deployment.
Quick answer
The short version of Omega Web Pro.
Build and preview first. Purchase one permanent-domain licence only if you want the protected licensed deliverable and lifetime same-domain workflow. After purchase, keep evolving that same website through Builder regeneration or direct Website Editor source editing.
About Omega Web Pro
About Omega Web Pro
What Omega is, how it differs from a one-shot AI generator and what the complete customer lifecycle looks like.
What is Omega Web Pro?
Omega Web Pro is a specification-driven, AI-assisted website generation and lifetime editing platform from Alpha & Omega Limited. It combines a public Universal Website Studio, structured planning, Omega-controlled generation, Pure HTML and native WordPress output, responsive preview before purchase, one-time lifetime domain licensing, My Account, lifetime Builder regeneration and a private licensed Website Editor with direct source editing, live preview, validation, version history and updated licensed ZIP export.
Is Omega Web Pro just an AI prompt-to-website generator?
No. AI-assisted planning is one part of a larger controlled production system. Omega first builds a structured website specification, then validates planning data, generates the project through its own renderers, runs quality checks, publishes a preview, manages licensing and later supports regeneration or direct licensed-code editing.
Who operates Omega Web Pro?
Omega Web Pro is a product of Alpha & Omega Limited.
Can I use Omega Web Pro without knowing code?
Yes. The Builder is designed for users who want to define the business, pages, design and functions without hand-coding. After purchase, customers who do want direct source control can also use Website Editor.
Can advanced users control the website in detail?
Yes. The Builder supports detailed architecture, design, content, media and technical controls, including a professional brief of up to 50,000 characters. Purchased customers can also edit supported source files directly in Website Editor.
Does Omega Web Pro require me to host the final site with Omega?
No. The generated licensed website ZIP is intended for deployment on compatible customer-selected hosting. Domain registration and hosting are separate from the Omega lifetime licence.
Universal Website Studio
Universal Website Studio
Questions about industries, architecture, design controls, supporting material and page-generation limits.
How many industry starting points are currently in the Builder?
The current Builder includes 73 industry starting points plus a custom industry/sub-industry path.
How many built-in page types are available?
The current Builder includes 105 built-in page types spanning business, commercial, ecommerce, content, education, hospitality, locations, careers, support, legal, campaign and utility needs.
How many pages can one website build generate?
The current production architecture supports up to 120 generated pages in one website build. The final count depends on selected pages, repeatable page entries and technical limits.
What are the repeatable page systems?
The current repeatable page systems are services, locations, products, case studies, team members and articles. Structured entries can expand into individual generated pages.
Can I add custom pages?
Yes. Built-in page types can be supplemented with custom page requirements when the project needs something outside the catalogue.
Can I provide a detailed business brief?
Yes. The professional brief supports up to 50,000 characters for project requirements, business rules, terminology, exclusions, technical direction and other context.
Can I upload source or supporting files?
Yes, within the supported file types and security limits. Controlled text, Markdown, HTML/HTM, XML and ZIP project material can supplement the Builder specification.
Do uploaded files override what I explicitly selected in Builder?
No. Explicit Builder choices remain authoritative. Supporting material is context, not permission to silently replace the customer's selected project requirements.
Can I control the design instead of using a fixed template?
Yes. Omega uses configurable blueprints/design systems rather than fixed template lock-in. You can control theme, colours, typography, widths, spacing, corners, shadows, backgrounds, header, navigation, mobile menu, hero, cards, images, galleries, buttons and motion.
Can I leave design choices on Auto?
Yes. Auto can be used where you want planning assistance. Explicit selections remain requirements.
AI-Assisted Planning
AI-Assisted Planning
How Groq-assisted strategy, plan validation and Omega Local Assist fit into the production workflow.
Does the external AI generate the final production code?
No. The external AI provider is constrained to structured planning. Omega validates the planning data and its own production engines generate the final website files.
Which AI provider can Omega use?
The current architecture can use a configured remote AI provider such as Groq for structured planning, with Omega Local Assist available as deterministic fallback behavior.
What can AI planning assist with?
AI planning can assist with positioning, content emphasis, layout strategy, calls to action, image allocation, search intent and other structured strategic choices.
Can AI override my explicit Builder selections?
No. Explicit customer selections remain authoritative within the supported production architecture.
What happens if the external AI provider is unavailable?
Omega can fall back to Omega Local Assist and continue through the same controlled generation workflow.
Does AI guarantee factual accuracy?
No. AI-assisted content can be inaccurate, incomplete, outdated or unsuitable. Customers must review factual claims, prices, legal text, professional advice, contact details and other important content before publication.
Does AI-generated content automatically have copyright protection?
Not necessarily. Contractual permission to use output and statutory copyright protection are separate legal questions that can depend on jurisdiction, human authorship and third-party rights.
Pure HTML & WordPress
Pure HTML & WordPress
How the two production targets differ and what the lifetime licence allows later.
Can Omega generate both Pure HTML and WordPress websites?
Yes. The lifetime licence includes rights to generate either supported production target for the same permanently licensed domain.
Does one build generate both formats at the same time?
No. Each build selects one production target so generation and validation remain deterministic: Pure HTML or WordPress.
Can I generate Pure HTML now and WordPress later for the same licensed domain?
Yes. The same domain licence can be used for a later generation using the other supported platform without buying a second licence for that same domain.
What is in the Pure HTML output?
The Pure HTML path is designed around semantic HTML5 pages, local CSS, vanilla JavaScript, responsive images and supporting files such as sitemap, robots, llms.txt and deployment resources appropriate to the specification.
What is in the WordPress output?
Omega uses a dedicated WordPress renderer to create a native WordPress package with theme architecture, generated content/setup material, responsive assets and WordPress-specific behavior rather than simply renaming HTML files.
Can WordPress output use block/Site Editor or classic PHP architecture?
Yes. The dedicated WordPress renderer supports platform-appropriate architectures including block/Site Editor and classic PHP theme structures where appropriate.
Does the WordPress package include WordPress Core?
WordPress Core remains independently maintained and updateable. Omega generates the website-specific package, theme/content/setup resources and related assets.
Does the WordPress package include every plugin I might ever need?
No. Third-party plugins, premium plugin licences and external integrations remain separate considerations.
Two Live Preview Workflows
Two Live Preview Workflows
The difference between Builder preview before purchase and Website Editor preview after purchase.
Does Omega Web Pro have more than one live preview?
Yes. Omega has two distinct preview workflows: public Builder preview for generated websites and private Website Editor preview for direct source editing after purchase.
What does the Builder preview show?
It shows the generated project in desktop, tablet and mobile modes before purchase and helps verify layout, content, imagery and responsive behavior.
What health checks are used in Builder preview?
The current preview workflow checks whether required generated CSS, JavaScript and image assets load successfully before the relevant purchase/export path proceeds.
Is Builder preview permanent hosting?
No. It is temporary generation infrastructure, not the durable production deployment.
What does Website Editor preview show?
It mirrors valid current source edits for the authenticated customer's licensed project in a sandboxed preview beneath the code editor.
Can Website Editor preview show desktop, tablet and mobile modes?
Yes. The private editor preview supports responsive viewport inspection.
Why are there two separate preview systems?
They solve different problems. Builder preview is for reviewing a newly generated project. Website Editor preview is for reviewing direct code edits to an existing licensed website.
Purchase, Checkout & Lifetime Licence
Purchase, Checkout & Lifetime Licence
Pricing, Stripe Checkout, pending orders, account creation and the permanent domain rule.
Can I build and preview before paying?
Yes. The Builder can generate and preview the website before purchase. The protected licensed deliverable and lifetime entitlement are the paid boundary.
What exactly costs NZ$999?
NZ$999 is a one-time payment for one Omega Web Pro Lifetime Single Website Domain Licence for one permanently assigned normalized website domain.
Is NZ$999 a subscription?
No. It is a one-time Omega Web Pro licence purchase. Separate third-party costs such as domain registration, hosting, email, premium plugins or external services can still recur.
Does NZ$999 include domain registration?
No. Domain registration and renewal are separate.
Does NZ$999 include web hosting?
No. Hosting is separate unless expressly supplied under another agreement.
Can one licence be used for several domains?
No. One licence is permanently assigned to one normalized website domain. A different domain requires its own licence.
Can I change the licensed domain later?
The standard licence is designed to keep the purchased domain permanent. My Account is not a domain-transfer control.
If I already own the licence for that domain, do I pay NZ$999 again?
No. Eligible future same-domain generation and editing workflows are recognized under the existing lifetime licence.
How is payment handled?
Omega uses secure Stripe Checkout for the hosted payment flow.
What happens after successful payment?
Omega verifies the payment server-side, creates or associates the customer account, creates/associates the permanent licence and authorizes the purchased project workflow.
Do statutory consumer rights still apply?
Yes where applicable law provides rights that cannot be excluded. The Terms explain Omega's contractual position and mandatory-rights boundaries.
My Account
My Account
How purchase-created accounts, licences, pending checkout, purchase history and security controls work.
Do I create an Omega account before purchase?
There is no public self-registration flow in the current architecture. A customer account is created or associated after a confirmed paid purchase.
How is a new customer account activated?
Omega sends a secure account setup process to the purchaser email associated with the confirmed transaction.
Can one account own multiple licensed domains?
Yes. One customer account can hold multiple separately purchased lifetime website domain licences.
What permanent IDs are associated with the account and website?
The system uses a Customer Account ID, a Licence ID for each permanent domain licence and a Website ID for the licensed website project.
What appears in My Account for each licensed website?
The dashboard can show the licensed domain, licence status, Licence ID, Website ID, supported platforms, generation count, last platform used, last generated time and lifetime editing rights.
What is Pending Checkout?
It lists unpaid Omega licence orders belonging to the signed-in customer account.
What does Proceed to Checkout do?
It returns the customer to the existing open Stripe Checkout Session for that exact pending order when available.
What does Delete Pending Checkout do?
It removes an abandoned unpaid order from the account and attempts to expire/cancel the active Stripe Checkout Session where available.
Can Delete Pending Checkout remove a paid order or issued licence?
No. Completed payments, paid purchase records, Licence IDs, Website IDs and permanent licensed domains are protected from that control.
What is Purchase History?
It shows the original paid lifetime domain licence transactions linked to the account.
Are later same-domain downloads recorded as new NZ$999 purchases?
No. Future eligible same-domain generations and updated ZIP exports are rights under the original licence, not new paid licence purchases.
Can I update my profile?
Yes. Customer contact details can be updated without changing the permanent Licence ID, Website ID, licensed domain or ownership relationship.
Can I change my login email?
Yes through the secure verification workflow. The new email does not replace the existing login address until verification succeeds.
Can I change or reset my password?
Yes. Password changes and reset-by-email are supported through the account security workflow.
Should I share my account credentials?
No. Keep account credentials private.
Website Editor
Website Editor
Direct source editing, live validation, canonical protection, versions and updated ZIP generation.
Who can use Website Editor?
Authenticated purchased customers can use it for active licensed Website IDs that belong to their account.
Can I edit the actual project source files?
Yes. Website Editor exposes authorized supported project files for direct editing.
What editing tools are available?
The current editor includes project/file navigation, line-aware editing, Undo, Redo, Find, Find Next, Replace and Replace All.
Does Website Editor have live preview?
Yes. Valid current edits can appear in the second real-time sandboxed preview beneath the editor.
What are the 14 Website Editor validation responsibilities?
They are 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.
What happens when the editor detects a blocking error?
A newly introduced blocking issue can be reported with the responsible validation area and line number. The affected line can be highlighted and changed Preview/Save can remain blocked until corrected.
Does the editor validate only in the browser?
No. Client-side validation provides immediate feedback, but accepted saves are revalidated server-side and backend checks remain authoritative.
What kinds of syntax/data issues can be blocked?
The current validation architecture can detect issues across HTML, CSS, JavaScript, JSON/JSON-LD, XML and malformed data such as invalid UTF-8 or NUL bytes, along with selected unsafe patterns.
Can I change the licensed root domain in Website Editor?
No. The permanent home canonical host remains locked to the licensed domain.
Can I rename an internal page such as terms.html?
Yes, if the project is updated consistently. An internal page can be renamed and its canonical path can change while remaining under the same permanent licensed host.
Does Website Editor execute customer-edited PHP in the live preview?
No. Customer-edited PHP is not executed in the preview environment.
Does Website Editor create version history?
Yes. Accepted saves create versioned revisions for the licensed project.
Can I generate a new ZIP after editing?
Yes. After whole-project validation, the editor workflow can generate an updated signed licensed ZIP.
Can Website Editor modify Omega Web Pro's own application source?
No. Editing is scoped to the authenticated customer's licensed website project, not the Omega Web Pro application.
Lifetime Re-editing & Licensed ZIP
Lifetime Re-editing & Licensed ZIP
How Builder regeneration, ZIP restore and Website Editor complement one another.
What is the licensed ZIP?
It is the protected deployable website package associated with the paid project/licence and can contain signed portable project information used by supported re-edit workflows.
Should I keep my downloaded ZIP?
Yes. Keep secure backups of the latest licensed ZIP and the deployed website. Temporary Omega build workspaces are not intended to be a permanent backup service.
How do I edit the website later?
You have two paths: return through Builder for specification-level regeneration, or use Website Editor for direct source-file editing.
How does licensed ZIP re-editing work?
Upload a previously downloaded licensed Omega ZIP through My Account. Omega verifies the authenticated account, Licence ID, Website ID, permanent normalized domain and Omega project signature before reopening supported project data in Builder.
Can I upload any arbitrary ZIP and make it licensed?
No. The import path validates Omega portable-project information, ownership/licence relationships, paths and other security conditions.
Can I switch from Pure HTML to WordPress later?
Yes for the same licensed domain. A later Builder generation can select the other supported production target.
Does lifetime re-editing mean the domain itself can be swapped?
No. Lifetime editing follows the permanently licensed domain; a different domain requires a separate licence.
Engines, Images & Quality
Engines, Images & Quality
Image production, SEO/schema, accessibility, performance, security and Web Metrics boundaries.
What are the coordinated Omega quality responsibilities?
The architecture covers Website Specification, Brief Normalization, AI Planning, Plan Validation, Site Architecture, Content Conversion, Design System, Image Engine, SEO + Schema, Accessibility, Forms + Backend, Deployment, Quality / Metrics and Final Validation, followed by platform-specific rendering.
What does the Image Engine do?
Uploaded media can be converted into responsive production image families such as AVIF, WebP, JPEG and PNG, with responsive delivery and icon/favicons where the workflow calls for them.
Does Omega unnecessarily upscale small source images?
The current image architecture is designed to avoid unnecessary upscaling beyond useful source dimensions.
Can Omega create favicons and multi-resolution ICO resources?
Yes. The current image architecture includes favicon and multi-resolution ICO/icon production.
Are Omega readiness checks the same as Lighthouse scores?
No. Omega's checks are build-time readiness diagnostics. Lighthouse and Core Web Vitals must be measured on the deployed URL because hosting, network, browser and third-party code affect runtime results.
Does a security readiness result mean the site cannot be hacked?
No. Omega can generate security-conscious structure and validate selected conditions, but no builder can guarantee a deployed website will never be compromised.
Does accessibility readiness certify WCAG compliance?
No. It is a structural readiness indicator, not certification or legal advice. Manual and real-world testing is still required.
Does SEO/schema generation guarantee Google rankings?
No. Omega can produce search-supporting structure, metadata, schema and crawl files, but rankings depend on many factors outside the platform's control.
What is Web Metrics for?
Web Metrics provides build-time diagnostics and quality/readiness information. It should not be misrepresented as deployed real-user performance data.
Forms, Email & Integrations
Forms, Email & Integrations
What happens with contact forms, SMTP and WordPress-native form handling.
Can Omega generate contact and conversion forms?
Yes. Builder features can include secure contact forms, newsletter sections, booking/appointment CTAs, quote CTAs and lead-magnet/download CTAs.
How do Pure HTML forms send email?
When server-side email delivery is required, the Pure HTML workflow uses compatible backend handling and authenticated SMTP configured privately on the server.
Where should SMTP passwords and API keys be stored?
In private server configuration outside public_html where the hosting environment permits, never in browser JavaScript or downloadable customer-facing source.
How are forms handled in WordPress output?
The dedicated WordPress renderer converts form handling to WordPress-native mechanisms such as admin_post/admin_post_nopriv, nonce verification and wp_mail where applicable.
Does a successful form button click guarantee email delivery?
No. Real delivery also depends on server handling, SMTP or wp_mail configuration, sender reputation, SPF/DKIM/DMARC and recipient filtering.
Hosting, Deployment & Backups
Hosting, Deployment & Backups
Deploying the ZIP, file permissions, DNS, HTTPS and production testing.
Does the final website require Omega hosting?
No. The exported Pure HTML or WordPress website can be deployed to compatible hosting selected by the customer.
What are typical public-site permissions?
A common hosting baseline is 755 for public directories and 644 for public files, subject to the hosting provider's requirements. Do not use 777.
What about private Omega-generated storage?
Where the host permits, tighter private permissions such as 750 for directories and 640 for files are appropriate.
How do I deploy Pure HTML?
Place the generated website files in the intended document root so index.html and its asset directories are not accidentally buried inside an extra wrapper folder.
How do I deploy WordPress?
Use a compatible WordPress installation and the generated theme/content/setup/import material according to the package instructions.
Who manages DNS and HTTPS?
The customer or chosen hosting/domain provider manages DNS and TLS/HTTPS unless separately supplied.
What should I test after deployment?
Test navigation, responsive behavior, forms, HTTPS, redirects, canonicals, sitemap, robots, schema, Lighthouse/Core Web Vitals, accessibility, security and browser/server errors on the final live URL.
Should I keep independent backups?
Yes. Keep the latest licensed Omega ZIP plus normal production backups. WordPress deployments should also include database backups.
Privacy, Security & Payments
Privacy, Security & Payments
Credential handling, card data, permanent records and sensitive-data considerations.
Where are Stripe secret keys and private credentials kept?
Production secrets are designed to remain in private server configuration outside public_html rather than in client-side JavaScript or downloadable website ZIPs.
Does Omega store my full card details?
Stripe handles the hosted payment flow. Omega stores transaction/licence references needed for fulfilment and account administration; it should not need to store raw card numbers from Stripe Checkout.
Why are licence/order records permanent if build projects are temporary?
Temporary generation data and permanent commercial records serve different purposes. Lifetime rights require durable Account, Order, Licence, Website and domain records even after temporary workspaces are cleaned up.
Can I use the Builder for highly sensitive personal information?
Avoid unnecessary sensitive data. Only submit information you are authorized to process and review the Privacy Policy, especially where AI-assisted planning or third-party services are involved.
Does Omega guarantee the generated website is legally compliant?
No. Generated wording and structural readiness checks are not a substitute for professional advice appropriate to the customer's business, jurisdiction and data practices.
Who is responsible for the final published content?
The customer. The customer decides what to publish and is responsible for checking accuracy, legality, rights clearance and suitability.
Legal, Accessibility & Support
Legal, Accessibility & Support
Binding policies, acceptable use, accessibility, support channels and what Omega does not guarantee.
Can I build any type of website?
Omega is intended for lawful use, but the Acceptable Use Policy prohibits harmful, fraudulent, infringing, malware-related and other abusive uses. Regulated industries may require specialist review.
Does Omega provide legal advice?
No. Generated policy wording and platform guidance are not a substitute for advice from a qualified professional.
Does Omega guarantee SEO rankings?
No. Search rankings depend on search engines, competition, content, authority, deployment quality and other external factors.
Does Omega guarantee security against every attack?
No. Generated security readiness is not a guarantee against compromise. Ongoing hosting configuration, credentials, updates and operational security remain important.
Does Omega guarantee accessibility compliance?
No. Structural accessibility readiness is not certification. Manual and real-world accessibility testing is still required.
Where are the binding legal documents?
See the Terms & Conditions, Privacy Policy, Acceptable Use Policy, Copyright & IP Policy, Accessibility Statement and Purchase & Lifetime Licence Guide.
Where can I get support?
Use support@omegawebpro.com or the Support page for account, licence, Builder, Website Editor, generation, export and deployment issues.
Where can I ask sales questions?
Use sales@omegawebpro.com for sales enquiries and contact@omegawebpro.com for general enquiries.
Need more detail?
Use the dedicated documentation for the workflow you are working on.
The FAQ gives direct answers. The documentation library provides deeper implementation and customer workflow detail.
Build • Preview • Licence • Regenerate • Edit Code • Own
Still deciding? Build the website before you buy the licence.
Open the Universal Website Studio, define the project, generate it and inspect the responsive preview. If you purchase it, the same licensed domain then gains the full lifetime My Account, Builder and Website Editor workflow.