Next.js agency: SEO-friendly web apps with React
SEO-friendly web apps with Next.js

We plan, build and run websites and web applications with Next.js – from a new product to migrating an existing React app. We are based in Mönchengladbach and support projects on site in North Rhine-Westphalia and remotely across Germany.
Next.js in figures
- 144K
- 89
- 16.4.6
- 20 days
- 362M
What does a Next.js agency do?
A Next.js agency plans, builds and runs websites and web applications with the React framework Next.js: page structure and rendering strategy, connections to CMS, shop and APIs, performance and technical SEO. nextlevels does this for company websites, customer portals and shop frontends, moves existing React applications to the App Router and runs its own website on Next.js.
Brands that work with us
Our Next.js services
Next.js compared
Next.js next to technologies of the same category, measured with the same public sources.
| Figure | Next.js | TanStack |
|---|---|---|
| Stars on GitHub | 144K | 15K |
| Releases in 12 months | 89 | 209 |
| Median between releases | 7 days | 2 days |
| Latest version | 16.4.6 (09/11/2026) | 1.170.46 (22/10/2026) |
| Median time to close an issue (90 days) | 20 days | 15 days |
| Downloads per month | 362M (npm) | 95M (npm) |
| Active contributors (12 months) | 87 | 44 |
| Security advisories (12 months) | 50 | 2 |
| Search interest in Germany (Google Trends, 12 months, 100 = most searched in the group) | 100 | 31 |
Sources: GitHub, Google Trends (DataForSEO), OSV.dev, npm · as of 18/11/2026. Figures are indicators, not a verdict on quality. Go to the pages: TanStack
Releases & issues
| Version | Date | Issues opened | of which closed |
|---|---|---|---|
| 16.4.6 | 09/11/2026 | 1 | 1 |
| 16.4.5 | 03/11/2026 | 0 | 0 |
| 16.4.4 | 02/11/2026 | 0 | 0 |
| 16.4.3 | 23/10/2026 | 0 | 0 |
| 16.4.2 | 15/10/2026 | 0 | 0 |
Source: GitHub · as of 15/11/2026
Pros and cons of Next.js
Pros
- Pages arrive as ready-made HTML from the server, which helps visibility in Google and AI search.
- Rendering can be chosen per route: static where possible, dynamic where content is personalized or live.
- Built on React, with a large pool of developers, libraries and examples.
- Open source under the MIT license, deployable on Vercel or self-hosted as a Node.js server or Docker container.
Cons
- App Router, Server Components and caching come with a real learning curve, even for experienced React teams.
- A high release cadence and regular security advisories call for timely updates.
- When self-hosting, image optimization and caching across multiple instances need their own configuration.
- Plain web hosting without Node.js only supports a static export with limited features.
Is Next.js right for you?
A good fit if …
- your content needs to be found in Google and AI search.
- you are building a corporate site, shop frontend or portal with public and protected areas.
- your editors work in a headless CMS and the frontend should be designed freely.
- your team knows React or you want access to a large pool of developers.
Probably not if …
- your application sits entirely behind a login and SEO does not matter.
- editors should assemble pages themselves and no development team looks after the frontend.
- you only have plain web hosting without Node.js.
- your team is firmly at home in Angular or another framework.
What Next.js is – in short
Next.js is an open-source framework based on React for websites and full-stack web applications. It is maintained by Vercel and MIT-licensed, so there are no license fees. React provides the components; Next.js adds routing, data loading, server rendering and the build.
The current version is Next.js 16, released in October 2025; version 16.3 followed in August 2026. The App Router is the newer of the two routers and supports React Server Components: parts of the interface render on the server and reach the browser as finished HTML. Since version 16, Turbopack is the default bundler, and with Cache Components the team decides explicitly what is cached. The older Pages Router is still supported.
Next.js runs on Vercel, but it can also be self-hosted as a Node.js server or Docker container. For data-heavy interfaces we combine it with TanStack Query and Table. We work out which combination fits your project in the first call.
When Next.js fits – and when it does not
Next.js is not the best choice for every project. This is how we weigh it up:
| Question | Rather Next.js | Rather something else |
|---|---|---|
| Visibility | When content should be found in Google and in AI search: pages arrive as finished HTML from the server. | A React single-page app, when everything sits behind a login and search engines do not matter. |
| Type of project | Company websites, shop frontends and portals with a public and a protected area. | TanStack Start, when you build an app with a lot of interaction and want filters and state typed in the URL. |
| Content | When editors maintain content in a headless CMS and the frontend should be designed freely. | A classic CMS, when editors assemble pages themselves and no development team looks after the frontend. |
| Hosting | On Vercel without further configuration, or self-hosted as a Node.js server or Docker container. | Plain web space without Node.js: Next.js only runs there as a static export with a limited feature set. |
| Team | When your team knows React or you want a large pool of developers and examples. | Angular, when your team is at home there and a large business application with many forms is planned. |
Our assessment from project work, as of October 2026 – not a binding verdict. We work out what fits your project in the first call.
How your Next.js project runs
Cost and duration depend on scope. Our project calculator gives you a first range; the binding figure comes with the offer after the workshop.
What is Next.js?
What is Next.js suited for – and what not?
Is migrating from the Pages Router to the App Router worth it?
Where do you host Next.js – only on Vercel?
Is Next.js good for SEO and AI search?
What does a Next.js project cost?
Sources
- Next.js documentation: introduction, App Router and Pages Router
- Next.js 16: release announcement
- Next.js 16.3: release announcement
- Next.js support policy: supported versions
- Next.js documentation: deployment and self-hosting
- Vercel documentation: Next.js on Vercel
- Next.js on GitHub: MIT license
As of October 2026
Last updated on
Why nextlevels as your Next.js agency?
Read on and check
Next.js Data & Insights
All postsReady for your Next.js project?
Let's talk about your requirements – we'll get back to you within one business day with concrete next steps.
What's it about?

Paul Kalisch
Executive Partner
- 30 minutes by video or phone
- You talk directly to a partner, not to sales
- You get the order of steps, risks and rough costs
Related services for Next.js






