This tutorial shows how to scrape LIPSCOSME reviews to CSV with the LIPSCOSME Comments Scraper template for UScraper. You will import the workflow, replace sample review URLs, set the export path, validate rows, and fix common layout issues.
Baseline
Prerequisites and compliance checks
You need the UScraper local desktop app, the free template JSON from the UScraper template library, a permitted list of LIPSCOSME product review pages, and a folder for the CSV. Start with the bundled sample product first. Its Navigate block covers four review-page URLs, which is easier to audit than an open-ended crawler.
Before collecting user-generated cosmetics reviews, read the current LIPSCOSME terms, privacy policy, and robots.txt. Public pages can still be governed by site rules, copyright, database rights, privacy law, and your own customer or research obligations.
Treat review comments as research input, not raw material to republish. Export only what your project needs, keep the run size modest, and stop if LIPSCOSME shows a CAPTCHA, login wall, consent screen, or block page.
Workflow
How the LIPSCOSME comments scraper works
The workflow is intentionally small: Navigate -> Wait for Page Load -> Wait for Element -> Structured Export -> Loop Continue. Navigate owns the finite URL list, Wait for Element confirms that .PostListMedium__item review rows exist, Structured Export treats each visible comment card as one row, and Loop Continue advances to the next review page.
LIPSCOSME review pages are rendered experiences, not stable CSV feeds. A supervised browser workflow lets you confirm that comments are on screen before you trust the export.
Runbook
How to scrape LIPSCOSME product reviews
Import the template
Open LIPSCOSME Comments Scraper, download the JSON, and import it into UScraper.
Review the sample URLs
Keep the bundled product pages for a first test, or replace them with a short approved list.
Set the export path
In Structured Export, confirm lipscosme-comments-scraper.csv, headers enabled, append mode, and a product-specific save folder.
Run one page while watching
Execute a single URL first. Confirm that review cards appear, images load when present, and the page is not replaced by a prompt or verification screen.
Validate before scaling
Open the CSV, compare several rows against the browser, then expand the URL list only after the selectors and row counts look sane.
Output
LIPSCOSME comments CSV fields
No CSV sample ships with the bundle, so the workflow JSON is the authoritative sample. The export shape is one row per visible review card.
| Field group | Columns | Validation tip |
|---|---|---|
| Reviewer context | reviewer_tag_1, reviewer_tag_2, reviewer_tag_3 | Tags can be age range, skin type, tone, or gender labels when visible. |
| Engagement | number_of_likes, number_of_quote | Compare counts against the card footer. Empty can be normal. |
| Comment body | publishing_date, review_brief, review_url | Spot-check dates, text cleanup, and source page URL. |
| Images | picture_url_1, picture_url_2, picture_url_3 | Add a longer wait only if image URLs are required. |
The shortened JSON excerpt below shows the workflow definition that drives those fields. Download the full template when you need complete block positions and connections.
{
"project": {
"name": "LIPSCOSME Comments Scraper"
},
"blocks": [
{
"title": "Navigate",
"config": {
"urls": [
"https://lipscosme.com/products/497682/review",
"https://lipscosme.com/products/497682/review?page=2"
]
}
},
{
"title": "Wait for Element",
"config": {
"selector": ".PostListMedium__item",
"timeout": 30,
"visible": true
}
},
{
"title": "Structured Export",
"config": {
"rowSelector": ".PostListMedium__item",
"fileName": "lipscosme-comments-scraper.csv",
"fileMode": "append",
"columns": [
{ "name": "reviewer_tag_1", "isJs": true },
{ "name": "number_of_likes", "selector": ".PostListMedium__info-like" },
{ "name": "publishing_date", "selector": ".PostListMedium__info-published_at" },
{ "name": "review_brief", "isJs": true },
{ "name": "review_url", "isJs": true },
{ "name": "picture_url_1", "isJs": true }
]
}
}
]
}
Validation
Common issues when extracting LIPSCOSME reviews
Most failed exports are visible before you open the CSV. Keep the browser in view during early runs and treat blank cells as debugging signals.
| Symptom | Likely cause | Fix |
|---|---|---|
| No rows exported | Review cards did not render or selector drifted | Open the URL manually and confirm .PostListMedium__item still exists. |
| Review text is short | The visible excerpt is all that rendered | Accept the brief field or add a supervised expand step after testing. |
| Image URLs are blank | Review card has no image or images lazy-loaded late | Add a wait or scroll step only if images are necessary. |
| Duplicate rows | Same URL list was rerun in append mode | Start a new file or dedupe before analysis. |
| Run stops mid-list | Prompt, rate limit, or block screen appeared | Pause, reduce scope, and review policy before retrying. |
Alternatives
When to use UScraper instead of hosted tools
Use UScraper when you want a lipscosme comments scraper with no-code editing, browser validation, and CSV output. Hosted options help with API calls, schedules, or infrastructure, but add vendor setup, metered usage, and third-party custody. Custom code is better for tests, retries, database writes, or a maintained pipeline.
For adjacent datasets, pair this comments workflow with the LIPSCOSME Product Info Scraper, browse more templates in Templates, or read other workflow guides in the UScraper blog.
FAQ
LIPSCOSME comments scraper FAQ
Public visibility does not automatically grant permission for automated collection. Review LIPSCOSME terms, privacy rules, robots guidance, copyright, database rights, and local law. Keep batches modest and do not bypass access controls.
Next step
Download the LIPSCOSME comments scraper template
Open the LIPSCOSME Comments Scraper template, import the JSON into UScraper, and run one product review page before widening the page list. Use Templates and the Blog for adjacent workflows.