All posts
SEO meta tags how-to

Landing Page Meta Tags: Title, Description, OG, Twitter (+ Templates) | PageFork

The 2026 guide to landing page meta tags: title, description, OG, Twitter, canonical, robots. Includes character limits, formulas, and copy-paste templates.

PageFork Editorial Updated May 26, 2026

Landing Page Meta Tags: Title, Description, OG, Twitter (+ Templates)

Last updated: May 26, 2026

Landing page meta tags are the HTML elements in the <head> of a page that tell search engines and social platforms how to display the page in results, previews, and link cards. The non-negotiable set in 2026 is six tags — title, meta description, canonical, meta robots, OG (Open Graph) image and title, and Twitter card — each of which has specific character limits, formatting rules, and ranking implications.

Meta tags are the lowest-effort, highest-leverage SEO improvement on most landing pages. A well-written title tag can move CTR by 20–40% in classic search and is the most-cited input that ChatGPT and Perplexity surface as the “page name” when they cite a source. A missing or wrong canonical can demote an entire page silently. And OG tags determine whether your page shared on LinkedIn looks like a polished asset or a broken preview card.

This guide covers every meta tag worth setting in 2026, the rules that make each one effective, and copy-paste templates you can adapt.

The six meta tags every landing page needs

If you only set six tags, set these:

  1. Title tag — <title>
  2. Meta description — <meta name="description">
  3. Canonical — <link rel="canonical">
  4. Meta robots — <meta name="robots">
  5. Open Graph (OG) tags — <meta property="og:*">
  6. Twitter card — <meta name="twitter:*">

Everything else (viewport, charset, theme-color, manifest links) matters but rarely needs per-page customization. The six above need to be intentional on every page.

1. Title tag

The single highest-leverage meta tag.

What it does

The title tag controls what appears in the search result, the browser tab, and most social previews when no OG title is set. Google uses it as a primary ranking signal and as the most prominent element of the search snippet.

Character limit

50–60 characters is the safe range. Google truncates around 580 pixels of width on desktop; for most fonts that’s roughly 60 characters but can be less if you use wide letters (W, M).

If you need to test how a title will render, use Mangools’ SERP simulator or Google’s own preview in the URL inspection tool inside Search Console.

Formula

[Primary Keyword]: [Hook or Specific Detail] | [Brand]

Examples:

  • “Landing Page Meta Tags: Title, Description, OG, Twitter (+ Templates) | PageFork” (75 chars — slightly over, will truncate the brand on small viewports, acceptable)
  • “PageFork vs Unbounce: Which Is Better in 2026? | PageFork” (56 chars — clean)
  • “AI Landing Page Builder: The Complete 2026 Guide | PageFork” (59 chars — clean)

Rules

  • One title per URL. Every page has a unique title. Programmatic templates that produce duplicate titles tank rankings.
  • Primary keyword first. Front-loading improves both ranking and CTR.
  • Brand at the end. Helps brand recognition without crowding out the keyword.
  • Use sentence case or title case consistently. Pick one, stick to it across the site.
  • Avoid all-caps and emojis. Both reduce CTR in 2026; emojis are also unreliable in AI search snippets.

Common mistakes

  • “Home | Brand Name” — generic, wastes the slot.
  • “Brand Name — Best [Product] for [Audience] | Brand Name” — duplicate brand, no keyword.
  • ”🚀 Launch Your AI Page in Seconds! 🎯” — emojis, no keyword, hype-y.

2. Meta description

Doesn’t directly affect ranking but does affect CTR — and CTR feeds ranking signals.

Character limit

150–160 characters. Google sometimes shows up to 160; rarely 320. Plan for 160.

Formula

[Action verb / hook]. [Main benefit or scope]. [Optional CTA / specifics].

Examples:

  • “Learn the 5-part prompt formula that turns a single sentence into a high-converting landing page in under a minute. Includes 7 ready-to-use templates.” (148 chars — clean)
  • “PageFork vs Unbounce compared on price, AI workflow, SEO, A/B testing, and ideal user. See the full feature matrix and pick the right tool for your team.” (158 chars — clean)

Rules

  • Include the primary keyword. Google bolds matched terms in search results, which lifts CTR.
  • Use action language. “Learn how to,” “See examples of,” “Compare 12 tools.”
  • Match the search intent. If the query is informational, lead with what the reader will learn. If transactional, lead with what they’ll get.
  • One meta description per URL. Same as title — uniqueness matters.
  • Don’t quote-mark the source HTML. Some renderers truncate at the first quote.

When to skip

If you don’t write one, Google generates one from page content. This is sometimes acceptable for very long pages where Google does a reasonable job. Most landing pages should have a hand-written description.

3. Canonical tag

The most under-discussed but most easily-broken meta tag.

What it does

The canonical tag tells search engines which URL is the “preferred” version of a page when multiple URLs serve similar content. It’s how you prevent duplicate-content dilution from UTM parameters, A/B variants, or print versions.

Format

<link rel="canonical" href="https://pagefork.ai/blog/landing-page-meta-tags" />

Rules

  • Absolute URL, not relative. https://..., not /blog/....
  • HTTPS, not HTTP.
  • No trailing slash inconsistency. Pick a convention site-wide and stick to it.
  • Self-referencing on canonical pages. If this is the canonical version, the canonical tag points to its own URL.
  • Cross-referencing on duplicate variants. A UTM-tagged version of /blog/foo?utm_source=email should canonical to /blog/foo.

Common mistakes

  • Canonical points to the homepage from every internal page (transfers all ranking authority to the home page — disastrous).
  • Canonical missing entirely on URLs accessible via multiple parameter combinations.
  • Canonical points to a different page than the indexed URL — Google’s mixed signals usually result in neither version ranking well.

4. Meta robots

Controls how search engines crawl and index the page.

Default

<meta name="robots" content="index, follow" />

For most landing pages this is what you want. Index = the page can appear in search results. Follow = links on the page pass authority.

Variants

  • noindex, follow — page won’t appear in results but links pass authority. Useful for thank-you pages, internal landing pages.
  • noindex, nofollow — page is invisible to search and doesn’t pass authority. Use sparingly.
  • index, nofollow — page can rank but its outbound links don’t pass authority. Rare use case.

Common mistakes

  • Inherited noindex from a staging environment — the most common SEO disaster. Always check view-source: on production.
  • Forgetting to remove noindex when launching. A pre-launch landing page often goes live with the launch flag still on.

5. Open Graph (OG) tags

OG tags control how your page appears when shared on LinkedIn, Facebook, Slack, Discord, and most other platforms.

Required set

<meta property="og:title" content="Landing Page Meta Tags: Title, Description, OG, Twitter (+ Templates)" />
<meta property="og:description" content="The 2026 guide to landing page meta tags: title, description, OG, Twitter, canonical, robots. Includes character limits, formulas, and copy-paste templates." />
<meta property="og:image" content="https://pagefork.ai/og/landing-page-meta-tags.png" />
<meta property="og:url" content="https://pagefork.ai/blog/landing-page-meta-tags" />
<meta property="og:type" content="article" />
<meta property="og:site_name" content="PageFork" />

Image specifications

  • Dimensions: 1200×630 pixels.
  • Format: PNG or WebP. JPEG is fine but larger.
  • File size: under 1 MB, ideally under 300 KB.
  • Safe zone: keep important text inside the central 80% — some platforms crop edges.
  • Text on image: under 20% of image area, large enough to read at 600px wide.

Rules

  • og:title can differ from <title> if you want a more shareable phrasing on social. Both should still match the page topic.
  • og:image must be absolute URL. Relative URLs break LinkedIn previews specifically.
  • og:type: use article for blog posts, website for product/landing pages, product for e-commerce items.

Common mistakes

  • Missing og:image — produces a default placeholder or blank preview card.
  • Image is too small (under 600×315) — LinkedIn shows it as a thumbnail instead of a full card.
  • Image cached badly — LinkedIn especially caches OG previews aggressively. Use LinkedIn’s Post Inspector to refresh.

6. Twitter card

Twitter (X) reads OG tags by default but you can override with twitter:* meta for finer control.

Minimum set

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Landing Page Meta Tags: Title, Description, OG, Twitter (+ Templates)" />
<meta name="twitter:description" content="The 2026 guide to landing page meta tags." />
<meta name="twitter:image" content="https://pagefork.ai/og/landing-page-meta-tags.png" />

Card types

  • summary — small thumbnail, useful for short titles.
  • summary_large_image — full-width image card. Default for content pages in 2026.
  • player and app — specialized; rarely used for landing pages.

Rules

  • Use summary_large_image for almost every landing page in 2026.
  • Image specs same as OG: 1200×630 ideal.
  • twitter:site is optional — adds the @handle. Useful if the brand has presence on X.

A complete meta tag template

Copy this into the <head> of any landing page and customize the 8 variables marked {{ }}:

<!-- Primary -->
<title>{{Primary Keyword}}: {{Hook}} | {{Brand}}</title>
<meta name="description" content="{{150-160 char description with primary keyword and action verb}}" />
<link rel="canonical" href="{{https://your-domain.com/page-url}}" />
<meta name="robots" content="index, follow" />

<!-- Open Graph -->
<meta property="og:title" content="{{OG title - can match <title> or differ}}" />
<meta property="og:description" content="{{OG description}}" />
<meta property="og:image" content="{{https://your-domain.com/og-image.png}}" />
<meta property="og:url" content="{{https://your-domain.com/page-url}}" />
<meta property="og:type" content="article" />
<meta property="og:site_name" content="{{Brand}}" />

<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="{{Twitter title}}" />
<meta name="twitter:description" content="{{Twitter description}}" />
<meta name="twitter:image" content="{{https://your-domain.com/og-image.png}}" />

<!-- Viewport (always include) -->
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta charset="UTF-8" />

How PageFork handles meta tags

In PageFork, meta tags are auto-generated from page content during the prompt-to-page generation step:

  • Title tag derived from the page H1 plus brand suffix, validated against the 60-char limit.
  • Meta description generated from the page summary, capped at 160 characters.
  • Canonical set automatically to the page’s live URL.
  • Meta robots defaults to index, follow (overridable per page).
  • OG image auto-generated as a 1200×630 card with the page H1 in the brand’s typography.
  • Twitter card set to summary_large_image by default.

You can override any of these in the editor, but the defaults pass the validation checks for SEO and social platforms out of the box.

Validation tools

Before shipping a page, run it through:

  • Google Rich Results Test — validates schema and shows how Google sees the page.
  • LinkedIn Post Inspector — refreshes LinkedIn’s OG cache and previews the share card.
  • Twitter Card Validator (now via developer.x.com) — preview Twitter card rendering.
  • Browser DevTools → Elements → <head> — quick visual scan of all tags, useful for catching missing OG images.

If you want a one-click full-stack check, Screaming Frog SEO Spider crawls a site and flags duplicate, missing, or out-of-spec meta tags across every URL.

FAQ

How long should a landing page title tag be?

50–60 characters. Google truncates around 580 pixels of width, which lands at roughly 60 characters in most fonts. Front-load the primary keyword and put the brand at the end so truncation, when it happens, drops the brand instead of the keyword.

Does the meta description affect SEO ranking?

Not directly — Google has confirmed multiple times that meta description isn’t a ranking signal. But it heavily affects CTR, and CTR is a ranking input. A well-written description on a page ranking #5 can lift it to #3 by improving click rate.

What size should the OG image be?

1200×630 pixels is the standard. PNG or WebP is preferred over JPEG. Keep file size under 1 MB, ideally under 300 KB. Keep important text inside the central 80% of the image because some platforms crop edges.

Do I need both OG tags and Twitter card tags?

Twitter falls back to OG tags when twitter:* tags are missing, so technically you can skip the Twitter set. In practice it’s worth setting them explicitly because it gives you control over Twitter-specific phrasing and avoids edge cases when Twitter’s parser misreads OG tags.

What’s the difference between noindex and nofollow?

noindex prevents the page from appearing in search results. nofollow prevents links on the page from passing ranking authority. They’re independent — you can combine them or use them separately. Most landing pages should be index, follow. Thank-you pages should usually be noindex, follow.

How do I check if my meta tags are working?

View page source (view-source: prefix in Chrome) and confirm each tag is present and well-formed. Then run the page through Google’s URL Inspection tool in Search Console — Google’s “rendered HTML” view shows what Googlebot actually sees.

Can I use the same title and meta description on multiple pages?

No. Duplicate titles and descriptions across URLs dilute ranking signals and confuse search engines about which page should rank for what. Every page needs unique meta. Programmatic page setups need a template that varies meaningfully per page.

Where to go next

For the full five-layer context, read Landing Page SEO: The Complete 2026 Playbook.

For the 40-item checklist (printable from the page — copy or save-as-PDF), use the checklist section in that playbook.

For structured data next to meta tags, validate with Google’s Rich Results Test; a dedicated schema deep-dive ships on the blog as we publish it.

Or open the homepage generator—PageFork writes title, description, canonical, OG, and Twitter tags on every generated page. Compare plans under pricing.

Sources: Google Search Central documentation on meta tags. PageFork internal SEO audit checklist, Q1 2026. Author: PageFork Editorial.