TikTok Shop Search Pro πŸ”₯ avatar

TikTok Shop Search Pro πŸ”₯

Pricing

from $8.00 / 1,000 results

Go to Apify Store
TikTok Shop Search Pro πŸ”₯

TikTok Shop Search Pro πŸ”₯

TikTok Shop scraper for keyword and region search. Extract product IDs, titles, brands, sellers, prices, ratings, reviews, SKU pricing, and ranking data in clean structured output for ecommerce research, competitor tracking, trend discovery, and product sourcing.

Pricing

from $8.00 / 1,000 results

Rating

4.5

(4)

Developer

Sentry

Sentry

Maintained by Community

Actor stats

1

Bookmarked

72

Total users

16

Monthly active users

7.9 days

Issues response

7 hours ago

Last modified

Share

TikTok Shop Search Pro Go

tiktok-shop-search-pro-go is the Go rewrite of the existing TikTok Shop search scraper.

It preserves the original actor’s core behavior:

  • search TikTok Shop by keyword and region
  • retry blocked or low-trust search responses with fresh HTTP sessions
  • extract embedded product payloads from hydrated page HTML
  • enforce the same query-token relevance filters
  • emit one dataset item per discovered product
  • return the same summary payload with resultsDatasetUrl

The Go port intentionally removes proxy configuration and does not use the guard library. All requests run through the built-in no-proxy HTTP client.

Input

Key inputs:

  • queries
  • searchRegion
  • maxPagesPerQuery
  • maxResultsPerQuery
  • includeRawProduct
  • compactNullFields
  • requestTimeoutSec
  • maxFetchRetries
  • queryRetryAttempts
  • failOnZeroAfterRetries
  • forceMaxPages
  • requireAllQueryTokens
  • minimumQueryTokenMatches

Output

Each dataset item contains normalized TikTok Shop product fields such as:

  • query
  • page
  • rank_on_page
  • rank_global
  • product_id
  • product_name
  • brand_name
  • seller
  • min_price
  • max_price
  • avg_price
  • product_rating
  • review_count
  • product_url
  • source_url
  • scraped_at

Optional:

  • raw_product

Notes

  • Proxy inputs are not exposed in the actor schema and are not used by the runtime.
  • Browser fallback and guard settlement flows are intentionally not part of this Go port.