The og:type meta tag is the easiest Open Graph field to get wrong, because omitting it breaks nothing loudly — it quietly downgrades your share card instead. Set it correctly and Facebook shows article author and publish date; leave the default and a blog post renders as a generic website card. Here's what the tag does, every valid value, and which platforms actually bother reading it.
Short version: og:type tells platforms what kind of page you're sharing — article, website, video, product, or music. Most sites never touch it, which is usually the mistake, because the spec default (website) is wrong for most content pages.
What og:type Actually Does
The Open Graph protocol defines og:type as the "type of your object." It's a namespace + object pair: website, article, video.movie, music.song, and so on. When the tag is missing entirely, the spec says platforms must treat the page as website — which is exactly why so many previews look generic even though the og:title and og:image are fine.
The type also unlocks secondary tags. Set article and platforms will look for article:published_time, article:author, and article:section. Set product and they expect product:price:amount. Declare the type and you opt into that object's full schema; skip it and the platform falls back to plain website behavior.
Which Platforms Actually Read og:type
This is where most guides mislead you. "og:type is essential" gets repeated everywhere, but the reality from running this site's link-preview series across 14 platforms is that only three social networks read it, and chat apps ignore it entirely:
| Platform | Reads og:type? | What it changes |
|---|---|---|
| Yes | Article layout with author, date, reading time | |
| Yes | Article treatment over generic link card | |
| Yes, required | Rich pins need og:type (article or product) | |
| X (Twitter) | No | Uses twitter:card; og:type is not consulted |
| WhatsApp / Telegram | No | Title, description, image only |
| Signal / LINE / Discord / Slack | No | Title, description, image only |
Pinterest is the strictest of the bunch — its developer docs list og:type among the required tags for rich pins, and product pins won't show price without og:type=product. Facebook is the most visible: an article share renders with the headline, author, and publish time, which measurably changes how a link looks in a feed. For everyone else, og:type is decoration.
The Full List of og:type Values
The official spec (ogp.me) defines these namespaces; namespace.object pairs are the format:
- website — the default when og:type is absent; fine for homepages and tool pages
- article — blog posts, news; enables article:published_time, article:author, article:tag
- book — book pages, optionally with book:author and book:isbn
- profile — person pages; enables profile:first_name, profile:last_name
- music.song / music.album / music.playlist / music.radio_station — audio content with duration and musician tags
- video.movie / video.episode / video.tv_show / video.other — video content, paired with og:video
- product — e-commerce pages; enables product:price:amount, product:availability
Real talk: 99% of sites only ever need two values — website for static pages and article for posts. If you run an online store, add product on product pages. The music and video namespaces matter only if the page itself is the media, not when it merely embeds a YouTube clip.
How to Check and Fix Your og:type
Paste your URL into the OG checker and look at the og:type row. A tip right in the tool spells out the usual values: "website" or "article". The most common failure I see in checked pages is a blog running og:type=website everywhere, killing the article layout on Facebook and rich pins on Pinterest.
The fix in code is one line. On Next.js metadata:
export const metadata: Metadata = {
openGraph: {
type: "article",
publishedTime: "2026-09-03",
},
}On plain HTML, mirror the og:type to each page's tags — article for posts, website for the rest. Then re-scrape with Facebook's Sharing Debugger if the old card cached. If og:type is missing from your checker output entirely, add the tag before regenerating the image, because the preview and the tag should ship together. Full tag-by-tag examples live in the Open Graph meta tags reference.
Summary
og:type declares your page's object type and quietly unlocks richer cards on the three platforms that care: Facebook, LinkedIn, and Pinterest. The default value of website is safe for homepages but wrong for blog posts, so most content sites should ship article on article pages and pair it with article:published_time. Chat apps ignore the tag completely, which is why previews there stay broken-looking even after you fix it elsewhere — those need og:image fixes, not og:type.
Check your current og:type with the free OG checker — it takes five seconds and shows every tag your page actually emits. Then generate a matching 1200×630 card at ogimgen.com so the share image and the article layout upgrade together.