User-facing change! SEO Optimization

Thread body

Your Work Deserves to Be Found Most platforms treat the stuff you build as feed content. You publish something, it lives in a timeline for a few hours, and then it's gone. Buried under the next wave of posts. Search engines never see it. The public web never knows it existed. I didn't want that for Vibecodr. If you ship something real here, whether that's a runnable app, a devlog, or a deep conversation thread, I think the open web should be able to find it, understand what it is, and send people to it. Not to a login wall. Not to a blank shell that says "content loads client-side." To the actual thing you made. Every public surface is a real page When a search engine crawls Vibecodr, it doesn't hit a single-page app and bounce. I intercept bot traffic at the edge and serve back a fully rendered snapshot of whatever public entity lives at that URL. Real titles, descriptions, images, structured data, visible content. Not a hollow SPA shell. This works across six types of public pages. Runnable app pages are the strongest showcase surface. If your vibe is a public app, its `/player` page becomes a full product listing: canonical URL, author attribution, engagement stats, tags, topic links, and `SoftwareApplication` structured data. Search engines read it as a live product, not a social media post. Standard post pages cover non-app content. Devlogs, launch notes, write-ups. These get `Article` structured data so search engines can distinguish editorial content from runnable products. Profile pages are indexed as creator hubs. Your display name, bio, about section, links, recent public work, all rendered for crawlers. A lot of discovery starts with the person, not the individual piece of work. If you're building interesting things consistently, your profile accumulates search value over time. Tags turn clusters of related work into discoverable shelves. Every tag gets its own indexed hub collecting matching public posts with their titles, snippets, and author info. Topic pages are the algorithmic curated version of tags. Thematic hubs with cover images, ranked lists of public vibes, and `CollectionPage` structured data. Entire categories of work become indexable destinations. Conversation threads are the secondary discovery layer. Public discussions get indexed with their titles, content, authors, and tags. Sometimes the thing people find first isn't the app itself. It's the thread where people are talking about it. You control what search engines see There are two layers of customization in this system, and the split is deliberate. The direct layer is what you'd expect. In the publish flow, you can set explicit SEO metadata for your posts: title, description, share image, plus separate overrides for Open Graph and X cards. On your profile, you can set default SEO fields and a brand suffix that carries across everything you publish. These aren't afterthought fields buried in settings. They're part of the publish experience because I think they matter. The indirect layer is more interesting. Search-facing surfaces across Vibecodr are also shaped by the real structure of your public work: - The tags you choose determine which tag and topic hubs your work appears in. - Whether something is a runnable app or a standard post changes the structured data type search engines receive. - Your profile content, pinned work, and recent public posts all feed into how your creator page renders for crawlers. - The quality of your titles and descriptions compounds outward into every discovery surface your work touches. So SEO on Vibecodr isn't a disconnected form you fill out once and forget. It grows out of the actual product you built, the context around it, and the identity behind it. Why I built it this way The goal was never "more pages in Google." The goal is that when you build something on Vibecodr, the public web can understand what it is. A runnable vibe should look like a runnable product. A creator profile should look like a body of work. A topic page should feel like a living scene, not a dead archive. If you publish public work here, the platform projects the thing you actually made. Not a generic page with some meta tags and hope for the best. That's a better foundation. And it's yours from the moment you hit publish.