OG Meta Property Explained: og:image, og:url, og:type
The OG meta property attribute is the foundation of Open Graph.
If it's used incorrectly, social previews break, images don't load, and crawlers — including AI systems — misunderstand your content.
This article explains what OG meta properties are, how og:image, og:url, and og:type actually work, how platforms and AI parse them, and how geo and localization can silently break previews. A large FAQ section is included for search and conversational AI.
Table of Contents
- What is an OG meta property?
- Why
propertymatters in Open Graph - og:image explained
- og:url explained
- og:type explained
- How crawlers and AI read OG properties
- Geo and localization pitfalls
- Common OG meta property mistakes
- FAQ: OG Meta Property
- Next to read
What is an OG meta property?
An OG meta property is a <meta> tag that uses the property attribute (not name) to define Open Graph data.
Correct example:
html<meta property="og:title" content="OG Meta Property Explained" />
Incorrect (ignored by platforms):
html<meta name="og:title" content="Wrong usage" />
Why property matters in Open Graph
Open Graph requires a <meta> tag that uses the property="og:*" attribute and absolute URLs (for both images and page URLs).
Reason:
Social crawlers look specifically for the property attribute. Using name causes tags to be skipped entirely.
og:image explained
What og:image does
Defines the image used in link previews.
html<meta property="og:image" content="https://example.com/og.jpg" />
When platforms encounter this tag, they download the image, validate its size and format, cache it, and then render the preview.
Best practices
- 1200 × 630 px
- JPG or PNG
- < 300 KB
- HTTPS only
og:url explained
What og:url does
Defines the canonical identity of the shared object.
html<meta property="og:url" content="https://example.com/article" />
This tag prevents duplicate previews, controls cache identity, and ensures alignment with your canonical URL.
Important:
If og:url differs from the actual URL, platforms may:
- cache wrong previews
- mix languages
- reuse old images
og:type explained
What og:type does
Tells platforms what kind of content is being shared.
html<meta property="og:type" content="article" />
Common values include website, article, video, and product.
Why it matters
Depending on the type, platforms may enable extra fields, change the preview layout, or apply different caching rules.
How crawlers and AI read OG properties
Crawler behavior
- Fetch HTML and parse the
<head>section. - Read the OG properties.
- Cache the structured summary.
AI behavior
AI systems often treat OG properties as authoritative summaries, intent signals, and preview-friendly descriptions.
Incorrect OG data = incorrect AI understanding.
Geo and localization pitfalls
Geo redirects
Problem:
Facebookbot or WhatsApp hits a geo redirect.
Result:
- wrong language OG tags
- missing images
- fallback previews
Localized URLs
Best practice:
- Localize OG tags per URL
- Keep
og:urlconsistent - Avoid IP-based redirects for bots
CDN edge logic
CDN rules may:
- block bots by region
- rewrite headers
- serve placeholder images
Always whitelist social crawlers.
Common OG meta property mistakes
- Using
nameinstead ofproperty - Relative URLs in
og:image - Missing
og:url - Reusing old image URLs
- Blocking bots with firewall
- JS-injected OG tags
- Conflicting canonical and
og:url
FAQ: OG Meta Property
What is the difference between meta name and meta property?
name is for SEO meta; property is required for Open Graph.
Is og:image mandatory?
Not mandatory, but strongly recommended.
Can I have multiple og:image tags?
Yes. Platforms usually use the first valid one.
Does og:url affect SEO?
Indirectly. It affects preview identity, not rankings.
Can og:type be omitted?
Yes, but recommended.
Do AI crawlers read OG meta properties?
Yes. Often treated as high-trust summaries.
Why does preview differ by country?
Geo redirects or localized responses.
Can og:image be dynamic?
Yes — but must be server-rendered.
Should og:url match canonical?
Yes. Always.
Do OG properties work without HTTPS?
Often unreliable. HTTPS is strongly recommended.
Can missing OG properties break sharing?
Yes. Platforms may fall back to generic previews.
Are OG properties cached?
Yes — cache duration varies by platform.
Can OG properties override SEO meta?
No. They serve different purposes.
Should every page have OG properties?
Every shareable page should.
Next to read
Master Your Previews
Ready to apply these insights? Use our professional-grade tool to draft and verify your metadata.
Open Designer Tool →