When a company looks for a freelance Nuxt developer in Rennes, it’s almost never for a brand-new, smooth project. It’s a Nuxt 2 site that refuses to update, an application that’s been lagging since its last update, or an agency that built the tool three years ago and no longer answers the phone.
I work with Nuxt and Vue.js every day, having done so for several years: a daily-used back-office at Izidoor, showcase websites, business applications, and my own site. Here’s what I actually do when someone calls me about a Nuxt project.
Why use Nuxt for a website or business application?
Nuxt is Vue.js with everything needed to deploy a project cleanly: server-side rendered pages, routing, SEO, and translations.
For a business, this translates simply to:
fast pages, loading before JavaScript even finishes executing;
good SEO, because Google (and AI) receive real content—not a blank page to fill out;
a single codebase for the homepage, blog, and connected space, instead of three poorly integrated tools.
And for small teams, Vue.js remains simpler to pick up and maintain than many alternatives. It’s a detail often overlooked when choosing a technology, only to be regretted two years later.
Migrating from Nuxt 2 to Nuxt 4 without breaking everything
This is the request I get most often. Nuxt 2 hasn’t been maintained since June 30, 2024, and Vue 2 since the end of 2023. In practice, no more security fixes, and dependencies failing one after another.
Migration isn’t an ‘update’ button. Here’s how I approach it:
1. A project audit: which modules are no longer compatible, which pages are critical, and what can be simplified along the way.
2. A Step-by-Step Migration: the Vuex store switches to Pinia, components gradually move to the Composition API, and each step is tested before the next.
3. A Smooth Rollout Without Surprises: same URL, same SEO, and the ability to roll back if anything goes wrong.
The most costly thing is waiting: every month of delay adds another dependency to replace.
SEO and Visibility in AI: Where a Nuxt Project Makes the Difference
A well-configured Nuxt project is excellent for search engine optimization. Poorly configured, it can hide part of your content without anyone noticing.
Two examples from my own site, dibodev.fr, built with Nuxt 4:
Texts Invisible to AI Robots. Some project descriptions were added via JavaScript after the page loaded. Google handled it well. But ChatGPT or Perplexity bots only read HTML: for them, these texts simply didn’t exist. Generating them during build fixed the issue—they now appear everywhere.
Overzealous Language Redirection. A default setting in the translation module redirected all browsers set to English to the English version of the site. Google’s rendering bot was included: it saw my homepage in English. One line of configuration fixed the problem.
These are details you won’t spot by testing your site from your own browser. I check them systematically: what Google, Bing, and AI bots receive, page by page.
A Concrete Example: A Business Back-Office in Nuxt
At Izidoor, for nearly three years, I developed a Nuxt-based back-office used daily by sports and leisure clubs: activity scheduling, online payments via Stripe, statistics, and the reservation module their clients use to sign up.
This kind of tool isn’t particularly impressive from the outside. But a schedule that takes three seconds to load, multiplied by dozens of uses per day, is a team losing patience. A big part of the work is making the tool fast and intuitive: loading only the relevant data, keeping forms simple, and avoiding screens where you don’t know what to do next.
It’s the same approach I apply today to custom business applications that I develop for SMEs.
How I work on a Nuxt project
in Rennes or remotely: I can come see you to define the project scope, then work remotely on a daily basis.
Fixed-price for a well-defined project (a migration, a new application), with a clear quote: scope, price, and milestones set before we start.
Reusable code: TypeScript, readable components, concise yet useful documentation. You’re never locked in with your service provider—including me.
Honesty: If Nuxt isn’t the right fit for your needs, or if an existing tool already does the job, I’ll tell you.
My full background is on the aboutpage, and my work on the projects.
My offer for businesses in Rennes, with the prices of each kind of project, is detailed on the freelance web developer in Rennes page.
Frequently Asked Questions
My Nuxt 2 site still works, why migrate?
Because it no longer receives any security updates as of June 2024, and its dependencies will continue to break one by one. The longer you wait, the more expensive the migration becomes.
How long does a migration from Nuxt 2 to Nuxt 4 take?
It mostly depends on the number of pages and modules. For a brochure site, it’s a matter of days. For a full-fledged business application, it’s more likely to take weeks. I always start with an audit to give you an accurate estimate.
Do you also work with Vue.js without Nuxt?
Yes. For a back-office or an application that doesn’t need SEO, a standalone Vue.js app can be sufficient, and I’ll suggest it if appropriate.
Can you take over a Nuxt project developed by someone else?
Yes, it’s actually quite common. I start by reviewing the code, identifying what’s solid and what needs fixing, before proposing a plan.
Let’s talk?
If you have a Nuxt project to launch, a Nuxt 2 site to migrate, or an application that could use a refresh, the easiest way is to discuss it. I’ll review your project and provide a written action plan with an honest budget estimate. And if an existing tool is sufficient, I’ll let you know.
