A headless CMS can be queried either way. The honest answer for most marketing sites is that REST is enough — and simpler to cache, authenticate, and reason about.
Where REST shines
Content is read-mostly and shaped in predictable ways. REST endpoints map cleanly to that, cache at the edge without effort, and authenticate with a single header. Fewer moving parts, fewer surprises.
Where GraphQL earns its keep
Once clients need deeply nested, highly variable data in one round trip, GraphQL removes over-fetching in a way REST cannot match. For a blog with a handful of fields, that flexibility is mostly unused weight.
Choose the boring protocol until the interesting one solves a problem you actually have.
