GetHubApps Logo
GetHubApps
🏷️
SEOFree · In-Browser

Meta Tag Generator

Generate SEO and Open Graph meta tags for any page in seconds.

0 / 60 characters

0 / 160 characters

Generate the meta tags a page needs — title, description, Open Graph and Twitter Card markup — with a live preview of how the result will look in a Google result and as a shared link, so you can see truncation before it happens rather than after.

Copy the finished block straight into your page's <head>. Every field is optional, but the previews show which omissions have visible consequences.

The tags that matter, and the ones that don't

TagUsed byWorth setting?
<title>Search engines, browser tabs, sharesEssential
meta descriptionSearch result snippetYes — influences click-through
og:title / og:descriptionFacebook, LinkedIn, Slack, WhatsAppYes
og:imageEvery link previewYes — the single most visible one
twitter:cardX / TwitterYes — set to summary_large_image
canonicalSearch enginesYes, wherever duplicates can exist
meta keywordsNothing, since 2009No — ignored by every major engine
meta robotsCrawlersOnly when you need to control indexing

Writing a description that earns the click

  • Aim for 140–155 characters. Longer gets truncated mid-sentence; much shorter looks thin next to competitors.
  • Google rewrites descriptions roughly half the time when it thinks a page passage answers the query better. A good description improves your odds, it doesn't guarantee the text.
  • Include the terms someone would actually search, because matched words are bolded in results and draw the eye.
  • Say what the page gives the reader, not what the page is. 'Compare 2026 rates from 14 lenders' beats 'This page discusses mortgages'.
  • Write a distinct one per page. Site-wide duplicate descriptions are worse than none at all.
  • Meta descriptions are not a ranking factor. They're a click-through factor, which is a different and still valuable thing.

Open Graph images

1200×630 (1.91:1) is the safe size across Facebook, LinkedIn, Slack, Discord and X. Use an absolute URL, not a relative one — several crawlers won't resolve relative paths.

Keep any text well inside the edges, since some platforms crop slightly and others overlay a rounded corner. And be aware that these previews are cached aggressively: after changing an image, use the platform's own debugger to force a refresh, or the old preview will persist for days.

Frequently asked questions

How long should a meta description be?
Around 140–155 characters. Google truncates by pixel width rather than character count, so the exact cut-off varies, but that range reliably survives on both desktop and mobile.
Do meta keywords still matter?
No. Google stopped using them in 2009 and every other major engine followed. They're safe to omit entirely.
Why is Google showing a different description than the one I wrote?
Google rewrites descriptions when it judges another passage on the page better answers the query. A clear, relevant description improves the chance yours is used, but it's never guaranteed.
What size should my Open Graph image be?
1200×630 pixels, referenced by an absolute URL. That ratio works across Facebook, LinkedIn, X, Slack and Discord without awkward cropping.
My link preview is showing an old image — why?
Platforms cache previews aggressively. Use the platform's sharing debugger — Facebook's Sharing Debugger, LinkedIn's Post Inspector — to force a re-scrape.
Do I need both Open Graph and Twitter Card tags?
X falls back to Open Graph tags when Twitter-specific ones are absent, so at minimum set twitter:card to summary_large_image and let the rest fall through.

Read more on this

Related tools