YouTube Hashtag Generator
Pricing
from $2.99 / 1,000 hashtags
YouTube Hashtag Generator
Collect currently observed YouTube hashtag signals from autocomplete and YouTube search pages. Evidence is retained with every result; ranks are evidence ranks, not popularity claims.
Pricing
from $2.99 / 1,000 hashtags
Rating
0.0
(0)
Developer
w3crawler
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Evidence-backed Public YouTube Hashtag Signals
Collect hashtags currently observed in YouTube's public autocomplete response or public search-page HTML. The actor keeps the exact observation behind each result and ranks by the number of distinct public signal types and observations. It does not estimate search volume, invent tags, or claim popularity/trending status.
Input
| Field | Default | Description |
|---|---|---|
topics | — | Required; 1–20 distinct topics, 2–120 characters. |
locale | en-US | Public page locale, such as en-US, hi-IN, or fr. |
limit | 20 | Maximum evidence-backed hashtags per topic, 1–50. |
includeDiagnostics | true | Emit exact four-field diagnostics for failed requests. |
enableProxyFallback | true | Try account-authorized Apify Proxy after direct access fails. |
maxRetries | 2 | Bounded retry attempts per public request. |
requestDelayMs | 250 | Delay between 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:
Each dataset row includes the topic, normalized hashtag, evidence rank/details, distinct signal sources, observation counts split between autocomplete and search HTML, public evidence URLs and timestamps, locale, and extraction/source metadata. The OUTPUT key-value record contains request, item, proxy, failure, and timing counts. Diagnostics contain only url, error, errorCode, and scrapedAt.
Run locally with apify run --purge --input-file qa-inputs/youtube-hashtag-generator/local-validation.json, inspect storage/datasets/default/, and run npm test and npm run validate-dataset. Deploy with apify push, then verify direct and proxy cloud calls.
