Answers to the Questions People Ask Before, During and After Building with Omega Web Pro.

The current Builder includes 73 industry starting points plus a custom industry/sub-industry path.

The current Builder includes 111 selectable page types spanning business, commercial, ecommerce, content, education, hospitality, locations, careers, support, legal, campaign and utility needs.

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.

The current repeatable page systems are services, locations, products, case studies, team members and articles. Structured entries can expand into individual generated pages.

Yes. Built-in page types can be supplemented with custom page requirements when the project needs something outside the catalogue.

Yes. The professional brief supports up to 50,000 characters for project requirements, business rules, terminology, exclusions, technical direction and other context.

Yes, within the supported file types and security limits. Controlled text, Markdown, HTML/HTM, XML and ZIP project material can supplement the Builder specification.

No. Explicit Builder choices remain authoritative. Supporting material is context, not permission to silently replace the customer's selected project requirements.

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.

Yes. Auto can be used where you want planning assistance. Explicit selections remain requirements.

Yes. The lifetime licence includes rights to generate either supported production target for the same permanently licensed domain.

No. Each build selects one production target so generation and validation remain deterministic: Pure HTML or WordPress.

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.

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.

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.

Yes. The dedicated WordPress renderer supports platform-appropriate architectures including block/Site Editor and classic PHP theme structures where appropriate.

WordPress Core remains independently maintained and updateable. Omega generates the website-specific package, theme/content/setup resources and related assets.

No. Third-party plugins, premium plugin licences and external integrations remain separate considerations.

Yes. The Builder can generate and preview the website before purchase. The protected licensed deliverable and lifetime entitlement are the paid boundary.

US$999 is a one-time payment for one Omega Web Pro Lifetime Single Website Domain Licence for one permanently assigned normalized website domain.

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.

No. Domain registration and renewal are separate.

No. Hosting is separate unless expressly supplied under another agreement.

No. One licence is permanently assigned to one normalized website domain. A different domain requires its own licence.

The standard licence is designed to keep the purchased domain permanent. My Account is not a domain-transfer control.

No. Eligible future same-domain generation and editing workflows are recognized under the existing lifetime licence.

Omega uses secure Stripe Checkout for the hosted payment flow.

Omega verifies payment server-side and activates only the entitlement actually purchased. For Hosting, the existing checkout-bound Account ID is promoted to paid entitlement; for a Lifetime Licence, an existing account is reused where available or the account is created after Stripe confirms the purchase.

Yes where applicable law provides rights that cannot be excluded. The Terms explain Omega's contractual position and mandatory-rights boundaries.

Authenticated purchased customers can use it for active licensed Website IDs that belong to their account.

Yes. Website Editor exposes authorized supported project files for direct editing.

The current editor includes project/file navigation, line-aware editing, Undo, Redo, Find, Find Next, Replace and Replace All.

Yes. Valid current edits can appear in the second real-time sandboxed preview beneath the editor.

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.

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.

No. Client-side validation provides immediate feedback, but accepted saves are revalidated server-side and backend checks remain authoritative.

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.

No. The permanent home canonical host remains locked to the licensed domain.

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.

No. Customer-edited PHP is not executed in the preview environment.

Yes. Accepted saves create versioned revisions for the licensed project.

Yes. After whole-project validation, the editor workflow can generate an updated signed licensed ZIP.

No. Editing is scoped to the authenticated customer's licensed website project, not the Omega Web Pro application.

The site's WordPress owner email provides its URL, WordPress admin address, assigned WordPress username, Omega Website Editor link and a password setup/recovery address. Passwords and private recovery tokens are not included in the example onboarding email. The WordPress account is separate from the Omega Web Pro customer account.

No second manual WordPress login is required for supported integrated management. Sign into Omega My Account, choose the correct paid WordPress Website ID under Your Purchased Websites and let Omega verify ownership, active hosting and platform. The WordPress setup email remains useful for optional direct WordPress account access.

Yes. The WordPress Source Code — Pages & Posts panel loads actual WordPress HTML and block content. Select a document and explicitly Save to WordPress to update the live database and preserve WordPress revisions. The embedded WordPress Manager supports additional authorised administration.

No. The dedicated Pure HTML Editor (website-editor.php) is a different page from the native WordPress Editor (website-editor-wordpress.php). The WordPress source editor and Manager work with native WordPress content, and the WordPress-responsive preview reflects the relevant WordPress page or post. Editing a separate static snapshot does not publish a WordPress theme or database update.

Eligible hosted WordPress websites have on-page validation, version history, licensed export and Deploy / Update Live Website controls. Protected native deployment is a distinct operation from Save to WordPress and must pass entitlement, platform, source and permanent-domain checks. No unsupported one-click conversion of the HTML snapshot into a WordPress theme is implied.

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.

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.

The current image architecture is designed to avoid unnecessary upscaling beyond useful source dimensions.

Yes. The current image architecture includes favicon and multi-resolution ICO/icon production.

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.

No. Omega can generate security-conscious structure and validate selected conditions, but no builder can guarantee a deployed website will never be compromised.

No. It is a structural readiness indicator, not certification or legal advice. Manual and real-world testing is still required.

No. Omega can produce search-supporting structure, metadata, schema and crawl files, but rankings depend on many factors outside the platform's control.

Web Metrics provides build-time diagnostics and quality/readiness information. It should not be misrepresented as deployed real-user performance data.

Recurring Monthly, Annual and Two-Year plans use Omega Web Pro Hosting while active. The US$999 lifetime single-domain software licence is portable and does not require Omega Web Pro Hosting; lifetime customers can add hosting separately or deploy the licensed export to compatible customer-selected hosting.

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.

Where the host permits, tighter private permissions such as 750 for directories and 640 for files are appropriate.

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.

Use a compatible WordPress installation and the generated theme/content/setup/import material according to the package instructions.

For an active Omega Web Pro Hosting plan, hosting-side HTTPS and deployment controls are managed through the Omega Web Pro hosting workflow, while the customer may still need to connect or update records at the domain registrar. Lifetime exports deployed elsewhere follow the requirements of that destination environment.

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.

Yes. Keep the latest licensed Omega ZIP plus normal production backups. WordPress deployments should also include database backups.

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.

No. Generated policy wording and platform guidance are not a substitute for advice from a qualified professional.

No. Search rankings depend on search engines, competition, content, authority, deployment quality and other external factors.

No. Generated security readiness is not a guarantee against compromise. Ongoing hosting configuration, credentials, updates and operational security remain important.

No. Structural accessibility readiness is not certification. Manual and real-world accessibility testing is still required.

See the Terms & Conditions, Privacy Policy, Acceptable Use Policy, Copyright & IP Policy, Accessibility Statement and Purchase, Hosting Plans & Lifetime Licence Guide.

Use support@omegawebpro.com or the Support page for account, licence, Builder, Website Editor, generation, export and deployment issues.

Use sales@omegawebpro.com for sales enquiries and contact@omegawebpro.com for general enquiries.