Test the public experience, not just the editor
Open the published version without being signed in. Check the address a customer sees, any platform branding, the mobile layout and whether inquiries reach your business. A convenient editing screen does not establish that the free plan supports your intended public experience. Write down which important features require a paid plan rather than assuming they are included.
Plan the route out before building a large library
Check whether you can retrieve your text, images and URL list in useful formats. An export of content is different from a transferable working website. Also identify who controls the domain and how existing links would be handled after a move. Free is an initial price, not a description of long-term ownership or operating costs.
A practical check before you buy
Create one service page and a real test inquiry using non-sensitive test details. Export its content, list its address and estimate the work of recreating it elsewhere. Use that exercise before adding dozens of pages.
| Decision | What to consider | What to check |
|---|---|---|
| Address | Own domain support | Check the applicable plan |
| Content | Usable export | Inspect the actual files |
| Inquiries | Delivery and receipt | Test outside the editor |
An illustrative business scenario
A US startup validating a service can test a free site before committing its domain, sales collateral and ongoing content to that platform.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.