How Basin got its users

Basin does not open with a blog. It opens with a grid: /guides/jamstack/nextjs, /guides/static/astro, /guides/cms/webflow. Three buckets, one page per stack, because the query typed is 'astro contact form no backend', not 'best form tool'. List the stacks your buyer already runs and claim one URL each. Ship only the ones you can demo yourself, before you write a single opinion piece.

done whenOpen your own sitemap and count URLs that contain a framework or platform name. If every page is named after your features instead of the reader's stack, there is no query for them to match.

Every guide runs one skeleton: Requirements, create the project, create a Basin endpoint, paste the form, a bonus webhook section, then a conclusion pointing at docs.usebasin.com. One complete copy-paste component, never fragments. No author byline on any of them. Whoever wired the integration writes the page, so the code is code that actually ran. Build the skeleton once and a new stack becomes an afternoon.

done whenPaste your own snippet into an empty project and run it. If it throws, or the reader has to stitch three blocks together to get a working form, the page will not be trusted, shared or linked.

Second grid: /compare/formspree-alternative, /compare/netlify-forms-alternative, one URL per rival, all hanging under /compare, whose intro promises 'We want you to choose the best solution for you, even if it's not us.' Each page carries a side-by-side table, a 'What's best for me?' verdict that concedes real cases, and a section on moving existing forms over. Name the rival in the H1. That buyer already decided to switch.

done whenWrite the verdict paragraph before the table. If you cannot name a buyer who should honestly pick the competitor, the page reads as an ad and they leave for a third-party review site instead.

Third grid needs no prose: /html-form-generator, plus a page per intent, contact-form, order-form, donation-form, volunteer-signup-form. Pick fields, watch the HTML update, copy it out. No account needed for the code. The account is needed only for the endpoint that makes the form receive anything. It ranks on 'html contact form code' and hands the reader a half-finished object your product finishes.

done whenCheck the handoff in your own free tool: does its output stop exactly where your paid product starts? If a reader can finish the job without you, you built a giveaway, not an entrance.

Only now the blog, at whatever pace the same developers can hold: 'How to Stop Bots From Submitting Forms', 'Creating an Effective Contact Us Form (+ Copy-Paste Code)'. Symptom queries, code in every one. usebasin.com/about names the developers by hand and no guide carries a byline, so nothing waits on a writer. The grids stay permanent: revisit a stack page when that framework ships a breaking release, not on a content calendar.

done whenLook at what you published last month. If a post would need a rewrite to still be true next quarter, it belongs in the blog. If it would only need a version bump, it belongs in the permanent grid.