What We Deliver with Next.js
- a page map and a rendering choice for each page type: static generation for articles and service pages, server-side rendering for prices, stock and search, client-side rendering for dashboards and carts;
- a React interface built with a check of how search engines see the pages: headings, markup, links, meta tags, sitemap;
- a headless CMS connection with draft previews and page updates after publishing;
- sign-in via email, Google or Apple, payments with Stripe or PayPal, leads sent to Salesforce or HubSpot, GA4 and GTM that do not slow the first render;
- Core Web Vitals measured on real pages, with images, fonts and third-party scripts optimized;
- deployment to Vercel or your own server, error tracking and caching.
When Next.js Is Right, and When We'd Suggest Something Else
We do not recommend Next.js by default. Another option makes more sense if:
- the site is mostly content, such as a blog, documentation or landing pages, with little interactivity: Astro is easier and cheaper;
- your team already works in Vue: the counterpart is Nuxt;
- it is an internal system that does not need to be indexed: a React app without server-side rendering is enough;
- the main complexity is business logic, not pages: a separate backend matters more, and Next.js serves only as the frontend.
Things to plan for: SSR needs a Node.js server rather than standard PHP hosting, Next.js has no admin panel of its own, and major versions change approaches to page structure and data fetching, so older projects eventually need rework.
Next.js with a Headless CMS
A common setup is Next.js as the frontend with content in a separate system, such as Strapi or WordPress. Editors add pages in a familiar admin panel, and the site picks up new content without a developer. We set up the field structure so editors cannot accidentally break the layout.
From Scratch or Building on What Exists
A new project starts with a page map and data sources: what gets indexed, what updates often, who edits content. For an existing React or Next.js project, we review versions, rendering methods, the size of JavaScript sent 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. After launch we take the project on as part of technical support or hand it over to your team with documentation.
What We Need from You
- A list of page types and which of them must appear in search.
- Design files, or a decision to design with us.
- Access to the existing backend, CMS or API documentation.
- Expected traffic and your hosting preferences.
What Affects Cost and Timeline
- Number of page types and how differently they are rendered.
- Data sources: an existing backend or CMS, or one built alongside the site.
- Interactive features: dashboard, filters, calculators, payments, multiple languages.
- Load and performance requirements, and where the project is hosted.
- For upgrades or migrations from a React SPA: how much UI code carries over.
After discussing your project, we break it into phases and show 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. A Next.js project also runs on your own server or in the cloud, though we handle some configuration, such as caching and image processing, ourselves.
Will the site have an admin panel? Next.js does not 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. Rankings also depend on content, structure and links, so we pair the technical work with an SEO specialist.
Can we pair Next.js with our existing backend? Yes. Next.js can serve as the frontend for a Laravel, Django, Node.js or other backend that exposes an API.
Can you upgrade a project on an old Next.js version? Yes. We upgrade gradually, page by page, so the site stays live during the work.
Why Promodex
Promodex has delivered 750+ projects since 2015. Relevant portfolio work includes Zoomerang and Kinodaran, plus Omio and Komoot, which we contributed to. Developers, designers and SEO specialists work as one in-house team of 30+, so rendering decisions are agreed with search requirements from the start, and we explain the reason for each choice before kickoff.