TRIKI DIGITAL – a multilingual agency site with SEO, AI-search and automation foundations

Project overview

TRIKI DIGITAL is Badie Triki's own studio, based in Kehl, Germany. The website doubles as a reference project: it demonstrates in practice how web design, technical SEO, AI-search readiness, tracking and automation fit together.

Initial challenge

An agency site has to carry four languages, six service pages, an FAQ hub, pricing, legal pages and project content — without compromising structure, language logic or loading behaviour.

Goals

The goals were defined in technical and editorial terms from the start:

• a clear service architecture instead of one catch-all page
• clean canonicals and complete hreflang groups for every language
• citation-friendly content for classic search and AI answer engines
• GDPR-compliant tracking with Consent Mode V2
• a traceable path from enquiry to internal handling

Target audience

Small and medium businesses, local service providers, self-employed professionals and export brands in Germany, France, Switzerland and Tunisia.

Strategic approach

Instead of a one-page layout, the site was split into thematic clusters: an SEO cluster, a digital foundation cluster and an automation cluster. Every service has its own page with method, audiences, FAQ and internal links to related services.

Information architecture

Navigation follows a consistent hub-and-detail pattern.

• home page with the AI mini-audit as the entry point
• Solutions hub with six detailed service pages
• Projects hub with individual case studies
• FAQ hub with categories and search
• process, pricing, contact and legal pages

Design and user experience

The design follows modern SaaS interfaces: calm surfaces, clear typography, rounded cards and a consistent colour code. Every page is tested from 390 px upwards, and the Arabic version runs fully right-to-left.

SEO and AI-search foundations

Each route emits its own title, description, self-referencing canonical and a complete hreflang group (de-DE, fr-FR, en, ar, x-default). Structured data lives in one central @graph with Organization, WebSite and Person; pages add Service, FAQPage and BreadcrumbList blocks.

Analytics and tracking

Google Tag Manager and GA4 are integrated but only fire after consent. Consent Mode V2 starts in a denied default state for analytics and advertising signals; the choice is stored locally and can be reopened from the footer.

Automation and integrations

The contact form calls a Supabase Edge Function, which sends confirmation and notification emails through Resend and forwards the lead to an n8n workflow — secured with a secret header and a timeout so the email flow is never blocked.

Multilingual implementation

German is served without a prefix; French, English and Arabic run under /fr, /en and /ar. The language switcher keeps the current page, and each language is written natively rather than machine-translated.

Current implementation status

Live and under continuous development. Delivered: service pages, FAQ hub, pricing, legal pages, Consent Mode V2, structured data and the lead workflow. Further content and case studies are added step by step.

Principles from this project

A website is a system, not a layout. Structure, language logic, measurement and processes belong together from day one — retrofitting any of these layers is always more expensive.