When Should I Use Headless WordPress?

The decision video in the roadmap, and the one that argues against itself for the last five minutes. The first half is the case for headless — performance and perceived performance, developer experience, sourcing data from more than one place, and a smaller attack surface.

The second half is the part that’s easy to leave out of a vendor’s video: when you shouldn’t. If the team wants no-code or low-code page building, if the time and budget trade-off doesn’t clear, or if the existing skill set is deep in traditional WordPress, headless is a tax rather than an upgrade.

There’s a written version of the same argument on the WP Engine developer blog.