XM Cloud Key Capabilities and Features

Content Modeling

XM Cloud uses Sitecore’s traditional content modeling approach:

• Data Templates: Define content schemas with fields, inheritance, and sections
• Template inheritance: Base templates provide shared fields (e.g., SEO metadata, navigation properties)
• Rendering variants: One component definition with multiple display variations
• Datasources: Components reference separate content items rather than storing content directly in layout

Best practice (2026): Break content into small, reusable components rather than monolithic page templates. This aligns with modern headless frontend patterns.

Example — Component-based approach:

# Anti-pattern: Monolithic Article Page with 20+ fields
Article Page Template
├─ Title, Subtitle, Author, Date, Hero Image, Hero Headline...
└─ (20+ fields in one template)

# Better: Component-based composition
Article Page Template
├─ Inherits from: Page Metadata Base
└─ Components Placeholder:
    ├─ Article Hero Component
    ├─ Article Body Component
    └─ Article Sidebar Component

Personalization

XM Cloud offers two personalization tiers:

Embedded Personalization (Included)

• Component-level variants (show different versions of a component based on rules)
• Simple rules: device type, referrer, URL parameters
• Configured in Pages Builder
• Good for basic personalization needs

Sitecore Personalize + CDP (Separate License)

• Advanced personalization with real-time decisioning
• Customer Data Platform (CDP) for unified customer profiles
• AI/ML-driven recommendations
• Real-time segment evaluation
• Significantly higher cost

Personalization Reality Check

If you’re migrating from Sitecore XP, know that xDB-based personalization (server-side rules, pattern cards) has no 1:1 equivalent in XM Cloud. Embedded personalization is simpler than xDB. For advanced needs similar to xDB, you’ll need Personalize + CDP (separate license, substantial additional cost).

Multilingual Content

Built-in language support with:

• Language versions per content item
• Fallback rules (if content doesn’t exist in French, fall back to English)
• Translate workflow integration points
• Standard Sitecore language architecture

Media Management

• Cloud-hosted media library
• Automatic image optimization and resizing (via Sitecore Image API)
• DAM integration via Content Hub (separate Sitecore product)
• Media items published to Experience Edge like content

Search

Critical change from XP/XM: XM Cloud does not include built-in search.

Solr (the traditional Sitecore search engine) is gone. Your options:

1. Sitecore Search (SaaS, separate license): Sitecore’s cloud search offering, integrates with XM Cloud
2. Third-party search: Algolia, Elasticsearch, Azure Cognitive Search, etc.
3. Build your own: Query Experience Edge GraphQL, index results in your own search solution

Most XM Cloud projects use Sitecore Search or Algolia.

GraphQL API (Experience Edge)

Experience Edge provides a GraphQL API for querying content:

• Schema introspection: Explore available types and fields via GraphQL IDE
• Pagination: Query large result sets efficiently
• Filtering: Filter items by template, field values, tree path
• Complexity limits: Overly complex queries are rejected (avoid deep nesting, request only needed fields)

Example query:

query GetArticles {
  search(
    where: {
      AND: [
        { name: "_path", value: "/sitecore/content/Articles", operator: CONTAINS }
        { name: "_templates", value: "Article-Page-Template-ID", operator: EQ }
      ]
    }
    first: 10
  ) {
    results {
      items {
        ... on ArticlePage {
          title: field(name: "Title") { value }
          publishDate: field(name: "Publish Date") { value }
        }
      }
    }
  }
}