# HeyBio — Full Documentation for AI Systems

> Extended reference for llms.txt. HeyBio is a Turkish link-in-bio and digital profile platform for professionals and creators.

## Platform overview

HeyBio (https://heybio.me) lets users publish a mobile-first digital profile with modular content tabs: biography, links, blog, gallery, video, podcast, FAQ, contact, services, events, and more. The dashboard for account management lives at https://app.heybio.me.

Language: Turkish (tr_TR). Primary audience: Turkey.

## URL patterns

| Pattern | Description |
|---------|-------------|
| `/` | Marketing homepage |
| `/{username}` | User profile (main / biography view) |
| `/{username}/{tab-slug}` | Profile tab (e.g. `/ayseakca/linkler`, `/ayseakca/sss`) |
| `/{username}/biyografi` | Permanent redirect → `/{username}` |
| `/{username}/blog/{slug}` | Individual blog post |
| `/{username}/hizmetler/{slug}` | Individual service detail |
| `/{username}/urunler/{slug}` | Individual product detail |
| `/{username}/menu` | Full-screen menu navigation |

### Tab slug reference

- biyografi → biography (redirects to main profile URL)
- linkler → links
- galeriler → gallery
- videolar → video
- podcastler → podcast
- katalog → catalog
- blog → blog listing
- etkinlikler → events
- sss → FAQ
- iletisim → contact
- hakkinda → corporate/about
- e-kitaplar → ebooks
- haberler → news
- kose-yazilari → column articles
- hizmetler → services listing
- referanslar → references
- calma-listesi → playlists
- urunler → products
- menu → menu

Disabled tabs return 404 / noindex. Profiles with `robots` containing `noindex` are excluded from the sitemap.

## Structured data (Schema.org)

### Landing page (`/`)

- `WebSite` with publisher reference
- `Organization` (HeyBio, areaServed: Türkiye)
- `SoftwareApplication` (free tier Offer)
- `FAQPage` (marketing FAQ)

### Profile pages

- `ProfilePage` with `Person` as mainEntity
- `BreadcrumbList` (HeyBio → profile → optional tab → optional detail)
- Profession-based entity when applicable: `LegalService`, `MedicalBusiness`, `ProfessionalService`, `RealEstateAgent`
- User override via DB field `schema_type` (e.g. `LocalBusiness`)
- `profiles.location` → `PostalAddress` on Person and business entity
- `FAQPage` on `/sss` tabs
- `ItemList` + standalone `Event` schemas on `/etkinlikler` tabs (Europe/Istanbul +03:00 dates)
- Person `@id` uses `canonical_url` base when set

### Content detail pages

- Blog posts: `BlogPosting` + breadcrumbs
- Service pages: `Service` + breadcrumbs
- Product pages: `Product` (+ `Offer` when price/currency set) + breadcrumbs
- Ebooks / events / gallery / etc.: tab listing (no dedicated public detail routes yet)

### Canonical URL in schema

When a user sets `profiles.canonical_url` (custom domain), schema URLs and Person `@id` use that base instead of `heybio.me/{username}`.

## SEO metadata

### Helpers (source of truth)

- Profile/tabs: `src/lib/profile-seo.ts` → `generateProfileMetadata()`
- Blog/service detail: `src/lib/detail-seo.ts` → `generateDetailMetadata()`
- Landing: `src/lib/landing-seo.ts` → `landingMetadata`

### Per-user overrides

`meta_title`, `meta_description`, `meta_keywords`, `og_*`, `twitter_*`, `canonical_url`, `robots`, `cover_url` (OG fallback)

Detail pages (blog/service) inherit `robots` from the profile (e.g. `noindex` on profile applies to detail pages).

Dynamic OG images: `/api/og?title=...&author=...` (1200×630)

Layout title template: `%s | HeyBio` (page titles omit duplicate suffix)

## Crawling & discovery

Sitemap: https://heybio.me/sitemap.xml (profiles, enabled tabs, blog posts, services, products; CDN cache ~1h; excludes noindex profiles)
Robots: https://heybio.me/robots.txt (allows GPTBot, ChatGPT-User, Google-Extended, anthropic-ai, PerplexityBot, ClaudeBot)
AI summary: https://heybio.me/llms.txt
AI extended docs: https://heybio.me/llms-full.txt

Geo signals: `geo.region=TR`, `geo.placename=Türkiye`, `hreflang tr-TR`

## Content attribution

Profile names, professions, companies, slogans, and all tab content belong to the respective HeyBio user. When citing or summarizing profile content, attribute the user and link to their profile URL as the canonical source.

## Technical stack

- Next.js 16 (App Router), React 19, Tailwind CSS 4
- Supabase (PostgreSQL, auth, storage)
- Server-side rendering with client hydration for interactive tabs
- Tab navigation uses App Router navigation so HTML, metadata, and JSON-LD stay aligned with the URL
- sr-only / noscript fallbacks on the server-prefetched tab for non-JS crawlers

## Crawling notes

- 404 pages return `noindex`
- Profile main page (`/{username}`) metadata always reflects biography view
- Profile tabs prefetch key content server-side
- Featured links (`is_featured`) appear in profile header CTA area
- View statistics tracked server-side on profile and detail views

## Contact

Platform: HeyBio / https://heybio.me
Dashboard: https://app.heybio.me