YouTube Shorts Scraper for Trends & Channels avatar

YouTube Shorts Scraper for Trends & Channels

Pricing

from $35.00 / 1,000 shorts results

Go to Apify Store
YouTube Shorts Scraper for Trends & Channels

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

scraping automation

Maintained by Community

Actor stats

2

Bookmarked

68

Total users

3

Monthly active users

a month ago

Last modified

Share

Monitor YouTube Shorts from channels or direct URLs and extract titles, views, likes, rankings, hashtags, and engagement signals.

Who this is for

  • Short-form video researchers
  • Social media teams
  • Trend monitoring workflows

What it helps you do

  • Collect Shorts from channels or direct URLs
  • Rank videos by position and performance
  • Extract engagement and trend signals for dashboards

Inputs you can use

  • YouTube channel or Shorts URLs
  • Maximum videos
  • Comment and transcript options

Data you get

  • rank
  • video title
  • Shorts URL
  • views
  • likes
  • comments
  • hashtags
  • channel
  • engagement rate
  • scraped date

How to get better results

  • Start with a narrow, specific query or a small list of source URLs.
  • Use realistic limits for the first run, then increase the volume once the output looks right.
  • Keep source URLs, dates, and location context when you need repeatable market monitoring.
  • Review a few sample records before connecting the dataset to a larger workflow.

Notes

  • Results depend on what the public source exposes at run time.
  • Some pages may hide, delay, rename, or remove fields, so individual records can have partial data.
  • Use the built-in output table to inspect results before exporting to spreadsheets, dashboards, or automation tools.

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.