// FirstSpirit CMS Integration

AI ready structured data for
FirstSpirit CMS.

FirstSpirit is an enterprise content management system developed by Crownpeak, designed for complex multi-channel content delivery. Known for its powerful editorial environment, FirstSpirit enables organizations to manage content across websites, apps, and digital touchpoints from a single platform.

enhancely automatically generates the right JSON-LD (schema.org) for each FirstSpirit page—fully event-driven, no manual markup required.

What sets FirstSpirit apart is its content-first approach. Content is managed independently of its presentation, allowing teams to create once and publish everywhere. The system supports multi-language projects natively, with dedicated workflows for translation and localization across markets.

FirstSpirit's architecture is built around modular components: the SiteStore manages page structures, the ContentStore holds structured datasets, and Content2 stores provide flexible database-backed content management. Templates use FirstSpirit's own scripting language with full access to project data, making it highly customizable.

The system includes built-in release workflows, role-based permissions, and a visual page editor. Its module system allows extending functionality through FSM (FirstSpirit Module) packages that are installed via the ServerManager.

The enhancely integration connects to FirstSpirit-powered websites and automates the generation of structured data. It listens for page release events, sends content to the enhancely API for JSON-LD generation, and stores the results directly in FirstSpirit's Content2 store for seamless template integration.

// How it works

Fully automatic, event-driven.

The integration is delivered as a FirstSpirit Module (FSM) and operates fully automatically once configured.
01

Event Listener

A FirstSpirit service listens for page release events in the SiteStore.
02

HTML Rendering

When a page is released, the service renders the page HTML, determines the public URL, and sends both to the enhancely API.
03

Dataset Tracking

A corresponding dataset in a Content2 store is created or updated to track the processing state.
04

Background Polling

A background process checks enhancely every 5 minutes for completed JSON-LD generation.
05

JSON-LD Storage

Once available, the JSON-LD is stored in the dataset and the state becomes "up to date".
06

Template Integration

The structured data is then included in page templates during the next full deployment.
07

Multi-language

The integration supports multi-language projects—JSON-LD is generated separately for each language.
// Architecture

Three components, one integration.

The integration consists of three main parts working together.
FS

FirstSpirit Service

Listens for release events and triggers processing. Also runs the background polling every 5 minutes to retrieve completed JSON-LD from enhancely.

API

Enhancely API

External service that analyzes page content and generates JSON-LD structured data.

C2

Content2 Store

Database-backed storage inside FirstSpirit where generated JSON-LD, processing states, URLs, and ETags are persisted per page and language.

// Real-time

Event-driven processing.

01
Release Events
Release events trigger immediate processing — no waiting for scheduled jobs.
02
Content Projections
Datasets with page references are also processed during release and initial setup.
03
Background Polling
Handles the asynchronous nature of JSON-LD generation — checking every 5 minutes until results are ready.
04
ETag Support
Ensures efficient change detection without unnecessary data transfer.
// Getting started

One-click initial setup.

01
Validate
Validates all configuration fields
02
Create Store
Creates the Content2 store and installs the database schema (if not already present)
03
Scan Pages
Scans all released pages in the SiteStore and datasets with content projections
04
Render HTML
Renders HTML for each language and sends it to enhancely
05
Track State
Creates datasets in the Content2 store to track processing state

API Response Codes

200: JSON-LD ready—structured data returned in response body

201: URL queued—submitted for processing, available on subsequent requests

202: Processing—URL currently being analyzed

304: Not modified—ETag match, cached version is valid

429: Rate limited—too many requests, retry later

Compatibility & Requirements

FirstSpirit Server >= 5.2.260308

enhancely Account with valid API key

ServerManager Access with administrator permissions

Database Layer configured for Content2 store

// Integration Partner

Freshly served by Neo Reply.

This integration was developed by Neo Reply, a Digital Experience Platform (DXP) specialist within the Reply Group. With decades of hands-on experience in enterprise content management, AI-powered personalization, search technologies, and e-commerce integrations, Neo Reply brings deep expertise to every CMS ecosystem they work with — and FirstSpirit is no exception.

The enhancely FirstSpirit CMS module can be obtained from Neo Reply. Please reach out at neoreply.de.
Neo Reply logo
This enhancely integration has been freshly served by Neo Reply

About Neo Reply

Neo Reply is the Digital Experience Platform specialist within the Reply Group. Together with their clients, they develop tailored DXP strategies and solutions—from conception and planning through architecture to successful frontend and backend implementation.

Learn more at neoreply.de

“FirstSpirit powers some of the largest, most complex enterprise websites out there — and that's exactly where enhancely delivers the most value. Thousands of pages, dozens of languages, constant content updates: all handled automatically, without a single manual line of markup. The Neo Reply team implemented the FSM module with impressive precision and deep understanding of what enterprise content teams actually need. AI readiness is often treated as a big, expensive project. It doesn't have to be. With the FirstSpirit integration, you install one module, run the initial setup, and you're done. The foundation is laid — at scale, in minutes.”

Bastian Sirvend, Founder, enhancely.ai

“Enterprise content teams don't need another big project — they need smart integrations that deliver impact fast. FirstSpirit's architecture made it straightforward to build something that's fully automated, multi-language ready, and requires zero ongoing effort from editors. Once the FSM module is in place, enhancely quietly does its job in the background. For large sites with hundreds or thousands of pages, the ROI is immediate. AI readiness shouldn't be a quarter-long initiative. With this integration, it isn't.”

Dr. Raphael Richter, Managing Director, Neo Reply
// Resources

Learn more.

Docs
Full Documentation
Complete API and integration documentation
Git
GitHub Repository
Source code and examples
NEO
Get the Module
Get the code for FirstSpirit CMS x enhancely integration from Neo Reply
// FAQ

FirstSpirit & enhancely
FAQ.

FirstSpirit is an enterprise content management system developed by Crownpeak, designed for complex multi-channel content delivery. It offers a powerful editorial environment where organizations can manage content across websites, apps, and digital touchpoints from a central platform. FirstSpirit supports both headless and hybrid delivery models, making it suitable for enterprises requiring traditional CMS authoring alongside modern API-driven architectures. It's known for its strong governance features and multi-site, multi-language capabilities.
FirstSpirit does not include automated Schema.org generation. Structured data must be implemented in frontend templates by development teams, which requires understanding the Schema.org specification, search engine compliance requirements, and ongoing maintenance as content models evolve. The enhancely integration for FirstSpirit — developed by Neo Reply, a DXP specialist within the Reply Group — automates this entirely with validated JSON-LD markup across all 806 Schema.org types.
The enhancely integration was developed by Neo Reply, a DXP specialist within the Reply Group with decades of experience in enterprise content management. It connects via FirstSpirit's ServerManager and ContentCreator modules. The integration uses a database-backed Content Layer for persistent caching, ensuring high availability in enterprise deployments. Setup requires FirstSpirit Server 5.2+ and administrator access to the ServerManager.
No. After the initial technical setup (handled by your FirstSpirit administrator or Neo Reply's team), enhancely operates autonomously. Content authors publish through FirstSpirit's editorial environment as usual — no schema configuration, no JSON-LD knowledge required. Schema markup is generated, validated against Google and Bing guidelines, and deployed automatically for every page. The enhancely dashboard gives marketers full visibility into structured data coverage and Rich Result eligibility.
Every piece of markup passes through a 3-layer curation pipeline before deployment. Layer 1 (Validity) checks against the full Schema.org specification — all 806 types, every property, every value range. Layer 2 (Factuality) cross-references structured data against your actual page content — no hallucinated data, no invented prices, no phantom opening hours. Layer 3 (Compliance) verifies Rich Result eligibility against Google, Bing, and AI search engine guidelines. Peer-reviewed research (Dang et al., Semantic Web Journal, IOS Press, 2025) showed that without such a pipeline, 40–50% of AI-generated markup is invalid or non-compliant.
Yes. Multiple JSON-LD blocks on a single page are valid and supported by all major search engines — Google, Bing, and others evaluate and merge all structured data blocks they find. enhancely adds additional, validated markup without conflicting with or overwriting your existing schema. If enhancely detects invalid or outdated markup from other sources, Schema Healing can automatically identify and repair it — so legacy schema from previous tools or manual implementations gets fixed and kept current.

Stop leaving
bots hungry.

Your content is already great for humans. Let us make it perfect for bots.
Get started → Contact Neo Reply