Migrating Weweb Code Export to Nuxt.js with SSR for SEO Improvement – Experiences and CI/CD Ideas

Hey @higorlacerda,

We’ve hit a hard stop trying to self-host the platform and enable SSR on WeWeb. It simply wasn’t viable. Initially, we planned to move forward by updating the sitemap.xml and robots.txt as discussed here, to at least give crawlers some visibility. But even after updating them, WeWeb’s default sitemap kept overriding ours—so that route’s blocked too.

At this point, we’ve shifted our Distribution front (the public-facing site where we rent and sell properties, like Airbnb) to a more SEO-friendly low-code builder—Nordcraft (ex-Toddle.dev). Their native SSR and SEO controls are much more aligned with what we need. We’re confident that in the next few months, this switch will positively impact traffic and sales. If you’re in a similar situation and SEO is critical to your business, happy to share the agency that helped us transition.

On the Operations side (concierge, services, internal tooling), we’re still running with WeWeb. SEO isn’t a concern there, and WeWeb allows for fast iterations and structured UI logic, which fits well with the SaaS-style backend we’ve built. That said, we’re keeping an eye on Nordcraft’s evolution, and we’ll likely shift the Ops side once the tooling there matures a bit more—we’re not fully confident in its dev speed yet.

So to sum it up, we’re playing it based on readiness:

  • Distribution → Nordcraft now (SEO + SSR ready)
  • Operations → Still on WeWeb for now (fast internal dev)Long-term, we might rehost everything on WeWeb if they ship real SSR—or move it all to Nordcraft once it’s mature enough.

Both tools are solid—the choice comes down to timing and business context.

Let’s stay in touch.

4 Likes