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
SUMMARYSearch-ready
Per-page metadata, canonical tags, structured data, sitemap generation, and safe crawl rules.
Measurement-ready
Google Analytics and Microsoft Clarity flow through GTM so tags stay easy to manage.
Privacy-ready
Google Consent Mode v2, granular preferences, and region-aware banner behavior come prewired.
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.
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
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
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.
VITE_GTM_ID is set, the GTM container can drive pageviews, events, heatmaps, and future marketing tags from one place.One GTM container ID
Set VITE_GTM_ID and the app is ready to route analytics and privacy signals through Google Tag Manager.
GA4 and Clarity together
Google Analytics handles pageviews and events while Microsoft Clarity adds session replay and heatmap visibility.
Centralized tag control
Future tags can be added, removed, or adjusted from GTM without changing application code or shipping a new deploy.
GDPR-aware consent banner
Every deployed app includes a consent flow built around Google Consent Mode v2 so analytics and advertising tags can respond to user choices in a privacy-aware way.
Denied by default
Before GTM loads, the app sends denied consent signals for analytics, advertising, and personalization categories.
Banner only where needed
Users in the EEA see the consent banner on their first visit, while users outside those regions keep a frictionless flow.
Granular choices
Visitors can accept all, reject all, or manage analytics and marketing preferences individually.
Preferences are remembered
Consent choices are stored in localStorage and respected on future visits until the user clears browser data.
Consent categories
Users can manage the categories that matter without losing access to the functionality required for the app itself to work.
| Category | Description | Can be disabled? |
|---|---|---|
| Necessary | Essential cookies required for the app to function. | No |
| Analytics | Google Analytics and Microsoft Clarity measurement. | Yes |
| Marketing | Advertising and retargeting cookies when they are configured. | Yes |
Region-aware display
EEA detection is handled through timezone-based logic so the app can decide when the banner should appear without adding another network dependency.
Users in EU and EEA-adjacent regions can be shown the consent banner on first visit, while users outside those regions continue straight into the app experience.
Consent Mode signal handling
The app sets ad_storage, ad_user_data, ad_personalization, and analytics_storage before GTM tags begin evaluating.
When a user accepts or rejects categories, GTM and downstream tags can respond immediately without requiring a reload or custom integration work.
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.
Consent banner UI
Adjust the banner copy, CTA labels, layout, and styling to match the brand of each app.
Consent logic
Update the EEA detection rules, change consent categories, or alter how stored preferences are managed.
Per-page SEO content
Change titles, descriptions, canonical URLs, and structured data directly in the page components that ship with the app.
Sitemap coverage
Add or remove public routes from the sitemap through the server-side route configuration.
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.
