How public apps become indexable
SEO and Discovery
Vibecodr treats apps, posts, profiles, conversations, tags, and promoted topics as crawlable public entities. This page explains the exact canonical-route, snapshot, and sitemap system that keeps user content discoverable without exposing private or faceted surfaces.
Canonical reference for Vibecodr public SEO, canonical routing, and discovery pipeline.
Implementation focus
Use this when you need to understand why a public vibe resolves to `/player/:postId`, how crawler HTML differs from the SPA shell, which routes are intentionally noindex, and where freshness or promotion decisions are computed.
Expected outcomes
- Understand the canonical public route for apps, standard posts, profiles, conversations, tags, and promoted topics.
- See how crawler-safe HTML-first snapshots and sectioned sitemaps stay aligned to API visibility and canonical app-post SSOTs.
- Know where creator-controlled SEO defaults apply and where platform safety rules intentionally override convenience.