Optimizely Content Graph is a GraphQL-based search and content delivery service in the Optimizely DXP. It exposes your content through a single GraphQL endpoint, aggregates data from multiple sources in one query, and runs on OpenSearch for fast, cross-platform search. It supports headless and composable delivery alongside the Optimizely CMS, which is why it keeps coming up in any conversation about going headless on Optimizely.
The Optimizely GraphQL and Content Graph updates brought a lot of talk about headless and the term Content Graph itself. Here is what those terms mean and how the GraphQL API and Content Graph change content delivery on the platform. For context on the release itself, see my notes on the Optimizely Q2 2023 update.
What is GraphQL?
GraphQL is a data query and manipulation language for APIs, with a runtime for executing queries against your existing data. It is an efficient and flexible alternative to REST.
Key points about GraphQL
- Strongly typed: every GraphQL API adheres to a specific schema and requires certain data types, which improves reliability and security.
- Hierarchical: the query mirrors the natural structure of your data, so you request what you need intuitively.
- Client-specified responses: clients request exactly what they need, which prevents over-fetching and under-fetching.
- Introspective: you can query a GraphQL schema for details about itself, which helps build dynamic clients and generate documentation.
- Version-free: you deprecate fields to manage change instead of versioning the API.
GraphQL also lets you aggregate data from several sources without separate calls to different APIs. A single query to the GraphQL server retrieves data from multiple sources. Optimizely offers GraphQL as a single endpoint on a multitenant SaaS platform, and you activate it from the CMS/DXP PaaS portal.
Is GraphQL faster than REST on Optimizely?
In raw server processing time, GraphQL is not necessarily faster than REST. It can be more efficient in how it handles data, which often makes it feel faster from the client side.
- Less over-fetching and under-fetching: REST endpoints return a fixed structure, while GraphQL returns exactly the fields you ask for, so fewer bytes cross the network.
- Fewer requests: you often get everything you need in a single request, which reduces apparent load time.
- Simpler data aggregation: REST often needs server-side logic to gather data from several sources, and GraphQL handles that in the query.
Content Graph, Search as a Service, and OpenSearch
Based on Optimizely’s documentation, blogs, and forum posts, Content Graph was built to go beyond basic search functionality.
Search powered by Content Graph
Content Graph offers functionality similar to Optimizely Search and Navigation, but the two are technically distinct. Content Graph delivers faster performance and added features.
- Faster search results
- Better error handling
- More flexibility over search logic
- Cross-application and cross-platform search
See the Optimizely docs on Content Graph and Search and Navigation for the technical detail.
OpenSearch under the hood
Content Graph runs on OpenSearch. Optimizely automated its multitenant distributed platform for rolling OpenSearch upgrades so the service stays available during updates. Search is central to most client implementations, so this is an area worth watching as the platform leans further into composable delivery and applied AI. Optimizely has also published a GraphQL demo tool for developers to explore the data.
If you are weighing Optimizely against other platforms, I cover the wider picture in Optimizely vs WordPress for enterprise and the case of the headless CMS.
Frequently asked questions
What is Optimizely Content Graph?
Content Graph is a GraphQL-based search and content delivery service in the Optimizely DXP. It exposes content through a single GraphQL endpoint, aggregates data from multiple sources in one query, and runs on OpenSearch for fast, cross-platform search.
Is Content Graph the same as Optimizely Search and Navigation?
No. They offer similar functionality, but they are technically distinct. Content Graph is faster, adds features, and is built on OpenSearch, while Search and Navigation is the older capability.
Does Optimizely Content Graph support headless?
Yes. The GraphQL endpoint makes Content Graph a good fit for headless and composable delivery, where a front end queries content over the API rather than rendering it through the CMS.
