What it is
A toolkit for building fast websites: pages are served as ready HTML, so they open instantly and are fully readable by search engines. Vue is the interface language inside it.
How we use it
The studio site and an online store with an admin panel are built on Nuxt. Content lives in files in git or in a database, the design is custom, with no builder templates.
Where Nuxt helps a business
- The site must rank in search and open fast on a phone from an ad link.
- Every service, product and case should have its own page and URL, not one long landing page.
- You need two language versions, and search engines must see them as pairs, not duplicates.
- A store needs a storefront and an admin panel built around what the owner actually changes.
Options
- SSR (server-side rendering). A page is assembled on every request and delivered as ready HTML. Needed when data changes often: stock, prices, orders.
- Static. Pages are built in advance and stored as files, so the server has almost nothing to do. Suits a site that changes only on deploy.
- Nuxt plus an API. A Nuxt storefront with data and logic in a separate back end, for example FastAPI.
Our Russian site runs as SSR in one container, while the international version of the same project is built as static files.
How we use it
- The studio website. Nuxt 4 and Nuxt Content 3: pages, cases and the glossary live as markdown and JSON in git, and a Zod schema checks their structure, so a typo in a field never reaches a visitor. Russian has no prefix, English lives at /en, the sitemap and robots.txt are built from the content, and pages carry their own JSON-LD. The container needs 150 to 300 MB of memory.
- An online store. Storefront and admin panel on Nuxt 4 with FastAPI. A search robot sees the products at once, every page has its own title and description, products carry Product markup, and the sitemap is built on the fly from visible products.
Nuxt websites are under Websites and online stores.
Common problems
- The build does not fit in the server's memory. A small VPS cannot build Nuxt. We build the image on a workstation and upload it ready-made.
- A staging site ends up in search. One environment variable switches the site to staging mode: noindex in the meta tags and a disallow rule in robots.txt.
- Content in git does not suit everyone. Editing the studio site means editing a file and rebuilding. An owner who wants to change prices and texts daily needs an admin panel.
- An in-memory counter resets. The brief's anti-spam counts submissions per address in process memory, so the counter resets when the container restarts.
When you do not need it
For a single business-card page Nuxt is overkill: HTML, CSS and JavaScript with no build step are enough, as on Valery Afanasiev's site. And if a client firmly wants the familiar WordPress admin, we build on WordPress with a custom theme.