How Bannerbear got its users

Bannerbear repeats one outcome across every host: auto-generate open graph images ships as its own post for WordPress, Webflow, Ghost, Airtable, Zapier, Make and Node.js, and again as a page under /use-cases/scenarios/. Before you write, list the 5 outcomes your API produces and every host it plugs into. The grid cells are your titles. Write the cell (one outcome plus one named host), never the topic.

done whenCount your grid cells. Under 20 and you have a few posts, not a channel. If two cells would produce the same screenshots and the same code, they are one cell.

The best posts never name the product in the title: How to Trim a Video Using FFmpeg, 10 Airtable Formulas All No-Coders Should Know. Each teaches the hard way in full, copy-pasteable commands with the output shown, then a late H2 called Using Bannerbear API does the same job in a few lines, then the conclusion. Keep your product out of the title and out of the first half. The query you rank on belongs to the other tool.

done whenDelete your product section and reread. If the tutorial still finishes the job on its own, ship it. If it breaks, you wrote an ad and it will not hold a ranking.

Who writes: you. The /about/ page puts the founder beside two first-name Marketing people, and the FFmpeg posts carry a byline that says automation enthusiast, not expert. Ship one integration, write its tutorial that same week, one post a week, alternating the two lanes the site keeps apart: /resources/developers/ (Ruby, Node.js, PHP quick starts) and /resources/nocode/ (Airtable, Zapier, Make, WordPress). File every post in one lane.

done whenCheck your last four posts: did each follow an integration you actually shipped and used? If not, the commands will be wrong and the first commenter will say so.

Bannerbear pairs its FFmpeg tutorials with no-signup browser tools at /tools/video/: trim, resize, watermark, subtitles, YouTube chapters, converter, each running FFmpeg through WebAssembly with nothing uploaded. The tool page carries one line of pitch, that the API does this automatically at scale. Take your most-read tutorial, build its one-click version, and let that page hold the CTA the article does not.

done whenOpen your top tutorial. Can a reader finish that job on your site with no account and no file leaving their browser? Count how many posts still have no tool twin.

Each tutorial ships twice. Bannerbear publishes a second post with a video- slug prefix that embeds the YouTube version and pastes a full Video Transcription underneath, so trimming video with FFmpeg holds two URLs and two entry points. Record your screen once while following your own written steps, publish the embed plus the transcript, and file both posts under the same tag.

done whenCheck that your video post carries the full written steps, not just the embed. An embed with two sentences around it ranks for nothing and the second URL is dead weight.