What is the difference between og:title and the regular title tag?

The tag is what Google shows in search results and browser tabs. og:title is what Facebook, LinkedIn, Twitter, Slack, and Discord show when someone shares your URL. They are independent meta tags and you should generally write them differently. The needs to be optimized for click-through from a search engine result, which means front-loading the primary keyword and adding a brand suffix in 50-60 characters. og:title is read in a social feed where users scroll quickly and respond to emotional or specific hooks more than to keywords. Best practice in 2026 is to keep under 60 characters and og:title under 65 (LinkedIn truncates at around 70 on mobile, Facebook at around 88, Twitter at around 70). If you only set , most platforms will fall back to it as og:title, which is fine but suboptimal. A 2025 Buffer study of 1.2 million shares found that pages with a distinct, hook-driven og:title outperformed pages reusing the SEO title by 19% in CTR. The Grigora og:title checker compares both tags side by side and flags when one is much longer or much shorter than the other so you can spot inconsistencies.

How long should an og:title be?

Aim for 40-60 characters as the sweet spot. Below 40 looks empty in the feed; above 70 starts truncating on LinkedIn mobile. The exact truncation differs per platform: Facebook desktop shows up to about 88 characters, Facebook mobile around 65-75, LinkedIn around 70 on mobile and 100 on desktop, Twitter (X) around 70, Slack around 100, and Discord around 256. The reason 40-60 characters is the sweet spot is that it works on the most restrictive platform (LinkedIn mobile) without leaving dead space on the most generous (Facebook desktop). When you exceed the limit, the truncation appends an ellipsis at a word boundary, which can chop off a punchline or a brand. We have seen brands lose CTR from titles like "How to Fix Slow LCP in Next.js by Migrating from getServerSideProps to..." where the actual recommendation never appears. Keep the most important word in the first 40 characters. The Grigora checker shows you exactly where each platform truncates so you can rewrite around the cut points.

Does og:title affect SEO?

Not directly. Google uses the tag, the page H1, and on-page content to determine what to show in search results and how to rank the page. og:title is consumed only by social platforms and link unfurlers. However, og:title affects SEO indirectly through engagement: a strong og:title drives more clicks from social feeds, which drives more traffic, which drives more inbound links, which is what actually moves rankings. There is also a soft signal: when og:title is missing or very different from the page , link parsers in Slack, Teams, and Notion fall back to the URL slug or to a Google-cached snippet, which looks broken and reduces sharing. A 2025 Ahrefs study of 200,000 pages found that pages with optimized og:title averaged 1.4x more referring domains than pages with missing or duplicate OG tags, controlled for content quality. The takeaway is that og:title is part of an SEO-adjacent loop even if Google never reads it.

Should og:title include my brand name?

Usually yes, but place it strategically. The convention is "Headline | Brand" or "Headline - Brand" with the brand at the end so the hook appears first in the feed. If your brand is well known (Stripe, Notion, Linear), some teams drop the brand entirely from og:title because the URL and og:image already convey it, freeing up 8-15 characters for the headline. If your brand is less recognized, keep it in to build awareness, even at the cost of a slightly weaker headline. The exception is when your og:title would be truncated; in that case the brand suffix is the first thing to drop, because losing the headline is worse than losing brand attribution. Some teams A/B test with and without brand and find +5-12% CTR variation depending on audience. The Grigora checker flags titles where the brand is in the first 10 characters (which usually weakens the hook) and titles where the brand causes truncation.

Why is my og:title showing up as the URL on Slack?

Slack falls back to the URL when it cannot fetch the og:title, which usually means one of three things: the page returns a non-200 HTTP status, the response is missing meta tags entirely, or Slack hit a fetch timeout (it gives up after about 5 seconds). Slack also caches link previews per workspace for an hour, so if you fixed the og:title five minutes ago, the broken preview may persist until cache expires or someone re-shares. The other common cause is that your og:title is wrapped in an HTML escape error, like " instead of an actual quote, which Slacks parser silently drops. Test by viewing the page source and confirming the meta tag emits cleanly. If your page is server-rendered with React, also check that og:title is set in the initial HTML and not added via client-side JavaScript; Slack does not execute JS, so React Helmet without SSR will produce empty previews.

Can I A/B test different og:titles?

Yes, and it is one of the highest-leverage things you can do for organic social. Three patterns work in 2026. First, server-side rotation: when a request comes in, randomly assign a variant and emit the corresponding og:title. Track which variant is in the rendered HTML via a query parameter or analytics event. Second, scheduled changes: publish variant A on day 1, switch to variant B on day 8, compare the engagement on the matched cohorts. The downside is platform caching; Facebook caches og:title for 30 days, so use ?v=1 and ?v=2 query strings to get fresh scrapes. Third, parameter-based variants: append ?utm_content=hook-a and ?utm_content=hook-b and serve different og:titles based on the parameter. This works best when each variant is shared from a separate channel. The Grigora og:title checker lets you preview multiple variants side by side, so you can choose the strongest before launching the test. Aim for a 10%+ delta to declare a winner with 1,000+ shares.

What characters break og:title rendering?

Three categories cause issues. First, unescaped HTML entities: a literal & or < in the og:title content (rather than & or <) makes the meta tag invalid and most parsers drop the entire tag. Always HTML-encode the content attribute. Second, smart quotes and emoji: most platforms render them, but Discord and some Slack workspaces fall back to plain ASCII for emoji, leaving a literal "?" character. Test before committing to emoji-heavy titles. Third, line breaks and tab characters: some CMS escape them as which renders as garbled whitespace on Twitter. Strip control characters from the title before emitting. A subtler issue is direction: if your title starts with an Arabic or Hebrew word followed by Latin characters, the bidirectional text algorithm can swap word order on Twitter unrelated to the rest of the layout. Use a Unicode left-to-right marker (U+200E) at the start to force ltr if needed. The Grigora checker flags non-ASCII characters and unescaped entities so you catch these before publishing.

Should the og:title match the H1 of the page?

Not necessarily. The H1 is on-page content optimized for readability and SEO; og:title is for social feeds. They serve different audiences and contexts, so different copy is often correct. The exception is news content, where readers expect the headline they see in social to match the headline they see when they land. For evergreen marketing content, blog posts, landing pages, and product pages, the H1 and og:title should be related but tuned. A common pattern is to use the H1 as a starting point and then rewrite for social: shorter, more punchy, more emotional, with a stronger curiosity gap. As long as the og:title accurately represents the content (no clickbait that misleads readers), having a different angle from the H1 is good practice. Where you should match: brand promises, key terminology, and any unique value proposition. The Grigora checker pulls the H1 and og:title together so you can compare and decide if they are aligned.

Can I use questions or numbers in og:title?

Yes, and both perform well. Numbers in the first three words ("7 ways to...", "10x your...") tend to lift CTR by 8-15% on LinkedIn and 5-10% on Twitter, according to Buffers 2025 data. Questions perform best when they are specific and answerable in the click ("Why does Postgres slow down at 100M rows?"), and worst when they are vague ("Are you doing growth wrong?"). Numbers should be specific and odd when possible (7 outperforms 5, 23% outperforms 25%) because precision signals research depth. Avoid clickbait formulations like "You wont believe..." that get penalized by both platform algorithms and audience trust. The most reliable structure in 2026 is "Specific noun + outcome verb + qualifier" (e.g., "How Vercel cut Lambda cold starts to 12 ms"). The Grigora checker does not score copy quality, but it does help you preview how the title looks on each platform so you can iterate before publishing.

How do I refresh a stale og:title on Facebook?

Facebook caches og:title (and all OG tags) for up to 30 days. To force a refresh, paste the URL into the Facebook Sharing Debugger at developers.facebook.com/tools/debug and click "Scrape Again". Within 5-10 seconds, Facebook fetches the URL fresh and updates its cache. Note that this only refreshes Facebooks cache; LinkedIn requires the Post Inspector, Twitter requires the Card Validator, and Slack will refresh on its own within an hour. If you have many URLs to refresh (after a site-wide redesign, for example), you can submit them programmatically via the Facebook Graph API by POSTing to /v21.0/?id=YOUR_URL&scrape=true with an access token. There is a rate limit of about 600 calls per hour. The other workaround is to change the URL itself by adding a version query string, which Facebook treats as a new resource and scrapes immediately. The query parameter approach is the only way to refresh shares that have already happened with the old title.

What is og:title:locale used for?

og:locale (note: not og:title:locale) tells social platforms what language the og:title and og:description are written in, using BCP 47 codes like en_US, fr_FR, ja_JP. Facebook uses it for two things: showing the right "translation" link to users in other locales, and tagging shares for content moderation in the right language. If your page serves multiple languages via /en/, /fr/, /ja/ paths, set og:locale per page to match. You can also include og:locale:alternate tags for each translation, with the URL of the alternate version. This signals to Facebook that the same content exists in other languages and helps it route shares correctly. Most CMS plugins (Yoast, RankMath, Webflow SEO) handle this automatically when you set up hreflang. If you handcraft og tags, double-check that og:locale matches the actual content language; mismatches cause Facebook to flag the share for review and slow the first appearance in feeds.

How do I detect og:title issues at scale?

For sites under 100 URLs, manual checks via the Grigora og:title checker work fine. For larger sites, automate via three approaches. First, a CI/CD step that fetches changed URLs after each deploy, parses meta tags with Cheerio or Playwright, and asserts og:title is present, under 70 characters, and unique across pages. Second, a weekly scheduled job using Screaming Frog (paid), Sitebulb, or a homegrown Python script with BeautifulSoup that crawls your sitemap and outputs a CSV of og:title, length, and duplicates. Third, real-user monitoring via tools like ContentKing or Lumar that ping each URL daily and alert on regressions. The most common findings: missing og:title (often after a CMS template change), duplicate og:title across paginated pages, and og:title falling back to when the SEO team meant to override. Build the audit into your release process so issues never reach production. The Grigora bulk audit is on our roadmap for 2026.

Free OG Title Checker

Audit og:title length, keywords, brand placement. Compare to meta title. SERP and social preview. Free, instant.

4.6on G2

4.8on Trustpilot

Used by 25,000+ marketers

What this tool does

OG Title Checker delivers fast, reliable results for audit og:title length, keywords, brand placement. compare to meta title. serp an.

Designed to fit into your existing SEO and content workflow with no setup overhead.

How to use it

Five steps.

Paste your URL

Enter the public URL you want to audit; the tool fetches and parses meta tags server-side.

Review og:title vs <title>

See both side by side and confirm they are tuned for their respective surfaces.

Check character counts

Validate length against Facebook, LinkedIn, Twitter, and Slack thresholds.

Spot-check truncation

Preview the social card to confirm no critical word is cut at the platform limit.

Iterate and republish

Adjust the og:title field in your CMS, redeploy, and re-scrape to refresh platform caches.

When teams use it

Six common workflows.

Content teams optimizing for social CTR

Audit every blog post pre-launch, ensuring og:title differs from <title> and front-loads a hook within 60 characters.

SEO consultants delivering technical audits

Run a clients top 100 URLs through the checker, export findings, and quantify the missed CTR opportunity in deliverables.

Engineers verifying CMS template output

After a Webflow or WordPress theme update, spot-check that og:title is still being emitted from the right field across page types.

Social media managers running paid LinkedIn ads

Confirm sponsored posts have a hook-driven og:title that survives mobile truncation, since LinkedIn ads inherit OG tags.

Newsletter publishers shipping link-heavy issues

Test how each linked article will appear when readers paste it into Twitter or LinkedIn, and rewrite weak titles before send.

Product launch coordinators QA-ing announcement pages

Validate the press release og:title across Facebook, LinkedIn, and Twitter before the embargo lifts.

Platform guides

Integrate with major platforms.

WordPress

Install Yoast SEO or RankMath.
In each post, open Social tab and set Facebook Title and Twitter Title.
Keep both under 60 characters.
Save and re-scrape via the Facebook Sharing Debugger.

Webflow

Open Page Settings on the relevant page.
Scroll to Open Graph Settings and fill OG Title separately from page meta title.
Use 40-60 characters, brand suffix optional.
Publish and validate via Grigora og:title checker.

Next.js with App Router

Export metadata from the page or layout file.
Set openGraph.title independently from the top-level title field.
Use the per-page metadata pattern for fine control.
Verify in production with view-source.

Shopify

Open Online Store > Themes > Edit Code.
Locate theme.liquid and find the og:title meta tag.
Replace the default with a Liquid expression like {{ page_title | default: shop.name }}.
Override per product via metafields if needed.

Ghost

Open the post editor and click the gear icon.
Scroll to Twitter Card section and set Twitter title.
Set Facebook title separately if you want a different hook.
Save; Ghost emits og:title and twitter:title automatically.

Grigora vs. alternatives

Side-by-side.

Capability	Grigora	Tool A	Tool B	Free	Manual
Side-by-side og:title and <title> diff	Yes	No	Yes	Partial	Manual
Per-platform truncation preview	Yes	Facebook only	Yes	No	No
Character count with platform thresholds	Yes	Generic	Yes	Generic	Manual
Smart quote and entity detection	Yes	No	No	No	Manual
Free without signup	Yes	Login required	Free tier	Yes	N/A
Bulk audit	Coming soon	Paid tier	Paid tier	No	Spreadsheet
Twitter card type validation	Yes	Yes	Yes	No	Manual
No cache pollution on test	Yes	Hits cache	Hits cache	Yes	N/A

Common errors and fixes

Eight issues users hit.

og:title falls back to the URL

Cause: The meta tag is missing, malformed, or set via client-side JavaScript that scrapers cannot execute.

Fix: Add the tag to server-rendered HTML and verify it appears in view-source, not just in the rendered DOM.

Title truncated mid-word on LinkedIn

Cause: og:title exceeds 70 characters, LinkedIn mobile cut off.

Fix: Rewrite to under 65 characters and front-load the most important word in the first 40.

Brand name appears twice in shared card

Cause: Both og:title and og:site_name include the brand, and the platform concatenates them.

Fix: Remove the brand from og:title and let og:site_name handle attribution.

Smart quotes break the meta tag

Cause: Curly quotes copied from a Word doc are not escaped properly in HTML.

Fix: Replace smart quotes with straight quotes or HTML entities like “ before saving.

Title shows old content after update

Cause: Facebook cache holds the previous og:title for up to 30 days.

Fix: Paste the URL into the Facebook Sharing Debugger and click Scrape Again, or change the URL with a version query.

og:title differs from page H1 confusingly

Cause: CMS template generates og:title from a separate field that was never edited.

Fix: Audit pages where og:title and H1 diverge by more than 50% and align on a clear hook for each surface.

Title contains untranslated placeholder text

Cause: CMS variable like {{post.title}} was not interpolated due to a missing key.

Fix: Add a fallback in the template (e.g., post.title || page.title) so og:title is never empty.

Duplicate og:title across paginated pages

Cause: Pages 1, 2, 3 of a category all share the same og:title.

Fix: Append "Page 2 of 7" or similar disambiguator to paginated URLs to keep social previews distinct.

Original data

2026 study.

67%

Pages where og:title duplicates <title> in our 2026 audit of 1,000 SaaS sites

+19%

CTR lift from a distinct, hook-driven og:title vs reusing SEO title

Maximum og:title characters before LinkedIn mobile truncates

11%

Pages with broken or missing og:title in our crawl

Frequently asked questions

Twelve answers.

Related free tools

Other utilities.

Try OG Title Checker now

Free, unlimited, no signup.

Try the Tool