CISNET: IT certification training.
Marketing site + SEO rebuild.

Legacy PHP that couldn't grow.

CISNET's site was a hand-coded PHP build from 2014. One person knew where everything lived. Nobody else could ship into it without an outage. Marketing wanted new certification pages, ads into specific groups, and leads captured into a CRM. Every new page meant a risky deploy.

The bigger risk was search rankings. The old site ranked for ~70 cert-related searches, and any redesign that didn't keep those URLs risked tanking organic traffic for months. ~40% of new business came from that traffic.

• Brittle stack: PHP 5.6, no tests, manual FTP deploys
• No lead handling: contact form to email, no CRM, no admin view
• Rankings at risk: 70+ ranked URLs that couldn't break
• Marketing blocked: no landing pages without engineering

Next.js 16, pages at scale, and a lead pipeline.

Three tracks over 12 weeks. Track 1 (weeks 1-4): stood up Next.js 16, Supabase, and Vercel, copied the marketing pages over exactly, and tested the redirects. Track 2 (weeks 4-8): 200+ pages, one per certification and city, generated from a single content source, plus a sitemap and structured data that tells Google what each page is. Track 3 (weeks 8-12): the lead pipeline. Facebook lead ads flow in through a verified connection, land in Supabase, show up in the admin portal, and trigger email through Resend. Stripe handles payment for paid courses.

The hardest early call was the redirect strategy. I mapped every old URL by hand instead of using a single catch-all rule. It was slower to build, and Google indexed the new URLs with full ranking value inside 6 weeks instead of 6 months.

• Foundation: Next.js 16, TypeScript, Supabase, Vercel
• Pages at scale: 200+, one per certification and city
• Redirects: 70+ old URLs mapped one by one, not catch-all
• Structured data: 7 types so Google reads each page right: Course, LocalBusiness, FAQPage, Organization, BreadcrumbList, ContactPoint, WebSite
• Lead pipeline: Facebook lead ads to verified connection to Supabase to admin portal to Resend
• Payments: Stripe Checkout for course enrollment

Boring, fast, debuggable.

The default stack: Next.js, Supabase, Vercel. A CMS was an option, but the page volume didn't justify the overhead. Page content lives in the repo as MDX, and copy ships through pull requests.

12 weeks. 3 tracks. Scope locked on day one.

Scope locked in week 0. Anything new went onto a v2 list, and none of it shipped during the engagement.

What it changed.

Numbers from the engagement, technical only. Business KPIs are CISNET's to share.

Marketing now ships new certification pages through MDX without engineering. Leads are traceable from ad click to enrollment. Ads now target specific group and city combinations that had no landing page before.

The admin portal I built.

The contact-form-to-email setup became a full operations console: lead pipeline, students, enrollments, email campaigns, content, and analytics, built from scratch on Next.js 16 + Supabase. No off-the-shelf CRM, no third-party analytics tax. The team runs the business from here.

Early SEO traction.

I took over the SEO operation in late April 2026: rebuilt the content architecture and structured data, fixed the technical foundation (canonicals, redirects, Core Web Vitals), and shipped a free tools and study-resource layer (subnet calculator, practice quizzes, cheat sheets). It's early, and the reach and visibility signals that move first are all up. Measured in Google Search Console across 28-day windows ending April 30 against June 18, 2026:

Source: Google Search Console, sc-domain property, queried live via a service-account API integration I built into the admin portal. Clicks up ~19% over the same window and compounding as the larger footprint matures; off-page authority is the next focus.

Live Google Search Console dashboards. Account identity blurred; all metrics unedited.