# quiXzoom Global Domain Masterplan ## Microsoft-Style Structure --- ## EXECUTIVE SUMMARY **Current State:** 22+ domains registered. 4 have real content. 8 redirect to .com. 8 are broken (no DNS or 404). **Goal:** Unified global presence like Microsoft — one master domain with locale paths, regional domains as redirects. --- ## PHASE 1: FIX BROKEN DOMAINS (Week 1) ### DNS/Content Issues | Domain | Issue | Fix | |--------|-------|-----| | quixzoom.de | No DNS | Add Route53 A/AAAA → CloudFront | | quixzoom.fr | No DNS | Add Route53 A/AAAA → CloudFront | | quixzoom.in | No DNS | Add Route53 A/AAAA → CloudFront | | quixzoom.be | No DNS | Add Route53 A/AAAA → CloudFront | | quixzoom.ch | 404 | Deploy redirect page to S3 | | quixzoom.dk | 404 | Deploy redirect page to S3 | | quixzoom.fi | 404 | Deploy redirect page to S3 | | quixzoom.es | 404 | Deploy redirect page to S3 | ### Redirect Strategy (All regional → quixzoom.com/locale/) ``` quixzoom.se → 301 → https://www.quixzoom.com/sv-se/ quixzoom.co.uk → 301 → https://www.quixzoom.com/en-gb/ quixzoom.de → 301 → https://www.quixzoom.com/de-de/ quixzoom.fr → 301 → https://www.quixzoom.com/fr-fr/ quixzoom.nl → 301 → https://www.quixzoom.com/nl-nl/ quixzoom.it → 301 → https://www.quixzoom.com/it-it/ quixzoom.es → 301 → https://www.quixzoom.com/es-es/ quixzoom.ch → 301 → https://www.quixzoom.com/de-ch/ (or fr-ch) quixzoom.dk → 301 → https://www.quixzoom.com/da-dk/ quixzoom.fi → 301 → https://www.quixzoom.com/fi-fi/ quixzoom.be → 301 → https://www.quixzoom.com/nl-be/ (or fr-be) quixzoom.jp → 301 → https://www.quixzoom.com/ja-jp/ quixzoom.in → 301 → https://www.quixzoom.com/hi-in/ (or en-in) quixzoom.mx → 301 → https://www.quixzoom.com/es-mx/ quixzoom.lat → 301 → https://www.quixzoom.com/es-419/ quixzoom.asia → KEEP → Multi-language hub (already working) quixzoom.eu → 301 → https://www.quixzoom.com/en-eu/ ``` --- ## PHASE 2: UNIFIED FOOTER STRATEGY ### Current Footer (quixzoom.com) Shows: EN, 🇸🇪 Sverige, 🇳🇱 NL, 🇹🇭 TH, 🇳🇬 NG, 🇰🇪 KE **Problems:** 1. Missing: UK (co.uk), Asia hub, DE, FR, JP, IN, etc. 2. NG/KE not launched (should show "Coming soon" or be hidden) 3. No distinction between Language and Region 4. Inconsistent across domains ### New Footer Structure (Microsoft-style) ``` ┌─────────────────────────────────────────────────────────────┐ │ 🌍 SELECT YOUR REGION 🌐 SELECT LANGUAGE │ │ │ │ Europe Americas Asia-Pacific Africa │ │ ───────── ──────── ──────────── ────── │ │ 🇸🇪 Sweden 🇺🇸 United States 🇯🇵 Japan 🇳🇬 Nigeria* │ │ 🇬🇧 UK 🇲🇽 Mexico 🇰🇷 South Korea 🇰🇪 Kenya* │ │ 🇩🇪 Germany* 🇧🇷 Brazil* 🇹🇭 Thailand │ │ 🇳🇱 Netherlands* 🇨🇦 Canada* 🇻🇳 Vietnam │ │ 🇫🇷 France* 🇦🇷 Argentina* 🇮🇩 Indonesia │ │ 🇮🇹 Italy* 🇮🇳 India │ │ 🇪🇸 Spain* 🇦🇺 Australia* │ │ 🇨🇭 Switzerland* 🇸🇬 Singapore* │ │ 🇩🇰 Denmark* 🇲🇾 Malaysia │ │ 🇫🇮 Finland* 🇵🇭 Philippines* │ │ 🇧🇪 Belgium* 🇹🇼 Taiwan │ │ 🇭🇰 Hong Kong* │ │ │ │ * Coming soon — notify me when available │ │ │ │ ───────────────────────────────────────────────────────── │ │ quiXzoom Global | Landvex AB | © 2026 │ └─────────────────────────────────────────────────────────────┘ ``` --- ## PHASE 3: TECHNICAL IMPLEMENTATION ### Option A: Static Site Generator (Recommended) - Next.js or Astro with i18n routing - `/[locale]/` path structure - Shared components, localized content - Deploy to Vercel/Netlify or S3+CloudFront ### Option B: Current Approach (Enhanced) - Keep current HTML structure - Build script generates all locale variants - Template + JSON translations (like quixzoom.asia) - Deploy to S3+CloudFront per locale ### Option C: CMS-Driven - Headless CMS (Contentful, Sanity, Strapi) - Content editors manage translations - API-driven rendering - More complex, better for large teams --- ## PHASE 4: CONTENT STRATEGY PER LOCALE ### Must-Have for Each Locale 1. **Localized pricing** (local currency, local payment methods) 2. **Local contact info** (address, phone, support hours) 3. **Legal compliance** (GDPR, local tax, labor laws) 4. **Local payment methods** (Swish, iDEAL, Alipay, etc.) 5. **Local mission examples** (relevant to that market) 6. **Local social proof** (testimonials from that country) ### Content Matrix | Locale | Currency | Payment | Launch | Status | |--------|----------|---------|--------|--------| | en-us | USD | Stripe, ACH | Q4 2026 | Planned | | en-gb | GBP | Stripe, BACS | Live | Active | | sv-se | SEK | Stripe, Swish | Aug 2026 | Active | | de-de | EUR | Stripe, SEPA | Q1 2027 | Planned | | nl-nl | EUR | Stripe, iDEAL | Q1 2027 | Planned | | ja-jp | JPY | Stripe, PayPay | Q2 2027 | Planned | | zh-cn | CNY | Alipay, WeChat | Q2 2027 | Planned | | ... | ... | ... | ... | ... | --- ## IMMEDIATE ACTION ITEMS ### For Erik/Johan to Decide 1. **Which markets are ACTUALLY launching in 2026-2027?** - Current plan: SE, UK, NL, DE, JP? - Remove NG/KE if not launching - Add/remove based on business priority 2. **Domain strategy:** - A) Keep regional domains (apple-style) - B) Redirect all to .com/locale/ (microsoft-style) - C) Hybrid (regional for launched, .com for planned) 3. **Budget for localization:** - Professional translation vs AI translation? - Local legal review per market? - Local payment provider integrations? ### For Me to Execute (Once Decided) 1. Fix all DNS/content issues 2. Build unified footer component 3. Deploy redirect pages 4. Update all domains consistently 5. Set up monitoring/alerting --- ## APPENDIX: Domain Inventory ### AWS Route53 Zones (Need to check) - quixzoom.com - quixzoom.se - quixzoom.co.uk - quixzoom.de (missing?) - quixzoom.fr (missing?) - quixzoom.nl - quixzoom.eu - quixzoom.asia - quixzoom.jp - quixzoom.in (missing?) - quixzoom.mx - quixzoom.lat - quixzoom.net - quixzoom.org - quixzoom.tech - quixzoom.be (missing?) - quixzoom.ch - quixzoom.dk - quixzoom.fi - quixzoom.it - quixzoom.es ### S3 Buckets (Need to check) - quixzoom-landing-prod - quixzoom-se-landing - quixzoom.asia - Others? ### CloudFront Distributions (Need to check) - EHBQ9EIYNM3O0 (quixzoom.asia) - Others?