Meta Property OG Reference: Title, URL, Description & Type

Q: Is og:keywords a real property?

No. There is no `og:keywords` and no `og:` equivalent of the old meta keywords tag. Put your effort into `og:title` and `og:description`; meta keywords have been ignored by Google for over a decade.

Q: Do I use property= or name= for Open Graph tags?

`property=`. Open Graph is an RDFa vocabulary, so ` ` is correct. Using `name=` for `og:` tags causes some validators to skip them. Twitter Card tags are the exception; they use `name=`.

Q: Which og tags are strictly required for a card to render?

In practice `og:title`, `og:type`, `og:image`, and `og:url`. Most platforms will assemble a card from those four; `og:description` and `og:site_name` improve it. Omitting `og:image` usually means a bare text card.

Q: Are article:* tags valid on a homepage?

No. They're only meaningful when `og:type` is `article`. On a `website`-type page they're ignored. Match the type to the page or the structured properties are wasted.

This is the lookup table to keep open while you wire up Open Graph tags: every og: property that platforms actually read, whether it's required, a concrete example value, and the gotcha that trips people up. It's deliberately a reference, not a tutorial. If you want the step-by-step build, see the Open Graph meta tags guide, and if you're brand new to the concept start with the beginner guide to meta OG tags.

Two things to know before the tables. First, every tag uses property= (not name=), which is how Open Graph differs from a normal <meta name="description">. Twitter Cards flip back to name=; that's covered in the Twitter Card implementation post. Second, the property namespace you're allowed to use is gated by og:type. Set og:type to article and the article:* properties below become valid; leave it as website and they're ignored. The full breakdown of that lives in og:type values explained.

Core properties (every page should have these)

| Property | Required | Example value | Notes | |---|---|---|---| | og:title | Yes | Open Graph Reference · SEOtest | Can differ from your <title>. Platforms truncate by pixel width, not a fixed character count; ~60–65 chars is a safe ceiling. | | og:type | Yes | website | Defaults to website if omitted. Determines which extra namespaces are valid. | | og:image | Yes | https://seotest.app/og.jpg | Must be an absolute HTTPS URL, publicly fetchable with no login or hotlink protection. | | og:url | Yes | https://seotest.app/blog/og | Should equal your canonical URL. Platforms dedupe and cache against this, not the shared link. | | og:description | Recommended | Every og:* property in one table. | Roughly 2–4 sentences. Facebook shows ~110 chars on mobile before truncating. | | og:site_name | Recommended | SEOtest.app | Slack and Discord render this as the attribution line above the card. | | og:locale | Optional | en_US | Format is language_TERRITORY with an underscore (en_US, not en-US). | | og:locale:alternate | Optional | fr_FR | Repeat the tag once per additional locale you serve. | | og:determiner | Optional | auto | The word before the title in some renderings (a, an, the, "", auto). Rarely used. |

Image sub-properties (the ones that fix broken previews)

og:image is a structured object, so these sub-tags must appear after the og:image they describe.

| Property | Required | Example value | Notes | |---|---|---|---| | og:image:width | Strongly recommended | 1200 | Without width/height, Facebook and LinkedIn often render nothing on the first scrape until they've fetched the file once. | | og:image:height | Strongly recommended | 630 | Pair with width. Declaring both lets platforms reserve the large-card layout immediately. | | og:image:alt | Recommended | Diagram of og properties | Accessibility text; Discord and some readers surface it. | | og:image:type | Optional | image/jpeg | MIME type hint. Lets a scraper skip a probe request. | | og:image:secure_url | Optional | https://seotest.app/og.jpg | Legacy HTTPS variant. If og:image is already HTTPS, this is redundant. |

You can supply multiple og:image blocks; most platforms pick the first valid one, Facebook may let users choose. Sizing rules (1.91:1, file-size ceilings per platform, format support) are their own topic. See OG image size & format best practices.

article:* (valid only when og:type = article)

| Property | Example value | Notes | |---|---|---| | article:published_time | 2026-06-17T09:00:00Z | ISO 8601. Drives the timestamp some platforms show. | | article:modified_time | 2026-06-18T11:00:00Z | ISO 8601. | | article:expiration_time | 2026-12-31T00:00:00Z | For time-bound content. | | article:author | https://seotest.app/team | A profile URL, not a plain name. Repeatable. | | article:section | Technical SEO | Top-level category, one value. | | article:tag | open graph | Repeat the tag once per keyword/tag. |

profile:* (og:type = profile)

| Property | Example value | |---|---| | profile:first_name | Ada | | profile:last_name | Lovelace | | profile:username | ada | | profile:gender | female |

video:* and audio:* (rich media)

These attach playable media. og:video/og:audio is the URL; the sub-properties describe it. Most feed scrapers fall back to og:image for the thumbnail regardless.

| Property | Example value | Notes | |---|---|---| | og:video | https://seotest.app/clip.mp4 | Absolute HTTPS. | | og:video:secure_url | https://seotest.app/clip.mp4 | Required by some platforms if og:video was HTTP. | | og:video:type | video/mp4 | MIME type. | | og:video:width / og:video:height | 1280 / 720 | Player dimensions. | | og:audio | https://seotest.app/ep.mp3 | Absolute HTTPS. | | og:audio:type | audio/mpeg | MIME type. |

A complete, valid head block

<meta property="og:type"        content="article">
<meta property="og:title"       content="Open Graph Reference">
<meta property="og:description" content="Every og:* property in one table.">
<meta property="og:url"         content="https://seotest.app/blog/meta-property-og-reference">
<meta property="og:site_name"   content="SEOtest.app">
<meta property="og:locale"      content="en_US">
<meta property="og:image"       content="https://seotest.app/og/reference.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt"   content="A table of Open Graph properties">
<meta property="article:published_time" content="2026-06-17T09:00:00Z">
<meta property="article:section" content="Technical SEO">
<meta property="article:tag"     content="open graph">

To confirm a live page exposes these exactly as a scraper sees them, including catching tags injected client-side that crawlers never read, paste the URL into our OG Checker. To draft titles and descriptions that fit before you ship, the Meta Generator gives you a live preview.

Frequently Asked Questions

Is og:keywords a real property?

No. There is no og:keywords and no og: equivalent of the old meta keywords tag. Put your effort into og:title and og:description; meta keywords have been ignored by Google for over a decade.

Do I use property= or name= for Open Graph tags?

property=. Open Graph is an RDFa vocabulary, so <meta property="og:title" ...> is correct. Using name= for og: tags causes some validators to skip them. Twitter Card tags are the exception; they use name=.

Which og tags are strictly required for a card to render?

In practice og:title, og:type, og:image, and og:url. Most platforms will assemble a card from those four; og:description and og:site_name improve it. Omitting og:image usually means a bare text card.

Why declare og:image:width and og:image:height if the image already has dimensions?

Because on the first scrape the platform hasn't downloaded the image yet. Declaring the dimensions in the tags lets Facebook and LinkedIn render the large card immediately instead of showing nothing until a later re-crawl, which matters most at launch.

Are article:* tags valid on a homepage?

No. They're only meaningful when og:type is article. On a website-type page they're ignored. Match the type to the page or the structured properties are wasted.

Technical Reference: Optimizing Meta Property OG Tags