gabrielcucos.dev: Autonomous SEO/GEO & Lead Triage Architecture
How a single Next.js 16 + n8n + Supabase stack compiles 612 bilingual MDX assets into 657 static routes, self-prunes dead content via GSC URL Inspection, and triages consulting leads without manual ops.
657 routes / 4.8s
Static App Router Build
612 files (EN + IT)
Bilingual MDX Corpus
6 free-tier engines
Interactive Tools
73 Playwright checks
E2E Verification
Executive Summary
Most technical consulting sites are static brochures that decay the moment they ship. gabrielcucos.dev was engineered as a living production proof-of-work: an autonomous growth, SEO/GEO, and lead-triage system running on Next.js 16, Supabase, and n8n.
Rather than publishing unverified marketing claims, every architectural decision on this domain is backed by deterministic build gates, automated Google Search Console (GSC) pruning, and a scope-first intake pipeline.
1. Deterministic Bilingual Content Engine (612 MDX -> 657 Static Routes)
All technical essays, architectural build logs, landing pages, and case studies live as typed MDX files validated at build time via Zod schemas (BuildLogFrontmatterSchema, StrategicMemoSchema, LandingFrontmatterSchema, and CaseStudyFrontmatterSchema).
- Strict Locale Isolation: English routes live at the root (
/build-logs,/memos,/tools,/case-studies), while Italian routes live under/it/...with bidirectionalhreflangalternates (en,it, andx-default) and zero cross-locale fallback leaks. - Build-Time Safety Gate:
scripts/validate-content.mjschecks every MDX file for placeholder strings, YAML errors, unlocalized links inside/itcontent, and bare<digittokens before Next.js compiles the657static pages in4.8s. - GEO & LLM Discovery: In addition to localized XML sitemaps (
/sitemap.xmland/sitemap-it.xml) with reallastmodtimestamps from frontmatter, the site exposes machine-readable/llms.txtand/llms-full.txtendpoints plus linkedTechArticle,SoftwareApplication,BreadcrumbList, andFAQPageJSON-LD graphs anchored to a canonical@id.
2. Self-Pruning SEO Loop via n8n & GSC URL Inspection
Scaling programmatic content without pruning creates index bloat and keyword cannibalization. To prevent that, an n8n workflow (GSC Autonomous Content Pruner) audits search performance and indexation automatically:
- Multi-Signal Pruning: It pulls Search Analytics from GSC alongside live URL Inspection API checks (
per_page=100pagination) to identify zero-traction or unindexed URLs. - Atomic Consolidation (
308+ Link Rewrite): In our latest consolidation pass,10zero-traction slugs were retired into canonical pillars via permanent HTTP308rules indata/pruned-redirects.json, while90+surviving MDX files had their internal links rewritten atomically to point directly to the surviving targets. - Database & Alert Guardrails: Every pruning run logs to Supabase and routes exceptions through a dedicated
System Alertworkflow.
3. Productized Lead Magnet Suite (6 Interactive Tools)
Instead of gating generic PDFs, /tools ships 6 free-tier interactive diagnostic and architectural utilities (combining instant zero-cost client engines with live-server analysis endpoints):
- Tracking, Platform, Consent & Security Headers Inspector
- AI-Readability, GEO & SERP/OpenGraph Scanner
- dataLayer, Meta CAPI & BigQuery SQL Tracking Plan Builder
- Redirect Chain & UTM Attribution Integrity Checker
- GSC Content Decay & Pruning Analyzer
- CRO, A/B Test Sample Size & Revenue Impact Calculator
4. Scope-First Lead Triage & Verification
Visitors who want an architectural review submit their stack and constraints on /audit. Submissions persist to Supabase (gc_audit_leads), trigger the Lead Scoring Engine in n8n, and receive a deterministic score before any calendar invite is issued.
Every release is gated by npm run validate:content, TypeScript (tsc --noEmit), production next build, and 73 Playwright E2E checks across Desktop Chrome and Pixel 5 viewports—enforcing >= 44x44px touch targets, WCAG AA contrast, and zero console/hydration errors.
Want this exact architecture adapted to your product? Run the Growth Architecture Audit or explore the Build Logs.
Want this working inside your business?
Whether you're a founder fixing tracking leaks or a team scaling SEO and AI workflows, share your site and bottleneck for a clear diagnostic within 48 hours.