Open Graph metadata isn't a direct Google ranking factor, but it can influence how your pages appear when shared. Google may also use certain Open Graph properties when generating search appearance elements, so saying it ignores these tags entirely goes too far.
We recommend treating Open Graph as presentation metadata, rather than a shortcut to higher rankings. First, let's separate its role in search from its main job: helping shared links look clear and useful.
Key Takeaways
- Open Graph tags control social link previews. Adding them doesn't directly improve Google rankings.
- Google can use some Open Graph information for search presentation, including title links.
- Four properties form the protocol's required foundation:
og:title,og:type,og:image, andog:url. - Reliable implementation means publishing accurate tags, accessible images, and refreshed previews after changes.
How Open Graph Metadata Relates to Google Search
The practical answer needs one distinction: ranking and presentation are different outcomes. A page can look different in search without moving to a higher position.
Search appearance isn’t a ranking boost
Google can consider og:title among the sources it uses to generate a search result's title link. It can also consider og:site_name when determining a site's name.
Those uses don't make Open Graph a general ranking signal. Adding keywords to every OG property won't make a weak page more relevant or useful.
Google's video SEO documentation also identifies Open Graph as a source of video information. The accurate takeaway is that Google can use OG data for particular purposes, without rewarding its presence with better rankings.
Social discovery can create indirect benefits
Social media discovery can introduce your content to customers, journalists, or publishers who might reference it.
Those opportunities depend on what people do next. A social share doesn't automatically create a valuable backlink or a ranking improvement.
Our guide to how social media supports SEO explains this relationship. Measure social media referral traffic separately from organic search performance.
What Open Graph Tags Control
Facebook introduced Open Graph in 2010 to standardize the information websites provide with shared links. The Open Graph protocol helps platforms identify a page's title, content type, image, and preferred URL.
Think of it as instructions for a link preview. Without those instructions, a platform may pull a headline, image, or description from elsewhere on the page.

Open Graph tags are HTML meta tags that belong in the document's head. They use meta elements with property and content attributes.
For example, <meta property="og:type" content="article"> identifies an article. The property names the field; the content supplies its value.
Google's social discovery guidance describes Open Graph's role in supplying titles, descriptions, and images for Facebook sharing. Other platforms also consume these properties, although their layouts differ.
The Required and Recommended Open Graph Properties
The protocol identifies four required properties. Add a description and image details to support them.
Use this table to separate the foundation from useful supporting fields.
| Property | Status | What to provide |
|---|---|---|
og:title | Required | A clear, page-specific title |
og:type | Required | The appropriate content type |
og:image | Required | An absolute, publicly accessible image URL |
og:url | Required | The object's preferred permanent URL |
og:description | Recommended | A short, useful page summary |
og:site_name | Optional | Your consistent website name |
og:locale | Optional | The page's primary language and territory |
og:image:alt | Recommended | A description of the image |
og:image:width | Recommended | Image width in pixels |
og:image:height | Recommended | Image height in pixels |
The og:description property provides a concise summary for the shared card. Use og:locale to identify the page's primary language and territory, such as en_US.
Start with the four essentials, then add fields that improve clarity and image handling.
For most blog posts, use article. Homepages usually use website. The protocol also supports profile, book, and specific video and music types, such as video.movie and music.song.
The og:url property establishes the object's canonical identity for social sharing. It doesn't replace Google's separate rel="canonical" link element.
Facebook generally displays the domain rather than the complete URL. Even so, the underlying URL matters when tracking parameters or duplicate addresses could split the same content into separate social objects.
How Long Should Titles and Descriptions Be?
Character recommendations are useful starting points, but they aren't reliable promises about what every person will see. Available space changes across platforms, devices, and preview layouts.
Keep the title’s main message near the front
IONOS lists a Facebook title allowance of a 95-character allowance, with a line break around the 50-character mark. FTDigital gives a 100-character guideline.
We wouldn't treat either number as a guaranteed display limit. Write a complete, useful opening phrase so the preview remains understandable if the ending disappears.
Your social title can differ from your HTML title tag, but both should describe the same page. Our beginner's guide to title tags covers the search-focused version.
Write descriptions for readers, not available space
IONOS cites roughly 300 characters for Facebook descriptions and recommends staying within 200 characters. FTDigital also recommends around 200.
We recommend a short summary that explains the page's value without repeating the title. Put the useful detail first, since some previews omit descriptions entirely.
Avoid keyword lists and promises the page doesn't deliver. Clear wording gives people a better reason to click than extra characters do.
Choosing Open Graph Image Dimensions
For a general-purpose sharing image, 1200 x 630 pixels is a practical starting point. It provides a wide format close to the commonly used 1.91:1 ratio.
IONOS recommends 1200 x 627 pixels, while FTDigital recommends 1200 x 628. Those small differences don't justify maintaining separate images. The image's content, accessibility, and crop matter more.

A suitable wide image can appear above Facebook's title and description as a large preview image. Keep important subjects away from the edges because other layouts may crop differently.
Add og:image:width and og:image:height with the file's actual pixel dimensions. These properties help platforms understand the image before processing it.
The optional og:image:secure_url supplies an HTTPS alternative. If og:image already uses HTTPS, a second URL is usually unnecessary.
Use a crawlable JPEG or PNG for broad compatibility. Avoid images behind logins, blocked URLs, or files that return an error instead of an image.
Adding Open Graph Tags Without Duplicate Output
We recommend choosing one place to manage social metadata. Multiple plugins, theme settings, and custom snippets can produce conflicting tags.
Manual HTML and JavaScript frameworks
A title tag follows this pattern: <meta property="og:title" content="Does Open Graph Metadata Affect Google Search Rankings?">.
Add the remaining properties as separate meta elements inside head. Use the page's real preferred URL for og:url and its public sharing-image address for og:image.
For a JavaScript application, include page-specific tags in the initial HTML response through server rendering or prerendering. Many social crawlers don't execute client-side JavaScript.
Changing the browser's document head after loading may look correct to you while leaving a crawler with generic homepage metadata.
WordPress and Shopify
Yoast SEO, All in One SEO, and Rank Math can generate Open Graph tags from WordPress titles, descriptions, and featured images. Their social settings also allow page-specific overrides.
Shopify themes commonly include social metadata by default, although customized themes can change that output. Inspect the published source before adding another implementation.
For WordPress owners who also need hosting, ZADiC's WordPress hosting includes backups and SSL. We recommend those practical safeguards alongside regular site maintenance.
Hosting doesn't replace social metadata configuration. Your theme or SEO plugin still needs to publish the right values for each page.
How Facebook, LinkedIn, X, and WhatsApp Differ
The same page can produce different previews without having broken metadata. Each platform chooses its own layout and caches information independently.
Here's what to expect when sharing one article across these platforms.
| Platform | Main consideration |
|---|---|
| Uses OG properties, with layout depending on available metadata and image suitability | |
| Reads OG information, but may crop images or shorten text differently | |
| X | Supports Twitter Cards and fallback to corresponding OG fields |
| Uses link metadata, but preview display varies by app context |
Consistent inputs improve presentation, but they don't force identical cards.
Twitter introduced Twitter Cards in 2012. X can fall back to supported Open Graph fields for titles, descriptions, and images when corresponding Twitter fields are missing.
We recommend adding twitter:card with summary_large_image when you want that card format. Place Twitter Card tags below Open Graph tags as an organizational convention, not a technical requirement.
Keep both systems. Twitter Card tags don't replace the OG properties other platforms expect.
Testing Tags and Refreshing Cached Previews
A saved CMS setting doesn't prove that the published page contains the right tags. Start with the response a crawler receives, then review the platform's preview.

Inspect the live page first
Open the published page's source and search for og:. Confirm that the values describe that page rather than another post or the homepage.
Next, open the og:image address directly. It should load publicly over HTTPS without authentication. Check for duplicate properties, incorrect dimensions, redirect problems, and crawler-blocking security rules.
Use Facebook Sharing Debugger to inspect the fetched tags, warnings, and rendered preview. LinkedIn's Post Inspector provides a similar platform-specific check.
X's former visual card preview tool is no longer available in its original form. Use a test post to assess the rendered card.
Clear caches in the right order
After editing metadata, refresh the information in this order:
- Publish the updated page and image, then clear the relevant website and CDN caches.
- Inspect the public source again to confirm the updated values are being served.
- Use Facebook Sharing Debugger's "Scrape Again" option and refresh LinkedIn through Post Inspector.
- Create a new share to assess the result, since existing posts may retain older presentation.
A missing fb:app_id warning can generally be ignored for ordinary link previews. An application ID isn't required simply to display your article's title and image.
A successful refresh on Facebook doesn't refresh LinkedIn, X, or WhatsApp. Each platform maintains its own cached information.
Keep Schema and SEO Measurement Separate
Open Graph, schema markup, and search metadata have different jobs. Treating them as interchangeable makes troubleshooting harder. Open Graph tags shape shared cards, but they don't replace the HTML title tag or search-facing meta description. Keep both accurate and consistent with the page.
Google-supported structured data can make a page eligible for rich results. Open Graph tags don't replace that markup. Google's structured data introduction explains how machine-readable information supports search understanding and presentation.
For articles, Google's Article markup guidance covers search-specific information beyond setting og:type to article.
We prefer JSON-LD for schema implementation. Mark up content visitors can actually see, and keep names, prices, availability, and other facts accurate.
The Schema Markup Validator checks schema validity. Google's Rich Results Test checks supported feature eligibility. Neither guarantees indexing or enhanced display.
For measurement, separate social referral traffic in GA4 from organic performance in Search Console. More social clicks after an image change don't prove a Google ranking improvement.
If organic visibility is the problem, investigate indexing, search intent, content quality, and internal links first. Our on-page SEO guide covers those page-level priorities.
Frequently Asked Questions
What happens when a page has no Open Graph tags?
A social platform may infer the title, description, and image from other page elements. That can produce an acceptable preview, but it can also select an unrelated image or navigation text.
We recommend explicit metadata for important pages rather than leaving those choices to automated extraction.
How can the Open Graph image of a website be found?
View the page source and search for og:image. Its content attribute contains the image address.
Open that address to inspect the file itself, then use a platform debugger to see how the platform processes it. A browser-loaded image can still fail for a crawler if access rules differ.
Does valid metadata mean a page is indexed?
No. Social preview validation and Google indexing are separate checks.
Use Search Console's URL Inspection tool and indexing reports when a page is missing from search. Correct OG tags won't resolve an accidental noindex instruction, blocked access, or Google's selection of another canonical URL.
Give Open Graph a Clear Job
Open Graph metadata deserves attention because shared links should accurately represent your content. Its strongest benefit is clear, consistent presentation, rather than a direct ranking advantage.
We recommend publishing one accurate set of tags and testing the public result after meaningful changes. Keep your broader SEO effort focused on accessible pages, useful content, and the needs behind each search.





