There is a particular kind of afternoon that WordPress users know well. It begins with a minor irritation — an option that does not behave, a setting that appears to have no effect, a folder structure that persists despite being told not to. It ends, some hours later, in the same place it started, except now there are seventeen browser tabs open and a vague sense that the problem was never really the problem.

Hugo is fast, flexible, and opinionated in all the right ways — but it ships without built-in search. Since Hugo generates a static site, there is no server-side query engine to call. Search has to be handled either at build time, client-side in the browser, or through a third-party service. Each approach has tradeoffs worth understanding before you commit to one. This guide covers the main options and walks through the implementation that works best for most publishing workflows.

Hugo is fast to build and fast to get started with, but a blank new site has some deliberate setup work before it is ready to publish. This walkthrough covers the full process from installation through your first deployed post. Installing Hugo Hugo distributes as a single binary — no runtime dependencies, no package manager required after the initial install. macOS: brew install hugo Linux (Debian/Ubuntu): sudo apt install hugo Or download the latest binary directly from the Hugo releases page and add it to your PATH.