Back to articles

    The Technical Checklist That Turns a Swiss Website Into a Traffic Engine (2026)

    Daniel Maitre· Fondateur d’AltioMay 22, 202618 min
    Updated on May 22, 2026
    SEO techniqueGSCGoogle Business ProfileJSON-LDllms.txtCore Web Vitals2026Suisse
    The Technical Checklist That Turns a Swiss Website Into a Traffic Engine (2026)

    Why this checklist exists

    After supporting 50+ SMEs in Western Switzerland since 2024, the same pattern keeps repeating: the site ships, looks great, goes live, and three months later traffic is still flat. The culprit is almost never design. It is everything we did not do around the site: indexing, structured data, Google profile, monitoring.

    This article is the checklist we apply at Altio on every project, before and after launch. It is intentionally technical and operational. If you work with an agency, use it to verify what is actually delivered. If you manage your site in-house, here is the full sequence.

    Golden rule: a site that is not indexed, not structured, and not measured does not exist for Google. Design only exists for visitors who already arrived.

    Phase 1: before launch

    Validate these on staging. Once in production, some mistakes cost weeks to fix (broken URLs, swapped hreflang, duplicate content).

    1.1 URL architecture

    • Short, lowercase URLs with single hyphens. No accents, no underscores, no useless parameters.
    • One search intent = one URL. Two pages targeting the same query cannibalize each other.
    • Maximum depth: 3 clicks from the home for any indexable page.
    • Slugs designed for the long run (/services/web-design rather than /services/2026-spring-promo).

    1.2 Meta tags and Open Graph

    Every indexable page needs:

    • A unique <title> of 50 to 60 characters, keyword first when possible.
    • A <meta name="description"> of 130 to 160 characters that earns the click (it is not a direct ranking factor, it is a CTR factor).
    • A <link rel="canonical"> pointing to the page itself, never to another language.
    • Open Graph (og:title, og:description, og:image, og:url, og:locale) and Twitter Card tags for LinkedIn, WhatsApp, X previews.

    Frequent mistake: the same <title> copied across 20 pages. Google detects it and demotes the whole set.

    1.3 Multilingual: hreflang and x-default

    If your site ships in French and English, each page must declare its alternates in the <head>:

    <link rel="alternate" hreflang="fr-CH" href="https://your-site.ch/page" />
    <link rel="alternate" hreflang="en" href="https://your-site.ch/en/page" />
    <link rel="alternate" hreflang="x-default" href="https://your-site.ch/page" />

    The x-default is mandatory as the fallback signal for search engines. It is the #1 mistake I find on poorly configured bilingual sites.

    1.4 Sitemap.xml

    The sitemap lists the canonical URLs you want indexed. Concrete rules:

    • One version per page (the canonical).
    • All multilingual pages declare their <xhtml:link rel="alternate">.
    • No noindex pages in the sitemap (conflicting signal).
    • <lastmod> kept current, ISO 8601 format.
    • File reachable at https://your-site.ch/sitemap.xml and declared in robots.txt.

    1.5 robots.txt

    A minimal file that opens the right doors:

    User-agent: *
    Allow: /
    
    User-agent: GPTBot
    Allow: /
    
    User-agent: Google-Extended
    Allow: /
    
    User-agent: ClaudeBot
    Allow: /
    
    User-agent: PerplexityBot
    Allow: /
    
    Sitemap: https://your-site.ch/sitemap.xml

    Blocking AI bots is defensible for some publishers. For an SME that wants to be cited in ChatGPT or Perplexity in 2026, it is self-sabotage.


    Phase 2: structured data (JSON-LD)

    This is the layer that turns a "readable" site into one Google and LLMs actually "understand". Without it, you exist. With it, you become eligible for rich results, AI Overviews and citations inside generated answers.

    2.1 Organization and LocalBusiness

    Place in the <head> of the home and about pages. For a local business, LocalBusiness (or a subtype like ProfessionalService) is far more powerful than Organization:

    {
      "@context": "https://schema.org",
      "@type": "ProfessionalService",
      "name": "Your Company",
      "url": "https://your-site.ch",
      "logo": "https://your-site.ch/logo.png",
      "image": "https://your-site.ch/og.jpg",
      "telephone": "+41 22 000 00 00",
      "email": "contact@your-site.ch",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "Sample Street 10",
        "postalCode": "1204",
        "addressLocality": "Geneva",
        "addressCountry": "CH"
      },
      "geo": { "@type": "GeoCoordinates", "latitude": 46.2044, "longitude": 6.1432 },
      "openingHoursSpecification": [{
        "@type": "OpeningHoursSpecification",
        "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
        "opens": "09:00", "closes": "18:00"
      }],
      "sameAs": [
        "https://www.linkedin.com/company/your-company",
        "https://www.google.com/maps/place/?q=place_id:YOUR_PLACE_ID"
      ]
    }

    The sameAs pointing to your Google Maps profile via place_id is one of the strongest consistency signals. It remains widely underused.

    2.2 BreadcrumbList

    Add it to every page other than the home. Google uses it to display breadcrumbs in the SERP, which lifts CTR.

    2.3 FAQPage

    If your page contains a real FAQ section, add the FAQPage schema. Note: since August 2023, Google no longer systematically shows FAQ rich snippets, but the schema is still consumed by LLMs and AI Overviews.

    2.4 Article, Service, Product, Review

    Pick what matches the page. A blog post = Article with author, datePublished, dateModified, image. A service page = Service linked to your ProfessionalService. A shop = Product + Offer + AggregateRating if reviews are verified.

    Anti-penalty rule: never declare a schema that does not match visible content. No fake ratings, no invented FAQ. Google penalises ("Spammy structured markup").

    2.5 Validate

    Before launch, run each page type through the Rich Results Test and the Schema Markup Validator. Zero errors, zero critical warnings.


    Phase 3: the AI layer (GEO/AEO)

    This is the 2025-2026 novelty. LLMs read sites differently from traditional crawlers. Three files to publish at the root:

    3.1 llms.txt

    Inspired by Jeremy Howard's proposal, this is a Markdown index meant for an LLM. Minimal format:

    # Your Company
    
    > Web design for SMEs in Western Switzerland, free prototype in 48h.
    
    ## Main pages
    - [Services](https://your-site.ch/services): our offer
    - [Pricing](https://your-site.ch/pricing): transparent grid
    - [Portfolio](https://your-site.ch/portfolio): client projects
    
    ## Reference content
    - [Blog](https://your-site.ch/blog): SEO, design, AI articles

    3.2 llms-full.txt

    Extended version, contains the full Markdown of your key pages. Useful for LLMs that do not crawl your site in real time.

    3.3 Raw Markdown access

    Serving an .md version of your articles (or exposing them via a predictable URL) eases ingestion by LLMs. Several SEO studios are adopting this pattern in 2026.


    Phase 4: launch day

    This is where most projects lose 3 to 6 months. The sequence to run within 24 hours after go-live:

    4.1 Google Search Console

    1. Add the property (prefer "Domain" property via DNS rather than "URL prefix").
    2. Submit the sitemap.
    3. Manually request indexing of the 10 priority pages via "URL Inspection".
    4. Check the "Pages" tab after 48h: no coverage error, hreflang detected, sitemap processed.

    4.2 Bing Webmaster Tools

    Often forgotten, although Bing powers ChatGPT Search and Copilot. Same procedure as GSC, and you can import the property directly from GSC to save 10 minutes.

    4.3 IndexNow

    A protocol co-built by Microsoft and Yandex, supported by Bing and several LLMs. A simple HTTP ping speeds up indexing of new pages. On our Altio projects, Bing indexing drops from 5-10 days to under 24h.

    4.4 Final production check

    • curl -I https://your-site.ch returns HTTP/2 200 and the correct content-type.
    • HTTPS enforced on every page (301 redirect from http://).
    • www and non-www resolve to a single canonical version.
    • No resource blocked by CSP or robots.txt that would prevent rendering.

    Phase 5: local SEO and Google Business Profile

    For 80% of SMEs in Western Switzerland, local SEO brings more qualified traffic than national SEO. It is also the fastest channel to activate.

    5.1 Create or claim your Google Business Profile

    • Very specific primary category ("Web design agency" rather than "IT service").
    • 2 to 3 relevant secondary categories.
    • 750-character description that conveys your value proposition and 2-3 natural keywords.
    • At least 10 photos: exterior, interior, team, projects, product.
    • Accurate opening hours, including Swiss public holidays (Geneva Fast Day, August 1st, etc.).
    • Service area if you travel (cantons covered).

    5.2 NAP consistency: the underestimated factor

    NAP = Name, Address, Phone. These three must be strictly identical across:

    • Your site (footer + contact page + LocalBusiness JSON-LD).
    • Google Business Profile.
    • local.ch, search.ch, moneyhouse.ch.
    • LinkedIn, Facebook, industry directories (accounting: TREUHAND-KAMMER; restaurants: GaultMillau, TripAdvisor; healthcare: doctena.ch, etc.).

    A single inconsistency in the street or phone format (space, country code, dot or dash) dilutes the local signal. It is one of the first things I fix in audits.

    5.3 Google reviews

    • Minimum target: 10 reviews over 12 months, average rating ≥ 4.7.
    • Set up a simple workflow: post-service SMS or email with a direct g.page/r/... link.
    • Reply to 100% of reviews, positive and negative, within 7 days.

    5.4 Citations and local backlinks

    A few Swiss directories that still carry weight in 2026: local.ch, search.ch, moneyhouse.ch, hotfrog.ch, swissguide.ch, cantonal chambers of commerce (CCIG in Geneva, CVCI in Lausanne).


    Phase 6: performance and 2026 Core Web Vitals

    Google replaced FID with INP in March 2024. The "good" thresholds at the 75th percentile in 2026:

    MetricGood thresholdWhat it measures
    LCP (Largest Contentful Paint)< 2.5sLoading speed of the main element
    INP (Interaction to Next Paint)< 200msResponsiveness to clicks, taps, keystrokes
    CLS (Cumulative Layout Shift)< 0.1Visual stability

    6.1 Concrete levers

    • WebP or AVIF images, resized to display size (no 4000px served at 400px).
    • Explicit width and height on every <img> to prevent CLS.
    • Native lazy loading (loading="lazy") on everything below the fold.
    • Self-hosted web fonts with font-display: swap or optional.
    • Fewer third-party scripts (each marketing pixel costs 50 to 200ms of INP).
    • Preload the LCP image (<link rel="preload" as="image">).

    6.2 Measurement tools


    Phase 7: security, compliance, trust

    7.1 HTTPS and headers

    • Valid certificate (Let's Encrypt is enough for 99% of SMEs).
    • Strict-Transport-Security (HSTS) header enabled.
    • Minimal but present Content-Security-Policy header.
    • X-Content-Type-Options: nosniff and Referrer-Policy: strict-origin-when-cross-origin.

    Quick check: securityheaders.com should return at least a B.

    7.2 nFADP (Swiss law in force since September 2023)

    • Cookie banner with real choice (Accept / Reject / Customize), no dark patterns.
    • Detailed "Privacy policy" page listing sub-processors (host, analytics, forms).
    • Internal processing register kept up to date.
    • Data controller identified with contact details.

    7.3 Swiss legal mentions

    Not as formally mandated as in the EU, but a clear "Legal notice" page identifying the publisher (legal name, UID, address, contact) reinforces E-E-A-T trust signals for Google.


    Phase 8: monthly monitoring (the link that separates a living site from an abandoned one)

    This is the phase 9 out of 10 SMEs skip. Yet 30 minutes per month is enough.

    8.1 Dashboard template

    SourceMetricTarget
    GSCClicks, impressions, average positionUpward trend over 3 rolling months
    GSCEmerging queriesIdentify 2-3 new intents to exploit
    GSCPages with CTR < 2% in positions 4-10Rewrite <title> and <meta description>
    GSCCoverage: error or excluded pagesZero 4xx, zero 5xx
    GSCCore Web Vitals100% of URLs "Good"
    AnalyticsEntry pages, CTA conversion rateIdentify pages to boost
    GBPViews, calls, direction requestsTrend and seasonality
    GBPNew reviewsReply within 7 days
    BacklinksNew inbound linksCheck quality (Ahrefs, Semrush or GSC "Links")

    8.2 Recommended cadence

    • Weekly (5 min): reply to new Google reviews.
    • Monthly (30 min): review the dashboard above, 1-2 corrective actions.
    • Quarterly (2h): editorial review (which articles drive traffic, which deserve an updatedDate refresh).
    • Annually (1 day): full technical audit (CWV, schemas, redirects, stale content).

    Summary: the one-page checklist

    Before launch

    • Clean URLs, unique titles and descriptions
    • Canonical, Open Graph, Twitter Card on every page
    • Complete hreflang with x-default if multilingual
    • Sitemap.xml and robots.txt validated
    • JSON-LD Organization/LocalBusiness, BreadcrumbList, FAQPage, Article validated on Rich Results Test
    • llms.txt and llms-full.txt at the root
    • LCP < 2.5s; INP < 200ms; CLS < 0.1 on PageSpeed Insights
    • HTTPS enforced, HSTS, CSP, securityheaders.com ≥ B
    • nFADP cookie banner and privacy policy published

    Launch day

    • GSC property created + sitemap submitted + 10 pages indexed manually
    • Bing Webmaster property created + sitemap submitted
    • IndexNow ping sent
    • HTTP 200 + www/non-www redirects verified

    Week 1

    • Complete Google Business Profile (categories, photos, hours, description)
    • NAP identical across site, GBP, local.ch, search.ch, LinkedIn, industry directories
    • Google review workflow live

    Monthly

    • GSC + GBP + Analytics review (30 min)
    • 100% of reviews answered within 7 days

    What we do at Altio

    All our projects include phases 1, 2, 3, 4 and 6 by default. Phase 5 (GBP, NAP, citations) is offered as an onboarding option, and phase 8 (monthly monitoring) is part of our maintenance packs. This is why an Altio site shipped today starts bringing in organic traffic in 6 to 10 weeks, versus 6 to 12 months for a site delivered without these phases.

    To see what this looks like on a real case, check our portfolio. If you are starting a project, begin your brief for free and we will show you a prototype within 48h, already wired for this checklist.

    To go further, also read:

    Frequently asked questions

    Sources & references

    Daniel Maitre

    Fondateur d’Altio

    Founder of Altio, a web agency based in Geneva. Specialist in website creation, web development and digital strategy for businesses worldwide.

    Learn more about the author →

    Ready to launch your project?

    Describe your project in 10 minutes and receive a free functional prototype in 48h.

    Start my free brief

    We use cookies 🍪

    This site uses cookies to improve your experience and analyze traffic. You can customize your preferences at any time.