I’m wondering if anyone has successfully migrated a Weweb code export to a Nuxt.js server with SSR enabled—specifically to boost SEO—and then deployed it to Vercel or another hosting provider.
My goal is to enhance the SEO of my current Weweb project by leveraging Nuxt.js’s server-side rendering capabilities, including custom sitemap & robots.txt generation, breadcrumb and structured data markup, and dynamic metadata management. I’m particularly interested in learning about any challenges or configurations you’ve encountered regarding SEO, environment variables, and SSR setup during the migration process.
Any tips, pitfalls, or detailed guides would be greatly appreciated!
If no one has taken this step yet, I’m considering starting a repository for a plug-and-play solution. This project would allow us to export our Weweb projects into a pre-configured Nuxt.js server with full CI/CD integration, enabling us to fully utilize Weweb as a studio and meet business-critical needs.
I think you’d be better off by rebuilding the app, if you wanna do Nuxt. Given WeWeb’s code is unusable by a developer. Also it’s very deeply rooted end entangled with a lot of their tooling and methods. What you could instead do is use some pre-rendering library for vue and pre-render it yourself. You could also check out prerender.io etc.
It’s definitely not the best option for us to rebuild a front end outside of Weweb, we are so tided and accustomed to the way we build with it.
I’m having a call with prerender team today, if any of you have questions in mind, please drop them below — I’ll bind the answers below
—
We are exploring the option of Webstudio for this part of the app (distribution) do you have any feedback about this tool, and if it’s possible to get something similar to what we have at privatevillasmexico.com ?
I have not used WebStudio to be honest, since it’s a young platform and I don’t miss anything at Wordpress, but it might be a simpler option indeed (compared to something like Nuxt)
I’m interested in learning how many self host a WeWeb site and how difficult it is? Not that I want to right now, but there could be a time in the future.
Keep an eye on the latest weekly updates as we’re awaiting on some research into SSR from the team.
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.
Not really, requires self hosting (doable but hard in my opinion) + need to change a few things within Weweb app exported script which is barely understandable. So I would say no, but who knows
I’m procrastinating on my migration, but I’ll have to make a decision sooner rather than later.
What annoys me the most is that this simple change (ending prerender without any prior warning) has given ammunition to all the developers and product owners in my company who were against no-code solutions. They argued that no-code wasn’t reliable, and from their perspective, this is the perfect demonstration of their point. In some ways, they’re right about this specific situation.
It resolved all the SEO issues and speed problems I had. the tool is so easy to build and their capbablity is beyond impressive. Everything is perfect.
I guess many people have not tried that tool or known this tool so do not know but
I strongly recommend anyone to try it out if you struglle budiling decent webapplication
I have tried Prerender.io. it is good and improved index but it is costy and moving into Toddle will solve all the issue for SEO and page speed
Nordcraft is a toy indeed, but you don’t need a bazooka to kill ants. For example your marketplace would do probably way better with their SSR, and you might not need a complex solution, but I don’t know your project that well, so take this with a grain of salt.
no it is not really.
you will be suprised at how much capability they will have. that was the best decision i ever had made
both web development experience and our seo peformance, page speed improved significantly
When using weweb, we were struggling with even having pages indexed first place.
Implementing SSR with Toddle has much bigger positive impact on page speed and SEO even compared to using Prerender. Weweb is aweome tool but it is for web application
of course no need to consider if you are totally happy with the current set up though.
For the SEO/SSR - Could you not just deploy WeWeb behind a cloudflare and let that handle all the cached versions of the pages which will be significantly faster.
The speed is not the main issue, the main issue is that weweb platform is very good at being an app but bad for seo, the main issue is the ssr that makes it impossible to google to “see” your pages and therfore to promot them on the search results
(compared to something like Nuxt)