Skip to content
50% OFF $299 $599
Lock in
§ 2.1.4 ARTICLE
Published VerifiedEvery 6 weeks Sources5 named Authored bySquareRank Team

SEO Panel · § 2.1.4 · How-to

Open Graph tags and the social sharing image on Squarespace

Squarespace auto-emits Open Graph tags2 on every page: og:title from Page Title, og:description from Page SEO Description, og:url from the page's canonical URL, og:type from the page kind. The one field you author manually is the Social Sharing Image (og:image) — uploaded at Settings > Marketing > Social Sharing (sitewide default) or Page Settings > Social Image (per page). The image must be 1200x630 pixels for clean previews on Facebook, LinkedIn, and Slack.

This leaf covers what Squarespace auto-emits, the Social Sharing Image field, the 1200x630 sizing rule, the Twitter Card overlap (Twitter falls back to Open Graph when its own tags are missing), validation in Meta's Sharing Debugger and LinkedIn Post Inspector, and the three gotchas that catch first-time owners.

What Open Graph is

Open Graph is a metadata protocol Facebook introduced in 2010 and now used across most major social platforms — Facebook, LinkedIn, Slack, Discord, iMessage, WhatsApp — for generating link previews. A page's Open Graph tags live in the HTML head as <meta property='og:*' content='...'> entries. The four required tags per the canonical spec: og:title, og:type, og:image, og:url. Squarespace auto-emits all four; you author the image.

The spec at ogp.me1 has not materially changed since 2014. Optional tags (og:description, og:site_name, og:locale, og:image:width, og:image:height) extend the basic four. Facebook's debugger and LinkedIn's Post Inspector both parse the spec strictly — missing required tags trigger warnings, malformed image URLs fail silently.

What Squarespace auto-emits without you doing anything

On every page, Squarespace renders og:title from Page Title (or Browser Tab Title fallback), og:description from Page SEO Description (or Site Description fallback), og:url from the page's canonical URL, og:type based on the page kind (article for blog posts, website for static pages), and og:site_name from Site Title. The auto-emitted layer is complete for everything except og:image — which uses the Social Sharing Image field you upload, falling back to the homepage default if empty.

HTML What Squarespace renders in the page head for Open Graph 
 <meta property="og:title" content="Coastal palettes for low-light rooms | Hollis Coastal Interiors"> <meta property="og:description" content="Five paint-and-fabric pairings we keep returning to..."> <meta property="og:url" content="https://yoursite.com/blog/coastal-palettes-low-light"> <meta property="og:type" content="article"> <meta property="og:site_name" content="Hollis Coastal Interiors"> <meta property="og:image" content="https://yoursite.com/s/coastal-palette-share.jpg">

The Social Sharing Image field, where it lives, what it controls

Two places set the Social Sharing Image. Settings > Marketing > Social Sharing sets the sitewide default — used on any page without a per-page override. Page Settings > Social Image sets a per-page override — used only on that page. The per-page override is the one that matters for blog posts (each post gets its own preview) and important landing pages. Leave the homepage Social Image as a sensible brand default, then override per-page for everything that has its own visual identity.

The platform's logic: if a page has its own Social Image, use it. If not, fall back to the homepage. If the homepage has none either, fall back to whatever logo image the template ships with — which is often not what you want. The first install task on any new Squarespace site is uploading a 1200x630 sitewide default at Settings → Marketing → Social Sharing.

The 1200x630 rule and why other dimensions break

1200 pixels wide by 630 pixels tall is the size every major social platform handles cleanly. Facebook displays the full image. LinkedIn displays the full image. Slack displays a thumbnail derived from it. Other dimensions get cropped, letterboxed, or downscaled in unpredictable ways. The aspect ratio is 1.91:1, which Facebook's documentation has named as the recommended ratio since 2014. Smaller images get upscaled and look blurry; larger images get downscaled and sometimes desaturate.

A practical workflow: design the share image at 1200x630, save as JPG (smaller file size) or PNG (sharper for text-heavy designs), upload directly to Squarespace's Social Image field. Avoid uploading the same image you use as the page's hero or featured image — those are usually cropped differently, and the social share frequently ends up showing the wrong part of the picture.

What the Open Graph install actually looks like

1200x630

the canonical aspect ratio every major social platform handles cleanly.

Open Graph · 2014
5 of 6

Open Graph tags Squarespace auto-emits — you only author og:image.

Squarespace Help · 2026
2 caches

to refresh after editing: Meta's Sharing Debugger and LinkedIn Post Inspector (independent).

Meta for Developers · 2026

Twitter Card overlap: when og: tags suffice

Twitter (X) has its own metadata protocol — Twitter Cards, using twitter:* tags. The good news: Twitter falls back to Open Graph tags when its own are missing. The og:title, og:description, and og:image you already authored work as Twitter Card content for most page types. For control over the card type (summary vs summary_large_image), you can author twitter:card explicitly via Code Injection — Squarespace does not auto-emit it on most templates.

The spec5 defines four card types: summary, summary_large_image, app, player. The default fallback from Open Graph produces "summary" with a small thumbnail. For the large-image card (the bigger preview most owners want), inject <meta name="twitter:card" content="summary_large_image"> in the page header via Code Injection.

Validating Open Graph in platform debuggers

Meta's Sharing Debugger (developers.facebook.com/tools/debug/) and LinkedIn's Post Inspector (linkedin.com/post-inspector/) are the two validators that catch most Open Graph issues. Paste the page URL, click Debug or Inspect, and the tool returns the parsed tags plus a rendered preview. The 'Scrape again' button on Facebook's debugger forces a cache refresh — necessary after editing tags, because Facebook caches previews for hours.

The LinkedIn cache is independent of Facebook's. Editing tags and re-debugging in Facebook does not refresh LinkedIn's cache. Run both debuggers separately. If a share still shows the wrong preview after both refreshes, check whether your CDN is caching the og:image URL with old content — Squarespace's CDN sometimes holds an old version when the same filename is re-uploaded.

Three Squarespace-specific gotchas

First: re-uploading an image with the same filename does not always refresh the og:image URL in the rendered HTML — Squarespace's CDN sometimes serves the old version. Upload with a new filename when in doubt. Second: blog posts inherit the homepage Social Image unless you set a per-post one, which produces 30+ blog posts all sharing with the same generic image. Third: og:image:width and og:image:height are not auto-emitted on most 7.1 templates, which can make previews load slightly slower as platforms infer dimensions.

A fourth pattern worth knowing: password-protected pages and member-area pages still emit Open Graph tags, but the page behind the share link asks for credentials when visited. Either keep social sharing disabled on those pages (most templates allow it via Page Settings > Advanced), or accept that the preview will work and the click-through experience will not.

Keep reading · § 2.1.4