# Tabelog Japan Restaurant Scraper (`piquno/tabelog-japan-restaurant-scraper`) Actor

Scrape restaurant data from Tabelog (食べログ), Japan's #1 restaurant review site. Extract ratings, reviews, genres, budgets, locations, hours, and photos from 800K+ restaurants across all 47 prefectures.

- **URL**: https://apify.com/piquno/tabelog-japan-restaurant-scraper.md
- **Developed by:** [Piquno](https://apify.com/piquno) (community)
- **Categories:** Travel, E-commerce, Lead generation
- **Stats:** 18 total users, 1 monthly users, 100.0% runs succeeded, 2 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 results

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/actors/running/actors-in-store.md#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

## Tabelog Japan Restaurant Scraper

Scrape restaurant data from [Tabelog](https://tabelog.com/en/) (食べログ), Japan's largest restaurant review site with **800,000+ listings** across all 47 prefectures.

**Now returns the individual reviews too** — reviewer, star rating, meal time, visit month, visit count and the full review text, not just the aggregate score. Paste any Tabelog listing URL, or search by prefecture and keyword.

### What data can you extract?

| Field | Source | Description |
|-------|--------|-------------|
| name | Listing | Restaurant name |
| url | Listing | Tabelog URL |
| rating | Listing | Rating score (0-5 scale) |
| reviewCount | Listing | Number of reviews |
| nearestStation | Listing | Closest train station |
| genre | Listing | Cuisine type (Sushi, Ramen, Yakiniku, etc.) |
| dinnerBudget | Listing | Average dinner price range |
| lunchBudget | Listing | Average lunch price range |
| closedDays | Listing | Regular holidays |
| features | Listing | Tags (credit card, non-smoking, children welcome, etc.) |
| awards | Listing | Tabelog Awards & Hyakumeiten (Top 100) badges |
| images | Listing | Up to 5 restaurant photos |
| address | Detail | Full address (Japanese) |
| phone | Detail | Phone number |
| businessHours | Detail | Opening hours |
| transportation | Detail | Directions from nearest station |
| paymentMethods | Detail | Accepted payment methods |
| seats | Detail | Seating capacity |

**Listing fields** are always included. **Detail fields** require enabling "Include Detail Pages" (slower, makes one extra request per restaurant).

#### Individual reviews

Turn on **Include individual reviews** and each review becomes its own row, tagged `recordType: "review"` and joined to its restaurant by `restaurantId`. Tabelog serves 20 reviews per request; a top Tokyo restaurant in our testing carried 942.

| Field | Description |
|-------|-------------|
| recordType | `restaurant` or `review` — filter on this to split the two |
| restaurantId, restaurantName, restaurantUrl | The restaurant the review belongs to |
| reviewerName, reviewerUrl | The reviewer and their Tabelog profile |
| reviewerPostCount, reviewerFollowers | How prolific and how followed the reviewer is — use it to weight credibility |
| reviewRating | That reviewer's score, or `null` when they left one unrated |
| reviewMealTime | `dinner` or `lunch` |
| reviewVisitPeriod, reviewVisitCount | e.g. "August 2026", and how many times they have visited |
| reviewTitle, reviewText | The review itself |

Measured fill on a live run: reviewer name, post count, followers, meal time, visit period and text all 100%; `reviewRating` 87% (unrated reviews stay `null` rather than becoming 0).

### Input parameters

- **Start URLs**: Paste Tabelog listing URLs directly, including ones with filters already applied on the site. Overrides Area, Keyword and Sort.
- **Area**: Any of Japan's 47 prefectures (Tokyo, Osaka, Kyoto, Hokkaido, etc.)
- **Keyword**: Search by cuisine or name — supports Japanese (ラーメン, 寿司, カレー) and English
- **Sort By**: Highest Rated, Most Reviews, Most Reserved (Travelers/Locals), Most Viewed
- **Max Results**: 1-500 restaurants per run. Tabelog caps a single search at 25 pages, so use a narrower area or keyword to reach past 500.
- **Include Details**: Toggle extra detail page scraping
- **Include individual reviews** + **Max reviews per restaurant**: return the review text itself
- **Proxy**: optional, off by default — Tabelog served every probe with no challenge

Rows are written as each listing page is parsed, so a run you stop early still keeps everything collected up to that point.

### Example output

```json
{
    "name": "Yoroniku",
    "url": "https://tabelog.com/en/tokyo/A1306/A130602/13042979/",
    "restaurantId": "13042979",
    "rating": 4.18,
    "reviewCount": 2923,
    "nearestStation": "Omote Sando Sta.",
    "genre": "Yakiniku (Japanese BBQ), Tripe",
    "dinnerBudget": "JPY 10,000 - JPY 14,999",
    "lunchBudget": null,
    "closedDays": null,
    "features": ["Multilingual menu", "Credit card accepted", "Non smoking"],
    "awards": ["The Tabelog Award 2026 Bronze winner"],
    "images": ["https://tblg.k-img.com/restaurant/images/..."],
    "searchArea": "tokyo",
    "searchKeyword": null,
    "scrapedAt": "2026-04-10T12:00:00+00:00"
}
```

### Use cases

- **Market research**: Analyze restaurant density, ratings, and pricing by area and cuisine
- **Travel apps**: Build restaurant databases for Japan trip planning tools
- **Food analytics**: Track trends in Japanese dining — top-rated cuisines, pricing patterns, regional specialties
- **Competitive analysis**: Compare restaurants by rating, review volume, and budget range
- **Location intelligence**: Map restaurant data by station and prefecture

### Compliance

This actor respects Tabelog's `robots.txt` guidelines with **2.5-second delays** between requests. Restaurant listing pages and detail pages are permitted for crawling.

### Cost estimate

Every row written is billed, and reviews are rows like any other result.

- **Listing only**: ~$0.25 per 100 restaurants
- **With details**: same row count, one extra request per restaurant
- **With reviews**: 100 restaurants x 20 reviews = 2,100 rows. Set **Max reviews per restaurant** deliberately.

# Actor input Schema

## `startUrls` (type: `array`):

Optional. Paste Tabelog listing URLs directly — including ones with filters already applied on the site. Overrides Area, Keyword and Sort.

## `area` (type: `string`):

Japanese prefecture to search. Ignored when Start URLs are given.

## `keyword` (type: `string`):

Search keyword (cuisine type, restaurant name, etc.). Supports Japanese: e.g. ラーメン, 寿司, yakitori

## `sort` (type: `string`):

How to sort results

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

Maximum number of restaurants to scrape. Tabelog caps a single search at 25 pages (500 restaurants); use a narrower area or keyword to reach past that.

## `includeDetails` (type: `boolean`):

Visit each restaurant's page for address, phone, opening hours, seats and payment methods. Costs one extra request per restaurant.

## `includeReviews` (type: `boolean`):

Also return the actual review text for each restaurant — reviewer, star rating, meal time, visit month and the full comment. Each review is a separate row tagged recordType "review". Costs one extra request per 20 reviews.

## `maxReviewsPerRestaurant` (type: `integer`):

Upper bound on reviews returned per restaurant. Tabelog serves 20 per request, and popular restaurants carry hundreds — a top Tokyo restaurant in our probe had 942.

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

Optional and off by default. Tabelog served every probe without a challenge, so the actor runs unproxied. Enable this only if the log shows repeated blocks.

## Actor input object example

```json
{
  "area": "tokyo",
  "keyword": "",
  "sort": "highest_rated",
  "maxResults": 100,
  "includeDetails": false,
  "includeReviews": false,
  "maxReviewsPerRestaurant": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "area": "tokyo",
    "sort": "highest_rated",
    "maxResults": 100,
    "maxReviewsPerRestaurant": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("piquno/tabelog-japan-restaurant-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 = {
    "area": "tokyo",
    "sort": "highest_rated",
    "maxResults": 100,
    "maxReviewsPerRestaurant": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("piquno/tabelog-japan-restaurant-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 '{
  "area": "tokyo",
  "sort": "highest_rated",
  "maxResults": 100,
  "maxReviewsPerRestaurant": 20
}' |
apify call piquno/tabelog-japan-restaurant-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,piquno/tabelog-japan-restaurant-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/zQZYaBMyKWruR1piR/builds/8Z4UemOyZx1pzGIBR/openapi.json