Skip to content
Muhammad Safyan

US marketing agency

19 insurance lead-generation sites from one Next.js codebase

One Next.js template rendering 19 insurance lead-gen sites, with AI page generation, location pages and SEO data pipelines: 1,233 pages indexed and 27 page-1 rankings.

live sites from one codebase
19live sites from one codebase
pages indexed by Google
1,233pages indexed by Google
weekly search impressions
533 → 6,271weekly search impressions

The problem

A US marketing agency builds lead-generation websites for local insurance agencies. Each new site meant hand-built pages and content, and there was no shared view of how the sites performed in search.

What I built

  1. 01Redesigned the multi-tenant Next.js template that renders every agency's site on its own domain: quote forms, a mobile call bar, estimate calculators, lead tracking and new site types.
  2. 02Built AI page generation that writes one section at a time and validates and corrects its own output, plus automatic repair of broken links in published content.
  3. 03Generated location and policy pages programmatically, with a queue that rewrites internal links when a page changes and redirects for retired URLs.
  4. 04Pulled Search Console, SE Ranking, BrightLocal, GA4, Bing and Clarity data into one pipeline behind a site-performance dashboard, and submitted 2,342 URLs to Bing through IndexNow.
  5. 05Shipped it as 128 pull requests across 15 repositories; as of 15 November 27 of 142 tracked keywords rank on page one, including one at #1.

Want results like these on your project?

Tell me what you are building and where it hurts, and I will come back with questions or a plan.