Launch a small business website with managed design

Guides

Define the launch scope

Build a website visitors can use to understand your business and contact you. A practical first version has Home, Services, About, and Contact pages. Use managed design so staff can update ordinary content without maintaining custom HTML or CSS.

Prepare approved business details, service descriptions, contact information, opening hours, and licensed images. Confirm the selected website and administrator access. If the website is private, keep it private during preparation; only an authorized super administrator should approve a website-wide public visibility change.

Write down the one action each page should support. For example, Home introduces a repair workshop, Services explains available repairs, and Contact provides verified ways to ask a question. Remove sections that exist only to fill space.

Build the essential pages

1. In Pages, inspect existing content before using Add Page. Reuse suitable pages rather than leaving duplicate home or service pages. Set each page's Page Title, Nav Title, and URL deliberately. A concise navigation label can differ from the visible page heading.
2. Organize the main navigation in the page structure. Put the most useful pages first, and nest only when the relationship is clear. Root structure determines membership and order; matching URL prefixes are not a substitute for arranging the tree.
3. Set site fonts through Settings > Design > Fonts. Choose body and heading families that remain legible on a phone. Use page and section design settings for surfaces and spacing rather than inserting decorative HTML into text blocks.
4. Edit each real page header and add body sections. On Services, use a grid for related offerings and a Buttons block for the next step. Link to existing site pages with the destination picker so links retain page identity when URLs change.
5. Add accurate business information to the shared footer through Settings > Design > Footer. Check any existing legal links before altering footer options. If you collect enquiries, configure and test a native form rather than publishing an unconnected form-shaped layout.
6. Save each page explicitly, then review Availability and Show in site navigation. Navigation visibility and access protection are different decisions. A page omitted from menus can still be public and indexable.
7. Review page metadata and the domain separately. Saving content does not connect a domain or publish a private website. Obtain explicit approval for those operational changes and use the domain screen's current instructions.

Conduct a launch rehearsal

Open every planned launch URL outside the editor. Follow the main menu, footer links, and contact actions. Check phone layout, text contrast, image crops, and one real test enquiry using non-sensitive test data. Confirm the enquiry appears in the form's submissions and reaches its intended recipient.

If a page is missing, inspect its root membership, availability, and date before creating another copy. Fix factual omissions before adding visual detail. Consult pages and navigation, design and styling, media and forms, and site administration.