OG Image Automation
Every page you publish deserves its own Open Graph image. Set it up once and it happens automatically — forever.
What is an Open Graph image?
When someone shares a URL on Twitter, LinkedIn, Slack, iMessage, or Facebook, the platform fetches the page and reads its Open Graph meta tags to build a preview card. The og:image tag specifies the image that appears in that card. It is typically 1200×630 pixels.
Most sites either use the same static image for every page (which looks generic and unconvincing) or upload a custom image manually for important posts (which doesn't scale). OG image automation generates a unique, content-specific image for every page, automatically, the moment it's published.
Why it matters for SEO and social
Higher click-through rates
Posts with a relevant, article-specific image get significantly more clicks on social platforms than those with a generic site logo. The preview image is often the deciding factor between a click and a scroll-past.
Brand consistency at scale
Define your OG card design once — typography, colours, logo placement, layout. Every generated image is on-brand, whether you publish once a week or ten times a day.
No manual work per post
The automation fires on publish. By the time a reader shares the article, the OG image already exists and is cached on a CDN — no delay, no placeholder thumbnail.
Works for every page type
Blog posts, product pages, landing pages, documentation — any page that can fire a publish webhook or be accessed programmatically can have its OG image generated automatically.
How to set it up with SwarmGen
- 1
Design your OG card template
Create a 1200×630 template in SwarmGen. Add merge fields for the content that will change per page — typically {{title}}, {{author}}, {{category}}, and {{featured_image}}. The rest (background, logo, typography) is fixed in the template.
- 2
Set up a publish webhook in your CMS
Ghost, WordPress, Webflow, and most headless CMSes support publish webhooks. Configure yours to fire a POST request to your automation endpoint (Make, n8n, Zapier, or a serverless function) every time content is published.
- 3
Extract the page data and call SwarmGen
In your automation, extract the relevant fields from the webhook payload — title, featured image URL, author name — and POST them to the SwarmGen render API as merge field values.
- 4
Write the image URL back to the page
Once the render is complete (via webhook callback or polling), update the page's og_image field using your CMS API. SwarmGen delivers the image from a CDN, so load time is negligible.
The correct OG meta tags
Once SwarmGen has rendered the image, download it and upload it to your own web server or CDN — SwarmGen render URLs expire after 7 days and should never be used directly in meta tags. Use your own permanent URL in the <head>:
<meta property="og:title" content="Your page title" /> <meta property="og:description" content="Your page description" /> <meta property="og:image" content="https://yoursite.com/images/og/your-page-slug.png" /> <meta property="og:image:width" content="1200" /> <meta property="og:image:height" content="630" /> <meta property="og:url" content="https://yoursite.com/your-page" /> <meta property="og:type" content="article" /> <!-- Twitter / X card --> <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:image" content="https://yoursite.com/images/og/your-page-slug.png" />
CMS-specific guides
Automate your OG images today
Free account — 50 renders included. Set up in minutes.
Get started free