// CoreMedia Content Cloud × enhancely

AI readystructured data forCoreMedia.

CoreMedia Content Cloud is an enterprise-grade, Java-based Digital Experience Platform (DXP) — trusted by leading global brands for its powerful editorial environment, multi-site management, and headless delivery capabilities. The enhancely integration connects directly to CoreMedia's CAE rendering pipeline and automates page-specific JSON-LD markup — without manual markup or ongoing development effort.
Get started → View on Marketplace

CoreMedia combines a robust content repository with flexible headless delivery and a Spring Boot–based rendering layer — the Content Application Engine (CAE). It powers complex editorial workflows, multilingual content, and high-volume page output across global sites: the exact environment where structured data breaks down without a dedicated pipeline.

The enhancely integration is available directly on the CoreMedia Marketplace as a Blueprint Extension — the standard CoreMedia pattern for adding capabilities without modifying the Blueprint core. One snippet. Full automation.

// How it works

Hooks into the CAE. Automatically.

The integration hooks into CoreMedia's CAE rendering pipeline via a ViewHook — a standard CoreMedia extension point that fires during page rendering, before the HTML <head> is closed.
Step 01

URL Detection

The ViewHookEventListener resolves the canonical public URL of the current page using CoreMedia's LinkFormatter — no manual URL mapping, no sitemap configuration required.
Step 02

API Call

The URL is submitted to the enhancely API. If JSON-LD for this URL was already generated, it is returned immediately from the ETag-aware cache. No redundant API calls.
Step 03

JSON-LD Return

enhancely returns ready-made JSON-LD structured data for that page — validated through the 3-layer pipeline (Validity, Factuality, Compliance) before it ever reaches your CAE.
Step 04

HTML Injection

The JSON-LD is injected as <script type="application/ld+json"> into the HTML <head> — fully server-side rendered. No client-side JavaScript. No layout shift. Crawler-ready from the first byte.
// Architecture

One approach. One module.

Two Maven modules, zero boilerplate. Registers automatically via Spring Boot — no manual Spring configuration required.
BPX

Blueprint Extension

The integration ships as a Blueprint Extension — the standard CoreMedia pattern for adding capabilities to the platform without modifying the Blueprint core. Two Maven modules, zero boilerplate. Registers automatically via Spring Boot auto-configuration.

CFG

Secure Configuration

API keys are configured via standard Spring Boot application properties or environment variables — compatible with any secret management approach (Kubernetes Secrets, HashiCorp Vault, AWS Secrets Manager). No credentials in code, no credentials in the repository.

CCH

Caching & Reliability

ETag-aware caching with a 7-day default TTL — configurable via Spring properties. Uses CoreMedia's native cache, no external caching dependencies required. Graceful fallback to a minimal @type: WebSite on API errors or rate limiting. Production-safe by design.

CAE

CAE Integration

Uses the ViewHookEventListener — a standard CAE extension point that fires during page rendering. No changes to existing FreeMarker templates. No modifications to editorial workflows. Transparent to content editors in CoreMedia Studio.

CTL

Per-Site Control

Activation is controlled via CoreMedia's content-based settings mechanism — without touching application configuration. Enable enhancely selectively per site, section, or individual page. Content editors and site administrators stay in control. No deployment required.

# Required
enhancely.api-key=YOUR_API_KEY

# Optional – defaults to https://app.enhancely.ai/api/v1
# enhancely.api-base-url=https://app.enhancely.ai/api/v1

Spring Boot. Plug in. Done.

CAE
// Compatibility & Requirements

Enterprise-grade. By default.

Java 17+
Modern Java runtime
Fully compatible with the current CoreMedia Content Cloud (Blueprint-based setup) and its standard Java 17 runtime.
Spring 3.x
Spring Boot 3.x
Native integration via Spring Boot auto-configuration. No manual bean wiring, no custom Spring XML.
CAE
FreeMarker rendering
Works with the Content Application Engine (CAE) and FreeMarker templating — the standard CoreMedia rendering stack.
7d
Default cache TTL
ETag-aware caching using CoreMedia's native cache infrastructure. Reduces API calls. Keeps schema fresh. Configurable.
806
Schema.org types
Full Schema.org coverage — all 806 types including every LocalBusiness subtype, FAQPage, Product, Article, Event, Organization.
<1h
Initial setup
Developer adds the extension to the Blueprint workspace, sets the API key — typically under an hour. After that: fully autonomous.
// Peer-reviewed science

Built on research. Not promises.

The University of Nantes published peer-reviewed research on LLM-generated Schema.org markup. Finding: 40–50% of markup generated by AI without a curation pipeline is invalid, non-factual, or non-compliant.

After applying a three-layer curation pipeline — the same architecture enhancely uses — GPT-4 outperforms human annotators. On CoreMedia sites, that pipeline runs before any JSON-LD ever enters the CAE rendering flow. That's not a claim. It's published science.

"After applying a three-layer curation pipeline, GPT-4 outperforms human annotators in generating accurate, comprehensive Schema.org markup." — Dang et al., Semantic Web Journal, IOS Press, 2025 · University of Nantes
40–50%
of markup fails without a pipeline. That's not a claim — it's peer-reviewed.
+82%
CTR uplift with Rich Results — documented by Nestlé (Google Search Central Case Study)
✓
Fabrice Canel (Microsoft Bing, SMX Munich 2025): Schema helps LLMs understand web content
<2min
From cached API response to rendered &lt;head&gt; — on every CoreMedia page.
// CoreMedia FAQ

CoreMedia Content Cloud & enhancely. Explained.

Everything about the Blueprint Extension, CAE integration, and how enhancely fits into your CoreMedia stack.
CoreMedia Content Cloud is a Java-based enterprise Digital Experience Platform (DXP) built on Spring Boot. It offers a powerful editorial environment (CoreMedia Studio), multi-site and multi-language management, personalization, and both traditional and headless content delivery. CoreMedia is particularly strong in regulated industries and complex omnichannel scenarios where content governance, workflow, and deep system integration are critical.
While developers can create custom FreeMarker templates with JSON-LD blocks, maintaining structured data at enterprise scale — across multiple sites, languages, and content types — is complex and resource-intensive. The enhancely integration automates this entirely using CoreMedia's standard ViewHook extension point, with a 7-day ETag-aware cache and graceful fallback for production reliability.
The integration uses CoreMedia's ViewHookEventListener — a standard extension point that fires during CAE page rendering. When a page is rendered, the listener resolves its public URL via LinkFormatter, fetches the JSON-LD from the enhancely API (or from the local cache), and injects it into the HTML <head> via a FreeMarker template. The whole process is transparent to content editors and requires no changes to existing templates.
Initial setup requires a developer to add the extension to the Blueprint workspace and set the API key — typically under an hour. After that, enhancely runs autonomously with no ongoing development work. Content authors publish as usual in CoreMedia Studio. Schema markup is generated, validated through the 3-layer pipeline, and deployed automatically for every page. The enhancely dashboard provides full visibility into structured data coverage across all your CoreMedia 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.
API keys are configured via standard Spring Boot application properties or environment variables — fully compatible with any secret management approach (Kubernetes Secrets, HashiCorp Vault, AWS Secrets Manager). The only required property is enhancely.api-key; the API base URL defaults to https://app.enhancely.ai/api/v1 and can be overridden via enhancely.api-base-url. No credentials are stored in code or the repository.
The integration includes a graceful fallback: on API errors or rate limiting, a minimal @type: WebSite JSON-LD is served instead. Combined with the 7-day ETag-aware cache using CoreMedia's native cache infrastructure, your pages stay fully rendered and valid even during temporary API issues. No blank <head>, no broken pages, no production incidents.

Stop leaving bots hungry.

Your CoreMedia content is already great for humans. Let enhancely make it perfect for bots. Blueprint Extension. ViewHook integration. 3-layer validation. One snippet — full automation.
Get started → View on Marketplace