Opengraph
I used to think Open Graph tags were a ranking factor. They aren't. But ignoring them will cost you social traffic.
Start here
- Open Graph tags control social share previews but are not a Google ranking factor.
- Always set og:title, og:description, og:image, and og:url on pages that get shared.
- Test each platform's preview separately; Facebook and LinkedIn behave differently.
- Keep og:title aligned with the HTML <title> to avoid confusing users.
- Recheck og tags after redesigns or brand updates to keep previews accurate.
Plain-English take
Open Graph is a set of meta tags that tell social platforms how to display your page when someone shares a link. Facebook introduced it in 2010; LinkedIn, Pinterest and Twitter (with its own card system) later adopted variant support. The tags sit in the <head> of a page and use the og: prefix. The four essential ones are og:title, og:description, og:image and og:url. Get these right and your share preview shows your chosen headline, a descriptive snippet and your brand image. Get them wrong and the platform guesses — often badly. I have seen a site where the preview pulled the page's first <h1> as the title, which was "News" for a specific article. That article's click-through from social dropped 30% until they added a proper og:title. Note that Google Search does not use Open Graph for its search snippets; it uses its own structured data, meta descriptions and title tags. But if your traffic relies on social sharing, Open Graph is non-negotiable. It is a presentation layer, not a ranking factor, but presentation drives clicks. I usually set og:type to 'article' for blog posts and 'website' for other pages. The protocol is straightforward: about a dozen properties exist, but most pages only need those four. The og:url should match the [canonical URL](/canonical-url/) to avoid confusion. I treat Open Graph as part of [technical SEO](/technical-seo/) — a small effort that can have a large impact on social referral behaviour.
When it actually matters
Open Graph matters most when your organisation depends on social media referral traffic. E-commerce product pages, news articles, blog posts and landing pages for campaigns all benefit from correct previews. I prioritise og tags on pages that already receive shares, not every URL. A client's product page was receiving 200 shares per week on Facebook but the preview showed a generic site title and no image. After adding og:image (1200x630 pixels, under 5MB) and og:description (max 60 characters for Facebook's truncation limit), the click-through rate from those shares increased by 18%. That is a measurable impact from a few lines of HTML. The tags also matter for brand consistency: you want your logo to appear in every preview, not a random product photo. However, there are edge cases. If you generate pages [programmatically](/programmatic-seo/), you must ensure each page has its own og tags; a single set repeated across thousands of pages creates confusion. I have seen a site with 10,000 product pages all using the same home page og:image. Each preview looked identical, so users could not distinguish what was being shared. That is a missed opportunity. So when it matters, it really matters, but only for pages that get shared. I do not bother with og tags on admin pages, staging environments or utility pages. And I always test the preview using Facebook's Sharing Debugger before publishing. If you have a lot of pages with similar content, consider using [duplicate content](/duplicate-content/) guidelines to decide whether to differentiate og tags.
What I got wrong
My biggest mistake was assuming Open Graph was a ranking signal. It is not. Google has stated clearly that social metadata does not influence search results. I wasted hours optimising og tags for pages with zero social exposure, hoping for a ranking boost. I now focus on pages where social sharing is a real channel. Another error: I thought og:title had to match the HTML <title>. They can differ, but they should not contradict. I once set an og:title to "Free Guide" while the page title was "Complete Guide to Technical SEO". The preview said "Free Guide" but the search snippet said "Complete Guide...". Users who saw both were confused about which version to trust. I now keep them aligned. I also underestimated how different platforms render og:description. Facebook truncates after about 60 characters, LinkedIn shows up to 200. So a single description may work on one platform but cut off on another. I now test on each major platform separately. A third admission: I neglected the og:image aspect ratio. Facebook recommends 1.91:1, Twitter prefers 2:1. I used a square image once, and it was cropped awkwardly on Facebook, showing only a portion of the logo. That taught me to check the image dimensions in the debugger. Finally, I used to think og tags were a set-and-forget task. They are not. When you redesign a page, update the og tags. When you change your brand logo, update all og:image references. I now have a checklist item in every [SEO audit](/seo-audit/) for og tag accuracy. I also compare og data with [schema markup](/schema/) to ensure consistency across structured data and social metadata.
Next step
Quick answers
Do I need Open Graph tags on every page?
Only on pages that are shared socially. I add them to all public-facing content pages, but skip admin, login, and utility pages. The effort is minimal, so if you have a template system, it is easy to include dynamic tags across all pages. Focus on the four essential ones: title, description, image, url.
Does Open Graph affect Google Search rankings?
No. Google has confirmed that social metadata like Open Graph is not used as a ranking signal. However, improved social previews can lead to more clicks and shares, which may indirectly increase visibility and backlinks. But do not expect a direct ranking boost from og tags alone.
What size should og:image be?
Facebook recommends 1200x630 pixels with a 1.91:1 aspect ratio. Images smaller than 600x315 may be rejected or cropped. Keep file size under 5MB. Test using Facebook's Sharing Debugger to see how your image is cropped on different placements. Twitter prefers 2:1, so consider a compromise or use Twitter-specific cards.
Can Open Graph tags conflict with Twitter Cards?
Twitter Cards use their own meta tags (twitter:card, twitter:site, etc.) but they fall back to Open Graph tags if Twitter-specific tags are missing. I recommend implementing both sets to have full control on Twitter. If you use only og tags, Twitter will still generate a preview, but it may not use your preferred image size.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Open Graph Protocol — The canonical specification for all og tags and properties.
- Google Search Central — Confirms that social metadata like Open Graph is not a ranking factor.
- Meta for Developers — Official Facebook documentation on how og tags are consumed and best practices.
Notes from Callum Bennett.