// Magnolia CMS Integration

AI ready structured data for
Magnolia CMS.

Magnolia is an enterprise-grade, Java-based content management system known for its flexibility and powerful authoring capabilities. Founded in 2003 in Basel, Switzerland, Magnolia powers websites for leading global brands with its intuitive page editor, multi-site management, and seamless integrations.

The enhancely integration connects to Magnolia-powered websites and automates the generation of structured data. It creates page-specific JSON-LD markup that helps search engines and AI systems interpret your content accurately—without requiring manual markup or additional development effort.

graph LR
  A["Browser Request"] --> B["Magnolia CMS"]
  B --> C["FreeMarker Template"]
  C --> D["enhancely API"]
  D --> E["JSON-LD"]
  E --> C
  C --> F["In-Memory Cache"]
  F --> C
  B --> G["HTML + JSON-LD"]

Fig. 1 — Magnolia CMS integration via FreeMarker template or Java Module

// How it works

Two options. Same result.

Choose the approach that best fits your Magnolia setup.

URL Detection

The FreeMarker template determines the current page URL.

API Call

The URL is sent to the enhancely API for analysis.

JSON-LD Return

enhancely returns ready-made JSON-LD for that page.

HTML Injection

The template injects it as <script type="application/ld+json"> in the HTML head.

Caching

Built-in ETag caching with 7-day TTL prevents repeated API calls.

Public Only

The integration only runs on the public instance—author remains unchanged.

// Two options

Java Module or Light Module.

Both options deliver the same result: automatic, page-specific JSON-LD.

JAR

Java Module

A single JAR deployed into your Magnolia webapp. Includes in-memory caching with configurable TTL, ETag-based revalidation, and graceful fallback on API errors. Recommended for production.

Light Module

No Java code required. Uses Magnolia’s built-in REST Client to call the enhancely API directly from FreeMarker templates. Configuration is a simple YAML file.

PWD

Secure Storage

API keys stored securely through the Password Manager, module configuration, or environment variables.

Caching & Reliability

ETag-aware caching (reduces API calls; keeps schema fresh)

7-day default TTL—configurable via Config App

Graceful fallback—serves cached content on API errors or rate limiting

In-memory cache—no external dependencies required

API Response Codes

200: JSON-LD ready

201: URL queued for processing

202: Processing

304: Not modified (ETag match)

429: Rate limited—serves cached content if available

Compatibility & Requirements

Magnolia >= 6.2

Java >= 11

FreeMarker Templates

Light Modules supported

// 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.

The enhancely Magnolia CMS module can be obtained from Neo Reply. Please reach out at neoreply.de.

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

“It’s remarkable how quickly Neo Reply understood, embraced, and executed the integration challenge. Enabling the enhancely integration through two different approaches showcases both the flexibility of Magnolia CMS and Neo Reply’s high level of expertise. The module is available free of charge on the official Magnolia Marketplace.”
Bastian Sirvend, Founder, enhancely.ai

“When enhancely approached us with their vision for automated structured data generation, we immediately recognized the value for enterprise content teams. Magnolia’s extensible architecture gave us the flexibility to create a solution that fits any project setup. We’re proud to contribute this module to the Magnolia community.”
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 from Neo Reply

// FAQ

Magnolia & enhancely
FAQ.

Magnolia is a Java-based enterprise CMS founded in 2003 in Basel, Switzerland. It's known for its powerful authoring experience, flexible architecture supporting both traditional and headless delivery, and enterprise-grade features including multi-site management, personalization, and DAM integration. Magnolia powers websites for leading global brands and is particularly strong in regulated industries requiring compliance, governance, and complex content workflows.

Magnolia does not include automated Schema.org generation out of the box. While developers can create custom FreeMarker templates with JSON-LD, maintaining structured data at enterprise scale — across multiple sites, languages, and content types — is complex and resource-intensive. The enhancely integration for Magnolia, developed by Neo Reply (a DXP specialist within the Reply Group), uses Light Modules with a 7-day ETag-aware cache and graceful fallback for reliability in enterprise environments.

The enhancely integration uses Magnolia's Light Modules — a lightweight extension format that doesn't require Java compilation. The integration was developed by Neo Reply, a Digital Experience Platform specialist within the Reply Group with deep expertise in enterprise content management. The Light Module includes a FreeMarker template, a 7-day ETag-aware cache, and graceful fallback that serves cached content during API outages, ensuring zero downtime for your structured data.

Initial setup requires a developer to install the Light Module and configure the FreeMarker template — typically under an hour. After that, enhancely runs autonomously with no ongoing development work. Content authors and marketers publish as usual in Magnolia's editorial environment. Schema markup is generated, validated through the 3-layer pipeline, and deployed automatically for every page update. The enhancely dashboard provides full visibility into structured data coverage across all your Magnolia sites.

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

AI ready structured data for Magnolia CMS.