Fragrantica.com Scraper
Pricing
Pay per usage
Fragrantica.com Scraper
Scrape Fragrantica for perfume reviews, ratings, fragrance notes & prices. Extract competitor data for ecommerce, market research & trend analysis. Build comprehensive fragrance datasets instantly.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Shahid Irfan
Actor stats
0
Bookmarked
6
Total users
2
Monthly active users
10 days ago
Last modified
Categories
Share
Fragrantica Designer Perfume Scraper
Extract and collect structured perfume data from Fragrantica designer pages in a fast, reliable, automated way. Gather fragrance listings, ratings, reviews, popularity signals, and localized perfume links into a clean dataset for research, analysis, and monitoring. Built for fragrance catalog teams, market intelligence workflows, and competitive tracking.
Features
- Designer-focused extraction — Collect perfume listings from designer pages like Zara, Dior, Chanel, and more.
- Clean structured records — Get normalized fields for names, URLs, IDs, release years, ratings, and review counts.
- Extended popularity metrics — Gather multiple popularity and pageview signals for deeper analysis.
- Flattened locale links — Receive locale URL fields such as
url_en,url_de, and locale review counters. - Pagination handling — Automatically continues through available pages until your
results_wantedtarget is reached. - Duplicate-safe output — Prevents duplicate perfume records and removes empty/null values before saving.
Use Cases
Fragrance Catalog Management
Build and refresh internal perfume catalogs from designer pages without manual copy-paste. Keep records searchable and consistently formatted for product and content teams.
Market Research
Track brand portfolio size, release timelines, and community engagement indicators. Compare how strongly different fragrances perform across reviews and rating signals.
Competitive Intelligence
Benchmark multiple designer pages to identify high-interest launches and strong performers. Use collected data to spot positioning differences between fragrance brands.
Trend Monitoring
Monitor recurring popularity patterns and new releases over time. Feed ongoing runs into dashboards for weekly or monthly fragrance trend reporting.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
startUrl | String | Yes | https://www.fragrantica.com/designers/Zara.html | Fragrantica designer page URL to start extraction. |
results_wanted | Integer | No | 20 | Maximum number of perfume records to collect. |
proxyConfiguration | Object | No | {"useApifyProxy": false} | Optional proxy settings for higher-volume or restricted environments. |
Output Data
Each dataset item contains structured perfume and designer information.
| Field | Type | Description |
|---|---|---|
designer_name | String | Designer or brand name. |
designer_url | String | Source designer page URL. |
designer_parent_company | String | Parent company when available. |
designer_slug | String | Designer slug value. |
designer_is_niche | String | Niche marker when available. |
designer_is_celebrity | String | Celebrity marker when available. |
designer_is_natural_perfumery | String | Natural perfumery marker when available. |
designer_total_perfumes | Number | Total perfumes found for the designer. |
designer_first_year | Number | Earliest detected perfume year. |
designer_latest_year | Number | Latest detected perfume year. |
perfume_name | String | Perfume name. |
perfume_url | String | Canonical perfume URL. |
perfume_id | Number | Perfume identifier. |
image_url | String | Perfume image URL. |
year | Number | Release year when available. |
gender | String | Gender label. |
reviews_count | Number | Primary review count. |
rating_value | Number | Rating value. |
rating_rounded | Number | Rounded rating bucket. |
popularity_score | Number | Overall popularity score. |
recent_popularity_score | Number | Recent popularity signal. |
source_index | String | Source collection identifier. |
source_page | Number | Source page number for the item. |
source_object_id | String | Source object identifier. |
perfume_slug | String | Perfume slug value. |
collection | String | Collection name when present. |
group_id | Number | Group identifier when present. |
pageviews_7d | Number | 7-day pageview signal. |
pageviews_30d | Number | 30-day pageview signal. |
pageviews_90d | Number | 90-day pageview signal. |
popularity_compound_score | Number | Compound popularity metric. |
url_* | String | Flattened locale URLs (for example url_en, url_fr). |
reviews_* | Number | Flattened locale review counts (for example reviews_en, reviews_fr). |
Usage Examples
Basic Extraction
{"startUrl": "https://www.fragrantica.com/designers/Zara.html","results_wanted": 20}
Larger Collection Run
{"startUrl": "https://www.fragrantica.com/designers/Zara.html","results_wanted": 100}
Proxy-Assisted Run
{"startUrl": "https://www.fragrantica.com/designers/Zara.html","results_wanted": 100,"proxyConfiguration": {"useApifyProxy": true}}
Sample Output
{"designer_name": "Zara","designer_url": "https://www.fragrantica.com/designers/Zara.html","designer_parent_company": "Inditex","designer_slug": "Zara","perfume_name": "Sunrise On The Red Sand Dunes","perfume_url": "https://www.fragrantica.com/perfume/Zara/Sunrise-On-The-Red-Sand-Dunes-79102.html","perfume_id": 79102,"image_url": "https://fimgs.net/mdimg/perfume/m.79102.jpg","year": 2023,"gender": "male","reviews_count": 304,"rating_value": 4.288,"rating_rounded": 4,"popularity_score": 15394,"recent_popularity_score": 6320,"source_index": "fragrantica_perfumes","source_page": 1,"source_object_id": "79102","perfume_slug": "Zara/Sunrise-On-The-Red-Sand-Dunes","collection": "Men's Collection 2023","group_id": 23,"pageviews_30d": 31062,"url_en": "https://www.fragrantica.com/perfume/Zara/Sunrise-On-The-Red-Sand-Dunes-79102.html","reviews_en": 304,"designer_total_perfumes": 1201,"designer_first_year": 2012,"designer_latest_year": 2025}
Tips for Best Results
Use Valid Designer URLs
- Use URLs matching
/designers/Brand-Name.html. - Start with a known working designer page before scaling.
Scale Gradually
- Begin with
results_wanted: 20for validation. - Increase to
100or higher after confirming output quality.
Work with Locale Fields
- Locale fields are flattened (
url_*,reviews_*) for easier filtering. - Keep these fields in downstream exports for multi-language analysis.
Use Proxy When Needed
- Enable proxy settings for larger runs or restricted environments.
- Keep your run configuration consistent across scheduled jobs.
Proxy Configuration
{"proxyConfiguration": {"useApifyProxy": true}}
Integrations
Connect the output dataset with:
- Google Sheets — Share and review fragrance records with non-technical teams.
- Airtable — Build searchable fragrance databases with custom views.
- Make — Trigger automated post-processing flows after each run.
- Zapier — Send records into CRM, alerts, and business workflows.
- Webhooks — Deliver fresh data directly into your own systems.
Export Formats
- JSON — Best for APIs and engineering pipelines.
- CSV — Best for spreadsheet workflows.
- Excel — Best for business reporting.
- XML — Useful for structured enterprise integrations.
Frequently Asked Questions
What pages are supported?
Designer pages on Fragrantica are supported. Use a designer URL as startUrl.
Can I collect more than 30 results?
Yes. Pagination is handled automatically, and the actor keeps collecting until results_wanted is reached or data is exhausted.
Can I collect 100+ records in one run?
Yes. Set results_wanted to 100 (or higher) and the actor will continue across source pages.
Are locale URLs flattened in output?
Yes. Locale URLs and locale review counters are provided as flat fields like url_en and reviews_en.
Will empty values be stored?
No. Empty and null-like values are removed before items are saved to the dataset.
How can I reduce blocked runs?
Use proxyConfiguration, keep input URLs valid, and start with smaller validation runs.
Support
For issues or feature requests, use the Apify Console issue/support channels for this actor.
Resources
Legal Notice
This actor is intended for legitimate data collection and analysis workflows. You are responsible for complying with website terms, local laws, and applicable data-use policies.