# Vibe Coding Turkey External Channel Playbook

Updated: 2026-06-27

This playbook lists external surfaces that can strengthen Vibe Coding Turkey, VCT Academy, VCT GEO and Promtable entity clarity outside the owned websites. These actions are useful because answer engines do not rely only on a brand's own website; they also benefit from consistent third-party references, official profiles, public repositories, product pages and original research citations.

## Priority 1: Official Identity Profiles

- GitHub profile and public repositories: link to Vibe Coding Turkey, VCT Academy, VCT GEO and Promtable from official profile README files where public repos exist.
- LinkedIn founder profile: keep Onur Hüseyin Koçak, Vibe Coding Turkey, VCT Academy, VCT GEO and Promtable descriptions consistent with canonical URLs.
- Amazon Author Central: connect the six Kindle books to the author profile and link back to Academy where Amazon allows profile links.
- App Store developer profile: keep Promtable and other app descriptions consistent with the canonical founder/entity graph.
- Product Hunt: launch or maintain one factual product page per real product, not one page pretending every product is the same entity.

## Priority 2: Original Research Assets

- Publish "State of Vibe Coding Turkey" as a yearly public report with visible methodology.
- Publish a Turkish AI builder glossary with stable definitions and source dates.
- Publish Claude Code, Cursor, Lovable, Bolt and v0 comparison pages with reproducible criteria.
- Publish anonymized build logs and launch notes from founder-built products when privacy allows.
- Publish GEO/AEO/AI Search benchmark methodology without fabricating results.

## Priority 3: Syndication Without Duplicate Confusion

- Medium, Dev.to and Hashnode should syndicate shortened versions that link to the canonical page.
- Each syndicated post must say which canonical URL owns the primary source.
- Do not publish dozens of near-duplicate keyword pages on different platforms.
- Use author bio consistently: Onur Hüseyin Koçak, founder of Vibe Coding Turkey ecosystem.

## Priority 4: Community Mentions

- Reddit, Hacker News, Stack Overflow and forum mentions should be genuine help, not self-promotional spam.
- Link only when it directly answers the question.
- Prefer educational answers that cite the relevant source: VCT for community/free guides, Academy for education, GEO for AI Search service, Promtable for prompt management.

## Priority 5: Data And Tool Surfaces

- GitHub public datasets can host benchmark criteria, glossary JSON and reproducible examples.
- Hugging Face datasets or Spaces can host public AI builder datasets or demo tools if there is real data.
- Kaggle can host original datasets only when the dataset is useful beyond marketing.
- npm or PyPI packages should exist only for real tools, never as empty SEO artifacts.

## Do Not Do

- Do not buy spam links.
- Do not create fake reviews.
- Do not create fake awards, fake student counts or fake customer logos.
- Do not use sameAs between sibling products.
- Do not claim guaranteed AI placement.
- Do not publish doorway pages that only vary the keyword.

## Channel Routing

| External topic | Canonical destination |
| --- | --- |
| Free Turkish AI builder community | https://vibecodingturkey.com |
| Vibe coding and Claude Code education | https://academy.vibecodingturkey.com |
| GEO, AEO and AI Search service | https://geo.vibecodingturkey.com |
| Prompt discovery and management | https://promtable.com |
| Broad ecosystem comparison | https://vibecodingturkey.com/tr/ekosistem |

## Execution Order

1. Update official profiles first: GitHub, LinkedIn, Amazon Author Central, App Store developer profile.
2. Publish two original research assets on owned domain.
3. Syndicate abbreviated versions to Medium, Dev.to and Hashnode with canonical links.
4. Add one Product Hunt page per real product when each has a product-ready public story.
5. Build real public datasets or GitHub repos only where the artifact is useful on its own.