Development
Next.js development
Next.js is what you reach for when a site has to be two things at once: fast and findable in Google, and an actual application behind the login. I build them, and I fix the ones where the second requirement quietly cost the first.
When this makes sense
- You need marketing pages that rank and an application, and would rather not run two codebases
- Your React app is invisible to search engines and that is starting to cost you
- A Next.js site is slow or expensive to host and nobody is sure which part is doing it
How it works
- 01
Decide what renders where
Which pages are static, which are server-rendered, and which are client-only. Getting this wrong is the cause of most Next.js sites that are slow or invisible, and it is cheap to get right at the start.
- 02
Build
Pages, API routes and the data layer, with the SEO fundamentals in from day one rather than retrofitted — canonicals, structured data, sitemap, and hreflang if you run more than one language.
- 03
Measure and hand over
Core Web Vitals on real devices, Search Console connected, and hosting you control. Numbers before and after, so you can see what changed.
What the work covers
- Server rendering and static generation, chosen per page rather than by default
- Technical SEO built in: canonical URLs, structured data, sitemap, hreflang
- API routes and the database layer behind them
- Hosting, deployment and monitoring you own and can move elsewhere
Common questions
- What does a Next.js build cost?
- A site starts at DKK 15,000 (25 hours) and an application at DKK 48,000 (80 hours), both at DKK 600 an hour with the scope agreed in writing first. Where a project sits between those two depends on how much of it is pages and how much is logic.
- Next.js or WordPress?
- WordPress if the point is content you edit yourself and the site is mostly pages — it is cheaper to build and cheaper to run, and I will say so. Next.js when the same product has to be both a fast public site and an application, or when the page has to do something a theme will fight you on. Picking the expensive one for a brochure site is a common and avoidable mistake.
- Is Next.js good for SEO?
- It can be excellent and it can be terrible, which is why the question is worth asking. Server-rendered and static pages index fine. A Next.js site built entirely client-side has the same problem as any other single-page application, plus a heavier bill. The rendering decisions are the SEO decisions.
- Where does it get hosted?
- Wherever you want, and you should keep that choice. It runs on a normal container on ordinary European hosting as happily as on a managed platform — I run HostStack, so this is well-travelled ground. What matters is that you own the hosting account and can move without asking permission.
- Can you take over an existing Next.js project?
- Yes. It usually begins with a technical review at DKK 6,000, and with Next.js the first thing worth checking is almost always the rendering strategy, because that is where the speed and the hosting bill are decided.
Other stacks I work in
Not sure which one to pick?
Send a couple of lines about what you are trying to achieve. You get a reply within 24 hours, and an honest yes or no.