The og:title meta tag decides the headline on every link preview, and it's the first thing people read before they click. Get it right and your card reads clean in WhatsApp, X, and LinkedIn alike. Get it wrong and the preview shows your browser-tab title, a truncated mess, or — worst case — the raw URL. This guide covers what og:title actually does, why it is not the same as your <title> tag, and the fixes for the title problems that keep showing up when real pages get checked.
Short version: og:title is one of the four required Open Graph tags, and every major platform reads it. When the tag is missing, scrapers fall back to your HTML title tag — which works, but leaves your card at the mercy of a string written for search engines, not for humans.
What og:title Actually Does
The Open Graph spec lists og:title as a required property on every page. In practice it drives the big headline line of your share card: the bold text under the site name on Facebook, the first line of a WhatsApp preview, the link header in Slack. From the link-preview series this site ran across 14 platforms, og:title is the single most consistently read tag — nothing ignores it the way several platforms ignore og:type or og:description.
Everything else on the card hangs off that line. og:site_name fills the small text above it, og:description sits below, og:image is the visual. But og:title is the field people actually read to decide whether to click, and it is the one most pages get wrong because nobody looks at their own card.
Real talk: the most common og:title problem in checked URLs is not a missing tag. It's a title copied straight from the SEO <title>, complete with keyword stuffing and brand suffixes. Browser-tab titles are compact by design. Card headlines can breathe. Treating the two as the same field is the root of most preview-title weirdness.
og:title vs the HTML title Tag
Your page technically carries two titles. The <title> tag fills the browser tab and feeds search results. og:title fills link previews. Search engines read the first; every scraper from Facebook to Signal reads the second.
They do not have to match. A product page can rank with a keyword-heavy <title> while its og:title says what a buyer actually wants to read — "Acme Noise-Canceling Headphones" instead of "Buy Acme ANC-100 Headphones Online | Free Shipping". Matching them is fine when the page title is clean already; the point is og:title gets to be its own sentence.
There is one real dependency between them. When og:title is missing, platforms quietly fall back to the <title> tag — the chat-app group showed that consistently in our testing. So the safe setup is a deliberate og:title with a clean <title> underneath as the safety net. A missing og:title just means your card inherits whatever the browser title says, including the suffix you would never put in a headline.
That fallback is also why the SEO habit of appending "| Site Name" to every title leaks into cards. On X or WhatsApp, that suffix eats the final characters of your headline. Brand belongs in og:site_name, not in og:title.
Common og:title Problems and How to Fix Them
Here is the short list of what surfaces when checking pages, with the fix for each:
- Missing og:title. The scraper grabs the <title> tag instead. Fix: add the property to your templates once, not page by page.
- Too long. The spec sets no maximum, but every UI truncates. Around 60 characters is the practical ceiling — past that, feeds start cutting mid-word. Count your headline, don't eyeball it.
- Empty string.
og:title=""behaves like a missing tag on most scrapers. Remove the attribute or fill it. - Duplicated tags. Two og:title lines confuse scrapers; they read the first and ignore the rest. Keep exactly one per page.
- One title for the whole site. Hardcoded og:title makes every article card read "Homepage" or the company name. Templates should pull each page's own headline.
One detail that came out of the 14-platform tests: none of the scrapers rejected or cut og:title during the crawl — every truncation happens in the UI after the scrape. A well-formed og:title is never the reason a preview shows wrong text. Wrong text comes from the tag being missing, copied, or empty, and those are template bugs, not platform quirks.
How to Check and Fix Your og:title
Paste your URL into the free OG checker and read the og:title row. That row shows exactly what the scrapers see, and the tool flags the tag the moment it is missing. If the title in the result does not match your headline, the template is the problem.
On Next.js, set it in metadata:
export const metadata: Metadata = {
openGraph: {
title: "Free Open Graph Image Generator for Social Links",
siteName: "ogimgen",
},
}On plain HTML, the tag is a single line:
<meta property="og:title" content="Free Open Graph Image Generator for Social Links" />After the fix, re-scrape with Facebook's Sharing Debugger if the old card is still cached — the checker shows fresh tags immediately, but social networks keep their own copies for a while. For the full tag-by-tag reference, see our Open Graph meta tags list, and for the sibling tag that controls card layout, read the og:type guide.
Summary
og:title is the headline of your link preview and the most-read tag in the Open Graph set. Every platform reads it, a missing one falls back to the browser title, and the common failures — missing, too long, empty, or hardcoded — are all template bugs with one-line fixes. Write it like a headline for humans, keep it under 60 characters, and let og:site_name carry the brand.
Check your current og:title with the free OG checker — five seconds and you will see the headline exactly as WhatsApp, X, and Facebook do. Then generate a matching 1200×630 card at ogimgen.com so the image and the headline land together.