Skip to content
Otoshek
OTOSHEK · DOCS
LAUNCH GUIDE · 07scheduleRead · 4 min

SEO, Analytics & Privacy

Every app deployed through Otoshek ships with a production-ready SEO, analytics, and privacy stack. Search controls, GTM-based analytics, Microsoft Clarity, and a GDPR-aware consent flow are already in place from day one, but nothing turns on until you choose to activate it.

Three stacks · one deployment

SUMMARY
01
search

Search-ready

Per-page metadata, canonical tags, structured data, sitemap generation, and safe crawl rules.

02
monitoring

Measurement-ready

Google Analytics and Microsoft Clarity flow through GTM so tags stay easy to manage.

03
shield_lock

Privacy-ready

Google Consent Mode v2, granular preferences, and region-aware banner behavior come prewired.

01

Search engine optimization

Otoshek deployments include the core SEO wiring needed to control how search engines discover and present the app, without relying on static HTML edits or third-party plugins.

sell

Dynamic meta tags

Every page can define its own search and social preview metadata through the shared SEO component.

  • —Titles and descriptions for search results
  • —Open Graph tags for LinkedIn, Facebook, and other social platforms
  • —Twitter/X summary_large_image cards
  • —Canonical URLs to avoid duplicate-content issues
  • —Keyword meta tags where they are still supported
  • —JSON-LD structured data for enhanced search results
find_in_page

Live robots.txt and sitemap.xml

Crawl controls and sitemap data are generated dynamically by Django instead of being hand-maintained static files.

  • —Development environments block crawlers with Disallow: /
  • —Development pages also carry a noindex meta tag
  • —SEO goes live only when SEO_ENABLED and VITE_SEO_ENABLED are turned on
  • —Public routes appear in /sitemap.xml with priority metadata
  • —Sensitive routes like admin, auth, and payment flows stay excluded
02

Google Analytics and Microsoft Clarity

Analytics are routed through Google Tag Manager so measurement stays centralized, flexible, and easy to change without redeploying the app.

One environment variable, full analytics activation
Once VITE_GTM_ID is set, the GTM container can drive pageviews, events, heatmaps, and future marketing tags from one place.
01
monitoring

One GTM container ID

Set VITE_GTM_ID and the app is ready to route analytics and privacy signals through Google Tag Manager.

02
show_chart

GA4 and Clarity together

Google Analytics handles pageviews and events while Microsoft Clarity adds session replay and heatmap visibility.

03
tune

Centralized tag control

Future tags can be added, removed, or adjusted from GTM without changing application code or shipping a new deploy.

04

Fully customizable

The stack is prewired, but it is still normal application code. You can adapt the behavior, copy, and route coverage without being locked into a plugin or external consent platform.

01
cookie

Consent banner UI

Adjust the banner copy, CTA labels, layout, and styling to match the brand of each app.

02
shield_lock

Consent logic

Update the EEA detection rules, change consent categories, or alter how stored preferences are managed.

03
search

Per-page SEO content

Change titles, descriptions, canonical URLs, and structured data directly in the page components that ship with the app.

04
language

Sitemap coverage

Add or remove public routes from the sitemap through the server-side route configuration.

05

Zero configuration, zero risk

The key benefit is not just capability. It is the fact that the capability starts in a safe state and becomes active only when you decide the app is ready.

  • SEO stays off in development, previews, and staging until you explicitly enable it.
  • No analytics scripts or cookies activate until a GTM container ID is configured.
  • Consent Mode v2 signals are in place before measurement tools begin listening.
  • The full stack stays in your codebase instead of depending on external banner plugins or SaaS add-ons.