WebmasterID logoWebmasterID
User agents

Twitterbot user agent

Twitterbot is the crawler operated by X (formerly Twitter) to fetch a shared URL and read its Open Graph and Twitter Card metadata so it can render a preview card in a post. It is a link-unfurling bot, not a human visit, and identifies itself with a documented Twitterbot user-agent token.

Verified against primary sources

What this means

When a link is shared in a post on X, the platform sends Twitterbot to fetch the URL and read its card metadata — Twitter Card tags and Open Graph tags — to render the preview shown in the timeline.

This is a preview fetch, not a person reading your page. The card image, title, and description come from the metadata Twitterbot reads, so missing or malformed tags produce a blank or wrong card.

How Twitterbot identifies itself

Twitterbot uses the user-agent token Twitterbot. Match on that stable token rather than any version suffix. The platform documents the crawler and the card tags it consumes.

As with any crawler, the user agent is a claim and can be copied. Twitterbot does not run JavaScript to build the card, so it relies on server-rendered meta tags being present in the initial HTML.

Debugging a missing card

If a shared link shows no card or the wrong image, check that the page returns the expected twitter:card, twitter:title, twitter:image (or Open Graph equivalents) in the initial response with a 200 status. Redirects, login walls, or JavaScript-injected tags can all break the fetch.

Seeing the Twitterbot token in your logs for the shared URL confirms the fetch happened; an absent fetch points to the URL being unreachable or blocked.

How it appears in analytics and logs

A request whose user agent contains the Twitterbot token means X fetched that URL to build a share card. It is a one-off unfurl triggered by a post, so a burst around a share is normal and should be counted as bot traffic, not audience.

Diagnostic use case

Confirm whether Twitterbot fetched a page after it was shared, debug a missing or wrong preview card, and exclude its requests from human analytics.

What WebmasterID can help detect

WebmasterID classifies Twitterbot server-side as a social-preview bot and surfaces its fetches on the bot-intelligence view, so card-debugging crawls do not inflate page views or look like referral traffic.

Common mistakes

Privacy and accuracy notes

Twitterbot detection uses only the request user agent. No human identity is attached — an unfurling crawler is not a visitor. WebmasterID records it as a social-preview bot event, separate from human analytics.

Frequently asked questions

Why is my X share card blank?
Twitterbot could not read valid card metadata. Confirm the page returns 200 with twitter:card / Open Graph tags in the initial HTML, with no redirect or login wall in the way.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.