How to Scrape Search.ch Leads from a URL

Start by importing the Search.ch Lead Scraper via URL template. This post explains the runbook, validation checks, export shape, and common issues around that downloadable workflow.

Prerequisites for a Search.ch scraper tutorial

You need UScraper installed as a local desktop app, the template linked above, a local export folder, and a Search.ch telephone directory URL your team is allowed to review. A good first URL is narrow: one category, one city or canton, and a page you would trust if you were copying records manually.

The sample workflow uses a URL shaped like:

https://search.ch/tel/?was=Restaurant&wo=Berne&pages=20

The important parts are was for the search topic, wo for the location, and pages=20 for the public listing batch. Change the category and location, but do not start with every possible combination.

Search.ch also provides official public API documentation for directory queries. Read the Search.ch API overview, phone directory API specification, API terms, general Search.ch terms, and current robots.txt before automating. This article is operational guidance, not legal advice.

A lead export is a research artifact, not permission to contact every row. Keep runs modest, avoid bypassing access controls, document the source URL, and review outreach rules before commercial use.

Search.ch scraper API or local template: which route fits?

A Search.ch scraper API, the official Search.ch API, and a local desktop template can all be valid. The best Search.ch scraper for a one-time CSV job is not always the best tool for production integration.

What the Search.ch lead scraper via URL exports

The bundled JSON export is the authoritative workflow definition. It navigates to the listing URL, waits for article.tel-resultentry cards, removes common consent overlays, scrolls until the page stops changing, fetches public detail pages when a detail link exists, and then runs Structured Export.

There is no CSV sample in the bundle. Treat the export shape summary and workflow JSON as the sample: they explain what the template collects and which columns it writes.

{
  "project": {
    "name": "Searchch Lead Scraper via URL",
    "description": "Scrapes Search.ch directory leads for https://search.ch/tel/?was=Restaurant&wo=Berne. Extracts title, address, phone numbers, fax, email, website, detail link, categories, information, rating, review count, and source URL."
  },
  "blocks": [
    {
      "title": "Navigate",
      "config": {
        "url": "https://search.ch/tel/?was=Restaurant&wo=Berne&pages=20"
      }
    },
    {
      "title": "Wait for Element",
      "config": {
        "selector": "article.tel-resultentry",
        "visible": true
      }
    },
    {
      "title": "Structured Export",
      "config": {
        "fileName": "search-lead-scraper-via-url.csv",
        "columns": ["title", "address", "phone_numbers", "fax", "email", "website", "detail_link", "categories", "information", "rating", "review_count", "source_url"]
      }
    }
  ]
}

How to scrape Search.ch leads from a URL

The enrichment step is useful but intentionally conservative. Email, fax, website, and information can stay blank when Search.ch does not expose those fields publicly. Check the source page before changing selectors.

Validate the Search.ch to CSV export

Next step

Import the Search.ch Lead Scraper via URL template, run the restaurant-in-Berne sample or your own approved listing URL, and keep the first CSV beside your QA notes. For adjacent workflows, browse the UScraper templates or continue through the UScraper blog.