Silayolu: SEO-First Community Portal for the Turkish-Belgian Diaspora
Silayolu is a community portal that has grown to several thousand organic visitors per day without paid acquisition. The strategy is unsexy: write for the actual questions your community searches, and let SEO do the rest.
Silayolu serves a specific audience: Turkish-speaking residents of Belgium, and Belgian residents with family ties to Turkey. The audience has a specific question pattern that is underserved by both Dutch-language Belgian sites and Turkish-language Turkey-based sites. The product strategy is to be the best answer to those questions.
What the audience actually searches
Three categories of query dominate the traffic:
- Administrative. "Belgium driving license exchange for Turkish nationals," "Belgian social security number for new arrivals," "Belgian tax filing deadlines." These have stable volume and high commercial intent.
- Cultural and community. "Turkish grocery stores in Antwerp," "Turkish-speaking lawyers in Brussels," "Ramadan prayer times in Belgium." These have lower volume but drive loyal repeat visits.
- Cross-border life. "Sending money from Belgium to Turkey," "Turkish consulate appointments in Brussels," "Bringing pets between Belgium and Turkey." These are the queries that no other site answers well.
The editorial workflow
Every published piece is written by someone who has lived the question being answered. That is non-negotiable. The workflow:
- Question intake. Community submissions via a form, plus search-console query mining to find gaps.
- Writer assignment. A community writer with direct experience of the question gets first refusal. Fallback to a staff writer who is briefed by a community member.
- Editorial pass. A second pair of eyes checks for accuracy, especially on administrative content where a wrong step costs the reader days.
- Publishing cadence. Two to three pieces per week. Not daily — consistency beats volume for an audience that values trust over novelty.
The SEO posture
We treat SEO as a downstream effect of answering questions well, not as the goal. That said, the mechanical bits matter:
- Clean URL slugs in Turkish. Slugs are Turkish-language, not transliterated English. This aligns with how the audience actually searches.
- Structured data on every page. Article, BreadcrumbList, and Organization schema on every published piece. LocalBusiness schema for the directory pages.
- A sitemap that updates hourly. Built into the Next.js sitemap route, regenerated whenever a publish event fires.
What we do not do
- No display ads. The audience is small enough that ad revenue would not fund a single full-time editor.
- No SEO link buying. A single bad backlink from a penalized neighbor is more damage than ten good ones are worth.
- No AI-generated content for community-facing pieces. The trust that drives the organic traffic was built by humans, and humans continue to write every published piece.
What is next
A Dutch-language sibling portal for the same audience, served from the same backend, with shared editorial workflow but Dutch-first answers for queries that surface in the Belgian-Dutch search index. The data model was built for multi-language from day one.