Microweber is a visual website builder and CMS. This guide helps you check hosting compatibility, choose an appropriate installation method and verify the first usable site. The application, its extensions and any commercial license remain separate from the hosting account.
IN THIS ARTICLE
01 Check Microweber and hosting requirements
Check the current package requirements and the hosting resources needed for building, uploads and optional shop features. Review the edition, extensions and update route before starting a public project.
Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.
02 Install Microweber in the correct location
- Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
- Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
- Find Microweber and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
- Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. Review database, backup and update choices instead of accepting unsuitable defaults.
- Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.
03 Configure Microweber for first use
Configure the site address and administrator access, then build a small test page with the visual editor. Review form delivery and any catalogue or commerce settings you enable.
04 Example: test a visual-builder service page
Build a small page with a heading, two service cards, an image and a contact form. Save and publish it, then open the public URL in a separate signed-out browser.
| Check | Expected result |
|---|---|
| Narrow mobile viewport | Cards and text remain readable without hiding the main contact action. |
| Image | The uploaded file loads over HTTPS and fits its content area. |
| Contact form | A clearly marked test enquiry reaches the intended inbox. |
| Editing access | Public visitors cannot open editing controls or unpublished content. |
If commerce is enabled later, add a separate payment-provider test-mode checkout. A working contact page does not prove order, stock and payment processing.
Confirm the expected result
Check the page on desktop and mobile, test a form and verify uploaded images. If selling products, test the complete checkout using the payment provider's supported test mode.
05 Maintain and troubleshoot Microweber
A large builder package and image library can consume considerable storage and processing resources. Check quotas and logs before repeatedly retrying a failed install or import.
Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.
A common question
Does a successful installation mean the whole application is ready for customers?
No. Verify the public content, permissions, forms or notifications and the features you actually use. An installer success message confirms provisioning, not your complete business workflow.