Starry night sky over mountains

Open Graph Image Size: Correct Dimensions for Every Platform

Open Graph Image Size: Correct Dimensions for Every Platform

Open Graph Image Size: Correct Dimensions for Every Platform

Open Graph image size explained: exact pixel dimensions, file limits and safe text zones for every platform. See how to stop previews breaking.

Open Graph image size explained: exact pixel dimensions, file limits and safe text zones for every platform. See how to stop previews breaking.

12 min read

A bright blank square of projector light clipped by an open doorway onto the far wall of a dark office corridor, with the words "Only The Middle Survives" set on it

A founder pastes the new case study link into a prospect's Slack channel. Grey box. No image, no title, just a bare URL sitting there looking like spam. The file was exported at 1200 x 630, the number every guide quotes, so the open graph image size was never the problem: the file was 2.4 MB, served from a path the crawler could not reach, and the preview had already been cached from a draft version three weeks earlier.

That is the pattern. Dimensions are the easy half. The failures we see on live client sites are almost always weight, URLs, duplicate tags or cache, and no amount of pixel-perfect exporting fixes those.

The one Open Graph image size that works everywhere

Use 1200 x 630 pixels, a ratio of roughly 1.91:1, as your single default file. Facebook's own sharing documentation recommends at least 1200 x 630 for high-resolution displays, and because Facebook got there first, nearly everything else fell in behind it: LinkedIn, Slack, WhatsApp, Discord and most CMS social fields all expect something in that shape.

One file. One ratio. Everything else is a special case you add later, not a reason to export five versions of every post.

The thresholds that downgrade your card

Two floors matter. Drop below 600 x 315 and Facebook renders a small thumbnail instead of a full-width card. Drop below 200 x 200 and platforms may skip the image entirely, which is exactly why a logo exported at 400 x 400 and labelled "social image"shows up as a postage stamp next to grey text. The 600 x 315 file is not "half as good"as the 1200 x 630 one: it is a different, worse unit in the feed, and in a LinkedIn timeline that difference is the whole click.

Format: JPEG, PNG, and why we leave WebP alone

Photographic or illustrative backgrounds go out as JPEG, quality around 80, because the weight saving is large and nobody can see the difference at feed size. Flat brand graphics with large type, solid colour fields and a logo go out as PNG, where crisp edges matter and JPEG artefacts around letterforms look cheap.

WebP is smaller and renders fine in browsers. Support across scrapers and chat clients has been uneven, and an og:image is not the place to find out which client in your prospect's company is the exception. Serve WebP to browsers if you like. Point og:image at a JPEG or a PNG.

Exporting at 2x

Export the same artwork at 2400 x 1260 and the ratio is unchanged, but the card holds up on retina screens where a 1200px file can look soft. Watch the weight. A 2400px PNG full of type can sail past 2 MB, at which point you have traded a sharp card for no card at all. Compress, check, and if it will not come down, drop back to 1200 x 630.

How each platform crops, compresses and caches your file

Every platform takes your single file and does something slightly different to it. Knowing what, in each case, is what stops you designing for a canvas nobody actually sees.

Facebook and Messenger

A 1.91:1 file at 1200 x 630 or larger gets the large link card. Facebook's documentation puts the maximum image file size at 8 MB at the time of writing, which sounds generous until you remember WhatsApp and LinkedIn are far stricter. Facebook also caches scrapes hard: once it has seen your URL, it keeps that version until something forces a re-scrape. The Sharing Debugger is the tool that forces it.

LinkedIn

LinkedIn's published guidance recommends 1200 x 627 with a file size cap of 5 MB. In practice a 1200 x 630 file works fine. What catches people out is placement: the main feed shows a wide card, but notifications, the right-hand rail and some mobile surfaces reduce it to something much closer to square, so a headline that runs edge to edge loses its first and last words. LinkedIn's Post Inspector is the only reliable way to re-scrape a URL it has already cached.

X (formerly Twitter)

Two card types matter. Summary_large_image gives the wide card, and X's card documentation specifies a 2:1 ratio with images under 5 MB and at least 300 x 157 pixels. Pla gives a small square thumbnail beside the text. Because 2:1 is slightly wider than 1.91:1, your 1200 x 630 file gets a thin slice trimmed off the top and bottom. Trivial, unless your logo is pinned to the very bottom edge.

WhatsApp, Slack, iMessage and Discord

This is where the wide card stops being a wide card. Slack and WhatsApp frequently unfurl a link as a compact row with a small square thumbnail on one side. A centred square crop of a 1200 x 630 canvas keeps only the middle 630 pixels: roughly 52 per cent of your artwork survives, and everything in the outer quarter on each side is gone. WhatsApp is also the fussiest about file weight, and heavy images tend to fall back to a tiny icon or nothing.

Pinterest and Instagram

Do not try to make one file serve these. Pinterest is vertical, around 2:3, and a 1.91:1 card pinned there looks like a mistake. Instagram does not unfurl link previews in the feed at all, so what you actually need is a separate square or 4:5 export built from the same template. Same brand, different canvas, produced in the same pass.

Designing inside the safe zone so nothing gets chopped

Design to the crop, not the canvas. That single habit prevents most of the embarrassment.

Keep roughly 10 per cent padding on all four sides of the 1200 x 630 canvas, so about 120 pixels left and right, 63 top and bottom, and centre the message. Then go further: assume a square crop of the middle, and check that the headline and logo still read inside it. If your logo lives in the bottom-left corner, it exists for Facebook and nobody else.

Type size is the other common miss. A card viewed on a phone often renders about 400 pixels wide, which is a third of your canvas, so 60px type on the artwork arrives at roughly 20px on screen. Set headlines at 54px to 72px minimum and write three or four short lines rather than one long sentence wrapped badly. The card is a signpost, not a paragraph.

Two more rules, learned the hard way. Never ship a transparent PNG as an og:image: transparency flattens to white or black depending on the client, and a dark logo on a dark feed background disappears. And test against both light and dark mode, because a near-white background with pale grey type looks clean in your design tool and invisible in a dark LinkedIn feed.

Finally, build the card from your real palette, logo and typeface. A link styled in your actual brand is recognisable before anyone reads the headline, and after a dozen posts the shape and colour do the recall work on their own. Generic stock photography and anonymous AI art do the opposite. That is why our article image styles generate blog headers, Open Graph cards and social crops from a client's own brand assets rather than from a prompt and a stock library.

The markup and CMS settings that make the image appear

The tags themselves are short. The Open Graph protocol specification is worth five minutes of your time if you have never read it. A working set looks like this: og:title, og:description, og:type, og:url, og:image, og:image:width, og:image:height and og:image:alt. Width and height are not decoration: supplying them lets a platform lay out the card correctly on first scrape, before it has downloaded the file.

Then the rules that break previews in the wild:

  • Absolute HTTPS URLs only. A relative path like /images/og.jpg is the single most common silent failure. Scrapers do not resolve it the way a browser does.

  • Publicly crawlable. Images behind a login, behind a staging password, behind a 301 chain or behind a CDN rule that blocks unknown user agents will not render. Bot-protection rules on image directories cause more blank cards than bad design ever has.

  • No query-string gymnastics that change the file on every request. Scrapers cache what they fetch.

For X, add twitter:card set to summary_large_image and twitter:title. You only need a separate twitter:image when you genuinely want different artwork, for example a true 2:1 crop or a version with the handle on it. Otherwise X falls back to og:image quite happily, and one file is one file to keep updated.

CMS specifics and the duplicate tag problem

Duplicate tags are a quiet killer. If Yoast or Rank Math is already outputting an og:image and your theme, a page builder or a pasted snippet in the header adds another, platforms pick one unpredictably, and the one they pick is usually not the one you designed. Before you add anything, view source on a published post and search for og:image. If it appears twice, fix the conflict first.

  • WordPress: set the social image in Yoast or Rank Math's social tab per post, and disable any theme-level Open Graph output rather than running both.

  • Webflow: the Open Graph fields sit in page settings, and on a CMS collection template you bind og:image to an image field so every item inherits its own card. A blank field means the template falls back, often to nothing.

  • Framer: site-wide defaults live in site settings, with per-page overrides; the default gets used far more often than people realise, so make the default something you are happy to see shared.

  • Squarespace: uses a thumbnail or the first image on the page unless you set a social sharing image explicitly, which is how a stray inline screenshot ends up representing your article on LinkedIn.

Testing, clearing the cache and fixing a preview that will not update

Two debuggers, plus one real-world check. Facebook's Sharing Debugger and LinkedIn's Post Inspector each show you what the scraper actually fetched, and both will force a re-scrape. Then paste the link into a private Slack channel and a WhatsApp message to yourself, because that is where the square-crop damage shows up and no debugger reports it.

If an old image keeps appearing after you have replaced it, the cache is the culprit, not your markup. Re-uploading a new file over the same filename will not clear it. Two fixes work: give the new image a new filename, or force a re-scrape in the Sharing Debugger and Post Inspector. On a post already circulating on LinkedIn, the existing shared posts keep the old card regardless; only new shares pick up the new one.

For a blank preview, work down this list in order:

  1. File size above the platform ceiling, or simply too heavy for WhatsApp.

  2. Relative instead of absolute URL.

  3. HTTP URL on an HTTPS page.

  4. Wrong or missing MIME type, usually a renamed file that is not really a JPEG.

  5. Crawler blocked by robots.txt, a firewall rule or CDN bot protection.

  6. Duplicate og:image tags fighting each other.

  7. Missing width and height, causing a layout fallback on first scrape.

All of this is fixable without touching the live URL, which matters: changing a published post's slug to force a fresh preview costs you whatever links and rankings it has already earned. Replace the image file, update the tag, re-scrape. Done.

A repeatable Open Graph spec for lean publishing teams

Write it down once and stop deciding per post. Ours fits on one page:

  • 1200 x 630 pixels, or 2400 x 1260 for retina, always 1.91:1.

  • Under 1 MB where possible, which keeps you inside every platform ceiling including WhatsApp's appetite.

  • JPEG for photographic, PNG for flat brand graphics with type. No transparency.

  • Headline and logo inside a central safe zone, readable in a square crop.

  • Alt text written as a real description, not the filename.

  • Filename convention that includes the slug, so cache-busting is just a version suffix.

Work template-first. One template, three exports: blog header, Open Graph card, social crop, produced in a single pass from the same brand assets. The alternative is a designer request at publish time, which is how posts go live with no card at all.

Better still, make the image part of the draft. In a research-first pipeline the card is built alongside the article, before anything is scheduled, so there is no gap between "the writing is ready"and "the preview is ready". That is how our publishing workflow handles it, and it is the same reason we treat images as editorial output rather than decoration, much as we do with the way we research and write each piece.

Then audit what you already have. Take ten published URLs, run each through the Sharing Debugger and the Post Inspector, and log the result in a spreadsheet: card renders, image correct, weight, any warnings. The faults repeat. Usually a cached old image, an og:image still served over HTTP from a pre-migration path, and one file well above the ceiling. Fix those three and most of your back catalogue starts sharing properly. If your images are also meant to earn traffic in their own right, measuring image performance in Search Console is the next step after the previews work.

Getting the open graph image size right is a ten-minute job. Getting the file weight, the absolute URL, the crawler access, the duplicate tags and the cache right is what makes the card actually appear, and that is the part worth building into your process rather than rediscovering every time a link lands in a grey box.

Frequently Asked Questions

What is the correct Open Graph image size in 2026?

1200 x 630 pixels at a 1.91:1 ratio remains the default that works across Facebook, LinkedIn, Slack and most messaging apps. Export at 2400 x 1260 if you want it sharp on retina screens, keeping the same ratio. Platform guidance does shift, so check the current Facebook and LinkedIn developer documentation before you rebuild a template.

Do I need a different Open Graph image for each platform?

No, one 1200 x 630 file covers the link-preview platforms. You do need separate exports for vertical formats such as Pinterest and for Instagram, since a 1.91:1 card is the wrong shape there. Build them from the same template in one pass rather than redesigning each time.

Why is my Open Graph image not showing when I share the link?

Usually one of five things: the file is too heavy, the URL is relative or still HTTP, the image path is blocked to crawlers, there are two competing og:image tags on the page, or the platform has cached an older scrape. Run the URL through the Facebook Sharing Debugger and LinkedIn Post Inspector, which will tell you what the scraper actually fetched.

What is the maximum file size for an og:image?

Facebook's sharing documentation sets 8 MB and LinkedIn's guidance sets 5 MB at the time of writing, with X's card documentation also specifying under 5 MB. Those are ceilings, not targets. Keep files under 1 MB and you stay comfortably inside every limit, including WhatsApp, which is the least tolerant of heavy images.

Should og:image and twitter:image be the same file?

In most cases yes, and X will fall back to og:image when twitter:image is absent. Use a separate twitter:image only when you want genuinely different artwork, such as a true 2:1 crop or a version carrying your handle. Two files means two files to keep in sync, so only split them when there is a reason.

A founder pastes the new case study link into a prospect's Slack channel. Grey box. No image, no title, just a bare URL sitting there looking like spam. The file was exported at 1200 x 630, the number every guide quotes, so the open graph image size was never the problem: the file was 2.4 MB, served from a path the crawler could not reach, and the preview had already been cached from a draft version three weeks earlier.

That is the pattern. Dimensions are the easy half. The failures we see on live client sites are almost always weight, URLs, duplicate tags or cache, and no amount of pixel-perfect exporting fixes those.

The one Open Graph image size that works everywhere

Use 1200 x 630 pixels, a ratio of roughly 1.91:1, as your single default file. Facebook's own sharing documentation recommends at least 1200 x 630 for high-resolution displays, and because Facebook got there first, nearly everything else fell in behind it: LinkedIn, Slack, WhatsApp, Discord and most CMS social fields all expect something in that shape.

One file. One ratio. Everything else is a special case you add later, not a reason to export five versions of every post.

The thresholds that downgrade your card

Two floors matter. Drop below 600 x 315 and Facebook renders a small thumbnail instead of a full-width card. Drop below 200 x 200 and platforms may skip the image entirely, which is exactly why a logo exported at 400 x 400 and labelled "social image"shows up as a postage stamp next to grey text. The 600 x 315 file is not "half as good"as the 1200 x 630 one: it is a different, worse unit in the feed, and in a LinkedIn timeline that difference is the whole click.

Format: JPEG, PNG, and why we leave WebP alone

Photographic or illustrative backgrounds go out as JPEG, quality around 80, because the weight saving is large and nobody can see the difference at feed size. Flat brand graphics with large type, solid colour fields and a logo go out as PNG, where crisp edges matter and JPEG artefacts around letterforms look cheap.

WebP is smaller and renders fine in browsers. Support across scrapers and chat clients has been uneven, and an og:image is not the place to find out which client in your prospect's company is the exception. Serve WebP to browsers if you like. Point og:image at a JPEG or a PNG.

Exporting at 2x

Export the same artwork at 2400 x 1260 and the ratio is unchanged, but the card holds up on retina screens where a 1200px file can look soft. Watch the weight. A 2400px PNG full of type can sail past 2 MB, at which point you have traded a sharp card for no card at all. Compress, check, and if it will not come down, drop back to 1200 x 630.

How each platform crops, compresses and caches your file

Every platform takes your single file and does something slightly different to it. Knowing what, in each case, is what stops you designing for a canvas nobody actually sees.

Facebook and Messenger

A 1.91:1 file at 1200 x 630 or larger gets the large link card. Facebook's documentation puts the maximum image file size at 8 MB at the time of writing, which sounds generous until you remember WhatsApp and LinkedIn are far stricter. Facebook also caches scrapes hard: once it has seen your URL, it keeps that version until something forces a re-scrape. The Sharing Debugger is the tool that forces it.

LinkedIn

LinkedIn's published guidance recommends 1200 x 627 with a file size cap of 5 MB. In practice a 1200 x 630 file works fine. What catches people out is placement: the main feed shows a wide card, but notifications, the right-hand rail and some mobile surfaces reduce it to something much closer to square, so a headline that runs edge to edge loses its first and last words. LinkedIn's Post Inspector is the only reliable way to re-scrape a URL it has already cached.

X (formerly Twitter)

Two card types matter. Summary_large_image gives the wide card, and X's card documentation specifies a 2:1 ratio with images under 5 MB and at least 300 x 157 pixels. Pla gives a small square thumbnail beside the text. Because 2:1 is slightly wider than 1.91:1, your 1200 x 630 file gets a thin slice trimmed off the top and bottom. Trivial, unless your logo is pinned to the very bottom edge.

WhatsApp, Slack, iMessage and Discord

This is where the wide card stops being a wide card. Slack and WhatsApp frequently unfurl a link as a compact row with a small square thumbnail on one side. A centred square crop of a 1200 x 630 canvas keeps only the middle 630 pixels: roughly 52 per cent of your artwork survives, and everything in the outer quarter on each side is gone. WhatsApp is also the fussiest about file weight, and heavy images tend to fall back to a tiny icon or nothing.

Pinterest and Instagram

Do not try to make one file serve these. Pinterest is vertical, around 2:3, and a 1.91:1 card pinned there looks like a mistake. Instagram does not unfurl link previews in the feed at all, so what you actually need is a separate square or 4:5 export built from the same template. Same brand, different canvas, produced in the same pass.

Designing inside the safe zone so nothing gets chopped

Design to the crop, not the canvas. That single habit prevents most of the embarrassment.

Keep roughly 10 per cent padding on all four sides of the 1200 x 630 canvas, so about 120 pixels left and right, 63 top and bottom, and centre the message. Then go further: assume a square crop of the middle, and check that the headline and logo still read inside it. If your logo lives in the bottom-left corner, it exists for Facebook and nobody else.

Type size is the other common miss. A card viewed on a phone often renders about 400 pixels wide, which is a third of your canvas, so 60px type on the artwork arrives at roughly 20px on screen. Set headlines at 54px to 72px minimum and write three or four short lines rather than one long sentence wrapped badly. The card is a signpost, not a paragraph.

Two more rules, learned the hard way. Never ship a transparent PNG as an og:image: transparency flattens to white or black depending on the client, and a dark logo on a dark feed background disappears. And test against both light and dark mode, because a near-white background with pale grey type looks clean in your design tool and invisible in a dark LinkedIn feed.

Finally, build the card from your real palette, logo and typeface. A link styled in your actual brand is recognisable before anyone reads the headline, and after a dozen posts the shape and colour do the recall work on their own. Generic stock photography and anonymous AI art do the opposite. That is why our article image styles generate blog headers, Open Graph cards and social crops from a client's own brand assets rather than from a prompt and a stock library.

The markup and CMS settings that make the image appear

The tags themselves are short. The Open Graph protocol specification is worth five minutes of your time if you have never read it. A working set looks like this: og:title, og:description, og:type, og:url, og:image, og:image:width, og:image:height and og:image:alt. Width and height are not decoration: supplying them lets a platform lay out the card correctly on first scrape, before it has downloaded the file.

Then the rules that break previews in the wild:

  • Absolute HTTPS URLs only. A relative path like /images/og.jpg is the single most common silent failure. Scrapers do not resolve it the way a browser does.

  • Publicly crawlable. Images behind a login, behind a staging password, behind a 301 chain or behind a CDN rule that blocks unknown user agents will not render. Bot-protection rules on image directories cause more blank cards than bad design ever has.

  • No query-string gymnastics that change the file on every request. Scrapers cache what they fetch.

For X, add twitter:card set to summary_large_image and twitter:title. You only need a separate twitter:image when you genuinely want different artwork, for example a true 2:1 crop or a version with the handle on it. Otherwise X falls back to og:image quite happily, and one file is one file to keep updated.

CMS specifics and the duplicate tag problem

Duplicate tags are a quiet killer. If Yoast or Rank Math is already outputting an og:image and your theme, a page builder or a pasted snippet in the header adds another, platforms pick one unpredictably, and the one they pick is usually not the one you designed. Before you add anything, view source on a published post and search for og:image. If it appears twice, fix the conflict first.

  • WordPress: set the social image in Yoast or Rank Math's social tab per post, and disable any theme-level Open Graph output rather than running both.

  • Webflow: the Open Graph fields sit in page settings, and on a CMS collection template you bind og:image to an image field so every item inherits its own card. A blank field means the template falls back, often to nothing.

  • Framer: site-wide defaults live in site settings, with per-page overrides; the default gets used far more often than people realise, so make the default something you are happy to see shared.

  • Squarespace: uses a thumbnail or the first image on the page unless you set a social sharing image explicitly, which is how a stray inline screenshot ends up representing your article on LinkedIn.

Testing, clearing the cache and fixing a preview that will not update

Two debuggers, plus one real-world check. Facebook's Sharing Debugger and LinkedIn's Post Inspector each show you what the scraper actually fetched, and both will force a re-scrape. Then paste the link into a private Slack channel and a WhatsApp message to yourself, because that is where the square-crop damage shows up and no debugger reports it.

If an old image keeps appearing after you have replaced it, the cache is the culprit, not your markup. Re-uploading a new file over the same filename will not clear it. Two fixes work: give the new image a new filename, or force a re-scrape in the Sharing Debugger and Post Inspector. On a post already circulating on LinkedIn, the existing shared posts keep the old card regardless; only new shares pick up the new one.

For a blank preview, work down this list in order:

  1. File size above the platform ceiling, or simply too heavy for WhatsApp.

  2. Relative instead of absolute URL.

  3. HTTP URL on an HTTPS page.

  4. Wrong or missing MIME type, usually a renamed file that is not really a JPEG.

  5. Crawler blocked by robots.txt, a firewall rule or CDN bot protection.

  6. Duplicate og:image tags fighting each other.

  7. Missing width and height, causing a layout fallback on first scrape.

All of this is fixable without touching the live URL, which matters: changing a published post's slug to force a fresh preview costs you whatever links and rankings it has already earned. Replace the image file, update the tag, re-scrape. Done.

A repeatable Open Graph spec for lean publishing teams

Write it down once and stop deciding per post. Ours fits on one page:

  • 1200 x 630 pixels, or 2400 x 1260 for retina, always 1.91:1.

  • Under 1 MB where possible, which keeps you inside every platform ceiling including WhatsApp's appetite.

  • JPEG for photographic, PNG for flat brand graphics with type. No transparency.

  • Headline and logo inside a central safe zone, readable in a square crop.

  • Alt text written as a real description, not the filename.

  • Filename convention that includes the slug, so cache-busting is just a version suffix.

Work template-first. One template, three exports: blog header, Open Graph card, social crop, produced in a single pass from the same brand assets. The alternative is a designer request at publish time, which is how posts go live with no card at all.

Better still, make the image part of the draft. In a research-first pipeline the card is built alongside the article, before anything is scheduled, so there is no gap between "the writing is ready"and "the preview is ready". That is how our publishing workflow handles it, and it is the same reason we treat images as editorial output rather than decoration, much as we do with the way we research and write each piece.

Then audit what you already have. Take ten published URLs, run each through the Sharing Debugger and the Post Inspector, and log the result in a spreadsheet: card renders, image correct, weight, any warnings. The faults repeat. Usually a cached old image, an og:image still served over HTTP from a pre-migration path, and one file well above the ceiling. Fix those three and most of your back catalogue starts sharing properly. If your images are also meant to earn traffic in their own right, measuring image performance in Search Console is the next step after the previews work.

Getting the open graph image size right is a ten-minute job. Getting the file weight, the absolute URL, the crawler access, the duplicate tags and the cache right is what makes the card actually appear, and that is the part worth building into your process rather than rediscovering every time a link lands in a grey box.

Frequently Asked Questions

What is the correct Open Graph image size in 2026?

1200 x 630 pixels at a 1.91:1 ratio remains the default that works across Facebook, LinkedIn, Slack and most messaging apps. Export at 2400 x 1260 if you want it sharp on retina screens, keeping the same ratio. Platform guidance does shift, so check the current Facebook and LinkedIn developer documentation before you rebuild a template.

Do I need a different Open Graph image for each platform?

No, one 1200 x 630 file covers the link-preview platforms. You do need separate exports for vertical formats such as Pinterest and for Instagram, since a 1.91:1 card is the wrong shape there. Build them from the same template in one pass rather than redesigning each time.

Why is my Open Graph image not showing when I share the link?

Usually one of five things: the file is too heavy, the URL is relative or still HTTP, the image path is blocked to crawlers, there are two competing og:image tags on the page, or the platform has cached an older scrape. Run the URL through the Facebook Sharing Debugger and LinkedIn Post Inspector, which will tell you what the scraper actually fetched.

What is the maximum file size for an og:image?

Facebook's sharing documentation sets 8 MB and LinkedIn's guidance sets 5 MB at the time of writing, with X's card documentation also specifying under 5 MB. Those are ceilings, not targets. Keep files under 1 MB and you stay comfortably inside every limit, including WhatsApp, which is the least tolerant of heavy images.

Should og:image and twitter:image be the same file?

In most cases yes, and X will fall back to og:image when twitter:image is absent. Use a separate twitter:image only when you want genuinely different artwork, such as a true 2:1 crop or a version carrying your handle. Two files means two files to keep in sync, so only split them when there is a reason.

Start Your Free Seven-Day Trial

Try Awareness Marketing free for seven days and see the blogs and social posts it creates for your business. No card needed.

Enter your website and see the blogs and social posts Awareness Marketing would create for your business. Free, no account needed.

Enter your website and see the blogs and social posts Awareness Marketing would create for your business. Free, no account needed.

Start for Free

In-House vs Agency Content Marketing: The Real Costs

The 4 Search Intent Types in SEO (And What They Need)

Content Marketing Retainer Cost UK: What You Actually Get

How to Choose AI Blog Writing Software in the UK

Monthly SEO Content Packages: What's Actually Included

Open Graph Image Size: Correct Dimensions for Every Platform

Cost to Hire a Content Writer in the UK: Real Numbers

What Is an Automated SEO Content Platform?

AI Mode in Google Discover: What It Means for Your Small Business Blog Traffic

What Is Genuine Thought Leadership Content?

Google Core Update Recovery: a One-week Audit Plan for Small Business Blogs

Rank Tracking Made Easy: From Numbers to Next Article

AI Overviews Now Hit 40% of Searches: What UK SMEs Should Change in the Blog Plan

Search Console's Multimodal Filter: How to Prove Your Blog Images Earn Traffic

Why Track Keywords If Nothing Changes Afterwards?

AI Mode Data in Search Console: How to Read Your Generative AI Report in 15 Minutes

Tracking Mobile Rankings: Is Your Site Really Slipping?

How Competitor Keyword Tracking Finds Content Gaps

CMA Google Search Choice Screens: What SMEs Should Do

Does AI Content Rank? What the Data Shows

UK Marketing Budget Benchmarks (And What They Buy)

Content Marketing Platform: What Lean Teams Need

Google AI Content Guidelines: A Publisher's Checklist

AI Social Media Post Generator: 7 Real Limits

Copywriting vs Content Writing: Which Do You Need?

Unconfirmed Google Update September 2026: What to Check

Rank Tracking: What the Numbers Won't Tell You

Google Spam Update AI Content: 7 Real Triggers

Site Reputation Abuse: How to Audit Your Own Site

How Much Does a Website Cost UK? (Real Quotes)

SEO Content Writing Service: What to Ask Before You Buy

Google Core Update 2026: What to Do If You Dropped

Is AI Content Penalised by Google? What Gets Flagged