Glowpick Scraper — K-Beauty Product Rankings & Ratings

Scrape Korean beauty product rankings from Glowpick (글로우픽) — Korea's leading consumer-driven beauty ranking site, built on hundreds of thousands of real user reviews. Point it at Glowpick's category ranking pages and get back clean, structured JSON for every ranked product: rank, product name, brand, category, star rating, review count, KRW price and image.

Glowpick rankings are decided by ordinary Korean beauty consumers, not by what a store is pushing — a review-driven "what Korea actually rates highest" signal. If you need to know which K-beauty products are winning by category in Korea right now, this is the source.

Privacy-first. No personal data is ever collected — no reviewer names, IDs, or profiles. Product, brand, ranking, rating, and price data only.

Try it free. Apify's free plan includes $5 of monthly platform credit — roughly 2,000 results from this actor, no credit card required. Set your input, click Start, and export JSON/CSV/Excel.

---

What it does

• Reads Glowpick's public, server-rendered category ranking pages (glowpick.com/categories/<id>?monthTerm=<n>) — works from most IPs, including datacenter.
• Extracts each ranked product from the page's embedded JSON-LD ItemList (rank, name, rating, review count, image, URL), reads the category label from the breadcrumb, and enriches brand + KRW price from the page's inline app data.
• Emits one clean record per product against a stable schema.

Input

Field	Type	Default	Description
categoryIds	string[]	popular set	Glowpick category IDs (the number in glowpick.com/categories/<id>). Empty = a built-in default set of popular categories. E.g. 100 Hair, 44 Suncare, 88 Skin health, 96 Men's cosmetics. Each category yields its ranked TOP-20.
monthTerm	string	"24"	Ranking time window in months (3, 6, 12, 24). 24 = Glowpick's default long-window ranking.
maxProducts	integer	100	Max products to scrape across all requested categories.
proxyConfiguration	object	none	Optional. Not required for ranking data.

Input example

{
  "categoryIds": ["100", "44", "88"],
  "monthTerm": "24",
  "maxProducts": 100
}

Output

One dataset item per product. This is real output from a live run (see samples/sample-output.json for 40 real records):

{
  "source": "glowpick",
  "product_id": "129745",
  "name": "데일리 볼륨 업 컬 크림",
  "brand": "다슈",
  "category": "헤어",
  "rank": 1,
  "rating": 4.38,
  "review_count": 80,
  "award": null,
  "price_krw": 25000,
  "url": "https://www.glowpick.com/products/129745",
  "image_url": "https://dn5hzapyfrpio.cloudfront.net/product/381/38121550-85a5-11ec-9239-3145a1882625.jpeg",
  "scraped_at": "2026-07-09T10:06:34+09:00"
}

Field notes

• product_id — Glowpick's stable product identifier (from the product URL).
• rank — 1-based position within the category ranking.
• rating / review_count — average star rating (1–5) and number of reviews behind it, straight from Glowpick's aggregate rating. Together these are the core "what Korea actually rates highly" signal.
• brand — brand name (Korean). Populated for every ranked product.
• price_krw — retail price in KRW when Glowpick lists one; null when no price is shown (e.g. discontinued items).
• category — the category label of the ranking (Korean leaf name, e.g. "헤어", "선젤").
• award — always null (see the known limitation below).

Use cases

• Market research for K-beauty market entry — pull the current top-rated products by category with real ratings, review counts and KRW prices before launching a competing SKU.
• Trend tracking — snapshot the rankings on a schedule to see what's rising and falling in Korean consumer favor over time.
• Pricing & dropshipping — track top K-beauty products by category and their KRW price.
• AI agents / analytics — a clean, PII-free ranking feed that drops straight into an LLM or BI pipeline with no PII to scrub.

Proxy & rate limits

The ranking data — the product this actor sells — reads from Glowpick's server-rendered JSON-LD and inline app data, and works from most IPs, including datacenter (the 40-record sample here was produced with no proxy). A residential proxy is only worth enabling for high-volume runs. The actor runs politely: effectively concurrency 1 with ≥600 ms between requests, and if a proxy tunnel hangs it retries directly so a bad tunnel never hangs the run.

Known limitation — award badges & review text (not currently sold)

• Award badges. Glowpick runs annual beauty awards, but the category ranking pages do not carry a per-product award badge, so the award field is always null. It is kept in the schema for contract stability but the actor is not sold on award data.
• Review text & ingredients. Full review text and ingredient lists live on separate detail views and are not part of this actor. Review text on Glowpick is also tied to reviewer profiles, so — per our privacy rule — it is intentionally not collected. This actor is sold on its ranking, rating, review-count, brand and price data, which are reliable and PII-free.

Legality & data ethics

• Only public ranking data is collected — no login, no private endpoints. Glowpick's robots.txt disallows /api, /profiles, /searches and /webview; this actor touches none of them — it reads only the public category ranking pages.
• No personal data. Reviewer names, IDs, and profiles are never read or stored.
• You are responsible for using the output in compliance with Glowpick's terms and applicable law. Because no personal data is emitted, output is safe to feed directly into analytics and LLM pipelines.

❓ FAQ

Is it legal to scrape this data? This actor collects only public, non-personal catalog data — the same category rankings any visitor sees without logging in. No personal data is collected. You are responsible for how you use the data; see the legality note above.

What does it cost in practice? $2.50 per 1,000 results (launch pricing) + a few cents of platform usage. Example: a 500-result daily pull costs about $1.25/day. Apify's free $5 monthly credit covers ~2,000 results.

Do I need to configure proxies? No — the default settings work out of the box (the sample data here was produced with no proxy). A residential proxy is optional and only worth enabling for high-volume runs.

How fresh is the data? Every run scrapes the live site at run time. Schedule the actor for recurring snapshots.

What is NOT included? Award badges (the award field is always null — ranking pages don't carry them) and full review text / ingredient lists, which live on separate detail views and are intentionally not collected because review text is tied to reviewer profiles. This actor is sold on its ranking, rating, review-count, brand and price data.

🇰🇷 More Korean data actors

This actor is part of a suite of Korean-platform scrapers by the same maintainer:

• hwahae-scraper — Hwahae cosmetics rankings and ingredient-safety data.
• oliveyoung-scraper — Olive Young best-seller rankings and product prices.

Browse all: apify.com/kdatafactory

Local development

npm install
# put input in ./storage/key_value_stores/default/INPUT.json, then:
npm start   # results land in ./storage/datasets/default

# polite lite test against the live site (<=2 categories, ~40 products):
GLOWPICK_SCRAPER_LITE_TEST=1 npm start

---

If this actor saves you time, a rating on the Store page helps a solo maintainer a lot. Found an issue? Open it in the Issues tab — I respond fast.