Independent Web Studio

Hosting is not just where a website “lives.” It is part of the operating system for backups, updates, recovery, performance, billing, and access. SiteGround can be a sensible option for a small web studio when its current offering fits the project, but a responsible decision should begin with the site’s needs—not a plan name or a promotional price.

Open the account in the identity that should own it. For a client project, that is usually the client. For your own studio site or sandbox, it may be you. Use a strong unique password, turn on available multi-factor protection, set recovery details deliberately, and record who can approve billing or infrastructure changes.

When you create a project, separate it clearly from other client work. Confirm where the domain’s DNS is managed, where backups are visible, whether staging is available for the selected service, and how you would restore a prior version if a change fails. Before installing WordPress, make one written note that identifies the production URL, staging URL if present, owner, recovery contact, and backup expectation.

Do not assume a host backup replaces your own launch discipline. Test updates in a safe environment when the change has risk, verify the public site after deployment, and keep a copy of approved assets and content outside the host.

Use SiteGround’s current official information for plan details and interface steps; those change. If you use another host, the same ownership, recovery, backup, and staging questions still apply.

Definition of done: one project has an identified owner, recovery contacts, documented domain/DNS relationship, and a known backup or rollback path.

Next: Set up your first WordPress website. Return to the Independent Web Studio guide.