Skip to Content
Workflow GuidesContent and Discovery

Content And Discovery

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

Content and discovery covers everything that helps a customer find, understand, trust, and navigate the business before taking action.

Outcome

At the end:

Website shell is complete

Homepage, navigation, footer, core pages, policies, contact paths, and mobile layout match the business being launched.

Supporting content is ready

Stories, help articles, forms, policies, and reviews are published only where they help customers decide or self-serve.

Discovery routes are verified

SEO metadata, redirects, Open Graph, sitemap, robots, and llms.txt reflect the final domain and launch content.

Operators know the publishing path

The team understands which console changes update the public site immediately, after revalidation, or after a manual review.

The goal is not just published content. The goal is content that customers can find, trust, share, and act on, with a console owner who knows how to update it when products, services, policies, or launch messaging changes.

Step 1: Build Core Pages

Console surfaces: Website, page editor.

Minimum content:

  • Homepage.
  • About.
  • Services or products overview.
  • Contact.
  • Policies.
  • FAQ or help.
  • Any campaign landing pages needed at launch.

Verify on sites:

  • /.
  • /pages/{slug}.
  • /contact.
  • /policies.
  • Any public catchall pages.

Quality bar:

  • Page has one clear purpose.
  • Page has a clear next action.
  • Copy matches the business.
  • Links are not placeholders.
  • Mobile layout is readable.

Step 2: Add Live Business Blocks

Use live blocks when content depends on product, service, or article records:

  • Product grid.
  • Service grid.
  • Article list.
  • FAQ accordion.
  • Contact form.
  • CTA section.

Verify:

  • Block data matches console records.
  • Empty states are acceptable.
  • Feature flags do not hide required content.

Step 3: Publish Stories

Console surface: Stories.

Use Stories for editorial or resource content:

  • Articles.
  • Announcements.
  • Local SEO resources.
  • Guides.
  • Category pages.
  • Author pages.
  • Tag pages.

Verify on sites:

  • /stories.
  • /stories/{slug}.
  • /stories/category/{slug}.
  • /stories/tag/{slug}.
  • /stories/author/{slug}.
  • /stories/search.
  • /stories/rss.xml.

Step 4: Configure Help And Knowledge Content

Console surfaces: Help or content editor.

Sites surfaces:

  • /help.
  • /help/{treeSlug}.
  • /kb.
  • /kb/article/{slug}.
  • /kb/category/{slug}.
  • /kb/search.

Verify:

  • Customers can find common answers.
  • Article links work.
  • Search returns useful results.
  • Escalation path exists when content is not enough.

Step 5: Configure Forms

Console surface: Forms.

Sites surface: /forms/{formSlug}.

Forms should have a visible owner before they go public. Decide whether each submission becomes an inbox item, a customer record update, a lead, a support request, or an intake artifact so operators know where to look after the customer submits.

Verify:

  • Form renders.
  • Valid submission succeeds.
  • Invalid submission shows errors.
  • Submission lands in console.
  • Notification sends when configured.

Step 6: Configure Reviews

Console surfaces: Reviews, Integrations > Google Business Profile.

Actions:

  • Connect Google Business Profile if reviews should sync.
  • Confirm listing access.
  • Review public display expectations.
  • Confirm review moderation or response process.

Verify:

  • Reviews dashboard loads.
  • Public review surfaces show intended data.
  • Operators know how to respond.

Step 7: Configure Discovery

Console surface: Discovery.

Configure:

  • SEO titles and descriptions.
  • GEO content.
  • Redirects and short links.
  • Search verification.
  • Canonical URLs.
  • IndexNow if used.
  • Open Graph image choices.

Verify on sites:

  • /sitemap.xml.
  • /robots.txt.
  • /llms.txt.
  • /og-image.
  • /indexnow.
  • Redirect paths.

Step 8: Test Social And Search Previews

Preview testing should use the production host whenever possible because social and search crawlers care about canonical URLs, image routes, redirects, and cache state. Check the pages most likely to be shared or advertised first.

Check:

  • Homepage title.
  • Homepage description.
  • Important page metadata.
  • Product metadata.
  • Service metadata.
  • Story metadata.
  • Open Graph image.
  • Canonical host.

Step 9: Understand Publishing And Cache

After a console save, public content may update through:

  • Direct render from updated data.
  • Cache tag invalidation.
  • Webhook invalidation.
  • Revalidation route.
  • Time-based cache expiry.

If content looks stale, check the owning console surface, the public route, the webhook category, and whether the page is cached.

Content Done Criteria

Use done criteria as a publishing gate for the public site. Content is ready when it is accurate, findable, shareable, and connected to a console workflow that someone owns.

  • Customers can understand the business.
  • Customers can find the primary action.
  • Search and sharing metadata are accurate.
  • Forms and help routes work.
  • Reviews are connected if promised.
  • No draft or placeholder content is public.
Content and Discovery | Sophosic Platform