What Next.js adds to React
React is a UI library, not a complete tool for building a website. Next.js covers the rest of the essentials:
- pages and URLs are generated from the project's folder structure, with no separate routing setup required;
- HTML can be rendered on the server at request time or ahead of time, during the build;
- static pages can regenerate in the background without a full rebuild;
- images are automatically compressed and served at the right size for each user's screen;
- simple server tasks — handling forms, receiving payment provider webhooks — can be handled right inside the project.
In other words, Next.js is React plus a set of solutions your team would otherwise have to assemble by hand.
Benefits of Next.js
- Search engines see your content. Text, headings, and links are in the HTML from the start, so pages get indexed as reliably as on a traditional website.
- Fast first render. Visitors see the page before all the JavaScript loads — a noticeable difference on slow mobile connections.
- Flexibility within one project. The blog can be static, the catalog server-rendered, and the user dashboard run as an in-browser app.
- The entire React ecosystem. The same libraries and components work, and React developers are easier to find than for most other frameworks.
- Easy deployment. A project can be deployed to Vercel in a few steps or run in Docker on your own server.
Limitations to know up front
- Requires a Node.js server. Standard shared PHP hosting isn't enough for server-side rendering, and server resources cost money.
- More complex than plain React. Developers must always keep track of which code runs on the server and which in the browser, or hard-to-catch bugs creep in.
- The framework evolves quickly. Approaches to page structure and data fetching have changed between major versions, so older projects eventually need rework.
- It's not a CMS. Next.js has no content admin panel: that comes from a separate content management system or custom development.
- Some features work best on Vercel. On your own server, caching and image processing have to be configured manually.
When you don't need Next.js
We don't recommend Next.js by default. Another option makes more sense if:
- the site is mostly content — a blog, documentation, landing pages — with little interactivity: such projects are easier and cheaper to build with Astro;
- your team already works in Vue: the Vue counterpart to Next.js is Nuxt, and switching stacks for the sake of a framework makes no sense;
- it's an internal system that doesn't need to be indexed: a React app without server-side rendering is enough;
- the project's main complexity lies in business logic, not pages: then designing a separate backend matters more, and Next.js serves only as the front end.
Static, server, or browser: how we choose
The most important decision in a Next.js project is how each page will be rendered. It determines speed, server load, and data freshness.
Static generation suits articles, service pages, and product descriptions that change infrequently. These pages load fastest and put almost no load on the server.
Server-side rendering is needed when data must be current right now: prices and stock, search results, personalized recommendations.
Client-side rendering is reserved for what makes no sense to index: user dashboards, settings, the shopping cart. Most projects combine all three.
Next.js with a headless CMS
A common setup is Next.js as the website's front end, with content living in a separate system — such as Strapi or WordPress — that serves data via API. Editors add pages in a familiar admin panel, and the site picks up new content without a developer.
In this setup, we configure draft previews, page updates after publishing, and a field structure that keeps editors from accidentally breaking the layout.
From scratch or building on what already works
Development from scratch starts with a page map and data sources, not with picking libraries. Once it's clear what gets indexed, what updates, and who edits content, the architecture practically designs itself.
For an existing project, we start with a review: Next.js and dependency versions, page rendering methods, the size of JavaScript shipped to the browser, and server errors. Often a site is slow not because of the framework, but because pages that could be static are rebuilt on every request.
Integrations and life after launch
A Next.js site usually relies on several external systems. Most often, we integrate:
- sign-in via email, Google, or Apple, with access control for dashboard pages;
- payments via Stripe or PayPal, with server-side confirmation handling;
- a CRM such as Salesforce or HubSpot for leads and orders, so your team doesn't re-enter data by hand;
- GA4 and GTM analytics, set up so scripts don't slow down the first page render.
After launch, the project needs ongoing attention: dependency updates, performance checks after new features, and server error monitoring. We take this on as part of technical support or hand the project over to your team with documentation.
What affects cost and timeline
- Number of page types and how differently they need to be rendered.
- Data sources: whether there's an existing backend or CMS, or whether they need to be built alongside the site.
- Interactive features: user dashboard, filters, calculators, payments, multilingual support.
- Performance and load requirements: expected traffic and where the project will be hosted.
- State of existing code — for improvements and upgrades from older versions.
After discussing your project, we break it into phases and show exactly what each one includes.
Frequently asked questions
Can we move our React site to Next.js without a full rewrite? In most cases, yes. UI components carry over almost unchanged; routing, data fetching, and some browser-dependent code need rework.
Do we have to host the site on Vercel? No. Vercel is convenient, but a Next.js project also runs on your own server or in the cloud — we just handle some of the configuration ourselves.
Will the site have an admin panel? Next.js doesn't include one. We connect a headless CMS or build a custom admin panel around your workflows.
Does Next.js really improve SEO? It removes a technical barrier — pages that look empty to crawlers. But rankings also depend on content, structure, and links, so the technical foundation should be paired with an SEO specialist's work.
Why Promodex
Promodex brings more than a decade of experience — the agency was founded in 2015 — and 750+ launched projects. Relevant portfolio work includes Zoomerang and Kinodaran, as well as Omio and Komoot, which we contributed to. Our Next.js sites are built jointly by in-house developers, designers, and SEO specialists (30+ people), so technical decisions are aligned with search requirements from the start. Before kickoff, we explain why we're choosing each rendering approach, and after launch we continue supporting and growing the project.
