Zola
A single-binary static site generator with Markdown, Tera templates, Sass, image processing, taxonomies, pagination, search indexes, link checks and local hot reload.
A small and reproducible static build
Zola uses one binary to turn Markdown, templates, Sass and assets into static HTML, CSS and media. It also supports taxonomies, pagination, search indexes, link checks and local hot reload.
Four commands define the workflow
init creates a project, serve previews locally, check validates content and links, and build generates the public output. The output directory is disposable; source files and uploads belong elsewhere.
Production SEO starts with base_url
The production base_url affects canonical URLs, internal links, sitemap and share addresses. Review third-party themes for scripts, external requests and meta tags, then inspect robots, 404 and structured data before deployment.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Zola to this cloud drive
Baidu Netdisk
Save Zola to this cloud drive
Zola initialization, preview, checks and secure build
Initialize an empty test project, set the intended base URL, preview and check locally, then build to a disposable public directory and inspect SEO files.
Before you start
- Create an empty test directory under version control rather than initializing an existing website root with force.
- Decide production domain, HTTPS, trailing slash and deployment subpath before setting base_url.
- Keep source content and static assets separate from the regenerable public output.
Installation steps
- 01
Extract and verify the binary
Confirm Zola 0.22.1 and Windows x64, then inspect version and the init, serve, check and build help.
- 02
Initialize an empty site
Create the project structure and review config, content, templates, static and Sass directories.
- 03
Set the base address
Configure the production base_url, site title and taxonomies, then add a small test page with relative assets.
Quick start
- 01
Preview on the local interface
Run serve with its local default, check navigation, templates, images and reload behavior without exposing the site to the network.
- 02
Check content and links
Run check, distinguish temporary network errors from real dead links and keep sensitive preview addresses out of public checking services.
- 03
Build and inspect public
Run build only after confirming public is disposable, then review canonical, title, description, structured data, sitemap, robots, 404 and asset paths.
Usage tips
- build and serve clean the output directory, so manual uploads must come from static or a separate release step.
- Review third-party themes for scripts, analytics, external requests, SEO tags and version compatibility.
- A wrong base_url propagates to canonical URLs, links, sitemap and share cards; do not carry a preview domain into production.
Troubleshooting and uninstall
Why are CSS or image paths broken after deployment?
Check base_url, deployment subpath, relative versus absolute links and static layout, then rebuild with production parameters.
Why can serve be reached locally but not from another device?
The default local listener is intentional; use a trusted network interface only for short testing and restore local binding afterward.
- Stop preview and remove the binaryStop serve, preserve the source project and configuration, confirm public is reproducible and remove Zola from PATH or the tools directory.
Frequently asked questions
Does Zola need Node.js or a database at build time?
The generator itself is a single binary; themes or deployment workflows may add their own tools.
What happens to public during a build?
The output directory is regenerated and may be cleaned, so unique source files and uploads should live outside it.
Is serve a production server?
No. It is intended for local preview and hot reload; production output should be hosted by a suitable static server.
Why is base_url important for SEO?
It influences canonical links, internal URLs, sitemap entries and share addresses generated by the site.