Which Platforms Can SignalQub Scrape Data From?
SignalQub currently supports scraping public data from four platforms: Reddit, Google Maps, YouTube, and TikTok. All four are covered by the same zero-auth approach — no login, no proxy management, and no risk of account bans — and results come back as structured JSON. The scope is limited to publicly visible data on those platforms; anything behind a login is out of reach.
Supported Platforms at a Glance
| Platform | Data type | Auth required | Output |
|---|---|---|---|
| Public posts and related public content | No | JSON | |
| Google Maps | Public place/business listings | No | JSON |
| YouTube | Public video data | No | JSON |
| TikTok | Public video data | No | JSON |
What "Zero-Auth" Changes About Coverage
Because SignalQub never logs in, the boundary of what it can return is defined by what each platform shows to a logged-out visitor. That has two practical consequences:
- No private or account-gated data. Content visible only after signing in — private subreddits, personalized feeds, saved items, account-specific views — is not part of the dataset.
- No account or proxy overhead. You don't supply credentials, rotate proxies, or worry about a scraping account getting banned, since there is no account involved.
For most public-data use cases — monitoring public sentiment, collecting public business listings, or tracking public video metrics — this covers the material you'd otherwise have to log in to see.
Choosing Between the Four Platforms
Pick based on where the data you need actually lives, not on volume:
- Reddit — public discussion and community content.
- Google Maps — public place and business information.
- YouTube — public video data.
- TikTok — public video data.
If your target data sits on a platform outside this list, or requires authenticated access, SignalQub is not the right fit for that portion of the task.
Verifying Coverage Before You Build
The fastest check is to run one small request against the platform you care about and confirm the JSON fields match what your pipeline expects. If a field you need isn't present, it's usually because that field is only exposed to logged-in users — a scope limit, not a configuration issue.
Pricing and any request limits are not specified in the available site information, so confirm those directly with SignalQub before committing to a high-volume workflow.