Skip to Content
Workflow GuidesSite Publishing

Site Publishing

console.sophosic.ai/workflows
PagesPublished
HomeLive
BookLive
Book
Site publishingConsole-managed content rendered as customer-facing pages and portal routes

This runbook turns console settings and content into a public site customers can use.

Outcome

At the end:

  • The site shell is branded.
  • Navigation, footer, legal links, and pages are complete.
  • At least one customer action works across the full customer path.
  • Discovery and sharing metadata are verified.
  • The site status is ready for real traffic.

Step 1: Decide The First Customer Action

Choose the action that matters most for launch:

Customer action

Buy a product

Console setup: Products, Payments, Shipping, Checkout and Tax

Public verification: Shop, product detail, cart, checkout, success, order portal

Customer action

Book a service

Console setup: Scheduling, Services, Payments, Calendar Sync

Public verification: Bookings, scheduler, confirmation, manage/reschedule

Customer action

Submit a request

Console setup: Forms, Inbox, Email Notifications

Public verification: Public form, success state, console submission, email

Customer action

Get support

Console setup: Help, Tickets, Inbox, Customers

Public verification: Help tree, ticket create, portal thread

Customer action

Read content

Console setup: Website, Stories, Discovery

Public verification: Public pages, stories, search previews

Do not publish without at least one completed customer action path.

Step 2: Build The Site Shell

Console surfaces: Website, Settings > Branding.

Configure:

  • Header navigation.
  • Footer sections.
  • Logo.
  • Theme and colors.
  • Typography.
  • Social links.
  • Legal links.
  • Public preview.

Verify on sites:

  • Header links work on desktop and mobile.
  • Footer links work.
  • Logo and colors are legible.
  • Public pages use the intended brand.
  • No placeholder content is visible.

Step 3: Add Core Pages

Console surfaces: Website, page editor.

Minimum page set:

  • Homepage.
  • About or business overview.
  • Product, service, or offering page.
  • Contact.
  • Privacy policy.
  • Terms.
  • Refund/cancellation policy.
  • Shipping policy when products ship.
  • Help or FAQ page when support volume is expected.

Verify:

  • Each page has a clear customer purpose.
  • Each page has a primary next action.
  • Mobile layout is readable.
  • No unpublished draft text is present.

Step 4: Add Conversion Blocks

Console surfaces: Website, Products, Scheduling, Forms.

Add live data blocks when possible:

  • Product grid.
  • Service grid.
  • Contact form.
  • FAQ.
  • Article list.
  • Call-to-action section.

Verify:

  • Blocks render live products, services, or forms.
  • Empty states are acceptable.
  • Links point to the intended customer path.

Step 5: Configure Discovery

Console surface: Discovery.

Configure:

  • Homepage title and description.
  • Important page titles and descriptions.
  • Redirects and short links.
  • GEO or answer-engine fields if used.
  • Search verification when ready.
  • Open Graph preview.

Verify on sites:

  • /sitemap.xml.
  • /robots.txt.
  • /llms.txt.
  • /og-image.
  • Short links and redirects.
  • Canonical URLs.

Step 6: Connect Domain And Email

Console surface: Settings > Domain and Email.

Actions:

  1. Add DNS records.
  2. Verify domain status.
  3. Verify email sender.
  4. Confirm all public links use the final host.
  5. Confirm redirects from temporary launch URLs if needed.

Verify:

  • Homepage loads from the final domain.
  • Login and portal callbacks use the intended domain.
  • Email links are not pointing to a stale staging host.

Step 7: Test Public Routes

Run these from a clean browser:

  • /{site} homepage.
  • /{site}/shop if commerce is enabled.
  • /{site}/bookings if bookings are enabled.
  • /{site}/contact.
  • /{site}/forms/{formSlug} for each launch-critical form.
  • /{site}/help and knowledge paths if enabled.
  • /{site}/stories if enabled.
  • /{site}/policies.
  • /{site}/account after customer login.

Step 8: Publish

When the launch path is clean:

  1. Set the site to public or remove protection.
  2. Open the final public URL.
  3. Repeat the customer action test.
  4. Watch console Inbox, Sales, Scheduling, Customers, and Insights.

Publishing should happen with an owner watching the first customer actions. Confirm the final host, site status, primary customer path, notification receipt, and rollback owner before announcing the site or sending campaign traffic.

After publishing, check crawler and sharing surfaces from the final URL: sitemap, robots, social preview image, redirects, and any short links used in launch communications.

Rollback Options

Use the narrowest rollback:

  • Hide a bad page.
  • Disable one feature.
  • Disable checkout.
  • Pause ads.
  • Put the site back into protected or draft status.
  • Revert a DNS cutover only when routing itself is the issue.
Site Publishing | Sophosic Platform