Headless WordPress: when it makes sense to separate design from content
What headless WordPress is, which problems it solves on a slow or hard-to-change site, and when migrating is not worth it.
· Pablo Lospennato
If your site runs on WordPress and every design change is slow, expensive or breaks something else, you’ve probably been told “it all has to be rebuilt”. Often it doesn’t. There is a middle path: headless WordPress.
What “headless” means
In a traditional WordPress site, the same system stores the content and also builds the page the visitor sees (the theme). In a headless setup the two are separated:
- WordPress remains the place where your team enters text, images and products, as it does today.
- A code-built frontend (for example with Next.js) requests that content and builds the pages.
Your team doesn’t change how it works. What changes is what the visitor sees.
Problems it usually solves
- Sites that got slow over time. Plugins and visual builders pile up, and every page loads more than it needs. A custom frontend loads only what the page uses.
- Design limited by the theme. If the design you want doesn’t fit the theme, you end up fighting the builder. In code, that barrier doesn’t exist.
- Risky changes. Updating one plugin can alter unrelated parts of the site. With a separate frontend, the risk is contained.
When it doesn’t make sense
Being honest about this matters more than selling the migration:
- If the site is small and works well, there’s nothing to fix. Migrating is cost without benefit.
- If you rely on plugins that generate the page (some e-commerce, booking or membership plugins), that logic has to be rebuilt, and the cost can outweigh the benefit.
- If nobody on your team can maintain it, a code frontend adds a technical dependency. Someone has to look after it.
- If the problem is the content, not the speed, migrating won’t fix it.
What to protect so you don’t lose rankings
This is the real risk of any migration. Before going live you should:
- Keep the current URLs, or redirect each one to its equivalent.
- Keep titles, descriptions and structured data for every page.
- Regenerate the sitemap and tell Google.
- Test with real content, not just placeholder data.
A real case
On Liderus Beneficios, a benefits platform for employees, I built the frontend in Next.js and WordPress stayed as the content manager. It’s the setup described above.
How to tell if it fits you
A quick test: is your problem how the site looks and how long it takes to load (the frontend), or how content gets entered (the admin panel)? If it’s the first and the panel works for you, headless is worth evaluating. If it’s the second, probably not.
If you’d like me to look at your case, tell me about your site and I’ll tell you plainly whether migrating is worth it.
Related service
Have a project in mind?
Tell me what you need and I'll reply with the key questions and a first plan.
Message on WhatsApp