# Architecture **Source:** https://de.multilipi.com/technology/architecture **Language:** German --- Technical Documentation # The MultiLipi Architecture A Technical Deep Dive Into Our Dual-Layer Infrastructure ## Übersicht Traditional translation plugins operate on the "Visual Layer"—swapping text strings in the browser. While this satisfies human readers, it creates a chaotic environment for search crawlers and AI agents. MultiLipi is the first platform to engineer a **Dual-Layer Architecture**: ### The HTML Layer Fully rendered, localized pages for humans and Googlebot. ### The Data Layer A parallel, structured infrastructure (Markdown + JSON-LD) optimized specifically for Large Language Models (LLMs). Below is the step-by-step documentation of how our **10-Step Pipeline** transforms a static URL into a global, AI-ready entity. PHASE 1 ## Infrastruktur-Setup Die Grundlage We establish the physical routing and security layer before touching a single word of content. ### Step 1: Intelligent Provisioning & SSL Upon connection, our system fingerprints your origin CMS (Shopify, Webflow, WordPress, or Custom Stack) to determine the optimal injection method. - **Aktion:** We instantly provision dedicated SSL certificates for your localized endpoints. - **Mechanism:** Secure Handshake Protocol (TLS 1.3) ensures that data passing between your origin server and our edge nodes is encrypted, with zero latency added to the Time to First Byte (TTFB). ### Step 2: URL Architecture Mapping We support three distinct routing architectures to match your SEO strategy. #### Option A: Subdomains (Fastest Deployment) **Structure:** `es.example.com`, `fr.example.com` **Am besten für:** Large enterprise sites needing separation of concerns. #### Option B: Subdirectories (Maximum SEO Authority) **Structure:** `example.com/es/` , `example.com/fr/` **Mechanism:** We provide a lightweight Reverse Proxy script (Cloudflare Worker or Nginx config) that routes `/es/` traffic to our edge servers while keeping the domain authority unified. #### Option C: ccTLDs (Local Dominance) **Structure:** `example.es` , `example.fr` **Mechanism:** Advanced CNAME mapping allows you to point custom country domains to our localization engine. PHASE 2 ## Inhaltsverarbeitung The Neural Layer We separate "Content" from "Code" to ensure perfect localization without breaking UI functionality. ### Step 3: Deep Ingestion & Slug Localization Our crawler ingests your original HTML and builds a dynamic content map. - **The Code Separation:** We parse the DOM to identify translatable text nodes while "locking" HTML attributes, scripts, and classes. This ensures your site layout never breaks, even in Right-to-Left (RTL) languages. - **Slug Translation:** Unlike standard proxies, we translate the URL path itself. Original: `example.com/products/red-running-shoes` Lokalisiert: `es.example.com/productos/zapatillas-rojas` Auswirkung: Increases Click-Through Rate (CTR) in local search results by matching user intent. ### Step 4: The "Spiderweb" Internal Linking To prevent "orphan pages" (a common issue where localized pages exist but aren't linked), we inject a dynamic routing block. - **Aktion:** A `