01 / THE OPERATIONAL CHALLENGE

How Do We Enforce a Single Source of Truth Across Silos?

Core Narrative: Consistent Entities

We know why entity consistency matters for GEO; now we need the operational mechanism to enforce it[cite: 1].

Diverse Touchpoints

Our brand touchpoints span internal systems (Website, Sanity CMS, Docs) and external channels (Atlassian Marketplace MPAC, Partner Portals)[cite: 1].

The Strategic Goal: Unified Distribution

Build a "Write Once, Distribute Everywhere" architecture.

Updating our entity definition in one central location automatically updates our entire digital footprint across marketing, documentation, and third-party channels[cite: 1].

02 / THE CORE ENTITY BLUEPRINT

Software Application Schema for Mosaic

Foundational Class

SoftwareApplication is our foundational schema class. It translates raw product capabilities into machine-readable structure[cite: 1].

Explicit Properties

Rather than dumping all copy into an unstructured description, we break Mosaic down into explicit schema properties[cite: 1].

Key Schema Fields

@type: SoftwareApplication (Fixes current MPAC vs Website discrepancy)[cite: 1]
name: Mosaic[cite: 1]
applicationCategory: Business Application / Project Management[cite: 1]
description: 1-2 sentence canonical definition (Immutable)[cite: 1]
sameAs: Array linking directly to MPAC listing URL to bridge uncontrolled channel[cite: 1]

03 / CAPTURING WORKFLOWS & JTBD

featureList, audience, and Disambiguation

Jobs To Be Done (JTBD)

How do we handle JTBD, target workflows, and user personas without muddying our core definition?[cite: 1]

Native Schema Arrays

We use native schema arrays designed specifically for functional capabilities and positioning guardrails[cite: 1].

Advanced Schema Fields

featureList: Array of core technical capabilities (e.g., "Cross-project capacity planning", "Real-time Jira issue sync")[cite: 1].
audience: Nested Audience object defining primary ICPs (e.g., "Jira Administrators", "Resource Managers")[cite: 1].
disambiguatingDescription: Explicit statement explaining what sets Mosaic apart from PM or CRM tools to prevent LLM hallucinations[cite: 1].
about: Array of linked entities (Atlassian Jira, Capacity Planning)[cite: 1].

04 / THE TECHNICAL EXECUTION

Interactive Master Schema Builder

Test the SSoT Architecture

Type your entity attributes below to generate production-ready JSON-LD code for your development and content teams[cite: 1].

1. Configure Entity Properties

PRODUCT NAME

APPLICATION CATEGORY

EXTERNAL BRIDGE URL (sameAs)

TARGET AUDIENCE

2. Generated JSON-LD Code

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Mosaic",
  "applicationCategory": "BusinessApplication",
  "sameAs": [
    "https://marketplace.atlassian.com/..."
  ],
  "featureList": [
    "Cross-project capacity forecasting...",
    "Real-time Jira issue synchronization..."
  ],
  "audience": {
    "@type": "Audience",
    "audienceType": "Resource Managers, Agile Coaches"
  },
  "about": [
    {
      "@type": "Thing",
      "name": "Atlassian Jira"
    }
  ]
}