Built with Chinaski

X (Twitter) Handle

The X handle field (Settings → Integrations → Social) is the simplest thing on the tab: one text field that controls one meta tag. When you set it (your handle, like @yourhandle), every built page carries twitter:site attribution so X and link-preview clients know which account an article belongs to. Leave it blank and that line is simply omitted — no other behavior changes.

What it does

On the next build after saving, every page and post gains an X/Twitter meta-tag set:

  • twitter:card — a large-image card when the page has a share image (OG image → featured image → the site’s default share image), and a plain summary card otherwise.
  • twitter:title / twitter:description — the same text rules as the OpenGraph tags: your per-page OG title/description, falling back to the meta title/description, then to the page title and the site tagline.
  • twitter:image — the resolved share image (same fallback chain), omitted when a page has no image at all.
  • twitter:site — your handle, exactly as typed.

These tags complement the OpenGraph set emitted on the same pages — X and other link-preview clients generally accept either set.

What it doesn’t do

  • No linking or sign-in to X. It’s a meta tag, nothing else — no script, no API call, no per-post social buttons added.
  • Works offline. Unlike the analytics fields, the handle isn’t network-related; air-gap mode doesn’t touch it, and the meta tags build fine on an isolated host.
  • A card exists without it. The card/title/description/image tags are emitted regardless; the handle only adds the attribution line. With no handle set, the card still renders — it just loses the attribution line that ties the content to your account.
  • Per-author attribution (twitter:creator) isn’t a feature. Authors are metadata on posts, but the built pages don’t emit per-author X tags.

Usage notes

  • Paste the handle, not the URL. The value should be the handle text: @yourhandle (with or without the @); pasting a full profile URL puts a wrong-looking string inside the tag. (The field’s placeholder shows the intended shape.)
  • It’s an all-or-nothing site-wide attribution — per-post author flatfields exist in the author system, and themes could render their own byline, but there’s no per-author twitter:site-style switch.
  • Any change takes effect on the next build of the affected pages (all of them, since it’s site-wide).
  • If your team manages multiple accounts, the same rule applies: one handle for the whole instance. Set the account that should be “replied to” when readers talk about your content.

The short version

One field, one meta line: twitter:site everywhere, courtesy of the Social section of Settings → Integrations. Cards, images, and titles are already handled by the build; the handle just says who posted it.