Budget: 2000 UAH Deadline: 2 days
Good day! I will create a parser in Python + BeautifulSoup that will collect names, ratings, the number of reviews from Google and Tripadvisor, as well as links to establishments from the entire section and all pagination pages. The result will be a neat Excel file, ready for use.
Budget: 1600 UAH Deadline: 3 days
Good day. The cost depends on whether you need the data or the parser itself. I indicate the cost for the parser; for the data, it will most likely be more.
Budget: 2000 UAH Deadline: 2 days
I can do this today-tomorrow
______________________________________
Budget: 2000 UAH Deadline: 7 days
Hello, I worked on a parser for collecting data from restaurant websites - I gathered information about 2500+ establishments with ratings and reviews in 3 days.
Do you also need to collect additional information about the establishments, such as addresses, phone numbers, or hours of operation?
I suggest we get in touch; I will provide you with free technical advice and we can create a development plan + I will tell you about my team!
Budget: 2000 UAH Deadline: 1 day
Good day! I can do it right now. I will be happy to collaborate — feel free to reach out!
Budget: 7000 UAH Deadline: 7 days
I will perform this task better than anyone else because I have extensive experience in parsing complex catalogs with dynamic content, bypassing anti-bot protections, and exporting structured data to Excel. My architecture ensures maximum accuracy: correct recognition of Google/Tripadvisor ratings even with partial data absence, automatic pagination handling, and uniqueness of entries. You will receive a clean, analysis-ready dataset without duplicates and errors, with a clear column structure.
Work plan:
1. Site structure analysis: studying HTML markup, identifying CSS selectors for establishment names, ratings, number of reviews, links, checking the pagination mechanism.
2. Parser setup: choosing the technology stack (Python/Scrapy or Playwright), configuring requests with User-Agent rotation, handling dynamically loaded blocks.
3. Data collection implementation: extracting restaurant names, parsing ratings and number of reviews from Google and Tripadvisor blocks, saving direct links to establishment pages.
4. Processing and validation: filtering records with missing values, normalizing number formats, checking for duplicates by link.
5. Export to Excel: creating a table with columns for name, link, Google rating, Google reviews, Tripadvisor rating, Tripadvisor reviews, formatting for easy analysis.
6. Testing: running on a test sample of districts, checking the accuracy of collected data, debugging network error handling and timeouts.
Budget: 2000 UAH Deadline: 2 days
Hello. Ready to implement.
Price: 2,000 UAH. Deadline - 2 days.
I will create a quality parser, I have extensive experience. Feel free to contact me.
Budget: 1000 UAH Deadline: 1 day
Good day, I am writing on behalf of the company Devoxen. We specialize in such tasks. We have extensive experience in developing parsers, collecting and processing data from websites, including complex cases with dynamic content and a large number of pages. We can implement a parser for Restaurant Guru to collect the names of establishments, ratings, and the number of reviews from Google and Tripadvisor, as well as links to restaurant pages with automatic saving of the results in Excel.
We can also scale for different cities/categories, provide filtering, protection against blocks, and the possibility of further automatic data updates.
We can do this without unnecessary questions and wasting time. We also provide a guarantee and support if desired. We can start working on your project immediately after discussing the technical specifications.
I suggest moving to private messages for a more detailed dialogue.
Budget: 1500 UAH Deadline: 1 day
Hello! Ready to collaborate. I have experience in data parsing. I offer quality and fast work. Write to me)
Yehor I.
Winning proposal- Projects 84
- Rating 5.0
- Rating 3 409
Budget: 1000 UAH Deadline: 3 days
Ready to take it on.
Need to clarify the order details, write to me!
I use python, uv, github, docker.
Budget: 2000 UAH Deadline: 2 days
I will write a parser in Python that will collect all the necessary data for you in Excel based on the link you provide to the required section.
Budget: 1000 UAH Deadline: 1 day
Hello! I am ready to help with your project. I have extensive experience in development and can implement all necessary components according to your documentation. I guarantee quality execution within the agreed deadlines.
Budget: 1000 UAH Deadline: 2 days
Ready to complete your task, write to discuss the details.
Budget: 2000 UAH Deadline: 2 days
Good day, I am ready to complete the task. The only question is - should the parser work on your PC or on the server?
Budget: 5000 UAH Deadline: 2 days
I will do it in Python + Playwright (for bypassing protection), collecting names, ratings, and the number of reviews from Google and Tripadvisor, links to the pages — all in .xlsx. Pagination logic is included to cover the entire section.
I have a ready-made parser template for similar sites with anti-blocking bypass, so I will adapt it quickly.
How many establishments are approximately in the target section, and is a cron job needed for regular updates, or is it a one-time collection?
Budget: 2000 UAH Deadline: 2 days
Good evening, I can gather the necessary data for your request. Message me privately and we will discuss.
Budget: 10000 UAH Deadline: 10 days
Good day. If only the data from the website is important, I can write a console parser - the results will be saved in an Excel file. Do you need to collect data from the entire site or from a specific section?
Budget: 3000 UAH Deadline: 3 days
Good day!
I can create such a parser
It will collect:
- the name of the establishment;
- Google rating and number of reviews;
- Tripadvisor rating and number of reviews;
- link to the establishment;
- collection from all pages of the category;
- export to Excel.
I will implement it in Python. If needed, I can add proxies, anti-ban, and auto-start.
To get started, please clarify:
- is the parser needed once or for regular use?
- will the launch be local for you or on a server?
Budget: 2000 UAH Deadline: 1 day
Hello, I can help you solve your problem) We will do it quickly and without issues)
Proposals concealed
Proposals are currently absent
-
Yaroslav Y. 11 MayУточніть, Вам потрібна послуга парсингу (разово зібрати дані) чи автономний парсер, який ви самостійно будете запускати?
Current freelance projects in the category Data Parsing
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).
An independent service handler for Excel files is required for the existing microservices system. The task involves creating a reliable pipeline for receiving, validating, and transforming data from tables into a structured database format. Functional tasks: Development of an API based on gRPC for receiving processing commands and returning execution statuses. Implementation of file parsing logic: reading large volumes of data (XLSX), cleaning, type checking, and mapping to business models. Implementation of a data access layer (Repository/Unit of Work) for saving results in PostgreSQL via Entity Framework Core. Ensuring thread safety and efficient resource usage (especially when processing large files). Technical requirements: Platform: .NET 10. Architectural patterns: Dependency Injection, CQRS, modular project architecture. Communication: Strictly gRPC. Working with Excel: Use of efficient libraries (e.g., EPPlus, OpenXML, or similar of your choice). Modularity: Code should be organized so that the service is easily scalable and testable. Expected results: A fully functional microservice ready for deployment in a containerized environment. A clean codebase adhering to SOLID principles. Documented .proto files. Basic unit tests for critical data processing nodes. Candidate requirements: In your response, please specify: Your experience with .NET in microservices architecture. Examples of how you organize DI and modularity in your projects. Experience with Excel libraries in .NET. Willingness to work with gRPC contracts.
Good afternoon. I need a keyword parser that outputs results through a Telegram bot. How it should work: Automatic search on 4 websites for keywords that change from time to time. Search queries are sent every few minutes. The words are uploaded in the form of a .txt file. The Telegram bot should have buttons: start bot, stop bot, download file (downloads a file with active keywords), upload file (uploads an edited file with new words). The bot should ignore previously found results, i.e., it should not indicate the same ad twice. The result comes to the bot in the form of a link with a photo, but just a link is sufficient. P.S. searching websites without API, VPS with 6TB and 50 IPs are already available. For detailed information, please contact me via private message.
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).