Headless WordPress
The CMS stays as a content panel and renders nothing the public ever sees.
A logistics product built to scale had a site that did not show it. We rebuilt the whole thing: a new identity, a Next.js front end over headless WordPress, and an SEO and performance strategy that holds on its own.
01 — The challenge
Zipnova connects merchants with more than 40 carriers from a single panel. The product was solid; the digital presence did not say so, a generic brand, a slow site, difficult navigation and almost no SEO at all.
The architecture
The CMS stays as a content panel and renders nothing the public ever sees.
Content blocks modelled as fields: the team assembles pages without new templates.
The front end asks for exactly the data it needs, and nothing else.
Static rendering and optimised routes: the speed is part of the architecture.
The content team publishes from ACF without touching code, and the front end is served statically: the speed does not depend on who is editing.
02 — What we built
Logo, colour system, typography and UI components made to say trust, speed and technical authority.
An App Router front end consuming WordPress through WPGraphQL, with ACF handling every flexible content type.
Technical audit, Core Web Vitals, structured data, a sitemap strategy and on-page content architecture.
03 — Results
04 — In short
With a solid rebrand and an SEO strategy with its feet on the ground, the digital presence is finally the equal of the product behind it.
Let's talk about the stack before we talk about the design.