YouTube Hashtag Video & Shorts Scraper
Pricing
from $2.99 / 1,000 hashtag videos & shorts
YouTube Hashtag Video & Shorts Scraper
Collect current YouTube hashtag videos and Shorts through YouTube browse continuations, with source-provided metadata.
Pricing
from $2.99 / 1,000 hashtag videos & shorts
Rating
0.0
(0)
Developer
w3crawler
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 hours ago
Last modified
Categories
Share
Collect rich public video and Shorts observations for one or more hashtags. The actor queries ordinary public YouTube search pages with the hashtag as the query, parses embedded public page metadata, and does not use private clients, browser automation, or continuation APIs.
Input
| Field | Default | Description |
|---|---|---|
hashtags | — | Required; 1–50 tags, with or without #. |
maxItems | 20 | Maximum unique records per hashtag, 1–200. |
locale | en-US | Public page language-country locale. |
enableProxyFallback | true | Try account-authorized Apify Proxy after direct access fails. |
requestDelayMs | 250 | Delay between hashtag requests, 0–5000 ms. |
requestTimeoutSecs | 60 | Public request timeout, 15–180 seconds. |
proxyConfiguration | — | Optional standard Apify Proxy configuration; proxy URLs must be credential-free. |
Example:
{"hashtags": ["travel", "food"],"maxItems": 10,"locale": "en-US","enableProxyFallback": true}
Dataset fields
Each row contains the hashtag, normalized tag, per-tag rank, video/short type, video ID, title, description and length, canonical watch/Shorts URLs, public thumbnail set, displayed and parsed view counts, duration and seconds, channel identity, verification/badge flags, publication label, query/page provenance, locale, extraction method, and scrape time. The OUTPUT key-value record contains counts, request coverage, proxy state, failures, and timings.
A zero-result hashtag is reported as NO_HASHTAG_RESULTS in logs and summary counts, with no dataset row. Empty completed searches remain successful; actual failures with no usable records fail the run.
Run locally with apify run --purge --input-file qa-inputs/youtube-hashtag-video-shorts-scraper/local-validation.json, inspect storage/datasets/default/, and run npm run validate-dataset. Deploy with apify push and verify the direct and proxy QA calls.