Social teams
Launch monitoring
Favorable to scraping
Export Twitter search results for a product name, campaign tag, or competitor phrase, then sort tweets by engagement, time, author, and media use.
Social Media$50Free
Twitter Advanced Search Scraper for CSV Export
This Twitter advanced search scraper turns public/search-visible X results into a structured CSV for social listening, campaign analysis, and research workflows. Import the template into the UScraper local desktop app, edit the X search query URL, and export tweet text, authors, timestamps, engagement counts, media URLs, reply-to fields, language, and diagnostics without wiring the X API.
Output
CSV
Columns
23
Input
X search URL
Scroll loop
Stabilizes
API key
Not required
At a glance
Export Twitter search results from advanced queries
Use this template when X advanced search is the fastest way to define the
conversation you need: keywords, phrases, accounts, replies, language, or date
windows. The default Navigate block starts with an editable
https://x.com/search?q=... URL. You can build the query in X
advanced search, copy the resulting URL, and paste it into the workflow before
running a controlled export.
The automation follows a transparent path: set the browser viewport, navigate to the search page, wait for load, pause for dynamic content, run a page collector, wait for cached rows, then export structured data. The collector scrolls until new tweets stop appearing or the safety loop finishes, which keeps the run bounded while still handling X's infinite-scroll interface.
Advanced search to CSV
Keep the exact query beside every row, so teams can audit which search operators produced each tweet export.
Infinite-scroll collection
The injected browser step scrolls, captures loaded tweet cards, and de-duplicates rows by tweet URL, post ID, or text.
Engagement fields included
Export replies, reposts, likes, views, bookmarks, media URLs, author fields, verification status, timestamps, and language where visible.
Local desktop workflow
Your query, browser session, and CSV stay in the desktop workflow unless you add your own upload, sync, or sharing step.
Who this helps
Use cases for Twitter search to CSV exports
Researchers
Public conversation review
Favorable to scraping
Collect a bounded set of visible posts from advanced search operators and preserve URLs, timestamps, language labels, and reply context for coding.
Agencies
Client reporting
Favorable to scraping
Run repeatable search exports for approved topics without maintaining a custom scraper API integration or sending client queries through a cloud actor.
Pair this page with the Twitter Data Scraper, Twitter X Comments Scraper, and Twitter Hashtag Scraper when a search export leads to profile, reply, or hashtag follow-up. Browse the UScraper template library for adjacent social and search-engine workflows.
How to use
Configure the X search scraper workflow
2
Paste your search URL
Replace the sample https://x.com/search?q=fringe&src=typed_query
URL with an approved X search or advanced-search URL that loads in your
browser session.
3
Confirm the export path
Structured Export writes twitter-scraper-by-keywords.csv with
headers and append mode. Change the save folder before client, topic, or
date-window batches.
4
Run the scroll collector
UScraper navigates to the page, waits, injects the collector, scrolls until results stabilize, and builds hidden rows from the collected tweet cards.
5
Open and verify the CSV
Spot-check row count, query string, tweet URLs, timestamps, and any diagnostic row before using the file in reports or analysis.
Output preview
CSV columns produced by the template
The export mirrors the workflow definition and keeps one row per collected
tweet card. When X redirects to login, onboarding, or a state with no visible
tweet articles, the template writes a diagnostic row under
Tweet_Content so the CSV explains what happened.
| Query_Str | Author_Handle | UTC_Time | Tweet_Content | Tweet_URL | Reply_Count | Repost_Count | Like_Count | View_Count | Tweet_Image_URL | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| product launch since:2026-06-01 | examplebrand | 2026-06-14T10:12:00.000Z | Launch thread with customer questions and a demo clip. | https://x.com/examplebrand/status/1800000000000000000 | 14 | 86 | 420 | 18K | https://pbs.twimg.com/media/example.jpg | en |
| product launch since:2026-06-01 | analyst_io | 2026-06-13T16:40:00.000Z | Comparing launch reactions across three vendors. | https://x.com/analyst_io/status/1800000000000000001 | 3 | 12 | 91 | 4.8K | en | |
| product launch since:2026-06-01 | NO_TWEETS_VISIBLE_OR_LOGIN_REQUIRED: X did not expose tweet articles to this browser session. |
twitter-scraper-by-keywords.csvColumn
Query_Str
The q parameter from the current X search URL.
Column
Post_URL
The X search page URL opened during the run.
Column
Author_Name
Visible display name from the tweet card.
Column
Author_Handle
Author handle parsed from the status URL or card text.
Column
Verified_Status
True when a verified indicator is visible in the card.
Column
UTC_Time
Datetime from the tweet time element.
Column
Tweet_Content
Tweet text or diagnostic message when no tweets are visible.
Column
Tweet_URL
Canonical status URL when exposed.
Column
Reply_Count
Visible reply count parsed from card labels.
Column
Repost_Count
Visible repost or retweet count.
Column
Like_Count
Visible like count.
Column
View_Count
Visible view count when X exposes it.
Column
Tweet_Image_URL
Visible tweet media URLs joined with separators.
Column
Language
Language attribute from the tweet text element when available.
Headers included - one row per loaded tweet card or diagnostic state
Alternatives
Local scraper vs X API and cloud actors
| Option | Good fit | Trade-off |
|---|---|---|
| UScraper Twitter advanced search template | No-code teams that need Twitter search to CSV from a local desktop app | Best-effort page-session export; visible rows depend on what X loads |
| Official X API | Developer teams with approved API access and stable query rules | Requires keys, code, plan limits, and policy review |
| Hosted scraping actors | Teams that prefer vendor-managed infrastructure | Queries and results pass through a third party and may bill per run |
Frequently asked questions
X/Twitter content can be public, but automated collection may be limited by platform terms, robots directives, login rules, privacy law, copyright, and local regulations. Use the template only for permitted research, do not bypass access controls, and get legal review before using exports commercially.
Before you run
Practical limits and maintenance notes
Operational guardrails for X search exports
Rate limits
Avoid aggressive repeated runs
X can slow, hide, challenge, or block automated sessions. Keep batches modest, avoid parallel loops, and pause when login, verification, unusual redirects, or incomplete search pages appear.
Layout drift
Tweet markup and labels can change
Empty exports, missing counts, or blank media fields usually mean the page did not load, X changed markup, or the browser session did not expose enough tweet cards in time.
Policy
Use the right access path
For sanctioned production integrations, compare the official X API and its policies. Use this scraper only where it fits your legal, privacy, and platform-compliance review.
Download the free template, install the desktop app from UScraper download, and run a short validation batch before you export Twitter search data at larger scale.
Get Started
Download and use this template instantly
$50Free
What's Included
- Template JSON file ready to import
- Pre-configured scraping nodes
- Works with UScraper desktop app
Open-source templates
UScraper templates are open source. Improve this workflow or contribute a new one to help the community grow.
Contribute on GitHubBrowse more templates in the library
All Templates