I’m a non-technical founder working on a niche job board platform. I’ve decided to use Xano for the backend and am now looking for the right frontend solution.
Here are my key requirements:
User Authentication: Both companies and job seekers should be able to sign up and log in.
SEO / LLMO is critical: I saw on the WeWeb roadmap that SSR (Server-Side Rendering) might be coming. This would be a game-changer for me.
Native App Feel: I want the app to feel seamless and native — so I’d prefer not to split the experience between a subdomain app and a separate blog or content layer built with Webflow, Framer, or WordPress.
Here’s a sample user journey I’m aiming for:
A user lands on a blog article (for SEO), signs up to create a profile, browses job listings, and might later return to read another article — all within the same seamless experience.
Has anyone in this community tackled a similar challenge or switched from another platform?
Would you recommend sticking with WeWeb (even in its current state) or using something like Nordcraft or another SSR/SEO-friendly frontend tool?
• Authentication: WeWeb + Xano is a solid combo for handling auth on both sides (job seekers and companies). We’ve seen this setup power pretty complex apps already.
• SEO & LLMO: You’re absolutely right, our content isn’t currently server-side rendered, which means tools like Webflow or WordPress still offer better out-of-the-box SEO for static content like blogs. That said, SSR is on our roadmap and we’re actively exploring how to make this a reality soon.
• Unified experience: This is where WeWeb shines. If your priority is to offer a native app feel — a single, cohesive experience without context switching, you’ll have a hard time replicating that by stitching together multiple tools. WeWeb gives you the control and flexibility to bring both blog content and app functionality into the same environment, even if it means being more intentional about your SEO strategy for now.
A few people in the community have already gone this route: publishing blog articles within their WeWeb app using CMS-style collections and manually optimizing pages with semantic HTML, meta tags, and structured URLs. It’s definitely doable, and for niche verticals, that’s often enough to rank.
If WeWeb is a match for your long-term vision, high interactivity, full control of UX, single tech stack, I’d recommend going for it. You’ll be able to iterate fast, connect deeply with your users, and when SSR drops, you’re already set.
