OG Images Generator for Blog Sites
If your entire site is content — Substack, Ghost, independent WordPress, hand-rolled Markdown — every post is a share opportunity and every share needs a card. Generate per-post Open Graph images with the real headline, byline and brand. No CMS plugin required.
Why a blog site needs per-post cards
On a content-first site, the card is the post — it's what determines whether the link in someone's tweet gets clicked or scrolled past. A single masthead card across 500 posts is a self-inflicted wound.
Pulls each post's real headline
Oginify reads the post's actual <h1>, byline and publish date from the rendered page. No editor has to remember to set an image, no template field to fill in. Publish a post, generate a card, ship.
Editorial typography by default
Blog cards look like blogs, not SaaS landings. The magazine preset gives you a tall serif headline, a left-margin byline rule and a discrete dateline chip — the visual system readers associate with publications they trust.
Works with every blog stack
Substack, Ghost, WordPress, Hugo, Astro, Next.js, hand-rolled — Oginify reads the rendered HTML, so the stack doesn't matter. Stamp the og:image URL into the head once per post and you're done.
Auto-runs on publish
Wire the Oginify API into your CMS's publish webhook (Ghost and WordPress both support this natively). Every new post hits the API with its URL and gets a card back before the post goes live to subscribers.
Per-author cards
Multi-author blogs get an author wordmark on each card automatically. Readers learn to recognize their favorite writer's byline in the feed, before they even read the headline.
Refreshes on rewrites
Headline changed after a copy-edit? Hero photo swapped on a republish? Re-run the URL and the card updates. The version on Twitter from last year unfurls with the fresh card next time someone clicks it.
Substack & Beehiiv
For Substack & Beehiiv newsletters
Substack issues live in inboxes first, but they spread on Twitter and LinkedIn afterward — and every quote-tweet shows the OG card. The magazine preset gives every issue a publication-style card with an issue number kicker and a serif headline. Readers learn to recognize the newsletter at a glance, the same way they recognize a magazine cover.
Ghost & WordPress
For Ghost & WordPress sites
Ghost and WordPress blogs span everything from personal essays to professional editorial sites. Oginify wires into both via the publish webhook — when a post is published, the API generates a card and the CMS stamps the URL into the og:image field. No editor action required.
Engineering blog
For engineering blogs
Engineering writeups need to look like the writer codes, not like the marketing team scheduled them. The terminal preset gives you a monospace headline, an accent rule and an optional code snippet — the card reads as something a developer wrote in a flow state, not something a content team pushed through a calendar.
News & op-ed
For news & opinion blogs
News and op-ed sites need tabloid weight — dense typography, dateline, byline rule, a clear hierarchy that signals reportage. The newspaper preset gives you all four. The card reads as journalism in a feed dominated by influencer takes and brand content.
The prompts behind these four cards
Each card above started as a one-paragraph prompt. Here are the four we used — paste them into Oginify with your own URL and you'll get the same direction in your brand.
Newsletter · the briefing / issue 47
Generate a 1200×630 Open Graph card for the briefing Substack newsletter, issue 47. Editorial magazine layout on warm cream, large serif headline "What changed in venture this week" centered, small mono kicker "the briefing · issue 47" above it, thin horizontal rule and byline "By the editors" below. the briefing serif wordmark top-left. The top 110 px and bottom 110 px will be cropped off — keep wordmark, kicker, headline and byline in the center band.
Blog · the meridian / weekly
Generate a 1200×630 Open Graph card for the meridian Ghost blog. Editorial masthead layout, tall serif wordmark the meridian centered at top, thin rule, featured post headline "On attention, after the feeds" in display serif below, small mono caption "Weekly · 6 min read". Warm cream paper, generous margins, ink only. The top 110 px and bottom 110 px will be cropped off — keep masthead and headline in the center band.
Engineering · forge.dev / log
Generate a 1200×630 Open Graph card for a forge.dev engineering blog post. Dark near-black background, terminal frame mock on the left with a soft monospace code snippet hint. Monospace headline "Why we rewrote the scheduler in Rust" centered-right in warm white, small mono kicker "forge.dev / log · 12 min read" above it. forge.dev mono wordmark top-left in muted gray. No color accents. The top 110 px and bottom 110 px will be cropped off.
News · the daily ledger
Generate a 1200×630 Open Graph card for the daily ledger news & op-ed site. Tabloid newspaper grid on cream, dense serif type, large bold serif headline "After the noise: a quieter case for slow news" across two lines, dateline "May 30 · Op-ed" in mono above, byline rule with "By the daily ledger" below. Wordmark the daily ledger top-left in tall serif. Black ink only. The top 110 px and bottom 110 px will be cropped off.
Blog site Open Graph FAQ
How to generate cards for every post automatically, when to switch presets, and what works with each platform.
Do Substack and Beehiiv even let me set a custom OG image?
Yes. Both platforms expose the og:image field per post — Substack via the post settings, Beehiiv via the per-post SEO panel. Generate the card in Oginify, paste the URL into that field, the unfurl uses your card on every channel instead of the platform default.
Can I generate cards for old posts in bulk?
Yes. Paste your sitemap.xml URL into Oginify's batch mode and the engine generates one card per entry. The output is a CSV of URL → og:image URL pairs you can pipe back into your CMS via its API.
What if I have 5,000 posts?
Batch generation handles that comfortably — it runs against the sitemap in chunks. The bottleneck is usually your CMS's update API, not Oginify. For very large archives, prioritize posts in your top 10% of organic traffic first; cards for those move the needle hardest.
Does it work with Mailchimp, ConvertKit, ButtondownStruct?
Newsletter platforms with hosted web archives (Substack, Beehiiv, Ghost, Buttondown) all work because the post has a public URL. Pure-email tools without a web archive don't have an OG image to set in the first place — there's nothing to share.
What's the right preset for my blog?
Editorial / lifestyle / personal essay → magazine. News / op-ed / political → newspaper. Engineering / technical / developer-audience → terminal. Mixed → magazine as default, switch presets per-post for posts that want a different voice.
Stop shipping posts without a card
Paste any post URL and get a per-post 1200×630 Open Graph card in seconds. No CMS plugin, no signup.