# Geolocaux Scraper — French Commercial Property Listings (`studio-amba/geolocaux-scraper`) Actor

Get French commercial property listings from Geolocaux.com: bureaux, entrepôts, locaux commerciaux, terrains and fonds de commerce, à louer or à vendre. Rents in EUR/m²/an and monthly, sale prices, surfaces, agencies and photos. No login required.

- **URL**: https://apify.com/studio-amba/geolocaux-scraper.md
- **Developed by:** [Studio Amba](https://apify.com/studio-amba) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 result scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Geolocaux Scraper — French Commercial Property Listings

Get French commercial property listings from [Geolocaux.com](https://www.geolocaux.com), the independent French portal for immobilier d'entreprise: bureaux, locaux d'activité and entrepôts, locaux commerciaux, terrains, fonds de commerce and coworking. The portal carries roughly 62,000 live listings across France and is the main independent alternative to CoStar-owned BureauxLocaux.

Search by any French city, department or region, filter by segment and by rent or sale, and get structured JSON with rents in EUR/m²/an, monthly rents, sale prices, surfaces, agency names and photos. No login or cookies required.

### Why use it

- **Market research** — track asking rents per m² per year across cities, departments and segments.
- **Deal sourcing** — investors and occupiers monitoring new stock in a target market.
- **Agency intelligence** — see which brokers (Cushman & Wakefield, BNP Paribas Real Estate, Arthur Loyd, JLL and hundreds of local agencies) list what, where, and at what price.
- **Lead generation** — every listing carries the marketing agency's name.
- **Portfolio benchmarking** — compare your own asking prices against the local market.

French commercial rents are quoted in EUR per m² per year (HT/HC), with the monthly rent alongside. This actor keeps both numbers and labels the unit explicitly, so a 280 EUR/m²/an office and a 280 EUR/month office stay distinguishable. Sale listings return the total price in EUR plus the per-m² figure.

### Input options

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `searchQuery` | string | — | French city, department or region (e.g. `Lyon`, `Lille`, `Rhône`, `Île-de-France`). Resolved through the site's own location search. Leave empty to search all of France. |
| `listingType` | string | `all` | `all`, `rent` (à louer), or `sale` (à vendre). Fonds de commerce only exists on the sale side. |
| `segment` | string | `all` | `all`, `bureau`, `entrepot`, `local-commercial`, `terrain`, `fonds-de-commerce`, or `coworking`. `all` covers the first five; coworking is only included when selected explicitly, because its listings carry desk counts instead of prices. |
| `fetchDetails` | boolean | `false` | This flag changes how complete each record is. ON adds one request per listing and fills the full description, GPS coordinates, city, postal code, department, annual rent, DPE/GES grades and feature tags. OFF returns the search-level fields only, which is much faster for bulk exports. |
| `maxResults` | integer | `100` | Hard cap on returned listings. The whole portal holds roughly 62,000. |
| `proxyConfiguration` | object | FR residential | No anti-bot was found in testing, so the automatic proxy pool may also work; French residential is the safe default. |

#### Example input

```json
{
    "searchQuery": "Lyon",
    "segment": "bureau",
    "listingType": "rent",
    "maxResults": 100
}
```

Or warehouses around Lille:

```json
{
    "searchQuery": "Lille",
    "segment": "entrepot",
    "listingType": "rent",
    "fetchDetails": true,
    "maxResults": 50
}
```

### Output fields

| Field | Type | Example | Description |
|-------|------|---------|-------------|
| `id` | string | `"728198"` | Geolocaux internal listing ID |
| `reference` | string | null | `"197647-0L"` | Agency's own reference |
| `title` | string | `"Bureaux atypiques Lyon 2"` | Listing title |
| `segment` | string | `"bureau"` | `bureau`, `entrepot`, `local-commercial`, `terrain`, `fonds-de-commerce`, `coworking` |
| `listingType` | string | `"rent"` | `rent`, `sale`, or `coworking` |
| `price` | number | null | `280` | Headline price. Rent: EUR per m² per year. Sale: total EUR. `null` when price on application |
| `currency` | string | `"EUR"` | Always EUR |
| `priceUnit` | string | null | `"EUR/m²/an"` | `EUR/m²/an` for rent, `EUR` for sale totals |
| `pricePerM2` | number | null | `280` | Price per m² (per year for rent, absolute for sale) |
| `priceMonthly` | number | null | `4596.7` | Monthly rent in EUR (rent listings) |
| `priceYearly` | number | null | `55160` | Annual rent in EUR (detail fetch only) |
| `surface` | number | null | `197` | Surface in m² |
| `surfaceMin` | number | null | `10` | Minimum divisible / bookable surface in m² |
| `surfaceUnit` | string | null | `"m²"` | |
| `divisible` | boolean | null | `false` | Whether the space can be split |
| `desks` | number | null | `85` | Desk count (coworking only) |
| `summary` | string | null | | Teaser text from the search card |
| `description` | string | null | | Full description, HTML stripped (detail fetch only) |
| `agencyName` | string | null | `"Cushman & Wakefield Lyon"` | Marketing agency |
| `city` | string | null | `"Lyon 2"` | City (detail fetch only) |
| `department` | string | null | `"Rhône"` | Department (detail fetch only) |
| `postalCode` | string | null | `"69002"` | Postal code (detail fetch only) |
| `latitude` / `longitude` | number | null | `45.7628` | GPS coordinates (detail fetch only) |
| `dpe` / `ges` | number | null | | Energy / emissions values where published (detail fetch only) |
| `tags` | array | null | `["Climatisé", "Parking"]` | Feature tags (detail fetch only) |
| `searchedLocation` | string | null | `"Lyon"` | The resolved location this run searched |
| `imageUrl` | string | null | | Primary photo, full resolution |
| `imageUrls` | array | | All photos, full resolution |
| `url` | string | | Canonical listing page URL |
| `source` | string | `"geolocaux.com"` | |
| `scrapedAt` | string | | ISO 8601 timestamp |

#### Example output

```json
{
    "id": "728198",
    "reference": "197647-0L",
    "title": "Bureaux atypiques Lyon 2 - Vue Fourvière et toits de Lyon",
    "segment": "bureau",
    "listingType": "rent",
    "price": 280,
    "currency": "EUR",
    "priceUnit": "EUR/m²/an",
    "pricePerM2": 280,
    "priceMonthly": 4596.7,
    "priceYearly": null,
    "surface": 197,
    "surfaceMin": null,
    "surfaceUnit": "m²",
    "divisible": false,
    "desks": null,
    "summary": "Bureaux en dernier étage avec charme de l'ancien...",
    "description": null,
    "agencyName": "Cushman & Wakefield Lyon",
    "city": null,
    "department": null,
    "postalCode": null,
    "latitude": null,
    "longitude": null,
    "dpe": null,
    "ges": null,
    "tags": null,
    "searchedLocation": "Lyon",
    "imageUrl": "https://backend.geolocaux.com/photos/original/1204_6392199405947490701204_1.jpg",
    "imageUrls": ["https://backend.geolocaux.com/photos/original/1204_6392199405947490701204_1.jpg"],
    "url": "https://www.geolocaux.com/annonce/bureaux-atypiques-lyon-2-vue-fourviere-et-toits-de-lyon-728198.html",
    "source": "geolocaux.com",
    "scrapedAt": "2026-08-18T10:30:00.000Z"
}
```

### How to scrape Geolocaux data

1. Open the actor on Apify and press **Try for free**.
2. Enter a French location in **Location** (e.g. `Lyon`, `Lille`, `Bordeaux`), or leave it empty for all of France.
3. Pick a **Property Segment** (bureaux, entrepôts, locaux commerciaux, terrains, fonds de commerce, coworking) and a **Listing Type** (à louer, à vendre, or both).
4. Set **Max Results** and press **Start**.
5. When the run finishes, download the dataset from the **Output** tab as JSON, CSV or Excel.

You can also run it via the Apify API or on a schedule to track new stock: the portal returns newest listings first, so a scheduled run with a modest `maxResults` catches what came on the market since the last run.

### Cost estimate

Without `fetchDetails` the actor fetches 200 listings per page request, so nearly all usage cost is the per-result charge: expect roughly **$0.002 per listing** plus a small run start fee, about $0.20 for a 100-listing run, or roughly 500 listings per $1. With `fetchDetails` enabled each listing adds one extra request, which makes large runs slower but barely changes the per-result price. A run's usage cost only settles once it reports SUCCEEDED; a cost read mid-run understates the final figure.

### Limitations

- Prices marked "prix sur demande" come back as `null` — the site publishes no number for them. This is common in French commercial property.
- City, postal code, GPS coordinates, full description and DPE/GES are only filled when `fetchDetails` is on; the search-level records identify location via your `searchedLocation` filter and the listing title.
- Coworking listings carry desk counts and surfaces but no prices — operators quote per seat on request.
- Fonds de commerce exists on the sale side only; combining it with `listingType: "rent"` returns nothing, and the actor skips that combination.
- Rents are as published (typically HT/HC — before tax and charges); the actor does not normalize tax or charge treatments.

# Actor input Schema

## `searchQuery` (type: `string`):

French city, department or region to search (e.g. 'Lyon', 'Lille', 'Rhône', 'Île-de-France'). Resolved through the site's own location search. Leave empty to search all of France.

## `listingType` (type: `string`):

À louer (rent), à vendre (sale), or both. Fonds de commerce only exists on the sale side.

## `segment` (type: `string`):

Commercial segment, as the site defines them. 'All segments' covers bureaux, entrepôts / locaux d'activité, locaux commerciaux, terrains and fonds de commerce — coworking is only included when selected explicitly, because its listings carry desk counts instead of prices.

## `fetchDetails` (type: `boolean`):

OFF by default, and the flag changes how complete each record is: with it ON the actor makes one extra request per listing and adds the full description, GPS coordinates, city and postal code, department, annual rent, DPE/GES energy grades and feature tags. Leave OFF for fast bulk exports of the search-level fields.

## `maxResults` (type: `integer`):

Maximum number of listings to return. Hard cap for the run — the whole portal holds roughly 62,000 listings.

## `proxyConfiguration` (type: `object`):

Proxy settings. Recon found no anti-bot on the Geolocaux backend (docs/site-recon/geolocaux.md), but that was verified from a residential IP only — French residential proxy is the safe default. The free automatic pool may also work if you want cheaper runs.

## Actor input object example

```json
{
  "searchQuery": "Lyon",
  "listingType": "rent",
  "segment": "bureau",
  "fetchDetails": false,
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "FR"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQuery": "Lyon",
    "listingType": "rent",
    "segment": "bureau",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "FR"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("studio-amba/geolocaux-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchQuery": "Lyon",
    "listingType": "rent",
    "segment": "bureau",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "FR",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("studio-amba/geolocaux-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQuery": "Lyon",
  "listingType": "rent",
  "segment": "bureau",
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "FR"
  }
}' |
apify call studio-amba/geolocaux-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,studio-amba/geolocaux-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/cn1YfbAfaSMceoXgN/builds/x2B13dzCLx3ZreVzM/openapi.json