Help centre

Answers before jargon.

BGH help is being designed around tasks customers actually need to complete, not around whatever menu structure cPanel happens to use.

Future control-panel destination.This help hub will become the customer-facing destination behind the cPanel Help and Documentation links once the live domain routes exist.Information architecture

Browse by job

What are you trying to do?

These are the launch help categories. Detailed articles will be filled with verified steps from the actual BGH child-account experience rather than copied blindly from generic hosting docs.

01

Getting started

First login, account basics and what happens after provisioning.

Guide set →02

Domains & DNS

Nameservers, DNS records, redirects and bringing a domain across.

Guide set →03

Email

Create mailboxes, routing basics and common delivery checks.

Guide set →04

WordPress

Install/manage WordPress and understand what hosting covers.

Guide set →05

SSL & security

HTTPS, certificates and the security surfaces exposed to customers.

Guide set →06

Backups & recovery

What recovery options exist, what they cover and where the boundaries sit.

Guide set →07

Resource usage

Read CPU/resource graphs and recognise a genuine hosting constraint.

Guide set →08

Renewal & billing

Annual renewal, plan changes and what happens before any suspension.

Guide set →09

Moving a site

What we need from the current host and how the migration process works.

Guide set →

Support model

Ask the right layer.

The fastest support starts by separating hosting problems from website-work requests.

H
Hosting supportAccount, server, DNS, SSL, email and hosting-platform issues.
W
Website workContent, plugins/themes, redesign and maintenance belong in Website Care or a scoped project.
M
MigrationHandled as a controlled move with evidence first.

FAQ preview

Straight answers.

The wording is ready; final platform-dependent details will be tightened after Lab validation.

Not yet. The commercial experience and pricing are being finalised now; a small set of infrastructure details still needs live DNS and child-account validation.
No. BGH will publish clear, enforceable allowances rather than pretending shared hosting has no practical limits.
Potentially, yes. We inspect the current host, platform, DNS and email setup first so the migration route is based on facts rather than promises.
No. Website architecture should fit the job. WordPress is useful when its editing and ecosystem benefits are justified, but it is not the automatic answer.
No. Hosting covers the hosting/account/server/DNS/SSL/email layer. Ongoing content, plugin/theme work, redesign and other human website work are separately scoped.