Skip to content

FAQ

Quick answers to common questions about scraping projects, timelines, deliverables, and maintenance.

Is web scraping legal?+

It depends on the target website’s terms, access controls, and your intended use of the data. We’ll ask how you plan to use the dataset and discuss safe crawling practices. You’re responsible for ensuring you have the right to access and use the data.

How fast can you deliver?+

For small, well-scoped extractions, a first sample is often possible within a few days. Larger or anti-bot-heavy targets take longer. Sharing example URLs and the fields you need speeds things up.

What formats do you deliver?+

Common outputs are CSV and JSON. We can also deliver database-ready tables, incremental deltas, or an export API depending on your workflow.

Can you handle logins or authenticated areas?+

Sometimes. If a project requires authentication, we’ll clarify access method, session handling, and any constraints. Some targets may be out of scope depending on terms and technical limitations.

What about CAPTCHAs and anti-bot systems?+

We prioritize compliant approaches: rate limiting, caching, stable selectors, and headless browsing where needed. Some anti-bot measures can make extraction impractical; we’ll flag that early after a quick technical check.

Do you provide ongoing maintenance?+

Yes. Sites change. If you need scheduled runs, we can offer maintenance to keep pipelines stable and update parsers when layouts shift.

Do you deliver the scraper code?+

Optional. Many clients want only the dataset; others need full handover. We can deliver code + run instructions when requested.

How do we define success?+

We agree on a schema, sample output, and acceptance checks (e.g., required fields, validation rules, match rates) before scaling extraction.