Tabelog Japan Restaurant Scraper
Pricing
from $2.50 / 1,000 results
Tabelog Japan Restaurant Scraper
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.
Pricing
from $2.50 / 1,000 results
Rating
0.0
(0)
Developer
Piquno
Maintained by CommunityActor stats
2
Bookmarked
16
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
Scrape restaurant data from Tabelog (食べログ), 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
{"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.