Create and publish a business website

Create your first page and publish the reviewed website#

Use Website Builder & Content in a Corporate workspace. An editor can prepare drafts and reviews. Publishing requires the publisher permission.

1. In Apps, find Website Builder & Content and click Install & set up. Complete the required fields and click Save site draft settings.
2. Open Overview and click Write a page. Enter a title, add your content sections and click Save page draft.
3. From Overview, click Review homepage and navigation. Select the saved page as the homepage and click Save draft navigation.
4. Return to Overview and click Create exact full-site review. Open the review and click Open exact preview to check the pages, links and business details.
5. In the review, confirm Publish this exact website and click Publish reviewed website. From Overview, click Visit public website to verify the published pages.

Identity, language and declared business country#

Use the business name, introduction, public email and optional phone/address that visitors should actually see. The site label is a workspace label; public routing uses a separate random stable site identifier under /w/.

Choose one content language and write your own text in it. Arabic and Urdu use right-to-left presentation. Choosing a language does not translate the site, determine legal jurisdiction or change the corporate workspace’s declared business country.

Preview a website theme and save it to your draft#

Studio uses generous space, strong service typography and a geometric focal point. Atelier uses an editorial arrangement, serif headings and warm paper. Horizon uses a corporate header, structured cards and a broad graphic direction. Local uses friendly rounded sections and prominent contact information.

Saving a design updates the draft layout. The sample copy and images in the gallery are illustrative.

1. In Website Builder, open Setup or Settings and click Browse website designs, or open the gallery below.
2. Click Preview beside the design you want. Choose Use in my workspace or Use in Demo to open Website Builder with that layout selected.
3. Confirm the corporate workspace in the header. Complete the required identity, contact and review fields, choose a palette, and click Save site draft settings.
4. Open the page editor and select Visual editor to edit headings and copy on the page. Open Page settings to add or reorder sections, select images and edit links. Switch to Preview layout and choose Desktop, Tablet or Phone. Click Save page draft, then review the complete website before publishing.

Create, revise and archive pages#

Give every page a clear title, a unique lowercase-hyphen address, a search title and a short search description. Save the page draft before leaving. Validation errors preserve the entered content so you can correct the specific issue. Stale versions require reloading the current source before trying a new save.

A site supports50 retained page identities, including archived pages. Reuse an existing page when appropriate rather than treating archive as permanent deletion. Each save retains a revision and attributable history.

Before archiving, deliberately remove the page from the draft homepage, navigation and other active draft page links. Archiving changes the draft; the previously published release remains separate until you publish a later review. Reopening an archived page in the editor and saving it creates a new active draft revision.

Build pages with seven clear section types#

An opening story supplies a short label, heading, introduction and up to two links. It can use an uploaded image or the original geometric illustration. Text sections provide a heading and up to ten readable paragraphs. Services/features provide up to ten labelled explanations with original built-in icons.

Image-and-story sections place a dedicated site image beside your paragraphs. Questions/answers use up to ten complete pairs. Next-step sections provide an honest invitation and one or two destinations. Business contact sections publish email, optional phone/address and safe links.

Select a section in the outline to edit it. Move up/down reorders sections, Add section appends a supported section and Remove section asks before discarding unsaved content. Use one to20 sections per page and keep structured page content below128KB; the complete review stays below2MB.

All content is plain text. Arbitrary HTML, CSS, JavaScript, SVG, iframes and remote embeds are unavailable. The safe renderer preserves text and paragraphs without executing supplied markup.

Choose a homepage and destinations people can find#

Select an active saved page as the homepage. Add up to20 uniquely chosen active pages to navigation, give each a meaningful visitor-facing label and order the links deliberately. Save the draft navigation before submitting a review.

Typed internal links point to active pages in this same site and are resolved against the retained release. Page archiving is blocked while current draft references depend on it. External destinations accept HTTPS, email or telephone links. To send visitors to your published Ecommerce store, open Page settings, select a section that supports links and click Add storefront link. The store handles catalogue access, checkout and its configured payment methods.

Receive website enquiries in CRM#

Install CRM in the same corporate workspace. Open CRM Setup, enable the Lead contact role and save your pipeline. In Website Builder, add a Contact section, enter your public contact details and select Accept website enquiries in CRM. Save the page, submit it for review and publish the approved release.

Open the published page in a signed-out window and send a test enquiry. In CRM, open the Leads filter, select the new lead and read its activity note. The form records the enquiry for follow-up. It sends no email and grants no marketing permission. To remove the form, clear the checkbox and publish the updated page.

Upload originals with rights and meaningful descriptions#

Use the dedicated Images area for private JPEG, PNG or WebP originals. Each image is limited to5MB,8000 pixels on either side and24million pixels; unsupported animation and visibly truncated or mismatched images are rejected. Current workspace storage allowances apply. Remote downloads and generic file-ID attachments are unavailable.

The runtime performs bounded metadata, signature, dimension and SHA256 integrity checks. It does not perform a complete image decode, re-encode or malware scan and cannot guarantee rejection of every malformed image. Export a clean still image and retry if an original fails validation or delivery.

Choose an image from this site’s selector and write a deliberate nonempty description of its meaningful content, up to200 characters. The selector can load every paginated retained image; it is not limited to the first25. Images are optional for opening stories.

Only images actually referenced by the current published release become publicly deliverable. Authenticated private/preview delivery rechecks current access. Retained originals support safe old-release restoration and are not ordinary permanently deletable files. Up to500 retained site images are supported.

Give named people the right role#

Workspace owners and administrators configure the site, its app writing policy and explicit grants. Named current editors can read/write drafts, select images and submit complete reviews. Named publishers can additionally publish, restore and unpublish. The owner/admin keeps management of the company site.

App policy remains a ceiling: Managers limits writing to owners/administrators; Team permits appropriately granted current members. A grant cannot bypass a viewer demotion, staff offboarding, workspace switch, subscription allowance, licence or synchronous demo expiry. Workspace membership alone does not open private site content.

Find current members by name in Access, grant editor/publisher deliberately and review the complete paginated grant directory. Remove a grant to revoke site authority; an offboarded person already loses access immediately even if a retained grant row remains. Source history retains attributable decisions.

Inspect, publish, unpublish and restore safely#

A full-site review freezes exact page revisions, site statements, navigation, image identities and their source integrity. Its authenticated preview uses the same closed renderer as public pages. A local editor layout preview shows entered content and is not an authorization to publish.

Publishing requires current publisher authority, the exact review fingerprint and the current draft version. If any source changes, create a fresh review and inspect it again. Concurrent publication attempts cannot both replace the same current reviewed version. UUID receipts make exact successful retries safe; changing the payload under a reused identifier is rejected.

Unpublish from Overview with a retained reason when the website should stop serving publicly. Drafts, original images, reviews and release history remain retained. Unpublishing and releasing a customer-domain routing claim are separate decisions.

To recover a former version, open Releases, inspect the exact retained pages and supply a reason to restore it. Restoration creates a new release from that source without editing historical facts or overwriting the current draft. A later edit still begins from your separate draft. Missing or corrupt originals must be replaced/reviewed before safe publication or restoration.

A deliberate homepage choice, with recovery#

The /w/ address is additive. A verified and entitled customer domain may also use the published website as its homepage after a deliberate current Ecommerce-choice review. Website cannot silently take a reserved Ecommerce, marketing, authentication, administration or unknown-host root. Draft reservation alone never renders a homepage.

Domain management can release either app’s routing claim without rewriting Site/Store content, even if that app’s authoring is disabled or unlicensed. The owner reviews the current routing version and records a reason. Release persists through reenable, configuration, publication and restoration.

Reclaim is a separate explicit owner/admin action. It requires active configured entitled authoring, current package and relevant licence allowances, a raw homepage source choice and a current review showing no opposing effective claim. A publisher may need the owner to refresh changed domain settings before publishing root content.

Search settings reflect the actual published pages#

Write a meaningful search title and description for each page. Indexable published pages enter the current sitemap; private drafts and unselected history do not. A deliberately published noindex page remains directly public to anyone with its address.

Authenticated previews use noindex/nofollow and are private, with no public bearer preview token. Canonical URLs come from the verified request host and published page slugs. Search indexing or ranking is not guaranteed.

Review the actual jurisdiction and publication rights#

The declared corporate business country is a setup fact, separate from content language, visitor IP or currency. Review appropriate public privacy, business identity, consumer, accessibility and legal information for your own services and country before publication.

The owner’s review is not statutory approval, professional legal advice, medical/regulated-service certification, verified translation or full accessibility certification. Use content and images you are entitled to publish; the app does not manufacture legal text or determine those rights.

Supported scope and honest availability#

This release covers one company site, four original layouts, four palettes, ten explicit content languages, up to50 retained pages,20 typed sections per page,20 navigation destinations and500 retained images. Management selectors and history are paginated rather than silently clipped.

Forms, trackers, analytics, arbitrary embeds, automatic translations, remote theme imports, commerce carts and business-app connector blocks are unavailable. A contact or destination link remains a link. No provider notification, payment or external delivery outcome is invented.

The isolated demo supports the same declared website workflow for its configured disposable lifetime, normally three hours. Expiry is synchronous and the demo is purged; never rely on it for permanent business content or production entitlements.

Recover without losing source facts#

For validation errors, correct the relevant field while keeping entered content. For a stale version or changed review, inspect the current draft and submit a new complete review. A rejected mutation does not partially publish the site.

When a page, settings or navigation save meets a newer source, your entered draft and its old version stay intact. Open Compare current saved source in a new tab. After reviewing the differences, explicitly choose Use reviewed version to keep your entered values against that version, then save separately. This replaces the complete saved draft with a new retained revision; it does not merge changes automatically. Another intervening save still requires a fresh comparison. Domain-choice conflicts require their own current routing review.

If permissions are revoked, ask the workspace owner to check current membership, app writing policy and the named site grant. After a subscription lapse, retained reads follow the platform’s read-only behavior; previews, image delivery and publication still need current paid allowance.

For a missing image, choose a valid retained original or upload a replacement, update the page, save and create a fresh review. For an incorrect live release, unpublish or deliberately restore a reviewed retained release with a reason. For a root conflict, use domain routing release/reclaim rather than editing immutable content history.