Budget: 25 USD Deadline: 1 day
Good day. I would like to know which websites need to be parsed. This depends on whether I will take on the task.
Looking for a freelance developer to create one-time scrapers for 5 Israeli websites.
We provide proxies and anti-captcha if needed.
The scrapers are currently needed as a one-time task, but it is important to build the architecture in such a way that it can easily be turned into a permanent, regularly working parser in the future.
Budget: 25 USD Deadline: 1 day
Good day. I would like to know which websites need to be parsed. This depends on whether I will take on the task.
Budget: 500 USD Deadline: 7 days
Ready to complete the task of developing 5 scrapers for Israeli websites.
I have been working with parsing for over 10 years, including complex resources with anti-bots, Cloudflare, and dynamic content.
🔧 How I will implement the task
I will create the scrapers not as a "one-time script," but as modules with an architecture prepared for further regular parsing:
language: Python
libraries: Playwright / Requests, if necessary – Selenium
support for proxies and anti-captcha (you provide, I connect)
processing dynamic content and bypassing basic Cloudflare checks
auto-retries, error logging, request rate limiting
a single configuration file for all 5 scrapers
📦 Format of the result
At your choice:
JSON / CSV
database (PostgreSQL / MySQL)
export to Google Sheets
a structure with fields that we will agree on in advance
🧩 Architecture for the future
I will immediately prepare:
separate modules for each site
a unified class for launching and processing
the ability to easily connect cron, n8n, or any scheduler
documentation: how to run, where to change parameters, how to add new sites
If necessary, I can provide limited support for 1 month for minor adjustments when the layout changes.
❓To get started, I need
links to 5 websites
a list of fields to extract
data storage format
After that, I will provide exact deadlines and break down the task into stages.
Budget: 25 USD Deadline: 1 day
Good day!
I am ready to develop scrapers for 5 websites.
I write in Python (Scrapy/Playwright). I will immediately lay down the correct modular architecture: the logic of requests, HTML parsing, and data export will be separated.
This will allow for easy translation of the script into a regular running mode (CRON/Serverless) in the future without rewriting the core.
There will be no problems with connecting your proxies and anti-captcha.
Send me the list of websites — I will assess the complexity of protection and deadlines.
Budget: 100 USD Deadline: 2 days
Good day, I have done a lot of parsing, I write in Python, I can also do automation if necessary. I use both parsing with requests and the Selenium library. I would be happy to discuss the details and start collaborating. I will do it quickly and efficiently!
Budget: 25 USD Deadline: 1 day
Hello. I have extensive experience in parsing of various complexity.
Can I see the links on the website to assess the complexity and cost?
Thank you.
Budget: 300 USD Deadline: 4 days
Hello. I am a specialist in web scraping and automation! I am ready to complete this project. Write to me in private messages.
Budget: 750 USD Deadline: 7 days
Good day. I am ready to work on your task. I will need links to the websites that need to be parsed and in what format to store the result. Thank you.
Budget: 300 USD Deadline: 10 days
Ready to cooperate.
Exact price and terms after more detailed information.
Budget: 44 USD Deadline: 10 days
Good day
Send the websites, we will discuss
I will make it so that they can be installed on the server or PC immediately
Budget: 25 USD Deadline: 1 day
Hello!
I am ready to perform scraping for 5 Israeli websites. I have worked with large parsers (including a project with over 1 million products, 86 categories), so I know how to build the architecture in a way that can be easily translated into a regular, automated parser.
I use proxy rotation, anti-captcha, proper error handling, request queues, caching, and anti-ban approaches.
I can create one-time scrapers and immediately lay the structure for further cron/auto-update.
Please let me know which specific websites — I will assess the timelines and price.
Budget: 200 USD Deadline: 5 days
Hello! I have extensive experience in creating various parsers and programming in general. I will do it quickly and efficiently as much as possible. I also promise to always be in touch and support the project in the future if needed. Feel free to reach out!
Budget: 50 USD Deadline: 1 day
Hello.
I am a NodeJS developer. I am ready to take on the task. Write to me, we will discuss.
Budget: 300 USD Deadline: 3 days
Hello!
I am ready to take on the development of scrapers for your Israeli websites. I have extensive experience in web scraping — I have scraped over 50 different websites, including those with various levels of protection (dynamic content, anti-bot, CAPTCHAs, non-standard structures).
I work with proxies, anti-CAPTCHA, headless browsers, and I can build the structure in a way that will allow for easy scaling of the solution into a permanent parser/crawler in the future.
I create each scraper as a module — with the ability for regular execution, logging, retries, anti-ban mechanics, and convenient export (JSON/CSV/XLSX/DB).
I am ready to discuss the details for each of the 5 websites and start working.
Budget: 300 USD Deadline: 5 days
Good day, Slava!
In general, the task is clear, but for an accurate response regarding deadlines and price, I would like to clarify some questions that arose after analyzing your task.
Please write in private messages — we will discuss the details and your wishes.
Budget: 500 USD Deadline: 5 days
Good afternoon
please provide links to the sources, specify what exactly we are parsing, the exact list of fields, in what format we are saving. according to what principle we are parsing - all records, certain categories. for a certain period, other filters - will depend on the specifics of the parsing entities
very extensive experience, I will send links to hundreds of reviews
Hello! I am looking for a performer for ongoing collaboration who is knowledgeable about Opencart. A person who is available and has a positive attitude) Parsing, uploading products in two languages UA + ru, as well as forming the necessary markup immediately I want to complete the work in several stages. 1. Update stock for all suppliers and completely remove outdated products from the site and database. 2. Refinement of the product category, specifically parsing subcategories. 3. Parse new items in old categories. 4. Parse new suppliers into new categories.
A project needs to be implemented for collecting and structuring a large array of images from open web sources (initially 2000 images). The task includes: - automated image collection; - uploading files in the highest available quality; - classifying images by categories. Expected results: - a structured image database; - a clear cataloging system; - delivery of the results via Google Drive or another agreed method;
Good day! Two tasks need to be completed: 1. Develop a product parser from an external website (10–40 thousand items, marketplace) with structured data saved in MySQL for subsequent output in WordPress. 2. Install and configure n8n on VPS, as well as organize AI content processing: prompt setup, text rewriting, image processing, SEO optimization, and text checking for AI detection. You can estimate the cost of completing both the entire project and each task separately. .
It is necessary to perform parsing from Viber channels (Total number - 49 channels, about 80 thousand subscribers).
Task: one dashboard with all business metrics — advertising, funnel, payments, manager performance, revenue planning. Data is pulled automatically via API. Scope: only the YCL direction (employment in Europe). Kommo has other directions — only YCL funnel deals will be included in the repository (filter by funnel/tag to be agreed upon).1. Data Sources (Integrations) Kommo CRM — leads, deals, funnel stages, responsible persons, sources, dates of transitions between stages (must keep history), reasons for refusals, custom deal fields (see point 2). Stripe — payments, amounts, statuses (success/failure/refund), linked to deals. Meta Ads — expenses, impressions, clicks, CPL, leads by campaigns (currently operational). Google Ads, Reddit Ads, LinkedIn Ads — planned; architecture — extensible connectors without core rework. SEO/organic— Google Search Console + GA4. Cross-link: traffic source → lead in Kommo → payment in Stripe (UTM, deal ID in Stripe metadata — propose the mechanism). 2. Mandatory Cuts (Deal Fields in Kommo) Each metric must be filtered/grouped by: Client Citizenship (Kenya, Nigeria, India, etc.). Residence Status: lives in their country / expat (already in Europe). These are two different segments with different cycles, conversion rates, and checks. Country of Placement / Service: Poland, Serbia, Slovakia, Germany (ZAV). Manager, team, traffic channel, period. If any fields are missing in Kommo — the executor indicates which fields need to be added, the client adds them.3. Funnel and Leading Indicators Data by funnel, for each stage — summary and leading metrics: Traffic → lead: leads, CPL by channels + day-to-day expense/click dynamics. Lead → qualification: conversion + first response speed, touches/calls to the manager per day, unanswered leads. Qualification → contract/invoice: conversion + sent offers, stalled deals (days in stage above norm). Invoice → payment: payments, average check + unpaid invoices, failed payments. Summary: revenue, ROMI by channels, run rate to monthly plan. 4. Deal Cycle Average and median lead → payment cycle (business benchmark ~4 weeks), cycle trend over time. Breakdown of cycle by stages (how many days a deal sits at each stage) — to see which stage is dragging. List of deals that have stalled at a stage longer than normal. Cycle breakdown by segments: citizenship, residence status, country of placement, manager. 5. Early Warning of Decline (Key Block) Since the cycle is ~4 weeks, today's leads = payments in a month. The system must: Compare leads/qualifications of the current week with the moving average (4 weeks) and issue an alert if there is a downward deviation: “leads -X%, with a 4-week cycle expect a payment decline in the week [date].” Build payment forecast for 4 weeks ahead from the current pipeline: deals at each stage × historical conversion of the stage × remaining cycle. Highlight in red weeks where the forecast is below plan — with time to react. 6. Additional Payments and Sales Planning In the Kommo deal card, the date and amount of the planned additional payment are stored. The system must: Collect a calendar of upcoming additional payments: total expected, by weeks/months. Highlight overdue additional payments (date passed, no payments in Stripe) — a separate list for follow-up. Calculate the monthly plan as: plan − already paid − scheduled additional payments = how many new sales are needed (in money and in deal units at average check). Weekly schedule: additional payments + forecast of new payments against the weekly plan. 7. Manager Performance Daily snapshot for each manager: touches/calls, conversations, sent offers, payments — for each day separately, with a chart over the period. Progress on personal plan compared to monthly pace (ahead / on pace / behind). Benchmarking with colleagues. 8. Visualization and Roles “Traffic lights” (green/yellow/red) for key metrics relative to norms/plans; progress scales; trend graphs; mobile adaptive. Roles: CEO — everything; COO — entire funnel and managers; team lead — their team; manager — their metrics and position relative to colleagues. 9. Reports and AI Automated reports on schedule (daily summary, weekly report) in the dashboard and/or messenger. Free-form queries (“how has CPL from Meta changed over 2 weeks?”) — LLM over the repository. Alerts in the red zone and according to the rules from points 5–6. 10. Technical Expectations and Staging Repository (PostgreSQL/BigQuery or equivalent) + ETL: Kommo webhooks + periodic synchronization (15–60 min). Frontend: custom or BI tool — propose with justification; requirements for roles, traffic lights, forecasts, and AI queries must be implementable. Stages: (1) audit and metrics map → (2) MVP: Kommo + Stripe + Meta, funnel, traffic lights, roles → (3) deal cycle, early warning, additional payments and plan → (4) SEO, AI reports, alerts → (5) new advertising channels. Payment is staged, with a demo for each stage. In the response, indicate: similar projects (end-to-end analytics), stack with justification, timeline and cost estimates by stages, monthly ownership cost (hosting, tokens, licenses).