Correct licensed ZIP
Use the package generated by the completed Omega workflow.
▤ OMEGA WEB PRO DOCUMENTATION • ZIP EXPORT & DEPLOYMENT
Take the Licensed Website ZIP from Omega to Your Production Hosting.
Omega generates and packages the website; the customer's hosting environment serves it publicly. This guide explains the handoff from licensed export to Pure HTML or WordPress deployment and the checks that should happen after the final URL is live.
Authoritative project ZIPNo required Omega hostingPure HTML deploymentWordPress package installationDNS + HTTPSPost-deployment testingIndependent backups
EXPORT • UPLOAD / INSTALL • DNS • HTTPS • TEST • BACKUP
DEPLOYMENT CHECKLIST● CURRENT PLATFORM REFERENCE
DocumentationBefore DeployPure HTMLWordPressDNS + HTTPSFormsTest ProductionBackupsOwnership Boundary
✓ Package validated✓ Hosting configured✓ Production URL tested
Before upload
Confirm you have the correct authoritative licensed package.
Do not deploy from a temporary preview cache or partial browser download.
Correct domain
Deploy the project to the domain covered by the licence.
Backup existing site
If replacing an existing production site, create a recoverable backup first.
Hosting compatibility
Confirm the host supports the selected platform and any optional server-side features.
Pure HTML deployment
Place generated files in the intended document root.
One of the most common deployment mistakes is leaving the actual website inside an extra wrapper directory.
Document root
Place index.html and its related directories/files at the web root intended for the domain/subdomain.
File permissions
Typical public-site files use 644 and folders 755 unless the host requires otherwise.
Optional backend
If generated PHP form handling is used, confirm PHP availability and private configuration paths.
Private files
Private configuration/storage should remain outside public_html where the hosting setup permits and use tighter permissions such as 640 files / 750 directories where appropriate.
WordPress deployment
Use the generated WordPress theme, content and setup/import material together.
The WordPress deliverable is more than a skin.
WordPress environment
Start with a compatible WordPress installation and server runtime.
Theme package
Install/activate the uniquely generated Omega theme.
Setup/import
Use the generated setup/installer material to create/update generated pages/content according to the package instructions.
Content package
Generated JSON/WXR/build-report/instruction files support installation and verification.
Public routing
Point the intended domain to the correct hosting and enforce HTTPS appropriately.
Domain registration and DNS are customer responsibilities unless separately supplied.
DNS
Configure A/AAAA/CNAME records according to the hosting provider.
TLS certificate
Issue/install a valid certificate for the production hostname.
Redirects
Choose one canonical host/protocol and configure redirects consistently.
Canonicals
Confirm generated canonical URLs match the final licensed production host/path.
Server features
Configure operational services the static ZIP cannot supply by itself.
Examples include authenticated mail, analytics accounts, external checkout links and other third-party services.
Pure HTML forms
Configure authenticated SMTP privately and test the deployed endpoint.
WordPress forms
Confirm WordPress mail and generated native form hooks operate in production.
Analytics
Add/configure the customer's chosen analytics provider if required.
Third-party links
Verify booking, checkout, maps, social and other external services use correct production URLs.
After deployment
Test the actual live URL—not only the local files.
Hosting, CDN, DNS and browser runtime can reveal issues that did not exist in the build workspace.
Navigation
Check menus, internal links, anchors, search and 404 behavior.
Forms
Submit every important form and confirm real delivery/validation.
Responsive
Test multiple real viewport sizes and devices.
Search files
Check robots.txt, sitemap.xml, canonicals, JSON-LD and noindex rules.
Performance
Run Lighthouse/PageSpeed and observe Core Web Vitals with appropriate browser/field tools.
Accessibility
Perform browser/tool/manual accessibility review.
Security
Check HTTPS, headers, server configuration, dependencies and platform update posture.
Errors
Review browser/server logs for 404s, PHP errors, blocked assets and console issues.
Ongoing operations
Keep the generated ZIP and production backups independently.
A downloadable project package is not a substitute for operational backups of the deployed site/database.
Keep Omega ZIP
Store the latest licensed export safely.
Hosting backup
Back up deployed files and configuration.
WordPress database
Back up the WordPress database separately where applicable.
Before changes
Create a restore point before major plugin/theme/server/DNS changes.
What Omega does and does not host
Generated sites do not require Omega Web Pro hosting to continue operating.
The customer controls the deployment environment after export.
Portable files
Pure HTML can run independently on compatible hosting.
WordPress portability
WordPress packages can be installed/migrated within normal WordPress hosting constraints.
Support scope
Omega support can help with generated-project/licence issues; the customer's chosen host remains responsible for its infrastructure.
Omega Web Pro documentation
Deployment is where build-time readiness becomes real-world performance.
Use the checklist on the final URL and keep both the licensed Omega ZIP and independent production backups.