Abhishek PatelPortfolio
Build.
000
Work
Marketing site + InfraDec 2024 - presentLive

Apex36 Website

A marketing site built from scratch, then migrated Vercel to GCP and tuned for AI search.

Sole developer, all phasesApex36 Technologies
Next.jsTailwind CSSFramer MotionFirebaseDockerGoogle Cloud RunGitHub ActionsGA4PostHog
Apex36 Website
Apex36 Website screenshot
01The problem

Apex36 needed a fast, well-ranked marketing site with a real blog pipeline. Later, 40+ blog posts on Vercel triggered large bandwidth overages, forcing an infrastructure migration - and AI crawlers could not see the structured data.

02The solution

I built the site from scratch (90+ SEO score, Firebase-backed blog), then migrated it end to end from Vercel to Google Cloud Run, and ran a GEO/AEO overhaul so the site is legible to both Google and AI crawlers.

03Architecture
Site

Next.js + Tailwind + Framer Motion, Firebase/Firestore blog pipeline

Migration

Multi-stage Docker standalone app, GCP Artifact Registry, Cloud Run, External Load Balancer + managed SSL

CI/CD

GitHub Actions with OIDC / Workload Identity - no stored service-account keys

Analytics & GEO

GA4 (14 custom dimensions, funnels), PostHog, server-rendered JSON-LD, llms.txt, AI-crawler allowlist

04Key features

From-scratch build

Full marketing site, 90+ SEO score, 30% faster load times.

Vercel to GCP

Resolved 183 GB bandwidth overages with a Cloud Run migration.

GEO/AEO overhaul

Server-rendered structured data, sitemap expansion, AI-crawler allowlists.

Analytics taxonomy

GA4 with 14 custom dimensions and lead/blog/chat conversion funnels.

05Results
MetricValue
SEO score0+
overage resolved0 GB
GA4 custom dimensions0
keyless CI/CDOIDC
06My role

Sole developer across every phase: the original from-scratch build, the Firebase blog pipeline, the Vercel to GCP Cloud Run migration (Docker, Artifact Registry, Load Balancer, managed SSL, OIDC CI/CD), the GA4 + PostHog analytics taxonomy, and the GEO/AEO implementation that made the site's structured data visible to AI crawlers.

07What I learned
  • NEXT_PUBLIC vars inline at build time - silent analytics breakage taught me that the hard way.
  • GEO is code-level: JSON-LD has to be server-rendered or AI crawlers never see it.
08FAQ

Want the deeper story?

Ask my AI about Apex36 Website for specifics, or reach out directly.

Get in touch
Next project
BrandGen