Author: connect@freelancingwithkinga.com

In production your Next.js site is deployed on a server (like Vercel). Every time a visitor loads a page, Next.js would normally call your WordPress API to get the posts. If you have 1,000 visitors, that’s 1,000 API calls to WordPress — which slows things down and puts load on your WordPress host.

With revalidate: 3600, Next.js instead:

1. Fetches from WordPress once and caches the result
2. Serves that cached response to all visitors for 1 hour — near-instant, no WordPress calls
3. After 1 hour, fetches fresh data from WordPress and updates the cache This is called ISR (Incremental Static Regeneration) — you get the speed of a static site but content still updates
   automatically. The tradeoff: If you publish a new post, it won’t appear on the live site for up to 1 hour. You can fix this with the
   revalidation webhook we already built (/api/revalidate) — when WordPress publishes a post, it calls that endpoint and
   Next.js immediately refreshes the cache, so new posts appear in seconds rather than waiting an hour. You can also tune the number — revalidate: 60 means 1 minute, revalidate: 0 means no cache (always fresh, but slower). For
   a blog, 1 hour is a sensible default.

WordPress Headless CMS: What It Is and Why It Matters

WordPress powers over 40% of the web — but the way we use it is changing.

Traditionally, WordPress handles everything: content management, design, and delivery. Headless flips that model. Instead of WordPress controlling what your visitors see, it focuses purely on managing content. The frontend — what users actually experience — is built separately using modern frameworks like Next.js or even tools like Webflow.

The two talk to each other via WordPress’s REST API or GraphQL.

So why bother?

Speed. A decoupled frontend isn’t weighed down by WordPress’s theme layer, meaning faster load times and better Core Web Vitals scores.

Flexibility. Your developers aren’t locked into WordPress templates. They can build any experience they want while editors keep using the familiar WordPress dashboard.

Scalability. As your site grows, you can scale the frontend independently without touching your content backend.

Security. With no direct connection between your CMS and what’s publicly served, your WordPress install is a smaller attack target.

Who is it for?

Headless WordPress makes the most sense if you have a content-heavy site, a team of editors who already live in WordPress, but a frontend that needs more than traditional themes can offer. Think media sites, large ecommerce stores, or businesses running complex marketing pages.

It’s not for everyone — the setup is more technical and the cost is higher. But if performance and flexibility are priorities, headless is worth the conversation.

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!