← Headless WordPress with Hugo
How do you build a multi-tenant directory on headless WordPress?
One shared WordPress backend manages content for multiple niche directories, each served by its own static Hugo frontend on its own domain, with search scoped per site so one niche’s listings never bleed into another’s results. Adding a new niche means a new frontend and a scoped data set, not new backend infrastructure.
One backend, many static frontends
Rather than standing up a separate WordPress install per directory, one backend holds the content for every niche, distinguished by taxonomy or post type rather than by separate databases. Each niche gets its own Hugo build and its own domain, pulling only the content that belongs to it. The backend’s operational cost doesn’t multiply with each new site, since it’s still one WordPress install to maintain, update, and secure, regardless of how many frontends read from it.
Per-site search
Search needs the same scoping the content does. Meilisearch indexes get scoped by taxonomy, so each directory’s search only returns results from its own niche, even though the underlying data lives in one shared backend. A visitor searching the vintage store directory never sees results from an unrelated niche sharing the same WordPress install.
Adding a new niche or site without new infrastructure
Because the backend, the hosting pattern, and the Hugo build process are already built and running, a new niche is mostly configuration: a new taxonomy scope, a new Hugo site pointed at that scope, a new Meilisearch index, and a domain. The infrastructure that took real engineering time to build once gets reused, not rebuilt, for every additional site.
Real example
84EM built and runs Directory Sites: one platform, multiple niches, the same engine underneath. The pattern is the same one behind the high-performance business directory case study, where a single WordPress backend and Hugo frontend serve thousands of location-based listing pages with sub-second load times.
Talk to 84EM about a multi-tenant directory build if you’re running (or planning) more than one niche site on the same content model.
