YouTube Shorts Scraper for Trends & Channels
Pricing
from $35.00 / 1,000 shorts results
YouTube Shorts Scraper for Trends & Channels
Scrape YouTube Shorts from channels or direct URLs and extract titles, views, likes, comments, hashtags, descriptions, transcripts, and automation-ready trend signals.
Pricing
from $35.00 / 1,000 shorts results
Rating
2.6
(2)
Developer
scraping automation
Maintained by CommunityActor stats
2
Bookmarked
70
Total users
0
Monthly active users
16 days ago
Last modified
Categories
Features
Share
中文简介 / Chinese summary
- 功能: 监控 YouTube Shorts:标题、播放量、点赞、评论、排名、话题标签、描述和字幕。
- 输入示例:
{"channel":"https://www.youtube.com/@Dior/shorts","max_videos":20}- 计费: 按结果付费(pay-per-result),价格见本页 Pricing 标签;可设置单次运行最大费用以控制支出。
- 支持: 遇到问题请在 Issues 标签提交,并附上输入参数和 Run ID。
Monitor YouTube Shorts from channels or direct Shorts URLs and extract titles, views, likes, comments, rankings, hashtags, descriptions, transcripts, and automation-ready trend signals.
Best for
- Social media teams tracking Shorts by channel or campaign
- Creator teams measuring short-form publishing velocity and engagement
- Trend researchers collecting hashtags, titles, and view signals
- Automation builders sending fresh Shorts records to Sheets, Make, Zapier, n8n, or dashboards
Quick start
Use a small, stable listing run first:
{"channel": "https://www.youtube.com/@Dior","max_videos": 5,"get_details": false,"include_channel_details": false,"extract_transcript": false,"max_comments_per_video": 0,"calculate_engagement": true,"batch_size": 1,"navigation_timeout_secs": 60,"video_timeout_secs": 10,"useApifyProxy": true}
Use a smaller enriched run when you need comments, channel details, or transcripts:
{"channel": "https://www.youtube.com/@Dior","max_videos": 3,"get_details": true,"include_channel_details": true,"extract_transcript": true,"max_comments_per_video": 5,"calculate_engagement": true,"batch_size": 1,"navigation_timeout_secs": 90,"video_timeout_secs": 20,"useApifyProxy": true}
Common workflows
- Trend monitoring: run daily on a list of channels and sort by views, hashtags, and engagement fields.
- Creator benchmarking: compare Shorts volume, ranks, views, likes, and comments across channels.
- Campaign tracking: scrape direct Shorts URLs and keep
sourceInput,rank, andscrapedAtfor repeatable reporting. - AI content research: enable transcript extraction on a small shortlist and feed titles, descriptions, hashtags, and transcripts into summarizers.
Useful input fields
| Field | Use |
|---|---|
channel | One YouTube channel or Shorts URL. |
channels | Batch multiple channels when you want a shared run. |
max_videos | Keep low for enriched runs. |
get_details | Opens each Short for richer metadata. |
include_channel_details | Adds channel-level metadata when available. |
extract_transcript | Best-effort transcript extraction. |
max_comments_per_video | Keep 0 for fast listing runs. |
batch_size | Lower values are slower but more stable. |
useApifyProxy | Recommended for cloud runs. |
Output fields
The dataset can include:
titleurlchannelNamechannelUrlviewslikescommentsrankhashtagsdescriptiondurationpublishedDateengagementRatequalityScoretranscriptscrapedAt
Settings that convert best
- First run:
get_details: false,extract_transcript: false,max_comments_per_video: 0. - Enriched run: keep
max_videossmall and raise volume only after a clean sample. - For scheduled monitoring, prefer several small runs over one large run.
- If timeouts occur, lower
max_videos,batch_size, comments, and transcript options.
Cost and runtime expectations
This Actor is pay-per-event. A small run is the best way to inspect output and estimate cost before scaling. Detail, comments, channel enrichment, and transcripts require extra browser work and can increase runtime.
Limitations
YouTube Shorts pages can hide exact metrics, comments, or transcripts and can change layout without notice. Transcript extraction is best effort. Keep source URLs and timestamps in downstream reports.
Support
If a run returns unexpected data, open an issue from the Actor page with the input used, the run ID, and the result you expected.