avatar / banner Profile photo / cover photo — direct CDN links, cookie mode only. On a tweet/reply record these are the author's photos, named user_avatar/user_banner instead so they don't collide with the tweet's own fields

text / full_text / article_text The post's own complete text — cookie mode always resolves the real full text even for long-form "Note" tweets that X itself truncates in its legacy API field

reply_to_mentions The @handles X auto-prepended to a reply's text when it was composed (everyone already tagged in that conversation) — x.com's own UI hides these from the visible tweet body and shows them as a separate "Replying to" line instead, which is exactly what every card/panel here does with this field too. The raw text itself still contains them untouched

hashtags Hashtags used in the post

description Profile bio (a user/follower/following record), or Google's own SERP snippet for that result (a CSE record) — which one depends on whether the record is a person or a web result

created_at When the post itself was actually made. Same field, every source: Cookie/Xquik get it straight from the API; Wayback and Google CSE decode it from the tweet id's Snowflake bits whenever the result links to a tweet permalink (absent otherwise — e.g. a profile page or a non-X result, where there's no post id to decode)

fetched_at When this tool pulled the record — same field, every source (Cookie, Xquik, Wayback, Google CSE), so results are comparable side by side. Not to be confused with created_at (the post's own creation time) or iso_date (a Wayback snapshot's capture time)

reply_count / retweet_count / favorite_count / view_count Counts reported by Twitter (can under-report)

followers_count / following_count / tweet_count Account stats at fetch time

verified Legacy blue checkmark (pre-2023)

is_blue_verified Paid X Premium checkmark

in_reply_to_tweet_id Parent tweet this replies to — also the drill-down anchor that fetches its replies

retweeted_text / retweeted_by_user / retweeted_by_name / retweeted_by_bio Content and author of the original tweet being retweeted

retweeted_at / retweeted_tweet_id When the original was posted, and its own ID

quoted_text / quoted_user / quoted_name Content and author of the tweet being quoted, when the record itself is a quote-tweet (retweet-with-comment) — the record's own text is the quoting user's added commentary, this is what it's commentary on

quoted_at / quoted_tweet_id When the quoted tweet was posted, and its own ID

media Photo/video attachments — normalized to [{type, thumb, url}] regardless of whether the source was Cookie or Xquik/API (the two use different raw shapes internally, unified before display/archive)

archived_media Local file paths once a result's media has actually been downloaded into an archive — archive view only

tweet_url Cookie/Xquik: direct link to the tweet, built from user + id. Populated the moment a result is fetched — the same value on the live card, in a JSON dump, and in an archive of it, not built separately each time. Wayback and Google CSE carry their own equivalent instead — see archive_url/original and result_url below

lat / lon / place Coordinates plotted on the map view (Geo Post Search)

user_location Free-text profile location string, geocoded client-side to produce lat/lon

account_created / account_age Derived from the account's numeric ID, not the API — see the Account age badges above

account_age_flag New / Recent / Established bucket, drives the badge color

account_age_precision exact (true Snowflake decode) / estimated (pre-Snowflake id, interpolated) / unknown

archive_url Link to the Wayback Machine snapshot

iso_date When that snapshot was captured

original The original URL that was archived

statuscode / mimetype / length HTTP status / content type / size of the snapshot

post_title / post_text / preview_image Scraped from the archived page's own meta tags (og:/twitter: tags, or <title>/<meta name="description"> on older captures)

content_type What kind of X/Twitter page a result actually is — tweet (a specific permalink) / profile (a bare profile page) / twitter_other (some other X page) / other (a non-X site, Google CSE only). Derived purely from the result URL's own shape — a keyword match isn't always a specific tweet, and this is how to tell without opening the link

serp_title Google's own SERP result title — always kept as-is, even if post_title below gets replaced by a fresher live fetch

description Google's own SERP snippet for this result — Google truncates this itself (ends mid-sentence in "…"), that's not this tool cutting it short. Kept untouched alongside post_text below since a live re-fetch of an X link often gets a less specific, bot-facing page instead

post_title / post_text "Best known" title/description — starts as Google's own SERP values, replaced by a live fetch of the page's own og:/twitter:/meta tags when one succeeds. See serp_title/description above for what Google originally had, in case the live fetch made things worse rather than better

result_url The live page Google indexed, shown as its full raw address

display_link The result's domain, as shown in Google's own results

preview_image Thumbnail — from Google's own indexed metadata, or the live page's og:/twitter:image when Google didn't have one

source Which of the 4 data sources this result came from — Twitter Cookie / Xquik API / Wayback Machine / Google CSE (Multi-Source Search only)

Search root The diamond node — the query you ran

Tweet A tweet/post returned by search, by Expand Posts on a user node, or by expanding another node

Reply A tweet fetched via Expand Replies on a tweet node

User / Retweeter A person — from Follower/Following Explorer, via Expand Retweets/Followers/Following on a node, or via View Author Profile on a tweet/reply (pulled from that tweet's already-fetched author info, no extra request). Once on canvas, select it and Expand Posts/Followers/Following works the same regardless of how it got there

Wayback snapshot An archived-page result, from Wayback Archive Search or the Wayback portion of Multi-Source Search

Web result A Google CSE result, from the Google CSE portion of Multi-Source Search

Viewed Turns a node solid white once you've clicked it — a visual "already looked at this" marker, not part of the underlying data