All articles

Meta tags: which ones actually affect search and social media

A page can have a perfect title tag and still show up wrong everywhere it's shared, because search engines, Facebook, and Twitter each read a different set of tags — and this site's own uk-default, 16-locale structure is a convenient example of why that matters.

Meta description is a suggestion, not a contract

The <meta name="description"> tag tells a search engine what text to use for the snippet. It's only a hint: Google routinely rewrites it, pulling a fragment from the page body instead if that fragment matches the user's query better than the description you wrote.

Open Graph versus Twitter's own Card tags

Open Graph — og:title, og:description, og:image — is a protocol Facebook introduced around 2010, and it's now read by LinkedIn, Telegram, Slack, and most other link-preview generators. Twitter is the outlier: it defines its own twitter:card, twitter:title, and twitter:image tags, and only falls back to Open Graph values for whichever ones are missing. Set both if you want predictable results on Twitter/X specifically.

hreflang: telling search engines about your other locales

A site with multiple language versions of the same page — like this one, where Ukrainian sits at the root and every other locale gets a URL prefix — should link them with <link rel="alternate" hreflang="en" href="..."> tags (one per locale, plus an x-default). Without hreflang, search engines may show the wrong language version to a visitor, or treat translated pages as near-duplicates of each other.

Why this is useful

  • Generate a complete tag set (SEO, Open Graph, Twitter Card) for a new page in one pass.
  • Catch a missing tag before a link goes out on social media with no image or the wrong title.
  • Understand why the snippet Google shows doesn't match your meta description word for word.

Image size matters for Twitter Card previews

The summary_large_image card type expects an image around 1200×630 pixels; a much smaller or oddly-cropped image either gets scaled awkwardly or Twitter silently falls back to the smaller summary layout. Open Graph is more forgiving, but matching the recommended ratio keeps the preview consistent across every platform that reads og:image.

Try the tool