How supastarter got its users

List every fork you had to resolve while building your product, then write one post per fork. supastarter's blog is that list: better-auth vs NextAuth vs Clerk, Prisma vs Drizzle, Hono vs tRPC vs oRPC, Stripe vs Lemonsqueezy vs Polar vs Creem, Next.js vs TanStack Start. One byline, Jonathan Wilke, the founder who maintains the code. You already made those calls, and the buyer types them into Google the week before buying. No keyword tool needed, just your commit log.

done whenOpen your repo and list the choices you argued about for more than an hour. If you cannot name five, you do not have a comparison series yet, so write setup guides first.

Use one template for every comparison: TL;DR, a short table, then 'When to choose X', 'When to choose Y', 'Our Take'. Only after the verdict comes a section named after your product, like supastarter's 'Prisma and Drizzle in supastarter', whose point is that both ship supported out of the box. Close with the same standing block every time, 'Start your scalable and production-ready SaaS today' and a Get started button to pricing.

done whenReread your last post: does a reader who never buys still get a usable answer? If the verdict is always your product, the page will not survive the query it targets.

Put the docs on the marketing domain, open, no login: supastarter.dev/docs/nextjs holds setup, payments, authentication and per-provider recipes for Neon, Supabase, PlanetScale, Turso, Railway. Then one deployment tutorial per host, each its own post: render-deployment, flydotio-deployment, netlify-deployment, self-host-nextjs-app-with-docker, neon-setup. Those are 'how do I run this on X' searches, and your codebase is the answer.

done whenCheck where your docs live. If they sit on a locked subdomain or in a Notion, the setup questions you already answer daily are ranking for somebody else.

Ship one landing page per phrasing the buyer uses, not per feature: /nextjs-subscriptions-template, /nextjs-admin-ui-template, /nextjs-ai-boilerplate, /nuxt, /tanstack-start. Same body underneath (auth, payments, multi-tenancy, testimonials, the pricing table), different headline and opening section matched to the search. Each page links to its siblings, so one framework query pulls the visitor across the whole set.

done whenWrite down the exact words a buyer would type for your product. If every one of them lands on your homepage, you owe yourself one page per phrase before your next blog post.

Every time you add a provider, publish the announcement as an indexable post: Dodo Payments, oRPC, Queuebase background jobs and Vemetric analytics each got one on supastarter's blog. It catches 'tool plus Next.js' searches nobody has covered yet, and the vendor often links back. Pair that with a free upstream tool like supastarter.dev/saas-ideas, where each generated idea gets its own URL and its own path back to the kit.

done whenLook at your integrations list. Each one you shipped silently is a post you already wrote in code. Ask the vendor to link it, and if they will not, the post still stands alone.